[05:53] <oSoMoN> good morning desktoppers
[06:00] <duflu> Morning oSoMoN
[06:05] <oSoMoN> hey duflu
[06:36] <didrocks> good morning
[06:46] <jibel> morning
[06:46] <didrocks> salut jibel
[06:47] <jibel> salut didrocks , ça va ?
[07:03]  * duflu returns and then leaves again to put on work clothes and fix 3 holes in the roof :P
[07:03] <duflu> Without rain I would never know
[07:19] <flocculant> without rain - you could leave it till another day :)
[07:19] <didrocks> jibel: ça va bien, et toi ?
[07:20] <flocculant> morning didrocks :)
[07:20] <jibel> didrocks, ça va bien. trying to find a release critical bug ;)
[07:20] <jibel> didrocks, then holidays next week before moving to a new house
[07:20] <didrocks> hey flocculant
[07:21] <didrocks> jibel: there is maybe this ATI one for you ;)
[07:21] <didrocks> jibel: sounds nice! and good luck ;)
[07:21] <jibel> terminal doesn't start in a live session on an uefi syste
[07:21] <jibel> m
[07:21] <jibel> same problem with the locale it seems
[07:21] <didrocks> yeah, probably
[07:22] <didrocks> I'm going to do a full reinstall on my main machine with current iso (but probably tomorrow morning)
[07:22] <didrocks> didn't reinstall since… 2011!
[07:22] <didrocks> cleaning up and migrating my home dir
[07:22] <jibel> my main machine has been installed in 2010 and upgraded since then
[07:23] <didrocks> even more hardcore :)
[07:23] <didrocks> mine is 2011 due to laptop refresh :p
[07:23] <jibel> why would you need to reinstall ?
[07:23] <didrocks> it's more an excuse to clean up most of my -dev packages and other tools installed
[07:24] <jibel> I run deborphan and deborphan -a from time to time to clean up stuff that accumulated over time
[07:24] <jibel> dpigs is also useful to free some space
[07:24] <flocculant> jibel: I regularly reinstall as I'm awesome at killing xubuntu with the dev ppa's we use :D
[07:25] <didrocks> oh, I don't know about dpigs
[07:25]  * didrocks looks
[07:33] <jibel> bug 1724153
[07:36] <jibel> didrocks, what's the bug # for the issue with ATI?
[07:38] <didrocks> jibel: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577
[07:38] <didrocks> I think amano's one is different (he has nvidia), and is due to the kernel
[07:39] <didrocks> at least 2 persons though confirms it so far
[07:40] <didrocks> duflu: I see you suggested the same packages than I did there (directly on the french forum, as both persons impacted are there). Looking at the upgrade list, I'm a little bit out of ideas
[07:41] <jibel> there is bug 1723619 too
[07:41] <didrocks> I aksed for the gdm logs in debug mode
[07:41] <didrocks> yeah, I guess that's amano's one
[07:41] <jibel> okay
[07:41] <didrocks> on the ATI bug it worked until the 5-7th October
[07:42] <didrocks> so, there is hope :)
[07:42] <didrocks> we should write some revert program taking a date in /var/log/apt/history.log and reverting all upgraded package that day
[07:43] <seb128> good morning desktopers
[07:43] <didrocks> (also, enabling rollbacking from a source package, with a particular version)
[07:43] <didrocks> I might do it next cycle, would be easier for contributors/debug situations like this
[07:43] <didrocks> hey seb128
[07:43] <seb128> jibel, could be that the uefi issue is fixed by https://launchpad.net/ubuntu/+source/casper/1.387 ?
[07:43] <seb128> just random guess, I saw that upload
[07:43] <seb128> but it has no bug reference
[07:45] <jibel> seb128, yes it should be. Respin is imminent
[07:46] <seb128> I read that on #u-r, good
[08:01] <Laney> ahoy
[08:02] <didrocks> hey Laney
[08:03] <seb128> hey Laney, how are you?
[08:04] <willcooke> morning all
[08:04] <seb128> hey willcooke
[08:06] <Laney> hey didrocks seb128 willcooke
[08:06] <didrocks> hey willcooke
[08:06] <Laney> what's up?
[08:06]  * Laney is good, nice climbing last night \m/
[08:07] <didrocks> nothing special, still mostly baby-caring time as another full time job :p (especially now that he doesn't want to do his last nap :p)
[08:08] <willcooke> didrocks, ahha!
[08:08] <willcooke> didrocks, so it begins
[08:10] <didrocks> it does!
[08:12] <seb128> begins?!
[08:15] <willcooke> First two naps, then one nap, then no nap, then they never. shut. the. hell. up.
[08:16] <didrocks> is there still a probation period, can you send him back? :)
[08:16] <jibel> pre-teens never. shut. the. hell. up. either ....
[08:19]  * Laney nelson laugh
[08:33] <duflu> didrocks, better to ask twice than not at all I guess.
[08:33] <duflu> Hey, good news: I didn't kill myself when replacing roof tiles
[08:37] <willcooke> glad to hear it duflu :))
[08:38] <duflu> Ha. "Very high (near 100%) chance of showers with gusty winds in the evening."
[09:31] <andyrock> hey all
[09:31] <didrocks> hey andyrock
[09:31] <willcooke> morning andyrock
[09:34] <duflu> Hi andyrock
[09:56] <duflu> willcooke, if I propose a patch to mutter today does that count as SRU yet?
[09:56] <duflu> Hopefully not
[09:57] <willcooke> Final freeze is in the past, so it might be.  seb128 or Laney will know for sure
[09:58] <jbicha> duflu: yes, it will likely be an SRU (possibly zero-day) unless it gets uploaded immediately (there will be a [final?] respin soon)
[09:58] <duflu> jbicha, gimme 60 seconds
[09:59] <willcooke> morning jbicha
[09:59] <duflu> jbicha, patch in the upstream bug link - https://bugs.launchpad.net/gnome-shell/+bug/1724185
[09:59] <didrocks> the respin will be started soon (waiting on some packages to publish), apart if there is another one, it will be a SRU
[10:00] <didrocks> maybe you can bribe infinity
[10:00] <didrocks> if the fixes are easy enough and warrant the wait for a respin
[10:00] <jbicha> duflu: I don't see a patch?
[10:00] <duflu> jbicha, it's the raw attachment inhttps://bugzilla.gnome.org/show_bug.cgi?id=789086
[10:01] <jbicha> oh there's 2 GNOME bugs for that LP bug
[10:02] <duflu> jbicha, ok attached in LP
[10:05] <Laney> not sure you should rush this in (seem Jonas's comment)
[10:06] <jibel> why do you want it in the image? 0d SRU should be fine
[10:08] <jbicha> Laney: where do you see Jonas' comment?
[10:08] <didrocks> (on the upstream bug)
[10:08] <duflu> Laney, yeah needs more work.
[10:09] <duflu> But the top gnome-shell crasher was worth pushing for
[10:09] <jbicha> duflu: ok, let's wait for that
[10:09] <jbicha> (Jonas' comment wasn't there a few minutes ago ;) )
[10:10] <jbicha> (let's wait  = let's not rush to get this patch in now)
[10:10] <Laney> sure
[10:10] <Laney> but if it wasn't I would have gone and asked him for an opinion :-)
[10:10] <duflu> Yeah. Sad we don't have any clues yet - https://errors.ubuntu.com/?package=xwayland&period=year
[10:23] <jbicha> seb128: for resizable tiling you need 2 things: mutter and gtk. There's enough mutter commits that reverting all of them doesn't make sense
[10:23] <jbicha> see the Florian and Georges commits just before 3.26.1 https://git.gnome.org/browse/mutter/log?h=gnome-3-26
[10:24] <jbicha> you're right that the feature hasn't gotten much Ubuntu testing because gtk3 was stuck in artful-proposed :|
[10:30] <duflu> jbicha, I noticed that. I have a gtk proposal behind yours
[10:31] <jbicha> duflu: the update got stuck because of LP: #1721828
[10:31] <duflu> jbicha, it's OK. My gtk proposal is less important than many other things
[11:36] <seb128> jbicha, was->is, gtk is still stucked in proposed and it looks like it's not going to migrate for release
[11:51] <duflu> OK, new mutter patch provided upstream. I need to run
[11:52] <duflu> (no, we don't need it this week)
[12:41] <willcooke> Can someone confirm this:  Go to control centre, search "users", click on it, long delay, finally opens?  Same with browsing Details -> Users there is a delay before the panel opens
[12:44] <jibel> willcooke, what do you mean by "long delay" ?
[12:44] <willcooke> ~ 5 seconds or so
[12:44] <jibel> it's slower than other panel but not so much
[12:44] <jibel> more like half a second here
[12:44] <willcooke> it's about 7 seconds here
[12:44] <willcooke> might just be me
[12:44] <willcooke> can someone else check when they get a mo please
[12:46] <andyrock> it's slower
[12:46] <andyrock> not 7 seconds
[12:46] <andyrock> but feels like a bug
[12:46] <jibel> willcooke, same result on another machine, it is not what I would call slow
[12:46] <willcooke> kk, must be me then
[12:47] <willcooke> :)
[12:47] <willcooke> thanks jibel andyrock
[12:47] <andyrock> maybe it depends on the number of users
[12:47] <willcooke> Dont think so, since I first saw it when I was trying to add a new user
[12:47] <willcooke> and it's the same now with 2 as it was with 1
[12:47] <andyrock> there must me some sync operation
[12:48] <seb128> willcooke, it's a known issue, was discussed at GUADEC by some of the fedora people, it's the new panel doing too much sync work on init
[12:49] <willcooke> ah, ok!  thanks seb128
[12:49] <willcooke> I'll add a known issue to the release notes then
[12:50] <seb128> could people install gtk from proposed and give it a try?
[12:51] <willcooke> doing now
[12:51] <seb128> it's being pondered to move out of proposed to the iso
[12:51] <seb128> thanks
[12:51] <willcooke> seb128, anything I should look for
[12:51] <willcooke> ?
[12:51] <seb128> no, just if you find anything weird/buggy with it
[12:52] <willcooke> ack
[13:05] <seb128> willcooke, do you have an external webcam connected? is it less slow without it?
[13:05] <willcooke> seb128, only the built in one
[13:05] <seb128> k
[13:05] <seb128> I was looking for open upstream bugs
[13:06] <seb128> willcooke, but basically https://bugzilla.gnome.org/show_bug.cgi?id=783789
[13:07] <seb128> which got marked as a duplicate of a cheese bug https://bugzilla.gnome.org/show_bug.cgi?id=782627
[13:07] <seb128> is cheese slow to start for you?
[13:08] <seb128> shrug, why is cheese listed twice in the dash?
[13:08] <willcooke> interesting, yes it does
[13:08] <willcooke> very slow
[13:08] <willcooke> seb128, do you have the snap installed as well?
[13:08] <seb128> k, good, so it's probably the same issue
[13:09] <seb128> willcooke, lol, I do, good thinking :)
[13:09] <willcooke> :)
[13:09] <seb128> I installed it during the rally to help Ken to debug it
[13:09] <seb128> kenvandine, btw did you ever manage to work on that/figure it out?
[13:11] <kenvandine> seb128, no, i haven't gone back to it yet
[13:12] <seb128> k, I might still have a look then :p
[13:13] <seb128> willcooke, Laney, jbicha, new gtk seems to work fine for me
[13:13] <willcooke> seb128, yeah, nothing bad happened here yet
[14:21] <didrocks> after trying some reboots (in vms only, didn't want to restart my session), I confirm that I didn't spot anything after 30 minutes of testing and various apps
[14:21] <didrocks> (with new gtk)
[14:22] <seb128> didrocks, thanks for testing/confirming
[14:22] <seb128> we should have forced migration that one some days ago :-/
[14:23] <didrocks> agreed
[14:23] <didrocks> or use the french community to test it at the same time
[14:23] <didrocks> speaking of which… let's ask them
[14:24] <Laney> It wasn't clear that it was not a GTK bug
[14:24] <Laney> I don't agree that we should have forced it
[14:24] <Laney> (or I would have argued for that and then probably done it)
[14:26] <seb128> well either wait we should have ignored it stucked in proposed for so long, it feels like we ended up having to make a bad call late
[14:26] <seb128> either reject or land without margin to get feedback about issues
[14:26] <Laney> I did not ignore it
[14:26] <seb128> should *not*
[14:26] <Laney> I was working on that bug for days
[14:26] <seb128> I don't say you did
[14:26] <seb128> but we delayed taking a decision too long imho
[14:26] <Laney> ok, I disagree with you but no need to argue there
[14:27] <seb128> we should as a team have discussion ours options when it was becoming late
[14:27] <seb128> discussed
[14:27] <seb128> k, fair
[14:28] <seb128> I just don't like to land it that late, unsure how we could have avoided that though
[14:30] <willcooke> Meeting time
[14:30] <jbicha> o/
[14:30] <kenvandine> \o
[14:31] <andyrock> o/
[14:31] <willcooke> Roll call:  andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)
[14:31] <seb128> o/
[14:31] <oSoMoN> o/
[14:31] <heber> o/
[14:31] <didrocks> hey!
[14:31] <jibel> hi
[14:31] <willcooke> Looks like we have enough people to get started.
[14:32] <willcooke> #topic andyrock
[14:32] <andyrock> hey
[14:32] <andyrock> 1. Spotting apport issues
[14:32] <andyrock> 2. Some work on livepatch dekstop integratation
[14:32] <andyrock> 3. Working on this: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723301 (I have a possible fix but not a way to reproduce this, so upstream asked me to try a way to reproduce this)
[14:32] <andyrock> 4. Working on this: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720400 (found a way to reproduce, trying to fix it)
[14:32] <andyrock> eow
[14:32] <willcooke> Thanks andyrock
[14:33] <willcooke> any other bugs assigned for release andyrock?
[14:33] <andyrock> nope
[14:33] <willcooke> cool,
[14:33] <willcooke> thanks
[14:33] <andyrock> I'm trying to fix some crashes around
[14:33] <andyrock> but nothing blocking
[14:33] <willcooke> great
[14:33] <willcooke> #topic dgadomski
[14:33] <dgadomski> hey
[14:33] <dgadomski> only 1 thing in desktop area: I was able to reproduce bug #1718688 with hostapd, checking wpasupplicant source code to fix it
[14:33] <dgadomski> eof
[14:33] <willcooke> thanks dgadomski
[14:34] <willcooke> #topic didrocks
[14:34] <didrocks> * Settings: fix background selection color and only apply the theme change to our ones.
[14:34] <didrocks> * Update to 3.26.1 & fix gnome-session migration for people running rhythmbox. Fix later a crasher for people not having it installed! Also make the "on Xorg" part translatable.
[14:34] <didrocks> * More Marco's theme reviews and discussion. Sponsored his work.
[14:34] <didrocks> * Cherry-pick fix for focus on GNOME Shell.
[14:34] <didrocks> * Tried to debug gdm for second user selection, found the regression, but a proper fix is complex and needs more digging
[14:34] <didrocks> * Review & discuss gdm fix for fallback session with Olivier
[14:34] <didrocks> * More community interactions on our hub
[14:34] <didrocks> * Worked with the french community (currently in progress) to debug https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577
[14:34] <didrocks> * Did some VM iso testing will do a real install tomorrow.
[14:34] <didrocks> * Write a blog post for the past week changes: https://didrocks.fr/2017/10/16/ubuntu-gnome-shell-in-artful-day-15/
[14:34] <didrocks> * Discussed with IS and p_opey, about discourse integration, which worked, didn't work and worked for a few hours without doing anything. Filed a RT now to get that properly tracked. Fallbacked to manual link posted (which probably refrain from getting comments).
[14:34] <didrocks> No RC bug assigned to me remaining
[14:34] <didrocks> .
[14:34] <willcooke> thanks didrocks
[14:34] <willcooke> seems I forgot to start the meeting properly.
[14:34] <willcooke> never mind
[14:34] <willcooke> #topic duflu
[14:35] <willcooke> * Totem CPU usage (https://bugs.launchpad.net/bugs/1698282)
[14:35] <willcooke>   - RELEASED the main totem CPU fix (to Debian actually): https://launchpad.net/ubuntu/+source/clutter-gtk/1.8.4-2
[14:35] <willcooke>   - The patch is also upstream awaiting review still.
[14:35] <willcooke>   - Re-profiled totem/gst-play-1.0 and provided status updates in: https://bugs.launchpad.net/bugs/1698282
[14:35] <willcooke>   - Temporarily finished this task? AFAIK the only remaining improvement is DMAbuf support which upstream has in progress already. Perhaps I will context switch away from this for a while and only step in again later if they haven't made progress on DMA-buf...
[14:35] <willcooke> * Totem stuttering (https://bugs.launchpad.net/bugs/1698270)
[14:35] <willcooke>   - Spent more hours retesting and trying to improve the GDK smoothness fix: https://code.launchpad.net/~vanvugt/gtk/fix-1698270/+merge/331846 (needs sponsorship)
[14:35] <willcooke>   - The good news is the above fix still works well in totem, gnome-maps and gdkgears. And seemingly can't be improved.
[14:35] <willcooke>   - Spent more hours analysing the clutter code again to see if another fix needs to go in there too. Probably not, so long as the GDK fix lands.
[14:35] <willcooke>   - Spent more hours trying to identify why totem and only totem stutters badly on disk IO, in one place (yet other gstreamer apps don't). SUCCESS: https://bugzilla.gnome.org/show_bug.cgi?id=788926 (although it now seems upstream has known about it since 2014 and the old bug report just wasn't adequately worded to notice :/)
[14:35] <willcooke>   - WORK IN PROGRESS on a final fix for totem/totem-pl-parser.
[14:35] <willcooke> * Appearance (https://trello.com/c/YgueNEZA/260-bug1714459-shell-panel-font-is-blurry-under-wayland)
[14:35] <willcooke>   - Iterated my fix for shell font rendering options a couple of times and proposed upstream again: https://bugzilla.gnome.org/show_bug.cgi?id=645433
[14:35] <willcooke> * Daily bug management across gnome-shell, mutter, gdm3, ubuntu-themes, bluez, pulseaudio, dkms and mir.
[14:35] <willcooke> (going to keep using the # commands so that I can parse the logs)
[14:35] <willcooke> #topic jbicha
[14:36] <jbicha> • robert_ancell's file-roller squashfs/snap patch is now upstream (after I poked the maintainer) https://bugzilla.gnome.org/662519
[14:36] <jbicha> • smcv got mozjs52 to build on s390x in Debian so I uploaded gnome-shell and friends to Debian unstable
[14:36] <jbicha> • Fixed and pushed upstream LP: #1723266
[14:36] <jbicha> • Disabled the non-working Actions for LP: #1720262
[14:36] <jbicha> • Rebased our patches to re-enable GNOME Builder's Terminal LP: #1722953
[14:36] <jbicha> • Sponsoring some mutter cherry-picked patches to artful
[14:36] <jbicha> • (no remaining rc bugs here) eof
[14:36] <willcooke> thanks jbicha
[14:36] <willcooke> #topic jamesh
[14:37] <willcooke> No update this week.
[14:37] <willcooke> :(
[14:37] <willcooke> #topic jibel / heber
[14:37] <heber> hey
[14:37] <heber> QA updates:
[14:37] <heber> * Wrote multi-monitor test cases
[14:37] <heber> * Release candidates testing (new image coming soon)
[14:37] <heber> * Daily bug triaging
[14:37] <heber> * See ubiquity and upgrade jobs that are failing
[14:37] <heber> * Add snap helpers to ubuntu-system-tests
[14:37] <heber> * Continue with gnome-shell test runner
[14:37] <heber> EOF
[14:37] <willcooke> thanks heber
[14:37] <jibel> just a note about the release
[14:37] <willcooke> #topic kenvandine
[14:37] <jibel> we are waiting for a new image to fix bug 1724224
[14:37] <willcooke> oops carry on jibel
[14:38] <jibel> and new translation for kylin
[14:38] <jibel> done
[14:38] <kenvandine> * Worked on the GNOME SDK build snap, still missing quite a bit of stuff but it builds with glib, gtk, vala, and some other basics now.
[14:38] <kenvandine> * Remmina fixes have been merged upstream and in the edge channel of the store
[14:38] <kenvandine> * Added a couple new GNOME snaps
[14:38] <kenvandine> * Doing some cross distro snap testing in preparation for a blog post on running the latest GNOME apps as snaps
[14:38] <kenvandine> * No RC bugs assigned
[14:38] <willcooke> thanks jibel
[14:38] <kenvandine> found our snaps don't work on fedora :(
[14:38] <kenvandine> because of /snap not being used
[14:38] <kenvandine> popey is going to escalate that issue
[14:38] <seb128> haha
[14:38] <willcooke> thanks kenvandine
[14:38] <kenvandine> works great on debian and mint though :)
[14:38] <seb128> "told you if would be an issue"
[14:39] <willcooke> great news on remmina too
[14:39] <kenvandine> seb128, yup :)
[14:39] <kenvandine> eof
[14:39] <willcooke> #topic Laney
[14:39] <Laney> • Went back to NYC
[14:39] <Laney> • Had a few meetings and 18.04 plan discussions, saw the plans of other teams
[14:39] <Laney> • Helped identify apport being broken, thanks Brian for fixing that
[14:39] <Laney> • Looked at gnome-software shell extensions category view being empty
[14:39] <Laney> • Spent a long long time looking into LP: #1721828, eventually fixed in the software-properties testsuite (that was my rls-aa-tracking bug)
[14:39] <Laney> • A lot of queue reviews
[14:39] <Laney> 🚏
[14:40] <willcooke> thanks Laney
[14:40] <willcooke> #topic oSoMoN
[14:40] <oSoMoN> hey
[14:40] <oSoMoN> • approved https://code.launchpad.net/~gunnarhj/gdm/language-switching/+merge/331980
[14:40] <oSoMoN> • continued discussing bug #1718446 and proposed a patch that got accepted upstream, now preparing a SRU to land it asap after release
[14:40] <oSoMoN> • managed to get chromium 62 (current beta, to become stable this week) to build on trusty amd64 and i386 with a backported clang 4.0 and a rather manageable distro patch, looking into armhf failure (linker OOM it seems)
[14:40] <oSoMoN> • updating chromium dev to 63.0.3236.7
[14:40] <oSoMoN> • some progress on bug #1697641, a11y was working in chromium at some point in the not too distant past, but it regressed − even then, OSK was not working so some more work will be required
[14:40] <oSoMoN> • gotta prepare libreoffice 5.4.2 SRU as I didn't have time for it before final freeze
[14:40] <oSoMoN> EOF
[14:41] <willcooke> thanks oSoMoN
[14:41] <didrocks> oSoMoN: can we try to get the fix in proposed tomorrow?
[14:41] <oSoMoN> didrocks, yes, on it
[14:41] <didrocks> oSoMoN: so that we release it in -updates quickly after the release
[14:41] <didrocks> as it's for upgrades
[14:41] <didrocks> great!
[14:41] <didrocks> thanks :)
[14:41] <willcooke> #topic seb128
[14:41] <seb128> - daily review of recent artful bugs and e.u.c reports
[14:41] <seb128> - some iso testing
[14:41] <seb128> - restored a part of the g-s-d patch dropped to fix the suspend on login issue (schemas still needed by u-s-d)
[14:41] <seb128> - discussed dh_translations vs meson a bit with Didier
[14:41] <seb128> - debugged/fixes outdated translations in launchpad on some projects due to translations sharing
[14:41] <seb128> - backported a libimobiledevice ios11 fix
[14:41] <seb128> - workarounded for duplicate items in the notifications panel in g-c-c
[14:41] <seb128> - debugged apport not starting with andyrock
[14:41] <seb128> - wrote an uncomplete patch for orca not starting in ubiquity describing the issue and how a fix could work, hopefully somebody from the ubiquity team pick up from there
[14:41] <seb128> - did another g-s-d regression fix, thanks to a contributor who pointed the merge error

[14:41] <willcooke> thanks seb128
[14:42] <willcooke> #topic tkamppeter
[14:42] <tkamppeter> - UDEV/systemd: Further testing on the problem with the USB printer auto setup not working. Reported bug to systemd upstream but no answer yet.
[14:42] <tkamppeter> - ippusbxd: Updated documentation upstream (readme.md).
[14:42] <tkamppeter> - avahi: Rithvik already started studying the localhost support problem for IPP-over-USB.
[14:42] <tkamppeter> - Bugs.
[14:42] <willcooke> thanks tkamppeter
[14:42] <willcooke> #topic Trevinho
[14:42] <willcooke> · Further fixes in the suggested-action button
[14:42] <willcooke> · Improvements to the inverted gradient on maximized windows
[14:42] <willcooke> · Lots of debugging in mutter and GS crashes
[14:42] <willcooke>   (https://bugzilla.gnome.org/show_bug.cgi?id=786557,
[14:42] <willcooke>    https://bugzilla.gnome.org/show_bug.cgi?id=782385,
[14:42] <willcooke>    https://bugzilla.gnome.org/show_bug.cgi?id=788971)
[14:43] <willcooke> · Some refactoring in mutter MetaScreen in order to fix a major crash
[14:43] <willcooke>   (https://bugzilla.gnome.org/show_bug.cgi?id=788860)
[14:43] <willcooke> · Looking into a way to get better JS dumps on GS crashes (seems to work)
[14:43] <willcooke> · Currently debugging https://bugzilla.gnome.org/show_bug.cgi?id=788627
[14:43] <tkamppeter> And good news for a11y: Large mouse cursor is finally working (using gdm as greeter) congrats to who fixed it.
[14:43] <willcooke> which
[14:43] <willcooke>   I can reproduce (or similar
[14:43] <willcooke> https://bugzilla.gnome.org/show_bug.cgi?id=788908)
[14:43] <willcooke> #topic robert_ancell
[14:43] <willcooke> - Fix RC critical crash in gnome-software (LP: #1723312)
[14:43] <willcooke> - Fix async operation cancelling not working in snapd-glib
[14:43] <willcooke> - snapd-glib refactoring
[14:43] <willcooke> - simple-scan 3.27.1 releas
[14:43] <willcooke> #topic APB
[14:44] <willcooke> Anyone got anything?
[14:44] <tkamppeter> And good news for a11y: Large mouse cursor is finally working (using gdm as greeter) congrats to who fixed it.
[14:44] <willcooke> ah, nice!  Good spot tkamppeter, and thanks to whoever fixed it
[14:44] <seb128> tkamppeter, nice
[14:44] <jbicha> willcooke: did we want to discuss some bugs from http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-aa-incoming-bug-tasks.html ?
[14:44] <willcooke> Yeah, lets take a look:
[14:45] <willcooke> https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1713313
[14:45] <tkamppeter> I have some vision problem and over the 20 years I used Unix/Linux the mouse cursor was always too small and never a way to get it bigger.
[14:45] <willcooke> I dont think there is much we can do about that bug for release is there?
[14:45] <jbicha> tkamppeter: :)
[14:46] <didrocks> I don't think we can, apart from the xhost arg, but I think it's a little bit counter-productive
[14:46] <jbicha> 1713313 is already release-noted
[14:46] <willcooke> ack
[14:46] <seb128> right, -notfixing imho
[14:46] <didrocks> and then, we can take that into account for the LTS plan
[14:47] <jbicha> maybe there's a way in 18.04 we could notify the user *why* the pkexec app doesn't work at the time it's attempted
[14:47] <willcooke> +1, what's the correct tag? rls-aa-notfixing - or is there something more desktop team specific we can use?
[14:47] <willcooke> +1 was at notfixing
[14:47] <didrocks> jbicha: for those using pkexec, but doesn't work for the traditional "sudo nautilus" that people do
[14:47] <seb128> I think that's the correct one
[14:48] <willcooke> k, next..
[14:48] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gst-plugins-ugly1.0/+bug/1723599
[14:48] <seb128> that's just a bug, nothing important for the release
[14:48] <seb128> Laney, ^ you might know where to reassign/what component might get it wrong?
[14:49] <willcooke> https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1720331  is already assigned to jamesh
[14:49] <seb128> is that still using the Gstreamer-Decoders info from the package description?
[14:50] <seb128> willcooke, that one is probably -notfixing since jamesh fixed the issue in whoopsie, the control center side is nice to land but not an important issue at this point
[14:50] <willcooke> yeah
[14:50] <willcooke> https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1717009
[14:50] <willcooke> fixed upstream
[14:50] <Laney> dunno
[14:50] <Laney> would have to dig
[14:50] <willcooke> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707898
[14:51] <willcooke> we're being pinged on that one by x_nox
[14:51] <seb128> willcooke, the fwupd is foundations and has been fixed upstream
[14:51] <seb128> right, I've the systemd one in a tab, I'm going to comment after the meeting
[14:51] <willcooke> thx
[14:52] <willcooke> https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1710377
[14:52] <willcooke> seb128 has already updated
[14:52] <seb128> Laney, k, well you did the switch to g-s for codecs install so you might have an idea where to look, if you want to do that when there is a more quiet time post release that would be nice
[14:52] <seb128> willcooke, right
[14:52] <Laney> ok
[14:52] <seb128> thx
[14:52] <jbicha> the Additional Drivers bug is won't fix for artful, right?
[14:52] <Laney> feel free to assign me
[14:52] <willcooke> k, I think that's the end of the list
[14:53] <seb128> jbicha, well at least for release, wouldn't be impossible to SRU if we think it's worth
[14:53] <jbicha> thoughts on LP: #1707352 ? should we release-note it?
[14:53] <didrocks> any reason it's missing? it's just an oversight, correct?
[14:53] <didrocks> (we didn't really test it, but I don't think it had been broken?)
[14:54] <jbicha> didrocks: my comment on the bugs says that the current icon will look bad in vanilla GNOME
[14:54] <seb128> jbicha, that seems unfortunate :-/ did you talk to robert about it?
[14:54] <jbicha> seb128: no but I can ask him later
[14:54] <didrocks> jbicha: hum, indeed, but the functionality is still important in some ways… I guess if we balance that with the icon look…
[14:56] <jbicha> didrocks: but at this point it's a user interface change so I'm suggesting we fix the !Humanity icon too if we're going to do an SRU
[14:56] <czajkowski> c
[14:57] <Laney> cockatrice
[14:57] <willcooke> vowel please Carol
[14:57] <didrocks> yes, fair enough, we'll need someone to have icon design experience then
[14:58] <willcooke> kk, let's wrap the meeting (since meeting ology isnt running it doesnt really make any difference)
[14:58] <willcooke> #endmeeting
[14:58] <willcooke> Please carry on if you need to though
[14:59] <seb128> thanks
[14:59] <didrocks> thx!
[14:59] <jbicha> didrocks: I thought the faenza 'jockey' icon looked good when I looked a year ago but I never got a reply from Matthieu James when I asked him about re-using it
[14:59] <oSoMoN> thanks
[15:00] <didrocks> jbicha: when did you ask, recently?
[15:01] <jbicha> I emailed him @canonical.com Aug 18 2016 and @gmail a few days ago
[15:01] <jbicha> I don't know if he left Canonical at some point so maybe didn't get the first email?
[15:02] <tkamppeter> Anyone already has copied MP3 (or Music in general) to an Android phone with Artful?
[15:03] <jibel> I didn't but saw a recent report about a crash of mtp
[15:03] <didrocks> jbicha: he isn't around anymore, but he was still here in 2016, I don't know more than you how to reach him though
[15:03] <didrocks> what license is faenza?
[15:04] <jbicha> it appeared to be GPL-3+ so that's why I asked. (software-properties is GPL-2+). I think we could probably use the icon without re-licensing though, right?
[15:05] <jibel> tkamppeter, why are you asking?
[15:05] <seb128> there is a gvfsd-mtp segfault high on artful e.u.c report
[15:05] <jibel> tkamppeter, bug 1724075 bug 1723815
[15:05] <tkamppeter> jibel, I get mtp crashes a lot, not on my attempts to tranfer music (it simply says that it cannot write onto the phone) but on connecting/disconnecting(?) the phone.
[15:05] <seb128> but I've been replacing the binary by a wrapper under valgrind for a few weeks and don't error
[15:06] <seb128> bug #1718694
[15:06] <seb128> k, need to go/move location, back in a bit
[15:07] <tkamppeter> jibel, thanks, looks like a feature which we have to skip in Artful. Or is there some special trick/workaround.
[15:09] <jibel> honestly it seems in a bad shape. something to fix for 18.04 and SRU if possible
[15:10] <tkamppeter> jibel, so I think the best  is to ask seb128 how to apply his workaround with valgrind.
[15:13] <didrocks> jbicha: thanks for the mail! I don't have a strong opinion on it, need to think about this with a fresh brain
[15:14] <jbicha> didrocks: take your time, the underlying issue has been there for years already ;)
[15:16] <didrocks> yeah ;)
[15:20] <jbicha> I worked around it for Ubuntu GNOME and forgot about it until I saw the new bug
[15:22] <tkamppeter> seb128, what did you exactly do with Valgrind to work around the mtp crash bugs.
[15:23] <tkamppeter> ?
[15:33] <tkamppeter> seb128, which binary did you replace by a Valgrind wrapper and how did you call Valgrind for that? Can you send me your wrapper script?
[15:41] <seb128> tkamppeter, well maybe I don't know how to trigger the bug, but what I did was basically
[15:41] <seb128> - sudo mv /usr/lib/gvfs/gvfsd-mtp /usr/lib/gvfs/gvfsd-mtp.bin
[15:42] <seb128> - sudo editor /usr/lib/gvfs/gvfsd-mtp
[15:42] <seb128> with that content
[15:42] <seb128> #!/bin/sh
[15:42] <seb128> export G_SLICE=always-malloc G_DEBUG=gc-friendly
[15:42] <seb128> valgrind -v --tool=memcheck --leak-check=no --log-file=/tmp/gvfs.%p /usr/lib/gvfs/gvfsd-mtp.bin $@
[15:42] <seb128> - sudo chmod +x /usr/lib/gvfs/gvfsd-mtp
[15:42] <seb128> then restarted the session
[15:42] <seb128> and it logs files in /tmp/gvfs.<pid>
[15:43] <seb128> if you get an error you should have an invalid read/write
[15:43] <seb128> better if you have a dbg of gvfs
[15:43] <seb128> tkamppeter, what do you do to trigger the issue?
[15:47] <tkamppeter> seb128, first thanks for the hint, applied the commands. Before restarting my session I will answer your question.
[15:47] <seb128> tkamppeter, in fact you don't need to restart the session I think
[15:48] <seb128> if gvfsd-mtp hit the bug it will close and restart a new instance
[15:48] <seb128> try and see if you get a log in /tmp
[15:49] <tkamppeter> seb128, gvfsd-mtp crashes practically always when I disconnect the phone, and this happened often to me, charging the phone's battery with my laptop.
[15:51] <tkamppeter> seb128, Now I also want to transfer music files and here I always get errors that I cannot write on the device, with both GNOME File Manager and Rhythmbox.
[15:52] <tkamppeter> Not yet restarted the session and still cannot write to my device.
[15:52] <tkamppeter> Will restart the session now.
[16:02] <tkamppeter> seb128, No gvfs-mtp process and also no appropriate log file in /tmp
[16:04] <tkamppeter> seb128, Sorry, valgrind  was not installed, one moment please.
[16:08] <tkamppeter> seb128, after installing valgrind, replugging the device and starting rhythmbox the device appears again.
[16:10] <tkamppeter> seb128, and when I copy a music file to it I do not get an error message any more that I cannot write to the device, but the music file does not appear on the device.
[16:13] <tkamppeter> seb128, here is the log file: http://paste.ubuntu.com/25760200/
[16:15] <tkamppeter> seb128, will try to restart again.
[16:21] <tkamppeter> seb128, restarted the machine, unlocked the screen of the device and on the device I tried once "MTP" and once"Media device USB 3.0" and in both cases I get "Could not transfer track, could not open resource for writing".
[16:23] <tkamppeter> seb128, new log file: http://paste.ubuntu.com/25760249/
[16:27] <tkamppeter> seb128, and another: http://paste.ubuntu.com/25760262/
[16:48] <oSoMoN> Laney, cheers
[16:49] <Laney> cheers to you
[16:50] <Laney> I looked a bit for how to fix that no session selected issue
[16:50] <Laney> would be annoying
[16:59] <oSoMoN> yeah
[17:01] <seb128> tkamppeter, you have errors in there but no dbg, can you install libglib2.0-0-dbgsym and maybe do a DEB_BUILD_OPTIONS=nostrip build from gvfs and copy that non stripped binary as gvfsd-mtp.bin?
[17:01] <seb128> ==5038==    by 0x53B3F3D: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.5400.1)
[17:01] <seb128> ==5038==    by 0x539193F: g_content_type_guess (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.5400.1)
[17:01] <seb128> ==5038==    by 0x10E3B4: ??? (in /usr/lib/gvfs/gvfsd-mtp.bin)
[17:03] <Laney> night!
[17:03] <oSoMoN> g’night Laney
[17:05] <oSoMoN> seb128, I've prepared source packages at https://people.canonical.com/~osomon/bug1718446/, can you upload them for me? I'll prepare the SRU paperwork after dinner
[17:08] <tkamppeter> seb128, how do I install libglib2.0-0-dbgsym, "sudo apt-get install libglib2.0-0-dbgsym" does not work.
[17:11] <jbicha> tkamppeter: have you seen https://wiki.ubuntu.com/Debug%20Symbol%20Packages ?
[17:12] <tkamppeter> jbicha, thanks
[17:22] <willcooke> night all
[17:37] <tkamppeter> seb128, jbicha: Everything installed as you asked for. restarting.
[17:44] <tkamppeter> seb128, jbicha, http://paste.ubuntu.com/25760647/
[17:45] <tkamppeter> seb128, jbicha: same error, new log: http://paste.ubuntu.com/25760647/
[17:53] <tkamppeter> seb128, jbicha: Also this crash happened during my tests: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1724323
[18:04] <amano> didrocks, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723619 is not my issue. I tried the new kernel with the revert and it took me again 3 reboots to have GDM starting up.
[18:04] <amano> uname -r
[18:04] <amano> 4.14.0-rc5-lp1723619+revert
[18:45] <seb128> tkamppeter_, thanks for the new log, that has debug infos indeed
[18:51] <tkamppeter_> seb128, yw, hope that it brings us closer to the cause of the problem. This also an important feature.
[18:53] <tkamppeter_> seb128, please subscribe me to the bug report in which you will handle this so that I can test the fix to verify the SRU.
[19:03] <seb128> tkamppeter_, sure, did you report the gvfs segfault to launchpad/using apport?
[19:05] <tkamppeter_> No, the segfault which I reported was on valgrind (or somethin underlying).
[19:05] <tkamppeter_> seb128, bug 1724323
[19:06] <seb128> tkamppeter_ it might be useful to report the gvfs one if you have a report in /var/crash
[19:06] <Tribaal> hi all, what is the canonical way to install the nvidia drivers in 17.10? I'm writing some kind of tutorial for end users, so I was going to suggest the "additional drivers" thing but I can't seem to find it?
[19:06] <tkamppeter_> seb128, Services asked for by UDEV do not get triggered
[19:06] <tkamppeter_> seb128, sorry, [Bug 1724323] [NEW] memcheck-amd64-linux crashed with SIGSEGV
[19:08] <Tribaal> (that's to workaround a nouveau bug in 17.10)
[19:08] <tkamppeter_> seb128, today I did not a crash report of gvfs-mtp but otherwise I got one nearly every day: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1706097 and duplicates.
[19:09] <seb128> tkamppeter_, thanks
[19:09] <seb128> tkamppeter_, do you know what steps you take to trigger the segfault? does it happen just when you plug your phone? or unlock it?
[19:09] <tkamppeter_> seb128, but for these I did not try to copy anything to my phone. AFAIK they were triggered by connecting/disconnecting the phone for charging its battery.
[19:11] <tkamppeter> seb128, the report happened delayed, usually after next boot, so I cannot really know whether the trigger was connect, disconnect, or unlock.
[19:11] <seb128> ok
[19:12] <seb128> you might be able to tell from the time recorded in the crash
[19:26] <seb128> Tribaal, it's in software-properties, is bug #1710377 what is confusing you?
[19:26] <seb128> jbicha, ^ maybe some data point
[19:27] <Tribaal> seb128: huh! Indeed I guess I was confused by this. I found "ubuntu-drivers" which nicely allowed me to have a CLI equivalent though.
[20:51] <flocculant> jbicha: just saw someone in #ubuntu+1 commenting on gnome-terminal - seems f11 on terminal - repeatedly - leads to terminal shrinkage, https://i.imgur.com/oNZ4yi5.png < this was quite a bit of f11 on my part in a vm, just thought I'd pass that along
[21:13] <Beret> I know there's a duplicate about this
[21:13] <Beret> we know that automatic timezone doesn't work in artful right?
[21:13] <Beret> I vaguely remember having a conversation about it already
[21:13] <Beret> probably at the rally
[21:26] <jbicha> Beret: LP: #1720829 is the only one I'm aware of, assuming you haven't turned off Settings>Privacy>Location Services
[21:31] <vithiri> Beret: "I vaguely remember" makes it sound like one awesome rally.
[21:31] <Beret> hahaha
[21:32] <Beret> I've probably had 300 meetings over the last few weeks - they tend to all run together
[21:32] <Beret> I forgot what was only in my head versus what was discussed
[21:32] <Beret> but yeah, it wasn't bad :)
[21:33] <vithiri> So, what's the issue with the automatic timezone? I recall having the correct timezone picked during installation.
[21:34] <jbicha> robert_ancell: hi
[21:34] <robert_ancell> jbicha: hello
[21:35] <jbicha> thoughts on LP: #1707352 ?
[21:54] <robert_ancell> jbicha: I think we should roll back to the older libsane to not break things.
[21:55] <jbicha> so 1.0.25+git20150528-1ubuntu4 instead?
[21:55] <jbicha> it's rather late for that kind of change…
[21:56] <jbicha> (sorry I didn't think to specifically ping you about this issue sooner)
[21:57] <robert_ancell> sane is a pain in that they don't do releases.
[21:57] <robert_ancell> Yeah, but I guess it has to work with third party drivers since they are commonly used.
[21:58] <jbicha> are you sure they don't? http://www.sane-project.org/
[21:58] <jbicha> what about just adding Provides: libsane ?
[21:59] <jbicha> I had trouble getting the Debian maintainer to respond to my comments :(
[22:00] <robert_ancell> jbicha: afaict the sane maintainers are effectively Debian.
[22:00] <robert_ancell> If the provides works then do that I guess? You probably know more about this than me.
[22:01] <robert_ancell> I've looked at updating the sane-backends package a number of times but it's too hard given upstreams lack of clarity.
[22:03] <jbicha> they use Alioth but it looks like sane upstream is different than the Debian packager
[22:03] <jbicha> https://anonscm.debian.org/git/sane/sane-backends.git/
[22:03] <jbicha> packaging: https://anonscm.debian.org/git/collab-maint/sane-backends.git
[22:04] <robert_ancell> oh, ok
[22:06] <jbicha> I don't have a scanner, PeterPall suggests that adding the Provides might work for any scanner drivers distributed as a .deb
[22:07] <jbicha> I don't know how common that is
[22:07] <jbicha> he suggested that at https://bugs.debian.org/870078 and no real response from the Debian maintainer :(
[22:09] <robert_ancell> jbicha: I think there are drivers delivered by debs
[22:09] <jbicha> do you have any hardware like that?
[22:09]  * robert_ancell looks
[22:10] <jbicha> I'm just wondering how we would verify that an SRU to add the Provides would help for real-world cases
[22:12] <robert_ancell> jbicha: I'm looking at the brscan package (http://support.brother.com/g/b/downloadlist.aspx?c=us&lang=en&prod=mfcj5620dw_us_eu&os=128)
[22:12] <robert_ancell> which is what my scanner uses.
[22:12] <robert_ancell> Looks like it doesn't have a specific dependency on libsane
[22:12] <robert_ancell> But the provides seems like a reasonable thing to do if the package has renamed but is otherwise identical?
[22:15] <jbicha> sane-backends/zesty's libsane had libsane.so.1.0.25 and artful's libsane1 has libsane.so.1.0.27 so it seems like the Provides makes sense
[22:15] <jbicha> I guess the Debian maintainer just wanted to fix the Lintian warning package-name-doesnt-match-sonames
[22:15] <jbicha> :(
[22:16] <jbicha> I'll prepare an SRU and hope the SRU Team doesn't mind the difficulty in verifying the fix
[22:18] <robert_ancell> jbicha: you're probably right about the lintian warning :)
[22:31] <jbicha> robert_ancell: uploaded to artful/unapproved and figured out a test case
[22:32] <jbicha> thanks for the help :)
[22:32] <robert_ancell> jbicha: nice work!
[23:38] <ignoo> hello, running ubuntu GNOME 16.04, have some issue with ubuntu ArtfulAardvark: https://pastebin.com/W1tBbqpq . Thank you for your support.