Final Focal on Kubuntu 20.04

[Radcliff]

Ryzen 2700u 20200308

Dolphin does not read Tumbleweed bootable stick, same for Device Notifier on the taskbar. The rest is OK = fat32, Windows, Mint.

The remove media message interferes with the LVM passphrase, both are shown rapidly back to back. This is a one shot message that is not removed from the boot sequence. When not encrypted (ext4 or btrf), the message appears permanently at boot time since day one.

[Radcliff]

Synaptic History

There was 168 packages to upgrade in Proposed for yesterday's build (18 today). A blue message was shown to stop some services while upgrading. Since at least a week, the installer scans the HD for NVDIA... We must press S twice to skip HD scan.

-History is empty in Synaptic
-Muon works normally
-Encrypted successfully message does not display correctly
-At boot, the message to remove media appears intermittently.
-Taskbar issues are gone
-Driver Manager requires root password now and scans normally

Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.2
KDE Frameworks Version: 5.67.0
Qt Version: 5.12.5
Kernel Version: 5.6.0-050600rc5-generic

[acheron]

Finally!

Qt4 has now been removed from the 20.04 archive.

[jglen490]

Yep! Looking forward to the end of April ...

[GreyGeek]

Not even 24 hours. Ya gotta love this!

[acheron]

A new upload with a 'fix' is on the way...

https://launchpad.net/ubuntu/+source...00109-0ubuntu7

[NoWorries]

Executing the patch fails here:

patching file /usr/share/initramfs-tools/hooks/plymouth
Hunk #1 FAILED at 119.
1 out of 1 hunk FAILED -- saving rejects to file /usr/share/initramfs-tools/hooks/plymouth.rej

ADDED:
Well, copied the patch content, pasted it into the file in nano, exited nano, ran: sudo su - and then cd'd into /home/paul and ran the patch command again. This time it worked.

I got exactly the same output, ie

patching file /usr/share/initramfs-tools/hooks/plymouth
Hunk #1 FAILED at 119.
1 out of 1 hunk FAILED -- saving rejects to file /usr/share/initramfs-tools/hooks/plymouth.rej

I had the patch file in my home directory, did sudo su, ran the patch and I got this error. I have two systems with 20.04 and both give the same result.

What have I missed or done wrong?

[GreyGeek]

I have just rebooted after having been through several updates and when I do a fresh update and full-upgrade I get a list of possible missing firmware relating to amdgpu because I have an AMD video card. At the end I get

cp: cannot create regular file '/var/tmp/mkinitramfs_Th52XT/usr/share/plymouth/themes/spinner/watermark.png': No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.4.0-17-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

These errors do not seem to stop my system from working in any way that I have noticed.

BTW, the initiramfs versions that I have are all at 0.136ubuntu1 and the available version is the same.

Is there anything you can suggest that I try, to show that these errors compromise my system?

One of the posts in the bug report suggested the following method to find what may be causing the problem:
https://bugs.debian.org/cgi-bin/bugr...cgi?bug=922754

You might find some of Bash's debugging functions useful when trying to
trace your own problem:

1. Change the problematic hook script to use #!/bin/bash
2. Set the following variable:
PS4=$'$? \\ (${BASH_SOURCE[0]}:${LINENO}): ${FUNCNAME[0]:--} [SHLVL=${SHLVL} BASH_SUBSHELL=${BASH_SUBSHELL}]\n '
3. Add 'set -x' at the point where you want to start tracing

That adds current line and function information to the normally terse
result of using 'set -x', which I find makes it a lot easier to figure
out what is going on in a complex shell script that sources lots of
files and makes use of lots of functions, etc.

And, there are other possible solutions:
https://askubuntu.com/questions/1136...lling-updating

[NoWorries]

So, when you did the update earlier, you did not get the failure of the initramfs to install over the previous version?
What happens when you do a "sudo apt update" and "sudo apt full-upgrade" ?

I have just rebooted after having been through several updates and when I do a fresh update and full-upgrade I get a list of possible missing firmware relating to amdgpu because I have an AMD video card. At the end I get

cp: cannot create regular file '/var/tmp/mkinitramfs_Th52XT/usr/share/plymouth/themes/spinner/watermark.png': No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.4.0-17-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

These errors do not seem to stop my system from working in any way that I have noticed.

BTW, the initiramfs versions that I have are all at 0.136ubuntu1 and the available version is the same.

Is there anything you can suggest that I try, to show that these errors compromise my system?

[GreyGeek]

I must be living a charmed existence as, after the updates this morning, I got a few unusual informative messages which I ignored as part of the "normal" occurrence with a pre-released version.

Anyhow, my understanding is that plymouth does the graphics during bootup. When I re-booted all was normal and I could not fault the system in any way - as stable as ever!

So, when you did the update earlier, you did not get the failure of the initramfs to install over the previous version?
What happens when you do a "sudo apt update" and "sudo apt full-upgrade" ?

[NoWorries]

I must be living a charmed existence as, after the updates this morning, I got a few unusual informative messages which I ignored as part of the "normal" occurrence with a pre-released version.

Anyhow, my understanding is that plymouth does the graphics during bootup. When I re-booted all was normal and I could not fault the system in any way - as stable as ever!

[GreyGeek]

Executing the patch fails here:

patching file /usr/share/initramfs-tools/hooks/plymouth
Hunk #1 FAILED at 119.
1 out of 1 hunk FAILED -- saving rejects to file /usr/share/initramfs-tools/hooks/plymouth.rej

ADDED:
Well, copied the patch content, pasted it into the file in nano, exited nano, ran: sudo su - and then cd'd into /home/paul and ran the patch command again. This time it worked.

The "ADDED" is, in essence, what I did. I edited my first post to make that clearer.

[Snowhog]

Executing the patch fails here:

patching file /usr/share/initramfs-tools/hooks/plymouth
Hunk #1 FAILED at 119.
1 out of 1 hunk FAILED -- saving rejects to file /usr/share/initramfs-tools/hooks/plymouth.rej

ADDED:
Well, copied the patch content, pasted it into the file in nano, exited nano, ran: sudo su - and then cd'd into /home/paul and ran the patch command again. This time it worked.

[GreyGeek]

Editing the file and reinstalling plymouth also didn't work for me. When it failed, edited the file again, and the added line wasn't there. Hmm??

Where did you save the diff file? In /usr/share/initramfs-tools/hooks?

No, I saved it under my home account and as root executed the patch command from there as well.

[Snowhog]

Editing the file and reinstalling plymouth also didn't work for me. When it failed, edited the file again, and the added line wasn't there. Hmm??

Where did you save the diff file? In /usr/share/initramfs-tools/hooks?