[Solved] Some troubles after the kernel update
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
[Solved] Some troubles after the kernel update
Bonjour,
Since the kernel update, I have errors for the other updates. As a result, I have a message that they are not taken into account but Linux says that it is up to date.
The system log does not detect any problem.
I don't know if this is a general problem.
System: Kernel: 5.4.0-109-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
Desktop: Cinnamon 5.2.7 wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una
base: Ubuntu 20.04 focal
Let me know if you see something wrong.
Apart from waiting for the next update, I don't see what to do.
Regards,
Leloup
Since the kernel update, I have errors for the other updates. As a result, I have a message that they are not taken into account but Linux says that it is up to date.
The system log does not detect any problem.
I don't know if this is a general problem.
System: Kernel: 5.4.0-109-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
Desktop: Cinnamon 5.2.7 wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una
base: Ubuntu 20.04 focal
Let me know if you see something wrong.
Apart from waiting for the next update, I don't see what to do.
Regards,
Leloup
- Attachments
-
- update_bug.txt
- (10.17 KiB) Downloaded 24 times
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Some troubles after the kernel update
The second part of file is attached here.
- Attachments
-
- update_bug02.txt
- (15.99 KiB) Downloaded 28 times
Re: Some troubles after the kernel update
Timeshift might be an option for you.Apart from waiting for the next update, I don't see what to do.
This might be useful if you want to see what was recently updated:
viewtopic.php?p=2072947#p2072947
Re: Some troubles after the kernel update
firejail being broken wouldn't break due to a kernel update. That's more likely conflicts caused by a PPA changing that shared library.
Re: Some troubles after the kernel update
Here is the typical error that appears on the screen:
The details....
Does it make sense to you?E: initramfs-tools: installed initramfs-tools package post-installation script subprocess returned error exit status 2
E: linux-image-5.4.0-110-generic: installed linux-image-5.4.0-110-generic package post-installation script subprocess returned error exit status 1
The details....
Code: Select all
(Reading the database... 699466 files and directories already installed)
Preparing to unpack .../libapt-pkg6.0_2.0.8_amd64.deb ...
Unpacking libapt-pkg6.0:amd64 (2.0.8) to (2.0.6) ...
Setting up libapt-pkg6.0:amd64 (2.0.8) ...
(Reading the database... 699466 files and directories already installed)
Preparation of the unpacking of .../archives/apt_2.0.8_amd64.deb ...
Unpacking apt (2.0.8) to (2.0.6) ...
Setting up apt (2.0.8) ...
Removing obsolete conffile /etc/kernel/postinst.d/apt-auto-removal ...
(Reading the database... 699465 files and directories already installed)
Preparation of the unpacking of .../apt-utils_2.0.8_amd64.deb ...
Unpacking apt-utils (2.0.8) to (2.0.6) ...
Preparing to unpack .../libldap-common_2.4.49+dfsg-2ubuntu1.9_all.deb ...
Unpacking libldap-common (2.4.49+dfsg-2ubuntu1.9) on (2.4.49+dfsg-2ubuntu1.8) ...
Setting up libldap-common (2.4.49+dfsg-2ubuntu1.9) ...
(Reading the database... 699465 files and directories already installed)
Preparing to unpack .../libldap-2.4-2_2.4.49+dfsg-2ubuntu1.9_amd64.deb ...
Unpacking libldap-2.4-2:amd64 (2.4.49+dfsg-2ubuntu1.9) to (2.4.49+dfsg-2ubuntu1.8) ...
Setting up libldap-2.4-2:amd64 (2.4.49+dfsg-2ubuntu1.9) ...
(Reading the database... 699465 files and directories already installed)
Preparation of the unpacking of .../lintian_2.62.0ubuntu2.1_all.deb ...
Unpacking lintian (2.62.0ubuntu2.1) to (2.62.0ubuntu2) ...
Setting up apt-utils (2.0.8) ...
Setting up initramfs-tools (0.136ubuntu6.7) ...
update-initramfs: deferring update (trigger activated)
Setting up lintian (2.62.0ubuntu2.1) ...
Setting linux-image-5.4.0-110-generic (5.4.0-110.124) ...
Processing triggers for libc-bin (2.31-0ubuntu9.9) ...
Processing of deferred actions ("triggers") for man-db (2.9.1-1) ...
Processing of deferred actions ("triggers") for doc-base (0.10.9) ...
Processing 1 modified documentation file...
Processing of deferred actions ("triggers") for [b]initramfs-tools[/b] (0.136ubuntu6.7) ...
[b]update-initramfs[/b]: Generating /boot/initrd.img-5.4.0-109-generic
/usr/sbin/mkinitramfs: 2: /etc/[b]initramfs-tools[/b]/conf.d/resume: Syntax error: newline unexpected
update-initramfs: [b][color=#FF0000]failed[/color][/b] for /boot/initrd.img-5.4.0-109-generic with 2.
dpkg: error processing initramfs-tools package (--configure) :
installed [b]initramfs-tools[/b] package post-installation script subprocess returned error exit status 2
Processing of triggers for linux-image-5.4.0-110-generic (5.4.0-110.124) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-110-generic
...done.
/etc/kernel/postinst.d/[b]initramfs-tools[/b]:
update-initramfs: Generating /boot/initrd.img-5.4.0-110-generic
/usr/sbin/mkinitramfs: 2: /etc/[b]initramfs-tools[/b]/conf.d/resume: Syntax error: newline unexpected
[b]update-initramfs[/b]: [b][color=#FF0000]failed [/color][/b]for /boot/initrd.img-5.4.0-110-generic with 2.
run-parts: /etc/kernel/postinst.d/i[b]nitramfs-tools[/b] exited with return code 2
dpkg: linux-image-5.4.0-110-generic package processing error (--configure) :
installed linux-image-5.4.0-110-generic package post-installation script subprocess returned error exit status 1
Errors were encountered during execution:
initramfs-tools
linux-image-5.4.0-110-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to install a package. Attempt to recover:
Setting up [b]initramfs-tools[/b] (0.136ubuntu6.7) ...
[b]update-initramf[/b]s: deferring update (trigger activated)
Setting up linux-image-5.4.0-110-generic (5.4.0-110.124) ...
Processing of triggers for[b] initramfs-tools[/b] (0.136ubuntu6.7) ...
[b]update-initramfs[/b]: Generating /boot/initrd.img-5.4.0-109-generic
/usr/sbin/mkinitramfs: 2: /etc[b]/initramfs-to[/b]ols/conf.d/resume: Syntax error: newline unexpected
[b]update-initramfs[/b]: [b][color=#FF0000]failed[/color][/b] for /boot/initrd.img-5.4.0-109-generic with 2.
dpkg: error processing initramfs-tools package (--configure) :
installed[b] initramfs-tools package[/b] post-installation script subprocess returned error exit status 2
Processing of triggers for linux-image-5.4.0-110-generic (5.4.0-110.124) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-110-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-110-generic
/usr/sbin/[b]mkinitramfs[/b]: 2: /etc/[b]initramfs-tools[/b]/conf.d/resume: Syntax error: newline unexpected
[b]update-initramfs[/b]: failed for /boot/initrd.img-5.4.0-110-generic with 2.
run-parts: /etc/kernel/postinst.d[b]/initramfs-tools[/b] exited with return code 2
dpkg: linux-image-5.4.0-110-generic package processing error (--configure) :
installed linux-image-5.4.0-110-generic package post-installation script subprocess returned error exit status 1
Errors were encountered during execution
Last edited by karlchen on Tue May 17, 2022 4:17 pm, edited 1 time in total.
Reason: applied [code] [/code] tags , where appropriate
Reason: applied [code] [/code] tags , where appropriate
Re: Some troubles after the kernel update
Most likely you have run out of space in your /boot partition. Clean out some old kernels.Leloup wrote: ⤴Tue May 17, 2022 9:52 am Here is the typical error that appears on the screen:
E: initramfs-tools: installed initramfs-tools package post-installation script subprocess returned error exit status 2
E: linux-image-5.4.0-110-generic: installed linux-image-5.4.0-110-generic package post-installation script subprocess returned error exit status 1
Does it make sense to you?
Re: Some troubles after the kernel update
Bonjour,
To be on the safe side, I almost doubled the size of the Boot.
Same issue.
Regards,
Leloup
To be on the safe side, I almost doubled the size of the Boot.
Same issue.
Regards,
Leloup
Re: Some troubles after the kernel update
ah, missed this line in the log before
Check that file (e.g.
If it comes back with multiple lines; remove the errant line(s) from the end of the file. The only line in the file should be something like "RESUME=UUID=[uuid_here]". Note that the line should be terminated with a line feed character.
/usr/sbin/mkinitramfs: 2: /etc/initramfs-tools/conf.d/resume: Syntax error: newline unexpected
Check that file (e.g.
wc -l /etc/initramfs-tools/conf.d/resume
). It SHOULD return that there is one line:Code: Select all
$ wc -l /etc/initramfs-tools/conf.d/resume
1 /etc/initramfs-tools/conf.d/resume
Re: Some troubles after the kernel update
~$ wc -l /etc/initramfs-tools/conf.d/resume
1 /etc/initramfs-tools/conf.d/resume
1 /etc/initramfs-tools/conf.d/resume
Re: Some troubles after the kernel update
Oops! I forgot. I saw a post a while back that couldn't find "resume". So I created it with the content as it appears below. There must be something wrong with it.
$ cat /etc/initramfs-tools/conf.d/resume
RESUME=UUUID=<swap "02b7e183-f999-415e-9710-644b540566ec">
maybe I should delete it. No?
$ cat /etc/initramfs-tools/conf.d/resume
RESUME=UUUID=<swap "02b7e183-f999-415e-9710-644b540566ec">
maybe I should delete it. No?
Re: Some troubles after the kernel update
I notice we don't have a "resume" file in that folder
Re: Some troubles after the kernel update
is that UUID the actual UUID of your swap partition? Also, is it really in there with angle brackets?Leloup wrote: ⤴Wed May 18, 2022 2:07 pm Oops! I forgot. I saw a post a while back that couldn't find "resume". So I created it with the content as it appears below. There must be something wrong with it.
$ cat /etc/initramfs-tools/conf.d/resume
RESUME=UUUID=<swap "02b7e183-f999-415e-9710-644b540566ec">
maybe I should delete it. No?
Re: Some troubles after the kernel update
Code: Select all
~$ blkid
/dev/mapper/vgmint-swap_1: UUID="02b7e183-f999-415e-9710-644b540566ec" TYPE="swap"
Code: Select all
michaou@michaou-VirtualBox:~$ cat /etc/initramfs-tools/conf.d/resume
RESUME=UUUID=<swap "02b7e183-f999-415e-9710-644b540566ec">
Code: Select all
~$ swapon --show
NAME TYPE SIZE USED PRIO
/dev/dm-2 partition 980M 0B -2
Code: Select all
~$ cat /etc/fstab | grep swap
/dev/mapper/vgmint-swap_1 none swap sw 0 0
RESUME=UUID=swap "02b7e183-f999-415e-9710-644b540566ec"
be more correct?normally, should I not find UUID in /etc/fstab | grep swap?
Re: Some troubles after the kernel update
depends on how /etc/fstab was written. One would imagine that it's using the UUID these days, but it doesn't "have" to.
I don't think you need it to read
I don't think you need it to read
swap "uuid-here"
(rather just resume=uuid=[uuidhere]
); but it would never hurt to double-check the manual.Re: Some troubles after the kernel update
/etc/initramfs-tools/conf.d$ cat resume
RESUME=UUID=02b7e183-f999-415e-9710-644b540566ec
For system updates, I don't see any error anymore.
To test the swap memory, I divided the RAM memory by 4 and launched several applications. I checked that swap increases as the activity with the system monitor.
But, maybe, you have a different way to test the swap memory. Wouldn't you?
Thank you Dear djph
RESUME=UUID=02b7e183-f999-415e-9710-644b540566ec
For system updates, I don't see any error anymore.
To test the swap memory, I divided the RAM memory by 4 and launched several applications. I checked that swap increases as the activity with the system monitor.
But, maybe, you have a different way to test the swap memory. Wouldn't you?
Thank you Dear djph
Re: Some troubles after the kernel update
swap is nothing more than harddrive space reserved to be "pretend RAM" . It's mainly there to give the system a "safety net" (or pressure release) in instances where the user spikes RAM usage.