[00:04] <user392> Hi. A problem happened during the last update. A new kernel package is available, but it didn't install because update-initramfs failed
[00:04] <user392> I'm on Xubuntu 20.04
[00:06] <user392> It seems to be a bug. This is the tail log of the update process: https://pastebin.com/VBHgLgEv
[00:13] <Bashing-om> user392: This report: https://answers.launchpad.net/ubuntu/+question/689181 yours ?
[00:16] <Bashing-om> Info linux-image-generic focal
[00:17] <Bashing-om> !Info linux-image-generic focal
[00:17] <Bashing-om> !info linux-image-generic focal
[00:17] <ubottu> linux-image-generic (source: linux-meta-5.4): Generic Linux kernel image. In component main, is optional. Version 5.4.0.14.17 (focal), package size 2 kB, installed size 16 kB
[00:19] <Bashing-om> user392: Show the channel ' dpkg -l | grep linux- ' in a pastebin , see what might be missing.
[00:20] <user392> No. it is not mine.
[00:20] <Bashing-om> user392: Then we may have a real update bug !
[00:21] <user392> https://pastebin.com/9ecBTc25
[00:21] <user392> It seems so. Well, such is life on the edge.
[00:24] <Bashing-om> user392: Appears the kernel is fully installed - but just as a check - what shows ' df -h ' ?
[00:25] <user392> https://pastebin.com/kmZt7gCU
[00:28] <user392> I don't like the line
[00:28] <user392> /dev/loop3                   45M   45M     0 100% /snap/gtk-common-themes/1440
[00:29] <Bashing-om> user392: Also not a disk space issue, Snaps are confined and will be at 100%.
[00:30] <user392> I don't like it because the failure was in
[00:30] <user392> cp: cannot create regular file '/var/tmp/mkinitramfs_Qnycxn/usr/share/plymouth/themes/spinner/watermark.png': No such file or directory
[00:31] <user392> I'm doing a couple of things that shouldn't be
[00:32] <user392> The first are two packages related to gimp which I installed from 19.10, but I remove them before the upgrade
[00:32] <user392> The other is something about Wine, but that doesn't relate to the kernel
[00:35] <Bashing-om> user392: I will bow to others greater experience here - but looks to me like what we have is a race condition in that the file "watermark.png" has not been created in time. But way over my skilll set !
[00:36] <user392> It should be fixed soon. I am going to hold the packages with the old kernels, just in case
[00:39] <Bashing-om> user392: Also in the mean time add your self to that ups bug report to increase the heat to gain developer attention.
[00:41] <user392> Today is Friday, it will get on fire at Monday.
[00:41] <user392> Let's see...
[00:59] <user392> https://bugs.launchpad.net/ubuntu/+bug/1866425
[00:59] <ubottu> Launchpad bug 1866425 in Ubuntu "apt upgrade fails with an error" [Undecided,New]
[00:59] <user392> Done
[01:00] <Bashing-om> thanks :)
[01:24] <Haxxa> Hi Guys, How easy is it to downgrade from 20.04 to 18.04.3?
[01:31] <guiverc> Haxxa, upgrade tools are designed to automatically go to later packages, backwards is manual so no its not easy.
[01:32] <guiverc> (also 18.04.4 is the latest 18.04)
[01:32] <Bashing-om> Haxxa: There is no go-back button, The better course is a fresh clean install.
[01:32] <guiverc> or restore backups (why we have them)
[01:35] <Haxxa> lets say I by mistake upgraded a production machine which was meant to be a test vm and have no backups, and one of the repos is only available for 18.04 just a hypothetical ofc :| . 
[01:36] <guiverc> Re-install using something-else/manual-partitioning and using existing partitions (ensuring you don't format) is the easiest solution; it'll note your packages, erase system dirs (so you need to restore apps that store data there, no desktop app should but server apps can), install, add back your additional packages then ask to reboot. No user files are touched (really great for desktop boxes; some server stuff will need restore)
[01:57] <Captain_Proton> Ubuntu Focal Fossa   Gnome 3.35.1 unable to open extensions settings, try both tweaks and gnome extensions web site
[02:22] <user392> Bashing-om: someone marked the bug as a duplicate, and there, a workaround was available; it fixed the issue.
[02:26] <Bashing-om> user392: looking :D
[02:33] <Bashing-om> user392: \o/ passed on to other affected too :D
[02:34] <user392> Of course
[02:45] <nt0> how's 20.04 for tinkering around?  i'm planning on creating a new VM to test out the linux version of matlab and also want to see how 20.04 looks.  don't care about rock-solid or doing any serious work.  so long as its stable enough to play around with as a casual user i'm good go go.  thoughts?
[03:17] <guiverc> nt0, i release-upgraded this box back in 2019-Oct and between then and now I've had few issues but it'll vary on what you do, what you use, and your hardware..
[03:22] <nt0> guiverc: that sounds good enough for me.  first gen ryzen and will be running in qemu/kvm.  so long as it works for the most part i'll be fine.  just want to test out MATLAB and play around a bit.
[03:23] <nt0> guiverc: thanks.
=== nt0_ is now known as nt0
[14:41] <evils> repost from #ubuntu
[14:41] <evils> i'm having a display/graphics issue on 20.04, in chromium and firefox, after closing a menu, that area doesn't redraw correctly (mixed remnants of the menu remain, even when moving the mouse over them, sometimes flickers), resizing the window fixes it, seems to happen on X and wayland; this is on a ryzen 3400g (integrated graphics)
[14:41] <evils> takov751: you said something about the composer, can you expand on that?
[14:43] <takov751> compositor
[14:43] <evils> isn't that wayland specific?
[14:45] <takov751> if i recall correctly by default the gnome compositor is mutter.
[14:46] <takov751> But i haven't seen any settings that might be helpfull
[14:47] <evils> i don't suppose this is a replaceable component?
[15:15] <evils> i suppose i could try i3/sway, but it's not my machine, and it's in use...
[18:15] <otyugh> Hey there ; got a graphical problem (graphical glitches, artefacts) with an old PC under the latest ubuntu20, while having no issue using ubuntu18.04 ; I tried to use the kernel from 18.04 in ubuntu20, but got stuck on loading initramfs.
[18:15] <otyugh> Any idea why ?
[18:16] <otyugh> Under debian I could use a kernel from stretch in debian buster as if it was nothing ; what did change in Ubuntu so it's not possible anymore ?
[18:18] <takov751> otyugh: this is a new bug presumebly . If the build fails with the message  plymouth spinner theme watermark.png  can not be found while building
[18:18] <otyugh> takov751: well it goes stuck even when launching removing "splash" and adding "nomodeset"
[18:18] <otyugh> Ahm
[18:18] <otyugh> maybe uninstalling plymouth then ?
[18:19] <takov751> there is a dirty whttps://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1866372
[18:19] <ubottu> Launchpad bug 1866377 in plymouth (Ubuntu Focal) "duplicate for #1866372 update-initramfs fails on plymouth hook due to missing target dir" [Critical,Fix committed]
[18:19] <otyugh> Argh
[18:20] <otyugh> takov751: update-initramfs didn't show any error though
[18:20] <takov751> whats your output when apt fails
[18:20] <takov751> ?
[18:21] <otyugh> apt does not fail
[18:21] <otyugh> The problem is at actually booting on the 3.4 kernel (If i remember correctly)
[18:22] <takov751> 3.4 is really old kernel
[18:22] <otyugh> Amh
[18:22] <otyugh> Maybe I'm not remembering staight
[18:22] <otyugh> I'll check 
[18:22] <otyugh> It's the main 18.04 kernel version
[18:22] <otyugh> 5.4 ?
[18:22] <otyugh> Arh, gonna check
[18:24] <takov751> right so you have run a full-upgrade and error still there
[18:25] <otyugh> ...Now you mention it, I only did an apt upgrade
[18:26] <otyugh> What I did is simple : added the 18.04 source, installed the linux-image from there and header package, and rebooted on it, found an error, got stuck :o
[18:32] <takov751> why did you wanted to use the older kernel?
[18:34] <takov751> yelp he left