[07:37] <didrocks> good morning
[08:03] <seb128> good morning desktopers
[08:49] <jibel> I'm doing the SRU verification of g-s-d in artful. Anyone would know how to reproduce the "custom binding" bug mentioned in https://git.gnome.org/browse/gnome-settings-daemon/tree/NEWS ?
[09:01] <Laney> hey hey
[09:03] <didrocks> hey Laney
[09:03] <didrocks> jibel: looking at the commits, https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=8778c2dd422f2a3589f24394896710284eff545f, I would say:
[09:03] <didrocks> 1. create a custom binding in g-c-c (one binding which runs a command, like a shell script)
[09:04] <didrocks> 2. change this custom binding command it's pointing at and try the key combination
[09:04] <didrocks> (or change the associate key combination and try again)
[09:07] <jibel> didrocks, yes, that's what I understood and did too, but it works fine with current version in artful
[09:07] <jamesh> Looking at the diff, it was only updating if the keyboard shortcut changed: not the command behind the shortcut
[09:07] <jamesh> jibel: maybe try creating the custom binding in gnome-control-center, and then change the command with dconf-editor?
[09:08] <didrocks> jamesh: yeah, you came to the same conclusion than I, changing the command behind the short…
[09:08] <didrocks> shorcut*
[09:09] <didrocks> I doubt this is a g-c-c vs dconf-editor, what replaces what is quite opaque to g-s-d (only listening to gsettings events)
[09:10] <jamesh> didrocks: right, but if g-c-c updates things in such a way that both settings get changed at once, it might not be possible to trigger there
[09:10] <didrocks> jamesh: oh, good idea
[09:11] <didrocks> so yeah, jibel dconf-editor, only change the "command" key, as jamesh hinted ^
[09:11] <jibel> didrocks, jamesh I can reproduced now, thansk
[09:11] <jibel> ks*
[09:11] <jibel> -d
[09:11] <didrocks> ok, I think it's really minor :p
[09:11] <didrocks> most of people would use g-c-c to update the keybindings when using custom command IMHO
[09:12] <jibel> didrocks, it's reproducible even with g-c-c
[09:13] <jibel> just being thorough and verifying upstream bugs, but they are poorly documented
[09:13] <didrocks> ah ok ;)
[09:13] <didrocks> jibel: yeah, unsurprised… good luck
[09:20] <Laney> hey didrocks jibel & jamesh
[09:20] <Laney> all good?
[09:20] <jibel> hi Laney
[09:20] <jibel> yep, all good
[09:20] <jibel> I finally have internet :)
[09:20] <jibel> just took a month
[09:21] <didrocks> Laney: lacking some sleep, otherwise, good! Yourself? :)
[09:21] <jibel> and I'm in the city center, I cannot imagine how long it would have taken if I lived in the country side :D
[09:21] <didrocks> jibel: time to download some ubuntu isos then! ;)
[09:22] <jibel> didrocks, time to push some major changes so there is something to test ;)
[09:22] <didrocks> heh
[09:30] <oSoMoN> good morning desktoppers!
[09:31] <didrocks> salut oSoMoN, bon week-end ?
[09:31] <oSoMoN> salut didrocks, très bon week-end, et toi?
[09:37] <didrocks> oSoMoN: ça va ;) un peu des nuits difficiles, mais globalement, bien, merci ! ;)
[09:53] <seb128> hey again desktopers
[09:53] <oSoMoN> hey seb128
[09:53] <seb128> lut oSoMoN
[09:53] <didrocks> re seb128
[10:17] <oSoMoN> seb128, my libreoffice test build with the upstream proposed patch for ICU 60 seems to work well, I'll prepare source packages with a clean version number
[10:24] <seb128> oSoMoN, ah, nice, they did more changes after you pointed out the test issue?
[10:25] <oSoMoN> seb128, that's https://gerrit.libreoffice.org/#/c/44871 , a patch currently under review
[10:25] <seb128> great
[10:28] <oSoMoN> seb128, https://people.canonical.com/~osomon/libreoffice-5.4.2/bionic3/
[10:29] <seb128> oSoMoN, 'ci
[10:46] <oSoMoN> chrisccoulson, I validated the chromium stable update to 62.0.3202.94 in https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+packages , it's good to go as far as I'm concerned
[10:59] <seb128> oSoMoN, seems like the libreoffice SRU got accepted
[11:00] <oSoMoN> great
[15:48] <Trevinho>  Morning guys
[15:50] <didrocks> good morning Trevinho!
[15:58] <seb128> hey Trevinho, how are you?
[16:04] <Laney> congrats to oSoMoN ;-)
[16:05] <seb128> I assume it's in context of his ppu?
[16:05] <oSoMoN> it is :)
[16:05] <oSoMoN> thanks Laney
[16:05] <seb128> oSoMoN, well done :)
[16:06] <oSoMoN> thanks seb128
[16:09] <didrocks> sweet oSoMoN, congrats! ;)
[16:10] <oSoMoN> thanks didrocks
[16:10]  * Laney shares the secret handshake
[16:11] <sil2100> Well job, good done oSoMoN!
[16:12] <oSoMoN> thanks sil2100
[16:12] <seb128> next libreoffice :p
[16:15] <oSoMoN> yup
[16:17] <kenvandine> oSoMoN, awesome, congrats!
[16:19] <oSoMoN> thanks kenvandine
[17:46] <Laney> while true; do trivial_tinker; sleep 600; echo ARGH; done
[17:46] <oSoMoN> chrisccoulson, do you think you could make me an admin of https://launchpad.net/~chromium-team so I can create PPAs? (I want to move my chromium-stable, chromium-next and chromium-dev PPAs over to the team)
[17:46] <Laney> the oSoMoN power grab begins
[17:46] <Laney> muhahah
[17:56] <oSoMoN> hehe
[18:49] <GunnarHj> jbicha: Has lp:~ubuntu-desktop/gnome-control-center/ubuntu been abandoned in bionic?
[19:53] <infinity> So, my gnome-shell just exited spontaneously for the first time I switched.  How/where does that get logged in a way that I can try to determine why?
[19:55] <infinity> Laney, darkxst, jbicha ^
[19:58] <sarnold> infinity: did you happen to hit ^C in a terminal?
[20:04] <mdeslaur> sarnold: WAT?
[20:05] <sarnold> mdeslaur: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1710637
[20:06]  * mdeslaur cries
[20:08] <infinity> sarnold: Yes.  Yes I did.  Double-U Tee Eff.
[20:09] <infinity> (I just did it a second time, argh)
[20:09] <sarnold> who knew that ^C might be something that we're used to typing?
[20:10] <infinity> I guess I need to reboot for this fix to apply?
[20:10] <infinity> And also, if it's been broken this long, how did I only hit it today?  I haven't rebooted in weeks.
[20:11] <infinity> Oh!
[20:11] <sarnold> I -think- i depends upon what programs were run in the terminal
[20:12] <mdeslaur> infinity: please refrain from using ctrl-c in Gnome, it's been deprecated. ;)
[20:12] <infinity> It's cause I'm installing ubuntu-minimal in a *xenial* chroot, and then hitting Ctrl-C later.
[20:12] <sarnold> and apt-get upgrade does it, once in a while
[20:12] <infinity> How disgusting.
[20:16] <infinity> sarnold: It's going to be reeeeeally hard to retrain my fingers to not use Ctrl-C as a shortcut for "abandon that really long thing I typed on the commandline, I don't love it anymore".
[20:16] <infinity> Which is about 99% of my Ctrl-C usage.
[20:17] <sarnold> infinity: why yes, I've got two valgrinds running now for .. 114 minutes. I suspect they aren't coming back. ^C was their planned future
[20:18] <infinity> sarnold: Oh, no, I literally mean "long thing I typed", not "long-running process".  As in, I start typing out a long shell pipe, halfway through decide there's a better way, and Ctrl-C is a lot faster than leaning on Ctrl-W.
[20:18] <sarnold> infinity: oh!
[20:18] <chrisccoulson> shit
[20:18] <sarnold> infinity: ^U and ^K
[20:18] <infinity> That's how I just killed my session twice today.
[20:18] <sarnold> infinity: sometimes ^G does the trick
[20:18] <chrisccoulson> oSoMoN, sorry, I just hit the deactivate button :/
[20:19] <chrisccoulson> oSoMoN, ok, fixed
[20:19] <infinity> sarnold: Or!  I could ignore the problem by dpkg-diverting that udev rule pre-emptively in all my << artful chroots!
[20:19] <infinity> I think I'll do that.
[20:23] <Laney> It would be nice to backport the console-setup fpixes
[20:24]  * Laney is on wet string so will go away now
[20:54] <oSoMoN> chrisccoulson, thanks
[20:59] <infinity> Laney: I've come to the conclusion that what it really needs is setupcon just refusing to run in chroots.
[21:00] <infinity> Laney: For the new bug, that is.
[21:22] <Laney> infinity: Fair enough - I'm not fully au fait with everything the script does but it does sound like it's probably not something that's good for a chroot, indeed.