[05:42] <oSoMoN> good morning desktoppers
[05:48] <jibel> salut oSoMoN
[05:59] <jibel> jamesh, could you have a look at bug 1723312
[06:00] <jibel> introduced by latest gnome-software
[06:01] <jibel> hmm, more likely for robert
[06:01] <oSoMoN> salut jibel
[06:06] <duflu> Morning oSoMoN, jibel
[06:07] <oSoMoN> hey duflu
[06:12] <jibel> morning duflu
[06:40] <jamesh> jibel: sure.
[07:14] <didrocks> good morning
[07:19] <oSoMoN> salut didrocks
[07:22] <didrocks> salut oSoMoN, ton jour off était bien ?
[07:25] <oSoMoN> didrocks, super, grosse bouffe avec la belle-famille et bricolage le reste de la journée, une journée très agréable
[07:25] <oSoMoN> et toi, ça va?
[07:25] <didrocks> ça va, Martin a la roséole, donc 39.5 de fièvre hier soir, pendant la nuit et ce matin… donc… fatigué :p
[07:26] <didrocks> (il vient de sortir d'un rhume/fièvre, 2 jours de répis et hop…)
[07:27] <oSoMoN> pas cool
[07:27] <oSoMoN> bon courage!
[07:33] <didrocks> 'ci ;)
[07:39] <seb128> re
[07:39] <seb128> lut les frenchies
[07:40] <duflu> et tout le monde?
[07:40] <seb128> hey duflu
[07:40] <duflu> Hi seb128
[07:40] <seb128> they were the only ones talking :p
[07:40] <seb128> but you are right
[07:40] <seb128> good morning desktopers :)
[07:40] <seb128> happy friday!
[07:41] <duflu> Trevinho, I'm happy with the maximize gradient :)
[07:42] <duflu> Oh wait, it's probably like midnight for you
[07:42] <oSoMoN> salut seb128, happy Friday!
[07:43] <didrocks> re seb128, hey duflu
[07:43] <duflu> Hey didrocks
[08:00] <jibel> jamesh, I think it's the crash identified when I tested g-s from the PPA but couldn't retrace. It happens when you log into U1
[08:46]  * duflu wonders why both gnome-system-monitor and iotop report video players as writing to disk and not reading
[08:46] <Tornado> Hello desktop team, what is the codename for Ubuntu 18.04LTS ?
[08:51] <jamesh> Tornado: it'll probably be announced shortly after 17.10 is released.  Until then, no one knows
[08:52] <Tornado> ok
[08:58] <Trevinho> duflu: it was 2ish... :D
[08:59] <Trevinho> but cool
[08:59] <jibel> duflu, iotop reports reads for me but g-s-m reports writes, which sounds wrong
[09:00] <jibel> vmstats reports reads too
[09:00] <jibel> tried with vlc
[09:01] <duflu> jibel, found the answer in the kernel structure. Those apps are reporting hardware reads for the process. Since I keep testing the same video it's in the cache and incurs no hardware reads. You need to monitor a different structure field to measure software disk reads
[09:01] <Trevinho> good night guys...
[09:01] <duflu> Good night/morning Trevinho
[09:02] <Trevinho> PS: I pushed some patches in mutter to be imported
[09:02] <andyrock> seb128: hey https://errors.ubuntu.com/problem/1ad213da84f3614497bc65e9e93dca262c1944a6
[09:02] <duflu> jibel, the writes occur in 4096 block increments, so that sounds like ext4 journaling maybe
[09:03] <andyrock> seb128: it looks related to the removed patch from gnome-settings-daemon
[09:03] <seb128> andyrock, Trevinho hey
[09:03] <andyrock> even if unity-settings-daemon should ship with its own schema?
[09:03] <seb128> andyrock, fixed in https://launchpad.net/ubuntu/+source/gnome-settings-daemon/3.26.1-0ubuntu4
[09:04] <andyrock> nice :)
[09:04] <duflu> jibel, so rightfully so, you only get hardware reads reported the first time. Then it's already in RAM :)
[09:05] <jibel> duflu, maybe but 12kB total reads reported by g-s-m for a 1.7GB video seems very little
[09:05] <jibel> i'll flush disk cache just to be sure
[09:05] <duflu> jibel, but is it the first time you've played/read it since rebooting?
[09:07] <jibel> duflu, yes
[09:07] <jibel> no difference
[09:07] <duflu> jibel, oh there's a second bug - g-s-m confuses reads for writes
[09:07] <jibel> I won't reboot now but it's odd
[09:07] <jibel> yup
[09:08] <duflu> jibel, iotop is more correct I think
[09:10] <Tornado> Have you planned to switch to Gnome 3.28 for the 18.04 ?
[09:11] <jibel> it's more accurate or use iostat
[09:17] <duflu> jibel, sigh. It seems gnome-system-monitor is comically inaccurate for both CPU and disk
[09:17] <duflu> Logging bugs now
[09:17] <duflu> (% CPU is only ever an integer multiple of NCPUs)
[09:21] <jibel> duflu, and the result seems to depend on the order of the colums
[09:22] <duflu> jibel, great! You log that one? :)
[09:22] <jibel> yes
[09:23] <jibel> I changed the order of the 'reads' column to be next to 'writes' and now it reports totem as 'reading' from disk and no more writes :)
[09:23] <duflu> jibel, OK that sounds less bad. It's just populating the table by column index
[09:24] <duflu> jibel, actually that's the same bug. I will log it
[09:28] <GunnarHj> seb128: Hi Sebastien, can you please have a look at bug #1722427.
[09:28] <GunnarHj> Would you be ok with uploading a lightdm patch with the proposed change?
[09:29] <seb128> hey GunnarHj
[09:29] <duflu> jibel, actually I can't reproduce what you say. Moving the columns keeps the same result. Just make sure you're playing some new video so the reads outweight the writes
[09:29] <seb128> GunnarHj, try emailing robert about it maybe?
[09:31] <GunnarHj> seb128: Don't think that's necessary in this case. The 'problematic' lightdm code was written by me...
[09:31] <seb128> GunnarHj, well he's the one uploading lightdm usually
[09:31] <seb128> GunnarHj, I'm sorry but I'm currently looking at Ubuntu changes trying to get those maybe on the iso today
[09:31] <seb128> lightdm can wait for next week
[09:32] <jibel> duflu, hmm, let me try again
[09:33] <GunnarHj> seb128: This is also an ISO issue, I think. Important for Kylin. Is Laney around today?
[09:33] <seb128> GunnarHj, no, he's travelling back from the U.S and having his friday off
[09:34] <GunnarHj> seb128: Can it wait till Monday? And still make it for the release?
[09:36] <duflu> jibel, https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bugs?search=Search&field.bug_reporter=vanvugt
[09:41] <seb128> GunnarHj, dunno but my focus is Ubuntu Desktop and lightdm is not used there so I've no time to spend on that review today sorry
[09:42] <GunnarHj> seb128: Ok, I'll try to reach out to Robert.
[09:42] <seb128> he's off for the w.e I expect
[09:44] <jibel> duflu, thanks. cannot reproduce the column swap, probably me misreading. However 1723376 is confirmed with a dd, write 2GB to disk and it sees only reads
[09:44] <duflu> jibel, thanks yeah I tried dd too
[09:45] <duflu> And in the end figured out where totem is skipping for a quarter of a second -- it's _writing_ something to disk
[09:49] <duflu> Although if that's the ext4 journal just recording access times then I'm out of luck :P
[09:51] <seb128> GunnarHj, is that a regression from this cycle?
[09:51] <GunnarHj> seb128: Yes. It's due to a workaround in im-config which I discussed with Laney. That's why I asked for him.
[09:52] <seb128> k
[09:52] <seb128> does it impact any flavor?
[09:53] <GunnarHj> seb128: Not by default, I think. But Kylin has the fcitx stuff there by default for everyone.
[09:54] <seb128> GunnarHj, so your fix is a workaround?
[09:54] <GunnarHj> seb128: Yes. I simply disable the error check code for ~/.profile and friends.
[09:57] <seb128> GunnarHj, that seems suboptimal? can't you just undo what you changed that made those errors be displayed?
[09:57] <GunnarHj> seb128: That would affect Ubuntu adversely wrt input methods.
[09:57] <seb128> GunnarHj, anyway I guess that can still be fixed on monday if it's important enough for kylin and they request to respin their iso to get it fixed
[09:59] <GunnarHj> seb128: Ok, let's hope so. It would really be good to talk with Laney about it, since he is updated on the im-config side of it and actually suggested the workaround there.
[10:00] <seb128> right
[10:24] <oSoMoN> seb128, is there still a chance to land a fix for bug #1718446 before release? note that it'd still need a review first, ideally from upstream
[10:28] <didrocks> oSoMoN: final freeze was yesterday, small fixes seem to still can go in, but that's it
[10:28] <didrocks> oSoMoN: we will need to upload it quickly to get a 0-day SRU though (as it's only going to impact people installing new packages, and so upgrades anyway)
[10:29] <oSoMoN> didrocks, yeah I know, I was unsure if that qualified for a freeze exception
[10:29] <seb128> oSoMoN, we discussed it with Didier yesterday and since unity isn't going to be picked instread of ubuntu-xorg (due to alphabetic sorting) we decided it was fine as a SRU and didn't need to be on the iso
[10:29] <oSoMoN> didrocks, do you think you could give it a review and let me know if the approach is sound?
[10:29] <oSoMoN> seb128, ok
[10:29] <didrocks> oSoMoN: I did give a look, but didn't test it, the approach is +1 for me
[10:29] <didrocks> oSoMoN: however, it will need some heavy testing IMHO
[10:30] <didrocks> like:
[10:30] <didrocks> - have gnome-classic, gnome-session, ubuntu-session and unity-session installed
[10:30] <didrocks> - have wayland enabled -> select a session (GNOME or Ubuntu), disabled wayland -> check the corresponding session is fallbacked to
[10:31] <didrocks> also, the contrary, don't select a session, have wayland disabled, log in in GNOME or Ubuntu, enable wayland -> check the correct session is selected
[10:31] <oSoMoN> I already tested the first use case (although I didn't have gnome-classic)
[10:31] <didrocks> - and every time check that all sessions appears as desired (on the menu item)
[10:32] <didrocks> are there any other corner cases we can think about?
[10:32] <didrocks> (that was the one that came to my mind)
[10:32] <didrocks> oSoMoN: if you can test those, I'm happy to +1 on the branches and we can prepare the SRU together
[10:33] <didrocks> (0-day SRU is possible and people won't see that it's not on the iso)
[10:33] <oSoMoN> didrocks, ok, I'll start another round of thorough testing right away
[10:33] <oSoMoN> I'll document what I test
[10:33] <didrocks> Thanks! If more scenarios come on your minds, do not hesitate
[10:33] <didrocks> in*
[10:41] <didrocks> Trevinho: hey, there is a regression the theme, similar to the one I fixed on the titlebar
[10:41] <didrocks> Trevinho: have a maximized app using headerbar
[10:42] <didrocks> switch between focus and backdrop mode
[10:42] <didrocks> there is a 2px shift, I guess due to your borders again
[10:42] <didrocks> (that was what I fixed a week ago, same for titlebars at the time…)
[11:04] <jibel> can anyone start a terminal in a live session with today's iso?
[11:04] <jibel> gnome-terminal
[11:09] <jibel> I get timeouts http://paste.ubuntu.com/25731598/
[11:11] <jibel> this is strange: cat /etc/locale.gen
[11:11] <jibel>  UTF-8
[11:12] <seb128> urg
[11:14] <jibel> and locale-gen works but return a bad entry for 'en_US.UTF-8 ' (with a space at the end
[11:14] <jibel> )
[11:14] <seb128> jibel, what language did you pick in the boot menu?
[11:14] <seb128> it works fine for me on yesterday's iso, let me download today's one
[11:15] <jibel> seb128, default
[11:15] <jibel> seb128, I booted directly to the lve session with 'Try ....'
[11:15] <seb128> k
[11:16] <jibel> please install xterm by default ;)
[11:17] <didrocks> I tried to donload today's one, can't even boot it despite trying 5 times to boot on boxes
[11:18] <seb128> didrocks, does it work in kvm/qemu?
[11:18] <didrocks> boot*
[11:18] <didrocks> I don't have the magic parameters for booting an iso there
[11:18] <didrocks> my previous config doesn't work
[11:18] <didrocks> do you have them?
[11:18] <seb128> kvm -m 1024 .iso
[11:18] <seb128> is what I do
[11:18] <seb128> on a stock install
[11:19] <seb128> it doesn't have proper resolution change handling etc
[11:19] <seb128> but it's enough to boot/test an issue
[11:20] <flocculant> jibel: grabbed ubuntu iso - terminal works ok for me
[11:20] <didrocks> confirming terminal not launching here
[11:22] <jibel> didrocks, it boots, you must skip the splash screen
[11:23] <jibel> fixed with latest kernel which should in theory be in next image
[11:23] <jibel> didrocks, or use cirrus or standard vga driver instead of qxl
[11:24] <jibel> seb128, againt which package should I file a bug for the locale
[11:24] <didrocks> jibel: yeah, so booted on kvm, and confirming your terminal issue
[11:24] <jibel> ?
[11:24] <jibel> didrocks, thanks
[11:24] <jibel> I'll report a bug for that too
[11:25] <seb128> jibel, good question, we might want to move that bug discussion to #ubuntu-devel, I don't see any recently changed package that could impact it
[11:26] <seb128> out of maybe livecd-rootfs
[11:26] <flocculant> jibel: is it likely to be something language/keymap related - wondering why it works ok for me
[11:27] <didrocks> flocculant: I'm using english, qwerty keyboard on that VM
[11:27] <flocculant> didrocks: ok - odd then :D
[11:27] <seb128> or systemd
[11:33] <seb128> didrocks, jibel. no such issue but I picked french on the syslinux menu by habit, trying with english noz
[11:33] <seb128> now
[11:34] <seb128> confirmed in english locale
[11:35] <didrocks> picking french works, confirmed
[11:35] <didrocks> yeah, reliably reproducible in English
[11:39] <jibel> bug 1723402
[11:39] <jibel> feel free to comment
[11:41] <jibel> when you select french there is no error when generating the locale
[11:41] <seb128> jibel, same issue on yesterday's iso
[11:42] <seb128> is that something you try to do often?
[11:42] <seb128> any idea around when it started being buggy?
[11:42] <jibel> seb128, no I don't often start a terminal in the live session
[11:42] <jibel> in english
[11:43] <jibel> and most of the time I use french when I test manually
[12:04] <willcooke> hi all. Friday!
[12:08] <didrocks> hey willcooke
[12:12] <oSoMoN> hey willcooke
[12:14] <oSoMoN> didrocks, seb128 : those are all the test cases I ran through, with results as expected
[12:14] <oSoMoN> http://paste.ubuntu.com/25731840/
[12:16] <didrocks> oSoMoN: waow, that's complete ;) the list of sessions displayed in GDM was always the one you expected I guess?
[12:16] <seb128> hey willcooke, happy friday
[12:19] <seb128> oSoMoN, the first item "log into ubuntu session, disable wayland, reboot, verify that it falls back to ubuntu" ... you mean "falls back to ubuntu-xorg"?
[12:19] <jibel> oSoMoN, can you update https://wiki.ubuntu.com/Process/Merges/TestPlans/ubuntu-session ?
[12:19] <jibel> or complete depending on the test
[12:19] <didrocks> ah, something to test if we shove that as a SRU is to ensure people doing partial upgrades aren't crashing at least
[12:20] <seb128> oSoMoN, though good, weird that sometime it doesn't indicate the selected session correctly but that's pretty minor
[12:20] <didrocks> yeah, it seems to be only in one case
[12:21] <didrocks> (from the code, the uploads can be independant and don't have side-effects)
[12:25] <didrocks> (commented and approved the code change at least, if all is ok, next step is to transform the bug in SRU, remove the extra old branch with -xorg hardcoding)
[12:26] <oSoMoN> didrocks, yeah, the list of sessions displayed was always as I expected
[12:26] <oSoMoN> seb128, no, I mean fall back to "ubuntu" indeed, because with those changes the fallback for /usr/share/wayland-sessions/ubuntu.desktop becomes /usr/share/xsessions/ubuntu.desktop
[12:27] <oSoMoN> jibel, I guess I'll wait for this to land before updating the test plane
[12:27] <oSoMoN> plan*
[12:27] <oSoMoN> didrocks, how do you test a partial upgrade?
[12:27] <didrocks> oSoMoN: just apt install <binary-package> you desired
[12:28] <didrocks> oSoMoN: but I think it's fine without testing (see my comments on the bug)
[12:28] <c-lobrano> hi all! (and happy Friday, too). I might have found a problem with ubuntu-themes revision 582
[12:28] <c-lobrano> scan-build headerbar button seems inverted
[12:28] <c-lobrano> https://usercontent.irccloud-cdn.com/file/dvJ4Jaev/inverted-button.png
[12:29] <c-lobrano> and I can't reproduce it in revision 581
[12:29] <jibel> oSoMoN, sure
[12:29] <seb128> oSoMoN, oh, right
[12:30] <seb128> hey c-lobrano
[12:30] <seb128> c-lobrano, try talking to Trevinho about it (he might be sleeping at this time though, he's in south america atm)
[12:31] <c-lobrano> hey seb128
[12:31] <c-lobrano> seb128: do you think I can leave a message here, or better try later?
[12:31] <seb128> c-lobrano, now should be fine, he might see that he go mentioned in the backlog already
[12:32] <c-lobrano> alright, thank you
[12:33] <seb128> yw, thanks for pointing it out
[12:33] <c-lobrano> so, Trevinho, could you have a look at ubuntu-themes rev 582, the picture above shows a weird scan-build button reverted
[12:33] <seb128> do you know if there is a such issue visible in any of the default installation softwares?
[12:34] <jibel> I didn't find any. It's the only app with a green drop down button I found
[12:34] <c-lobrano> seb128: afaik there isn't
[12:35] <c-lobrano> seb128: but there is a release version at version 584
[12:36] <c-lobrano> 16.10+17.10.20171012.1-0ubuntu1
[12:37]  * c-lobrano was working on LP 1721102 and couldn't figure out why on gtk inspector the fix looked good and on my patch didn't :D
[13:19] <willcooke> Trevinho, nice work on those crashers
[13:20] <willcooke> who will get them in to Ubunut?
[13:20] <willcooke> (re: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722811)
[13:20] <willcooke> will you do that Trevinho?
[13:23] <seb128> jbicha, ^ hey, can you help Trevinho to land those?
[13:27] <jbicha> Trevinho is already on weekend?
[13:27] <jbicha> just the 4 patches from https://bugzilla.gnome.org/show_bug.cgi?id=788860 ?
[13:30] <jbicha> https://git.gnome.org/browse/mutter/log?h=gnome-3-26
[13:31] <jbicha> the UI scaling and wayland-dma-buf commits look interesting too (we already have the error traps commit)
[13:33] <seb128> jbicha, he's in south america but on his own tz so likely not started his friday yet
[13:33] <jbicha> wow, he goes to all the continents :)
[13:34] <seb128> indeed
[13:36] <willcooke> if we can get those in this morning, I have lots of people here ready to test ;)
[13:36] <seb128> hehe
[13:37] <jbicha> seb128: so those 6 commits? (the 4 from the bug and the other 2 I mentioned?)
[13:37] <seb128> sounds right yes
[13:37] <seb128> jbicha, thanks
[13:38] <willcooke> thanks a lot jbicha
[13:38] <willcooke> (if indeed that was you offering to do it)
[13:39] <jbicha> yes, uploading directly to Ubuntu since Debian sync won't be available until this evening
[13:48] <willcooke> nice one, thanks jbicha
[14:17] <jbicha> mutter is in the artful unapproved queue now
[14:18] <seb128> thanks jbicha!
[14:25] <seb128> pitti, hey, do you offhand if there is/was some systemd encoding/mangling issue with %i use in unit (bug #1721839 is a side effect of that making usb printer not being correctly autoconfigured in artful because /sys entries have "x2d" instead of "-")
[14:27] <pitti> seb128: in meeting and I don't have context, but just quick pointer: maybe %I instead of %i?
[14:28] <pitti> (see man systemd.unit for the macros)
[14:30] <seb128> pitti, thanks, Till says that the printer stack side didn't change but somewhat in artful the "-" are transformed to "x2d" and xnox wrote that "The service is started, but the encoding/decoding of the %i name appears to be not round-trip safe."
[14:31] <seb128> pitti, anyway no worry, I was just asking in case it was a known issue/you would say "oh, it's fixed in trunk" or something
[14:31] <seb128> pitti, we just need to get it debugged, it's just that xnox seems too busy with other things, pre-release rush :)
[14:31] <pitti> no, I'm not aware of any recent change there; but then I haven't closely followed the recent release
[14:31] <seb128> pitti, enjoy your meeting (and then the w.e!)
[14:32] <seb128> pitti, thanks for replying!
[14:32] <seb128> pitti, oh and thanks for commenting on that shotwell bug as well
[14:32] <xnox> pitti, i don't have a proof that encoding has changed but Till did also say that using ="'%c'" vs ="%c" helped to preserve \ in the encoded strings.
[14:33] <xnox> pitti, i think it has something to do with the udev rules, units, and commands in question
[14:33] <xnox> pitti, but there is no way to umockdev record plugging printers in and out (interactive log of events) =/
[14:36] <pitti> xnox: recording uevents sounds like a nice addition :) but indeed, umockdev doesn't currently do that
[14:40] <jbicha> why does GDM apparently want to start the first session in alphabetical order?
[14:40] <seb128> xnox, does https://github.com/systemd/systemd/issues/5072 sound like similar?
[14:40] <jbicha> for instance, I installed gnome-session and after rebooting, I got logged in to GNOME
[14:40] <seb128> jbicha, you mean?
[14:41] <jbicha> https://ubuntuforums.org/showthread.php?t=2374046&page=2&p=13697457#post13697457
[14:41] <seb128> weird, there is a default session no?
[14:41] <jbicha> says he got logged in to some Kodi session after installing it
[14:44] <jbicha> I don't know if it's alphabetical but it is surprising
[14:44] <seb128> well it should select the default/previously selected session
[14:44] <jbicha> right
[14:44] <seb128> then it fallbacks alphabetically if that one is missing
[14:44] <seb128> maybe they uninstalled the ubuntu session somehow?
[14:45] <jbicha> this happened to me yesterday with a new clean install of Ubuntu (no old /home)
[14:46] <seb128> xnox, ignore that, sounds different, well I can't find an upstream report matching
[14:46] <seb128> jbicha, what session did you have on a new install? what did you get logged into?
[14:46] <jbicha> hmm, I should check again just to make sure that I didn't copy some file over
[14:47] <xnox> seb128, i believe in till's udev rules there is care taken to escape instance names, and then later use unescaped instance name.
[14:51] <seb128> jbicha, default install should only have ubuntu/ubuntu on xorg no? what did you get logged into? win10? ;-)
[14:52] <jbicha> I installed gnome-session, rebooted and got GNOME instead of Ubuntu but I'm going to try reproducing the issue to make sure it wasn't something else I did
[14:52] <seb128> k
[14:52] <seb128> thanks
[14:52] <seb128> open a bug if you can reproduce
[14:53] <seb128> oSoMoN, ^ you didn't see any behaviour like that in your testing?
[14:56] <oSoMoN> seb128, no, I didn't
[14:57] <seb128> oSoMoN, thanks
[15:23] <oSoMoN> seb128, didrocks: good news, halfline acked my patch and wants it upstream
[15:23] <willcooke> nice oSoMoN :)
[15:26] <mitya57> tkamppeter, hi! One of my friends asked me about bug 559331. It is old but apparently still happens for him and is quite annoying. Do you know if modern printing stack has any solutions for this problem?
[15:27] <mitya57> He is using ‘sed -i '/Reason media-empty-warning/d' /etc/cups/printers.conf’ as a workaround, but that is not optimal :)
[15:34] <tkamppeter> mitya57, does this message disable the printer or does the printer still print?
[15:35] <mitya57> It disables it.
[15:37] <tkamppeter> mitya57, probably the best is if you report it upstream, at http://www.cups.org/
[15:38] <mitya57> tkamppeter, ok, will do
[15:40] <didrocks> oSoMoN: nice!
[15:53] <mhall119> kenvandine: ping
[15:54] <mhall119> is https://wiki.gnome.org/UbuntuMigrationToGNOME finished or are you planning on adding more?
[15:54] <kenvandine> mhall119, i'll probably add a little more
[15:55] <kenvandine> davidcalle, are you still planning to write the scopes part?
[15:55] <mhall119> are you going to put screenshots (before and after style)?
[15:55] <jbicha> you can get a form of LIM with Tweaks > Top Bar > turn off Applications Menu then log out and log back in
[15:56] <kenvandine> mhall119, yeah
[15:57] <jbicha> probably one of the trickiest parts of GNOME 3 for new users is the Application Menu in the top bar so please mention that
[15:58] <jbicha> if someone wants file search, they'll need to install tracker and log out and log in.
[15:59] <jbicha> It can be configured with Settings > Search (click the gear button)
[15:59] <kenvandine> jbicha, would you mind adding that to the wiki page?
[15:59] <kenvandine> that's good stuff to mention
[16:00] <jbicha> uh oh, I'm getting trapped into writing docs again ;)
[16:00] <kenvandine> lol
[16:02] <mhall119> lol
[16:08] <jbicha> didrocks: are you saying that a main Depends: xterm | gnome-terminal will still try to pull xterm in to main?
[16:09] <xnox> seb128, Laney, didrocks - who can i discuss languagepacks and systemd translations with?
[16:09] <jbicha> because that's how I did the uploads so that it's easier to upstream to Debian
[16:09] <xnox> it seems they are currently broken, not sure if we care, and what is the ideal path forward to fix that?
[16:10] <jbicha> didrocks: did you want to try demoting xterm and see if component-mismatches complains ?
[16:10] <didrocks> jbicha: I think it needs to be tested if it doesn't pull it in any iso
[16:10] <didrocks> jbicha: as told on the email, I vary doing that at that time of the cycle
[16:10] <didrocks> jbicha: I would prefer doing that next cycle now
[16:11] <didrocks> it's late, I don't want potentially to break some iso builds so close to the release
[16:11] <didrocks> xnox: hum, langpacks are really seb128's special favorite :)
[16:11] <jbicha> xterm isn't on the Ubuntu 17.10 iso, it is on MATE, Kylin, Studio, Xubuntu
[16:12] <didrocks> jbicha: ok, so no iso with Main enabled only?
[16:12] <xnox> didrocks, i think journal catalogs is the bulk of systemd translations, and they are in their own special format (naturally) thus i guess i need to somehow ship them all, and then disect that into langpacks.
[16:12] <didrocks> unsure still if we should do that now, I don't really see any benefit than waiting for a week
[16:13] <jbicha> didrocks: right, there should only be one desktop Main iso :)
[16:13] <xnox> didrocks, maybe a custom tarball/byproduct, generated by the lang-pack extractor.
[16:13] <didrocks> xnox: yeah, I didn't look for some years at the whole launchpad import machinery/extractions, so I wouldn't be a good advisor TBH :)
[16:13] <didrocks> nice that they have their own special format… humf
[16:14] <jbicha> didrocks: the benefit is we can have ubuntu-release-upgrader mark xterm as obsolete if it's not in main any more (I believe) so it makes the Activities Overview cleaner for upgraders
[16:14] <didrocks> what is translated in systemd? the journal catalogs
[16:14] <didrocks> jbicha: which can happen during 17.10 -> 18.04 update as well, no?
[16:14] <jbicha> I've been fighting with xterm for 6 years so what's a little bit longer? ;)
[16:15] <didrocks> yes! :)
[16:15] <didrocks> jbicha: seeing the number of time it has been promoted and demoted, I would stay on the cautious side
[16:16] <seb128> oSoMoN, of, nice for gdm, well done ;-)
[16:17] <seb128> xnox, I plan to comment on that systemd bug, just got busy today
[16:17] <jbicha> willcooke: mutter just landed in artful so maybe an hour or so for it to show up on mirrors? https://launchpad.net/ubuntu/+source/mutter/3.26.1-2ubuntu1
[16:22] <jbicha> didrocks: btw, Debian managed to get gjs/mozjs52 to build on s390x https://buildd.debian.org/status/package.php?p=gjs&suite=experimental
[16:22] <didrocks> hum, do we want to reintroduce desktop on s390x for next cycle? We'll see :p
[16:22] <xnox> didrocks, no
[16:22] <xnox> didrocks, no
[16:23] <xnox> didrocks, no
[16:23] <jbicha> well we'll get the packages back for free
[16:24] <jbicha> we don't have to build 'ubuntu-desktop' for s390x if we don't want to, but I don't think having a gnome-shell package that no one uses would hurt?
[16:24] <didrocks> and next cycle, we'll have breakage agian
[16:24] <didrocks> it's going to block on migration
[16:25] <didrocks> we'll have to spend time removing them again
[16:25] <didrocks> so not really "for free"
[16:25] <jbicha> we're sticking with mozjs52 for 18.04
[16:25] <xnox> whatever is the least maintainance.
[16:25] <jbicha> at least for 18.04's initial release
[16:27] <jbicha> Mozilla introduced a big-endian regression that Debian's Firefox package untangled so we could probably get firefox/s390x back too
[16:27] <xnox> jbicha, last time we had it built, it would fail to start to the point of drawing the main window =/
[16:35]  * oSoMoN EOW
[16:35] <oSoMoN> have a good week-end everyone
[17:31] <kenvandine> jdstrand, i have a question about dbus names
[17:31] <kenvandine> 2017-10-13T13:19:42-04:00 INFO snap "gnome-2048" has bad plugs or slots: gnome-2048 (DBus bus name must not end with -NUMBER)
[17:31] <kenvandine> gnome-2048 registers org.gnome.gnome-2048
[17:47] <willcooke> jbicha, Trevinho - initial report is that the problem is fixed!  Thanks a lot
[17:52] <jdstrand> kenvandine: I did this for a reason. gimme a sec
[17:54] <jdstrand> ah right
[17:55] <tkamppeter> Any one has an idea what to do with bug 1723197: There a crash in cups-browsed is reported and the threaded stack trace does not touch any line of the cups-browsed code.
[17:56] <jdstrand> kenvandine: https://github.com/snapcore/snapd/blob/master/interfaces/builtin/dbus.go#L237
[17:56] <kenvandine> jdstrand, ah
[17:57] <jdstrand> kenvandine: and https://github.com/snapcore/snapd/blob/master/interfaces/builtin/dbus.go#L178
[17:57] <jdstrand> it's kde
[17:57] <Trevinho> willcooke: :)
[17:57] <Trevinho> willcooke: I was able to reproduce it eventually, and so I did some refactoring
[17:58] <jdstrand> kenvandine: with kde, they do org.kde.foo-$pid
[17:58] <Trevinho> jbicha: thanks for the patch
[17:59] <jdstrand> as a result, I could request a snap with org.gnome.gnome, then claim org.gnome.org-2048 and break you
[17:59] <kenvandine> jdstrand, in this case it's the gapplication registration, the name is actually org.gnome.gnome-2048
[17:59] <kenvandine> yeah
[17:59] <jdstrand> no, I understand
[18:00] <sarnold> tkamppeter: dmesg looks unhappy -- maybe suggest a reboot followed by fsck?
[18:05] <tkamppeter> sarnold, done, thank you.
[18:12] <Trevinho> jbicha: for having the complete crash fixes (well at this point it would just be a warning), can you also backport to g-s https://git.gnome.org/browse/gnome-shell/commit/?h=gnome-3-26&id=5f8a5114833d7d31d4bd64affbd323bb7252c3d0 ?
[18:28] <willcooke> jibel, is a suspend resume cycle part of our testing?  Hard to do in a vm I expect.
[18:52] <jbicha> Trevinho: if it's just a warning, shouldn't we just wait for 3.26.2?
[18:54] <c-lobrano> Hi Trevinho, I was wondering if you've seen my message about ubuntu-themes, since I sent it when you were not connected
[19:58] <Trevinho>  c-lobrano: nope...
[19:58] <Trevinho> jbicha: well.. It could still cause some problems in allocation. So better to land it
[19:59] <jbicha> Trevinho: could you file a LP bug for it then for queue tracking?
[20:00] <Trevinho> jbicha: I think there's already let me check
[20:03] <Trevinho> jbicha: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1717170
[20:08] <c-lobrano> Trevinho: ubuntu-themes revision 582 seems having inverted simple-scanner's button. I can't reproduce this behavior on 581
[20:08] <c-lobrano> ^ https://usercontent.irccloud-cdn.com/file/dvJ4Jaev/inverted-button.png
[20:37] <dmj_s76> https://bugzilla.gnome.org/show_bug.cgi?id=788901
[20:37] <dmj_s76> Can we get this patch into the artful mutter package.
[20:39] <dmj_s76> It fixes a regression between zesty and artful that prevents users (especially on nvidia) from using their hidpi laptop display with an external monitor plugged in.
[20:43] <jbicha> dmj_s76: it's not been pushed upstream yet. Could you ask again Monday morning when more people are around?
[20:43] <dmj_s76> jbicha: sure
[20:44] <jbicha> because we are in Final Freeze, one answer might be to do it as a zero-day SRU (in other words, it will be available in -updates on release day instead of on the official Ubuntu ISO)
[20:44] <dmj_s76> jbicha: That would work for us.
[20:45] <dmj_s76> It's needed for use so we can automatically handle hidpi multimonitor configuration like we do on Unity.
[20:47] <jbicha> are you using an extra tool for that in 17.10?
[20:49] <dmj_s76> jbicha: So, this patch fixes issues for mutter's monitor config that impact gnome control center in ugly ways too...
[20:50] <jbicha> did you see the mutter update earlier today in artful?
[20:50] <dmj_s76> jbicha: It also fixes issue that block us from shipping a tool with our system76 driver in 17.10 that we've been shipping on 16.04 and 17.04.
[20:51] <jbicha> if you'd reached me 20 minutes sooner, I might have pushed it in a Debian mutter upload I just did
[20:51] <dmj_s76> jbicha: ah darn!
[20:56] <dmj_s76> Right now our tool is fairly specialized to system76 hardware, but once I finish porting to gnome, I'm hoping to find a sane way to generalize it.
[23:17] <Trevinho> c-lobrano: ouch, yeah.. also the cancel button seems not to be the best (you can enable it with the inspector, setting it visible)... If you have some time to check why, it would be cool :)
[23:18] <Trevinho> c-lobrano: I guess borders are wrong since we override them, but not doing it properly for inline buttons when it's :first-child or :last-child
[23:19] <Trevinho> c-lobrano: otherwise assign me a bug
[23:19] <Trevinho> but I can't do it too quickly, thanks for spotting it though
[23:20] <Trevinho> in that scenario also distructive action seems not to be correct (if you enable the cancel button from the inspector, again, or you actualy start scanning :)
[23:20] <Trevinho> enable = set the visibile property to TRUE