[08:03] <lotuspsychje> ruenoak: https://dpaste.org/Gcv1i
[08:51] <hateball> I upgraded to Kubuntu noble, and for some reason the system does not boot with the default kernel parameters with splashscreen. It just gets stuck on a grey screen and I can't switch to a tty or anything. Removing "quiet splash" from /etc/default/grub and then running "sudo update-grub" to rebuild the configuration makes the system boot as expected.
[08:52] <hateball> Tried finding any errors in logs so I could file a bug report against... something, but I am not really finding anything
[09:33] <lotuspsychje> hateball: we had a user reporting something similar on xubuntu yesterday, his second boot did succeed
[09:36] <lotuspsychje> hateball: maybe share your full sudo dmesg here, volunteers can take a look
[11:15] <hateball> lotuspsychje: good idea, I just need to figure out which of the logs would be from a non-working boot :)
[11:19] <lotuspsychje> hateball: last boot; journalctl -b -1
[11:20] <hateball> weird, that only shows me for the 30th of march :D
[11:20] <hateball> anyways, I had a dmesg.4.gz which seems to be from a failed boot
[11:21] <lotuspsychje> hateball: check journalctl --list-boots
[11:21] <hateball> ah my mistake, I typed 1 instead of -1
[11:22] <lotuspsychje> ah
[11:27] <hateball> This is the log from a failed boot https://pastebin.com/TtrJAgcu and for comparison this is from booting without "quiet splash" which works https://pastebin.com/E7xWiXcG
[11:27] <hateball> The only actual errors I see are related to virtualbox, I had those on 23.10 as well. And I had no issue booting with splash enabled then.
[11:32] <hateball> For me personally it's no biggie just disabling the splash screen to have a working system... but for someone that does not know how to edit grub and remove that it would be a poor experience if they upgrade and no longer can use their system
[11:33] <lotuspsychje> hateball: yeah end of the logs give virtualbox lines
[11:34] <lotuspsychje> apr 14 09:54:39 megingjord kernel: UBSAN: array-index-out-of-bounds in /var/lib/dkms/virtualbox/7.0.14/build/vboxdrv/SUPDrvGip.c:2208:20
[11:49] <hateball> yeah, as I said that's present since 23.10 as well, and the system works just fine as long as  I boot without splash, so I don't think that's what breaks the boot
[11:50] <lotuspsychje> hateball: you got autologin enabled? and do you log into xorg or wayland?
[11:50] <hateball> lotuspsychje: no autologin. I use wayland
[11:50] <lotuspsychje> ok
[11:50] <lotuspsychje> i had no boot issues myself on the whole noble cycle
[11:50] <hateball> so when it fails it doesnt even reach sddm, it just halts
[11:51] <lotuspsychje> hmm
[11:51] <hateball> I was going to test noble a bit earlier but... I did not, for whatever reason
[11:51] <lotuspsychje> maybe kubuntu related then
[11:52] <hateball> as for the vbox thing there's a bug report for it https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2037082
[11:52] -ubottu:#ubuntu-next- Launchpad bug 2037082 in virtualbox (Ubuntu) "UBSAN: array-index-out-of-bounds with kernel 6.5 on Mantic" [Undecided, Fix Released]
[11:52] <lotuspsychje> system up to date right hateball ?
[11:52] <lotuspsychje> a lot of kubuntu packages were held for long due that xz repair
[11:53] <lotuspsychje> so make sure apt doesnt spit out errors anymore
[11:53] <hateball> lotuspsychje: yeah, I switched to 24.04 yesterday, and funny enough it worked properly the first reboot. but this morning is when I noticed the grey screen issue
[11:53] <lotuspsychje> weird yeah
[11:53] <hateball> lotuspsychje: yes I think that's why I didnt upgrade, since there were held packages preventing me to do so. then I just didnt think about upgrading until yesterday
[11:54] <lotuspsychje> its beta time, so base should be working
[11:57] <lotuspsychje> hateball: lets have a look in; systemd-analyze critical-chain
[11:57] <hateball> will that show historical boots?
[11:58] <hateball> I mean there's not much to troubleshoot now, since everything is working :D
[11:59] <lotuspsychje> right
[11:59] <lotuspsychje> but would be good to find the rootcause
[11:59] <hateball> this is what it spits out anyways https://pastebin.com/ENxaX20A
[11:59] <lotuspsychje> hateball: your amdgpu gives a bit much output lines too
[12:00] <lotuspsychje> systemd analyze looks sane, but thats from this working boot
[12:00] <hateball> yeah... and I can't really get anything from when it fails, since I can't even get to a tty
[12:02] <lotuspsychje> maybe you could try a previous kernel version with the failed boot/ quiet splash
[12:03] <hateball> yeah I didnt actually try booting on 6.5, I can do that I guess
[12:03] <lotuspsychje> maybe we can prove its amdgpu on kernel 6.8
[12:05] <hateball> let me test
[12:10] <hateball> yep, kernel 6.5 works as expected
[12:10] <lotuspsychje> aha progress
[12:10] <hateball> with 6.8 I dont even get the Kubuntu EFI splash to begin with, I noticed
[12:11] <lotuspsychje> hateball: can you grab the dmesg from 6.5 booting?
[12:11] <hateball> lotuspsychje: yep it's here https://pastebin.com/M3CPwFtZ
[12:12] <lotuspsychje> checking
[12:14] <lotuspsychje> hmm amdgpu also gives similar lines there, im not sure now
[12:14] <hateball> lotuspsychje: which lines in particular ?
[12:14] <hateball> the vbox related stuff is always there
[12:14] <hateball> otherwise I dont really see any errors related to amdgpu, just that it's quite verbose about what it is doing
[12:15] <lotuspsychje> hateball: starts all at 1626
[12:17] <lotuspsychje> apr 14 14:06:36 megingjord kernel: WARNING: CPU: 12 PID: 468 at drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_capability.c:1525 dp_retrieve_lttpr_cap+0x19b/0x1d0 [amdgpu]
[12:17] <lotuspsychje> anyway we proved its kernel related..but what beats me right now
[12:18] <hateball> lotuspsychje: the amdgpu stuff seems to be about some "secure display" feature that not all GPUs support as I understand it, there's this bug https://gitlab.freedesktop.org/drm/amd/-/issues/1415
[12:18] -ubottu:#ubuntu-next- Issue 1415 in drm/amd "amdgpu: RAS: optional ras ta ucode is not available" [Opened]
[12:19] <hateball> so not an error per se, as I understand it
[12:19] <hateball> and everything works, so :)
[12:19] <lotuspsychje> yeah and this is your working boot dmesg
[12:19] <hateball> yep
[12:19] <lotuspsychje> so im just trying to think of a 6.8 bottleneck preventing to graphical boot
[12:20] <lotuspsychje> graphics were a possible road but..
[12:24] <lotuspsychje> hateball: bug #2057155 exists, but this user reaches desktop
[12:24] -ubottu:#ubuntu-next- Bug 2057155 in linux (Ubuntu) "amdgpu driver crashes running electron application after some time" [Undecided, New] https://launchpad.net/bugs/2057155
[12:25] <hateball> I tried entering my password and pressing enter as well, in case it was like a display bug with sddm, but no desktop loaded so I don't think it actually makes it that far
[12:26] <hateball> Looking at that bug report it's about GPU issues inside the session, I have none of that... at least not thus far :D
[12:26] <lotuspsychje> yeah, so different bug
[12:32] <lotuspsychje> i would file a bug hateball 
[12:32] <hateball> I'm just not sure against what, but I suppose the kernel?
[12:32] <lotuspsychje> as you're testing with nobles latest kernel version and get a failed boot
[12:32] <lotuspsychje> yeah file against 'linux'
[12:33] <hateball> Will do!
[12:33] <lotuspsychje> the devs might find something
[12:33] <hateball> (just another episode of Fallout first)
[12:33] <lotuspsychje> sure, enjoy
[12:33] <hateball> lotuspsychje: thanks for taking time to look into it
[12:33] <lotuspsychje> np
[14:31] <hateball> I filed this bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061295
[14:31] -ubottu:#ubuntu-next- Launchpad bug 2061295 in linux (Ubuntu) "No graphical boot with default Kubuntu 24.04" [Undecided, New]
[14:38] <lotuspsychje> checking hateball 
[14:38] <hateball> I mean there's nothing new there, I think... but at least it exists
[14:39] <lotuspsychje> looking good hateball just i would also add the 6.5 dmesg, so the devs can also compare
[14:39] <hateball> lotuspsychje: good idea! thanks
[14:42] <lotuspsychje> ive seen a recent bug about not able to boot 6.8 with a gigabyte mobo, but yours is asrock
=== mandem0110 is now known as nandem0110
=== nandem0110 is now known as mandem0110