=== simoniz0r[m] is now known as simonizor
=== _thumper_ is now known as thumper
=== maclin1 is now known as maclin
didrocksgood morning07:37
seb128good morning desktopers08:03
jibelI'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 ?08:49
Laneyhey hey09:01
didrockshey Laney09:03
didrocksjibel: looking at the commits, https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=8778c2dd422f2a3589f24394896710284eff545f, I would say:09:03
didrocks1. create a custom binding in g-c-c (one binding which runs a command, like a shell script)09:03
didrocks2. change this custom binding command it's pointing at and try the key combination09:04
didrocks(or change the associate key combination and try again)09:04
jibeldidrocks, yes, that's what I understood and did too, but it works fine with current version in artful09:07
jameshLooking at the diff, it was only updating if the keyboard shortcut changed: not the command behind the shortcut09:07
jameshjibel: maybe try creating the custom binding in gnome-control-center, and then change the command with dconf-editor?09:07
didrocksjamesh: yeah, you came to the same conclusion than I, changing the command behind the short…09:08
didrocksI 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:09
jameshdidrocks: 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 there09:10
didrocksjamesh: oh, good idea09:10
didrocksso yeah, jibel dconf-editor, only change the "command" key, as jamesh hinted ^09:11
jibeldidrocks, jamesh I can reproduced now, thansk09:11
didrocksok, I think it's really minor :p09:11
didrocksmost of people would use g-c-c to update the keybindings when using custom command IMHO09:11
jibeldidrocks, it's reproducible even with g-c-c09:12
jibeljust being thorough and verifying upstream bugs, but they are poorly documented09:13
didrocksah ok ;)09:13
didrocksjibel: yeah, unsurprised… good luck09:13
Laneyhey didrocks jibel & jamesh09:20
Laneyall good?09:20
jibelhi Laney09:20
jibelyep, all good09:20
jibelI finally have internet :)09:20
jibeljust took a month09:20
didrocksLaney: lacking some sleep, otherwise, good! Yourself? :)09:21
jibeland I'm in the city center, I cannot imagine how long it would have taken if I lived in the country side :D09:21
didrocksjibel: time to download some ubuntu isos then! ;)09:21
jibeldidrocks, time to push some major changes so there is something to test ;)09:22
oSoMoNgood morning desktoppers!09:30
didrockssalut oSoMoN, bon week-end ?09:31
oSoMoNsalut didrocks, très bon week-end, et toi?09:31
didrocksoSoMoN: ça va ;) un peu des nuits difficiles, mais globalement, bien, merci ! ;)09:37
seb128hey again desktopers09:53
oSoMoNhey seb12809:53
seb128lut oSoMoN09:53
didrocksre seb12809:53
oSoMoNseb128, 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 number10:17
seb128oSoMoN, ah, nice, they did more changes after you pointed out the test issue?10:24
oSoMoNseb128, that's https://gerrit.libreoffice.org/#/c/44871 , a patch currently under review10:25
oSoMoNseb128, https://people.canonical.com/~osomon/libreoffice-5.4.2/bionic3/10:28
seb128oSoMoN, 'ci10:29
oSoMoNchrisccoulson, 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 concerned10:46
seb128oSoMoN, seems like the libreoffice SRU got accepted10:59
Trevinho Morning guys15:48
didrocksgood morning Trevinho!15:50
seb128hey Trevinho, how are you?15:58
Laneycongrats to oSoMoN ;-)16:04
seb128I assume it's in context of his ppu?16:05
oSoMoNit is :)16:05
oSoMoNthanks Laney16:05
seb128oSoMoN, well done :)16:05
oSoMoNthanks seb12816:06
didrockssweet oSoMoN, congrats! ;)16:09
oSoMoNthanks didrocks16:10
* Laney shares the secret handshake16:10
sil2100Well job, good done oSoMoN!16:11
oSoMoNthanks sil210016:12
seb128next libreoffice :p16:12
kenvandineoSoMoN, awesome, congrats!16:17
oSoMoNthanks kenvandine16:19
Laneywhile true; do trivial_tinker; sleep 600; echo ARGH; done17:46
oSoMoNchrisccoulson, 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
Laneythe oSoMoN power grab begins17:46
GunnarHjjbicha: Has lp:~ubuntu-desktop/gnome-control-center/ubuntu been abandoned in bionic?18:49
infinitySo, 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:53
infinityLaney, darkxst, jbicha ^19:55
sarnoldinfinity: did you happen to hit ^C in a terminal?19:58
mdeslaursarnold: WAT?20:04
sarnoldmdeslaur: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/171063720:05
ubot5Launchpad bug 1710637 in console-setup (Ubuntu) "Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland" [High,Fix released]20:05
* mdeslaur cries20:06
infinitysarnold: Yes.  Yes I did.  Double-U Tee Eff.20:08
infinity(I just did it a second time, argh)20:09
sarnoldwho knew that ^C might be something that we're used to typing?20:09
infinityI guess I need to reboot for this fix to apply?20:10
infinityAnd also, if it's been broken this long, how did I only hit it today?  I haven't rebooted in weeks.20:10
sarnoldI -think- i depends upon what programs were run in the terminal20:11
mdeslaurinfinity: please refrain from using ctrl-c in Gnome, it's been deprecated. ;)20:12
infinityIt's cause I'm installing ubuntu-minimal in a *xenial* chroot, and then hitting Ctrl-C later.20:12
sarnoldand apt-get upgrade does it, once in a while20:12
infinityHow disgusting.20:12
infinitysarnold: 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
infinityWhich is about 99% of my Ctrl-C usage.20:16
sarnoldinfinity: why yes, I've got two valgrinds running now for .. 114 minutes. I suspect they aren't coming back. ^C was their planned future20:17
infinitysarnold: 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
sarnoldinfinity: oh!20:18
sarnoldinfinity: ^U and ^K20:18
infinityThat's how I just killed my session twice today.20:18
sarnoldinfinity: sometimes ^G does the trick20:18
chrisccoulsonoSoMoN, sorry, I just hit the deactivate button :/20:18
chrisccoulsonoSoMoN, ok, fixed20:19
infinitysarnold: Or!  I could ignore the problem by dpkg-diverting that udev rule pre-emptively in all my << artful chroots!20:19
infinityI think I'll do that.20:19
LaneyIt would be nice to backport the console-setup fpixes20:23
* Laney is on wet string so will go away now20:24
oSoMoNchrisccoulson, thanks20:54
infinityLaney: I've come to the conclusion that what it really needs is setupcon just refusing to run in chroots.20:59
infinityLaney: For the new bug, that is.21:00
Laneyinfinity: 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.21:22
=== _thumper_ is now known as thumper

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!