[07:50] <dholbach> good morning
[07:54] <svij> hey dholbach
[07:54] <dholbach> hey svij
[08:29] <Mister_Q> morning
[09:45] <czajkowski> Aloha
[09:49] <Mister_Q> svij ubucon europe meeting today ? :D
[09:51] <svij> Mister_Q: sure thing :D
[10:17] <Mister_Q> \o/
[10:19] <svij> Mister_Q: erm, rather tomorrow. Today is not tuesday :P


[13:28] <zenadm1n> Why does this make me feel dirty, "The following security updates require Ubuntu Pro ..."
[13:30] <oerheks> known issue
[13:30] <oerheks> https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1992026
[13:30] -ubottu:#ubuntu-discuss- Launchpad bug 1992026 in ubuntu-advantage-tools (Ubuntu) "Ubuntu Pro APT integration is a bit much" [Critical, In Progress]
[13:31] <zenadm1n> I should just write some scripts that download the source debs and build them in my own PPA.
[13:34] <zenadm1n> I know what's going on. This is just the first time I've encountered this myself. It's funny how Canonical will rely on Debian for development and maintenence for upstream, but they're going to start charging for their contributions. I was building packages for Ubuntu's early versions before they even built the Launchpad build system.
[13:36] <oerheks> its all about universe packages that get support after 5 years. https://ubuntu.com/pro
[13:36] <oerheks> who would use such old linux ..
[13:37] <zenadm1n> For versions before Launchpad Canonical had no capacity to build universe, so they put it out to the community.
[13:40] <zenadm1n> I don't even remember which packages I built I basically just took the debian source and repackaged it. I taught myself Linux on Gentoo building everything myself so it was not difficult.
[13:42] <ogra> there were no ubuntu versions before launchpad ... it has been our build system from day one (in fac it pre-dates ubuntu by about a year)
[13:48] <zenadm1n> I worked on version 5 and actually got a letter from Shuttleworth thanking me. My handle at the time was "smokeslikeapoet". Ubuntu 4.10 was released in 2004. Launchpad didn't come along until 4 years later.
[13:49] <zenadm1n> I'm looking at wikipedia right now to verify I'm not in some sort of Mandela effect. I've been running Linux for 21 years.
[13:50] <zenadm1n> I graduated school in 2007 and had Ubuntu on my laptop from the inital 4.10 release all through school.
[13:51] <ravage> 👍
[13:52] <zenadm1n> "Do not quote the dark magic to me, I was there when it was written."
[14:28] <leftyfb> zenadm1n: Bug #1 was filed on August 19th 2004. Ubuntu 4.10 was released October 04 2004.
[14:28] -ubottu:#ubuntu-discuss- Bug 1 in Ubuntu Malaysia LoCo Team "Microsoft has a majority market share" [Critical, In Progress] https://launchpad.net/bugs/1
[14:30] <leftyfb> The initial public release of launchpad was June 15th 2005
[14:30] <leftyfb> so not 4 years later
[14:30] <leftyfb> but that doesn't mean it wasn't already in use
[14:31] <leftyfb> the wiki page also says the website was launched "January 2004"
[14:34] <leftyfb> Multiple people here have been working with linux and Ubuntu for 20+ years.
[15:02] <zenadm1n> leftyfb, yes, I had to go to my Lanchpad acct, it's been a while. I joined 6/2005, started my own PPA in 2007.
[15:04] <zenadm1n> Nevertheless, my point stands. Canonical has asked volunteers to port, maintain upstream universe for close to 2 decades. It kinda leave a bad taste in my mouth for them to try and monetize universe security in my command line.
[16:07] <zenadm1n> Where can one find the source packages for these Ubuntu Pro universe updates? Is there a source repo I can add?
[16:08] <zenadm1n> I'm serious about building them in my own PPA.
[16:11] <oerheks> There is no such list published.
[16:13] <PaulW2U> zenadm1n: You get access to the packages if you enable Pro. I assume the same applies to the source packages.
[16:48] <zenadm1n> PaulW2U, it is a violation of the GPL to distribute binaries without making availble the source and modifications.
[16:50] <oerheks> maybe the source will be available?
[18:48] <popey> zenadm1n https://askubuntu.com/questions/1454409/where-do-i-get-the-source-for-esm-packages
[18:51] <leftyfb> man, if popey doesn't know the answer, Canonical is doing a really horrible job at documentation and informing it's users
[18:51] <popey> lulz
[18:51] <ravage> popey is just one of us now :)
[18:51] <popey> yeah, I'm just a pleb like the rest of you :D
[18:52] <leftyfb> bah, you still know whats up and how to find answers and have connections
[18:52] <leftyfb> even I do, to a point
[18:53] <aaronprisk[m]> Let me see if I can get an answer on this.
[18:56] <ravage> i think apt-source just does not understand the login method
[18:57] <ravage> as in it does not use "/etc/apt/auth.conf.d/90ubuntu-advantage"
[18:58] <ravage> https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwiBz5uT0Yv9AhXuS_EDHYynDVIQFnoECAYQAQ&url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1904068&usg=AOvVaw2j3OSC3SNBdKN__39xjD2k
[18:58] <ravage> sorry
[18:58] <ravage> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1904068
[18:58] <ravage> this
[18:58] -ubottu:#ubuntu-discuss- Launchpad bug 1904068 in apt (Ubuntu) "apt(-get) source fails to use credentials from /etc/apt/auth.conf(.d)" [Undecided, Confirmed]
[18:59] <arraybolt3> That looks promising.
[19:01] <ViatonWidz[m]> sudo apt source <esm-packagename> works for me
[19:02] <ravage> i get the same error as described on askubuntu
[19:03]  * arraybolt3 doesn't use esm or Ubuntu Pro yet so I can't test :P
[19:03] <ViatonWidz[m]> ravage: did you use sudo?
[19:04] <arraybolt3> zenadm1n: Looks like it's just an apt bug, a person in the bug report ravage linked to was able to pull the source packages.
[19:04] <ravage> heh
[19:04] <ravage> it works with sudo
[19:05] <ravage> let me see if changing the permissions of that authfile helps too
[19:05] <ravage> yep
[19:06] <ravage> some info that it cant read the file would be useful maybe
[19:07] <arraybolt3> ravage: You're able to add that info to the bug report right?
[19:07] <arraybolt3> That sounds like a very easy fix if it's just a permissions issue.
[19:07] <arraybolt3> (And knowing that sudo works as a workaround it awesome.)
[19:07] <ViatonWidz[m]> If you chmod 644 /etc/apt/auth.conf.d/90ubuntu-advantage it works as regular user
[19:08] <ravage> yes
[19:09] <ravage> added a comment
[19:10] <ViatonWidz[m]> Of course you leave the login and password open though 😬
[19:10] <ravage> true
[19:11] <ravage> on my system i really dont care :)
[19:12] <arraybolt3> ravage: Just added a comment there, can you test with it?
[19:13] <arraybolt3> Some people probably do have systems where they care, so if there's a way to avoid opening up everything that would be good - I suggested changing the permissions back to something strict and then changing the file ownership.
[19:13] <ravage> as long as the user can read the file it works
[19:14] <ravage> so yes. if you add yourself to a group that can read the file thats fine too
[19:17] <ravage> i removed the example
[19:17] <ravage> pretty sure that bug will be closed anyway. works as intended :D
[19:41] <aaronprisk[m]> Hey folks, got verification that using sudo with apt source is indeed the correct and safe method for obtaining these esm source files. One of our devs updated the bug report with a comment providing some additional context.
[19:42] <ravage> thanks aaronprisk[m]


[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


[12:59] <Brainstorm> Updates for Bangladesh: +864 cases, +9 deaths, +21543 tests (4.0% positive) since 23 hours ago