[05:40] <didrocks> good morning
[05:41] <didrocks> 2nd day experiencing the Shell without ubuntu dock wanting to load, quite annoying
[06:12] <jibel> Good morning all
[06:15] <didrocks> salut jibel, ça va ?
[06:19] <jibel> Salut didrocks, très bien et toi?
[06:24] <didrocks> ça va :)
[06:53] <duflu> Morning didrocks 
[06:53] <duflu> Morning jibel 
[06:54] <duflu> didrocks, are you using https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/72ubuntu1 ?
[07:08] <seb128> goood morning desktopers!
[07:08] <duflu> Hi seb128. How goes?
[07:14] <seb128> duflu, hey! doing alright! you?
[07:15] <seb128> IRC doesn't like the flaky connectivity here, the desk is a bit far from the AP, which is fine for other things though
[07:16] <duflu> seb128, doing OK. Just had my 4th dose so if I vanish tomorrow then that's the reason :)
[07:17] <seb128> I wonder if I should also do it, numbers are raising again...
[07:18] <didrocks> hey duflu, seems I still have 72~ubuntu5
[07:18] <didrocks> salut seb128 
[07:21] <seb128> lut didrocks, en forme ? tjs au frais ?
[07:30] <didrocks> seb128: relatif le frais, mais ça va pour l’instant :)
[08:09] <jbicha> good morning
[08:09] <duflu> Hi jbicha 
[08:15] <jbicha> duflu: hi :)
[08:29] <seb128> hey jbicha, how is it going?
[09:36]  * enyc grumbles about powercuts
[09:36] <enyc> seb128: THANKYOU r.e. SRU queue #1970473
[09:37] <enyc> I'm sure somebody said they needed testing help for SRU, how best to do that / where?
[09:37] <seb128> enyc, np!
[09:37] <seb128> enyc, wait for the SRU to be accepted, a comment will be added to the bug asking to do the verification then
[09:38] <enyc> seb128: ok!  where do I see these SRU queues generally, for all packages / pending fixes ?
[09:38] <enyc> when is focal-proposed-updates involvel, when does anything appear on packages.ubuntu.com etc?
[09:40]  * enyc found https://people.canonical.com/~ubuntu-archive/pending-sru
[09:41] <enyc> doesn't appear there (yet??)
[09:47] <duflu> enyc, I went looking for a stack trace for that one today, because it would identify other instances of the crash. But never found one(?!)
[09:50] <enyc> duflu: if you give detailed instructions on how to collect this  [do you need extra -dbg packages installed?]  I can do so easily, have radeon machines etc.
[09:50] <enyc> that is, atop 22.04 or derivs (pop22.04 / mint21 / etc using same binary xorg packages)
[09:52] <duflu> enyc, Start with the dbgsyms from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4816-deletedppa/+build/23500955 ... I'm not sure if you will also need dbgsyms for all of Xorg :P
[09:53] <duflu> Or don't worry about it because I need to think about dinner soon
[09:58] <jbicha> enyc: also there's https://launchpad.net/ubuntu/jammy/+queue?queue_state=1 for Jammy "unapproved": things that haven't been accepted as proposed updates yet
[10:20] <enyc> bother, duflu left!
[10:21] <enyc> I crashed Xorg with those packages installed, not sure Xorg.0.log contains backtrace and not sure if saved anywhere
[10:21] <enyc> Do I need to do something to start X manuallt with debugging??
[10:22] <enyc> quite able to start manuallyy.. wondering about debug/backtrace on Xserver or run through gdb or SOMETHING
[10:25] <seb128> enyc, is apport not picking it up and generating a report in /var/crash?
[10:28] <seb128> enyc, one 'classic' way to get a backtrace from Xorg is to ssh from another box and attach gdb to the process
[10:28] <seb128> the issue is that if you attach from your current machine gdb blocks the xserver which blocks your session and you can't continue in gdb
[10:33] <enyc> seb128: can I use tty1-6 local console or ttyS0 serial console to do that, too?
[10:41] <enyc> seb128: nm now..
[10:42] <seb128> enyc, sorry, tty probably doesn't work because once you hit the segfault gdb will block things and I think that includes the keybinding to go back to your tty
[10:42] <enyc> seb128:  One crash caught   https://ec2.sheer.us/~enyc/noidx/radeonx-randr-crash/    ... technically this is on deriv as what is conveniently available ob the machine but all the ubuntu xorg dbg as above, doesn't seem to make any difference pop-os mint etc.
[10:43] <enyc> *** please pass this to duflu upon duflu return.  I may be able to do gdb, test plain-ubuntu-22.04 or otherwise in time if actually needed.
[10:43] <seb128> enyc, right, can you try to send it using ubuntu-bug on the .crash?
[10:43] <seb128> enyc, ack
[10:43] <seb128> thanks
[10:44] <enyc> seb128: not right now  but can try later or another day if time... hope that helps!  messages in IRC I should see eventually.
[11:43] <lissyx> seb128, is osomon on pto?
[11:44] <seb128> lissyx, yes, he's back next tuesday
[11:44] <lissyx> oh ok
[11:44] <seb128> redirect any firefox question to me while he's away
[11:44] <lissyx> I was wondering if I could get a final review on the firefox snap changes :)
[11:45] <lissyx> but it can probably wait next week
[11:45] <seb128> and my IRC is a bit flaky here so feel free to ping again if I fail to reply
[11:45] <lissyx> wanadoo :)
[11:47] <seb128> :)
[12:37] <fossfreedom> Hi all. I would like to tackle bug #1969303 gnome-software for jammy. I took the fix from the snap-store-41 branch. Can I complete the SRU and upload myself or should I propose a merge somewhere on launchpad / salsa first?
[14:02] <jbicha> fossfreedom: I'd prefer if you do a merge proposal against the ubuntu/jammy branch for https://salsa.debian.org/gnome-team/gnome-software/
[14:02] <jbicha> do you need sponsorship for it too?
[14:08] <fossfreedom> jbicha: thx. I will fork and propose a merge on salsa. I have packageset rights to upload to jammy
[14:08] <jbicha> great, thank you very much for the fix!