[06:26] <oSoMoN> good morning desktoppers
[06:27] <Trevinho> morning oSoMoN
[06:27] <oSoMoN> hey Trevinho
[07:02] <duflu> Hi oSoMoN, Trevinho
[07:02] <Trevinho> hei duflu
[07:18] <didrocks> good morning
[07:23] <oSoMoN> hey duflu
[07:23] <oSoMoN> salut didrocks
[07:23] <didrocks> salut oSoMoN
[07:25] <Trevinho> morning didrocks
[07:27] <duflu> Morning didrocks
[07:27] <didrocks> hey hey Trevinho, duflu
[07:28] <duflu> Hey hey (Krusty laugh)
[07:30] <didrocks> isn't it rather "hey hey hey"? (at least, in the french version, there are 3 of them ;))
[07:31]  * Tribaal never considered how many "hey" he uses
[07:31] <Tribaal> maybe fr_CH differs from fr_FR :)
[07:31] <Tribaal> (hi all, by the way :) )
[07:31] <duflu> The world is full of Simpsons experts and I am not one of them
[07:31] <duflu> Hi Tribaal
[07:33] <didrocks> salut Tribaal
[07:33] <Tribaal> salut didrocks :)
[07:33] <sb87> hello, what's up ?
[07:47] <seb128> good morning desktopers
[07:47] <willcooke> morning seb128, all
[07:47] <seb128> hey oSoMoN Trevinho duflu
[07:47] <seb128> hey willcooke
[07:47] <duflu> Hi seb128
[07:47] <Trevinho> bonjour seb128
[07:47] <seb128> how is everyone today?
[07:48] <willcooke> hey Trevinho, which timezone this week?
[07:48] <Trevinho> willcooke: hey
[07:48] <Trevinho> still the same... Cancun area :)
[07:48] <willcooke> So a late night then?
[07:48] <Trevinho> yeah...
[07:48] <willcooke> you kids
[07:48] <willcooke> ;)
[07:49] <Trevinho> mornings are not my thing :-D
[07:49] <willcooke> :D
[07:50] <seb128> we are getting quite some feedback/bugs reported against 17.10, that's nice
[07:50] <seb128> I went through the bugs from my 3 days w.e yesterday, had to do a 10-11pm round to finish the list, it was like 700 reports (only including main package in the list)
[07:50] <seb128> quite a difference of most weeks where it takes 1.5 hours to review the w.e activity :p
[07:52] <willcooke> heh
[07:52] <willcooke> Thanks for taking time to do that
[07:52] <willcooke> but yeah, it's good that people are logging bugs
[07:52] <willcooke> I think we've got the message out quite well
[07:55] <oSoMoN> salut seb128
[07:55] <didrocks> hey willcooke, Trevinho
[07:55] <oSoMoN> hey willcooke
[08:01] <Laney> hey ho
[08:02] <willcooke> hi Laney
[08:04] <Laney> hey willcooke
[08:04] <Laney> all good?
[08:05] <willcooke> Today is "hammering and drilling" day at the soon-to-be-opened Barbra Cartland Wing of Cooke Towers.
[08:06] <seb128> hey Laney!
[08:07] <seb128> haha
[08:07] <seb128> willcooke, summary of going through the report is that we don't get that many user complains about the experience or softwares
[08:07] <seb128> but nautilus/gnome-control-center/gnome-calendar are hitting quite some segfaults
[08:07] <seb128> and gnome-shell quality is poor
[08:08] <seb128> I wonder if 3.26 was just not a good cycle for it
[08:08] <seb128> lot of reports about screens handling, 3 monitors not working, rotation being buggy, configs lost between reboots, still people having to suspend on lid close with external monitor in use, etc
[08:08] <seb128> then the segfaults
[08:09] <seb128> but overall it seems like things we can get in shape next cycle
[08:09] <willcooke> shall we start tagging bugs for trello?  Or do another pass through next week first?
[08:09] <seb128> I would wait a bit before starting to tag, let's digest the feedback a bit more during this week?
[08:09] <willcooke> +1
[08:10] <willcooke> thanks
[08:10] <seb128> yw!
[08:11] <didrocks> morning Laney
[08:16] <seb128> duflu, does https://patchwork.freedesktop.org/patch/182709/ sounds like something worth SRUing to 17.10?
[08:16] <duflu> seb128, I think a few of those issues have been known for years. They just haven't received attention
[08:17] <duflu> seb128, yes I was thinking that but as mentioned in the report, I also can't reproduce the problem to test an SRU
[08:17] <seb128> duflu, they reworked the screens handling in 3.26 afaik, before it was gnome-settings-daemon which was applying the configurations
[08:18] <duflu> seb128, there are however some users who swear profile selection is still broken for them so the most reliable solution is also slow -- ask them to test 18.04 when the fix is there
[08:19] <seb128> duflu, sounds good, I don't understand why it works because the commit message from ^ seems to make pretty clear thatg with current priorities hsp should be used by default
[08:19] <seb128> anyway, let's see if we get more reports and people testing the new version
[08:19] <duflu> seb128, I think it's a function of what your device advertises - device specific?
[08:20] <seb128> could be yes
[08:20] <seb128> duflu, I'm catching up with backlog, just saw your totem-pl-parser fix, I like it :-)
[08:21] <seb128> small and makes sense
[08:23] <duflu> seb128, unfortunately not foolproof though. It /assumes/ disk writing is fast, and only fsync is slow
[08:23] <duflu> which seems to be true for myself and the upstream reporter
[08:24] <duflu> A proper fix would span two projects and require much more code
[08:25] <seb128> right, well that's an improvement and simple
[08:25] <seb128> so a step in the right direction still
[08:26] <duflu> Yeah I don't want to talk anyone into wanting the latter
[08:26] <duflu> I don't like that GTK apps in general share one main loop between rendering and disk IO
[08:28] <sb87> Hello developper, why choose Gnome-Shell for 17.10 and not Kde/Plasma or Xfce or Mate ?
[08:33] <duflu> sb87, the decision is not one we developers make (or disagree with). It came from a higher authority: https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-rather-than-phone-and-convergence/
[08:33] <krashekspress> What an interesting question, I actually prefer Gnome, but some "features" are just ridiculous
[08:35] <sb87> what is the preferred desktop environment for Ubutu developers ?
[08:36] <sb87> Gnome ? Xfce ? Kde ? Lxde ? Cinnamon ? Mate ? Pantheon ? Lxqt ? Enlightnment ? i3wm ? Budgie ?...
[08:37] <duflu> sb87, Ubuntu developers actually like to use a bunch of different ones but if working on the desktop itself then mostly Gnome
[08:39] <sb87> According to the developers, what should you improve in the gnome shell ?
[08:39] <krashekspress> Are you planning to redo Ambience for Gnome? From my POV Adwaita looks way better throughout the shell
[08:41] <seb128> sb87, Ubuntu has always used GNOME technologies, that's what we have most experience with, the community we know best and there release cycle, etc is aligned with ours
[08:42] <sb87> Ubuntu 18.04 will be released with Gnome 3.28 ?
[08:42] <seb128> it's not decided
[08:43] <seb128> it depends of how much change and if we believe the changes to be suitable for the LTS
[08:43] <sb87> what change is planned for Gnome 3.28 (compared to 3.26) ?
[08:44] <seb128> sb87, that's a question for GNOME, I don't think they decided on everything yet
[08:44] <seb128> sb87, https://wiki.gnome.org/ThreePointTwentyseven
[08:45] <sb87> thx
[08:45] <sb87> one last question
[08:46] <seb128> sb87, https://wiki.gnome.org/ReleasePlanning/FeaturePlans has some details
[08:46] <sb87> what is the codename of Ubuntu 18.04 ?
[08:47] <seb128> we don't know yet
[08:47] <sb87> how long will you know?
[08:48] <seb128> this week probably
[08:49] <seb128> interesting, the featureplans GNOME package has "New On-Screen-Keyboard"
[08:53] <willcooke> Oooh, nice
[08:56] <duflu> One with more keys?
[08:56] <duflu> And more languages?
[09:00] <duflu> One that uses the full width of the screen?
[09:03] <willcooke> earlier in the cycle it did use the full width, then one day it changed
[09:16] <Trevinho> duflu: do you use git bz for patches?
[09:16] <duflu> Trevinho, git when I can
[09:16] <Trevinho> duflu: I mean git bz, to add patches to gnome bugzilla
[09:16] <Trevinho> and manage them
[09:17] <duflu> Trevinho, never heard of it. Thanks
[09:17] <Trevinho> to automatize things
[09:18] <Trevinho> duflu: install it, then use the -h, or read the man, but basically use file to open a new bug to send a patch, or use attach to push /update patches to bug
[11:08] <oSoMoN> chrisccoulson, hey, did you see my message yesterday about chromium 62.0.3202.62 being ready in the stage PPA ?
[11:33] <chrisccoulson> oSoMoN, yeah, I'm on that at the moment
[11:33] <oSoMoN> chrisccoulson, excellent, thanks!
[11:34] <oSoMoN> chrisccoulson, also, did you do something wrt bug #1725238, or are you leaving it to me?
[11:54] <willcooke> chrisccoulson, can we get an answer on that q. please?  We need to get moving with it and don't want to tread on toes if you're already on the case ^
[12:06] <chrisccoulson> willcooke, I don't plan to do anything with that. It's fixed upstream already, so will be in a future update, and it was broken for several months before anyone noticed
[12:08] <ricotz> chrisccoulson, if so, putting some pressure on it to get it uplifted for 57 would still help
[12:10] <willcooke> So it's fixed in 58 right?
[12:10] <ricotz> yes
[12:10] <chrisccoulson> it is
[12:10] <willcooke> so maybe another 2 months until it's "fixed" in Ubuntu?
[12:11] <ricotz> like 2018-01-16
[12:12] <willcooke> oSoMoN, sounds like we should aim to back port them to 57 then, wdyt?
[12:14] <oSoMoN> willcooke, yeah, if the fix can be safely backported
[12:15] <chrisccoulson> I think the probability of getting upstream to uplift it to 57 is low (see https://bugzilla.mozilla.org/show_bug.cgi?id=1382323#c40)
[12:15] <chrisccoulson> It's quite an old regression (Firefox 54, which was january)
[12:15] <oSoMoN> what's interesting is that those snap:// links work here on my artful in firefox (but not in a clean VM), I wonder what in my config makes it work
[12:16] <chrisccoulson> oSoMoN, you've probably got an addon that disables multiprocess
[12:22]  * kenvandine waves
[12:22] <oSoMoN> hey kenvandine
[12:23] <kenvandine> i won't be around long, need to logout to use my laptop as a demo machine for the GNOME booth :)
[12:23] <kenvandine> oSoMoN, tons of people had questions yesterday about Ubuntu switching to GNOME
[12:24] <kenvandine> i'd say about half were disappointed and about half were excited
[12:25] <kenvandine> i was surprised how many people walked up to the GNOME booth to tell us they were going to really miss Unity but would try to get used to GNOME
[12:25] <oSoMoN> same on IRC and forums, the switch to GNOME is generating a lot of heat
[12:25] <kenvandine> they didn't really know i'm from Ubuntu :)
[12:25] <kenvandine> but just as many were saying it was about time ubuntu switched
[12:26] <kenvandine> system 76 is a big presence here and giving away some of the best stuff
[12:27] <kenvandine> lots of Pop!_OS buzz
[12:27] <didrocks> hey kenvandine!
[12:28] <kenvandine> hey didrocks
[12:29] <kenvandine> oSoMoN, i hit the same problem as popey did with your chromium snap yesterday
[12:29] <kenvandine> just tested the latest and works now :)
[12:29] <oSoMoN> kenvandine, so you managed to upgrade the snap, or did you have to uninstall the previous revision to install the new one?
[12:30] <kenvandine> i had uninstalled it last night
[12:30] <kenvandine> although the uninstall looked like it failed
[12:30] <oSoMoN> right, that's what I did too, but it looks like the upgrade path is broken because of snapd having become too strict
[12:30] <oSoMoN> I'm talking to m_vo about it on #snappy
[12:30] <kenvandine> LaunchProcess: failed to execvp:
[12:30] <kenvandine> xdg-desktop-menu
[12:31] <kenvandine> i see lots of that in the console
[12:32] <oSoMoN> with the chromium snap? mind adding that to the call for testing thread?
[12:32] <kenvandine> sure
[12:33] <kenvandine> oSoMoN, done
[12:34] <oSoMoN> cheers
[12:34] <kenvandine> ok, time to logout and repurpose the laptop for demos :)
[12:34] <popey> I can't even install it now
[12:34] <kenvandine> popey, i win :)
[12:35] <ricotz> oSoMoN, willcooke, regarding https://bugzilla.mozilla.org/show_bug.cgi?id=1382323 -- the patch still applies cleanly, so I can add it with the next 57 beta 12 upload
[12:39] <willcooke> thanks ricotz, would be good to be able to test.
[12:41] <ricotz> willcooke, ok, should be available during this Friday
[12:41] <willcooke> nice one
[12:42] <oSoMoN> neat
[12:42] <oSoMoN> thanks ricotz!
[13:05] <seb128> andyrock, hey, could you prepare a SRU for https://bugzilla.gnome.org/show_bug.cgi?id=789141? e.g update the bug to be SRU compliant (impact/test case/regression potential) and put a merge request up against the packaging vcs?
[13:11] <sb87> You should put the default "Xorg session" on 18.04 ! Xorg session has less trouble than wayland !
[13:12] <ogra_> it will surely be available (unless nvidia proprietary drivers make a quantum leap in the next 6 months and support wayland)
[13:12] <mgedmin> nah, better fix all the bugs in wayland :)
[13:13] <ogra_> that too ...
[13:13] <ogra_> but if the wayland session is unusable on nvidia the xorg session will still have to be there
[13:14] <sb87> Xorg session must be default!
[13:15] <ogra_> that wont fix wayland :)
[13:15] <sb87> and wayland as a secondary choice
[13:15] <ogra_> there is 6 months to fix all the remaining issues
[13:15] <ogra_> this is why it is the default right now
[13:15] <ogra_> so you can file bugs that can get fixed in time
[13:16] <ogra_> make sure to file them if you find them ;)
[13:17] <sb87> it's not just a problem
[13:18] <sb87> it is not compatible with the proprietary drivers (essential to play)
[13:18] <ogra_> see what i said above :)
[13:19] <sb87> and applications like gparted or synaptic are not compatible
[13:19] <ogra_> so they need to be fixed
[13:20] <sb87> why not put xorg first and wayland 2nd (and not the other way around)
[13:21] <ogra_> why should we ? if you use nvidia, xorg is already auto-selected today ... and if the apps get fixed to properly use polkit they will work ... what are your other issues beyond this ?
[13:22] <gQuigs> next version of gparted is already compatible (not in archive yet).. things won't get fixed without something/someone to push them forward
[13:22] <ogra_> indeed
[13:22] <ogra_> but all distros that default to wayland are pushing currently :)
[13:23] <andyrock>  seb128 sure thing
[13:23] <andyrock> can I do that in few hours
[13:23] <andyrock> ?
[13:23] <andyrock> I'm busy with another thing
[13:23] <sb87> ok
[13:24] <seb128> andyrock, sure, it's not urgent, another day this week is fine as well
[13:24] <sb87> if it does not have more bug on wayland than xorg for the 18.04 it's ok for me (for now it's not the case).
[13:24] <andyrock> kk thanks
[13:24] <ogra_> that is why it was made the default right now ... so these bugs can be fixed :)
[13:25] <gQuigs> sb87: I've seen reports that wayland is less crash prone for certain video playback, but I don't have the machines myself - one of those things that depends on hardwarew
[13:25] <ogra_> (and found)
[13:26] <sb87> for example, vlc works better under xorg than under wayland
[13:27] <ogra_> file bugs then :)
[13:27] <sb87> when i run a movie, if I move the cursor quickly in vlc, under wayland from time to time it freezes several seconds, I do not have this behavior under xorg.
[13:28] <sb87> it's just an example
[13:42] <sb87>  when will the first dailybuild for 18.04 be available?
[13:50] <jbicha> gQuigs: I don't know if we want the gparted "fix" https://bugzilla.gnome.org/776437
[13:52] <jbicha> mdeslaur: what do you think? https://git.gnome.org/browse/gparted/commit/?id=f38ccd02
[13:53] <jbicha> sb87: there hasn't been a codename announced for 18.04 yet, ask again about daily builds next week
[13:53] <gQuigs> jbicha: I'd only read the changelog.. hmm
[13:53] <gQuigs> yes, it's the Bionic Beaver :)
[13:53] <gQuigs> my favorite name yet
[13:54] <jbicha> gQuigs: oh he updated his blog :) thanks
[13:57] <mgedmin> mispositioned gnome-terminal tab tooltips in a dual-head scenario: gtk+ bug or gnome-shell bug?
[13:58] <sb87> ohoh
[13:58] <sb87> Ubuntu 18.04 Bionic Beaver
[14:00] <mgedmin> https://imgur.com/a/rwkxZ
[14:06] <mdeslaur> jbicha: "wtf!" is what I think of that
[14:06] <willcooke> lol
[14:07] <willcooke> mgedmin, I /think/ that's a know issue, tooltips being generally misplaced, looking for the bug
[14:07] <jbicha> mdeslaur: well if you have time, feel free to comment on their bug. Maybe I should have pointed out what they were intending sooner
[14:07] <jbicha> the devs did hesitate enough to not enable it by default
[14:08] <mdeslaur> jbicha: that doesn't even make sense
[14:13] <ricotz> chrisccoulson, oh no ... error: failed to build archive: Cannot allocate memory , error: Could not compile `gkrust`.
[14:14] <ricotz> chrisccoulson, if they bump to rustc 1.21 this week as scheduled, it might get better
[14:14] <ricotz> so looks like gcc/rust runs out of memory on the ppa builder
[14:28]  * willcooke rings the bell
[14:28] <jbicha> o/
[14:29] <didrocks> hey hey
[14:29] <andyrock> o/
[14:30] <willcooke> #startmeeting Desktop Team Weekly meeting - 2017-10-24
[14:30] <meetingology> Meeting started Tue Oct 24 14:30:01 2017 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:30] <meetingology> Available commands: action commands idea info link nick
[14:30] <willcooke> Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber (both on hols), kenvandine (out), laney, oSoMoN (out), seb128, tkamppeter, trevinho (out), robert_ancell (out)
[14:30] <willcooke> lots of people out today
[14:31] <seb128> hey
[14:31] <willcooke> Since andyrock is here, let's start
[14:31] <willcooke> #topic andyrock
[14:31] <andyrock> hey
[14:31] <andyrock> 1. Theme fix for osd progressbar: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1724808
[14:31] <andyrock> 2. Fix for https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724703
[14:31] <andyrock> 3. Fix for https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720400
[14:31] <andyrock> 4. Fix for https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1703046
[14:31] <andyrock> 5. Some debugging and some work for: https://bugs.launchpad.net/ubuntu-themes/+bug/1724651
[14:31] <andyrock> 6. Started to work on an oem bug on unity-control-center/16.04
[14:31] <andyrock> + some bug triaging
[14:31] <andyrock> eow
[14:32] <willcooke> Thanks andyrock, how's the LP API working out?
[14:32] <willcooke> LivePatch
[14:32] <andyrock> I'm planning to work on this starting from tomorrow
[14:32] <willcooke> oki thanks
[14:32] <willcooke> #topic dgadomski
[14:32] <andyrock> after I finish with the oem bug
[14:32] <willcooke> sorry andyrock
[14:32] <andyrock> np!
[14:33] <willcooke> looks like dgadomski is off
[14:33] <willcooke> #topic didrocks
[14:33] <didrocks> * Debug with the community the ATI card issues. Found regression commits and revert those just in time for release (after a late respin). Probably prevented (from the feedback) every non wayland supported configuration to start with a headless display.
[14:33] <didrocks> * Prepared SRU with real upstream fix. In proposed right now, confirmed to work on previously broken configuration (and they run wayland now!)
[14:33] <didrocks> * SRU for gnome-shell-extension-appindicator & Qt apps icon disappearing after lock/resume.
[14:33] <didrocks> * SRU fixing a g-c-c crash due to dock panel, enable another patch from seb
[14:33] <didrocks> * Discussed desktop snap not working on Fedora and workaround review on desktop helper
[14:33] <didrocks> * Pinged about extensions still blocked on extensions.gnome.org (for us owning our extension naming). Still blocked on some legal constraints.
[14:33] <didrocks> * Wrote the last blog post for the 17.10 series: https://didrocks.fr/2017/10/18/ubuntu-gnome-shell-in-artful-day-16/
[14:33] <didrocks> * Answer to people on the hub + monitor french forum and discussions on the blog.
[14:33] <didrocks> * Filed a RT for discourse integration not working on the blog. Willcooke: do you mind nudging this on IS side?
[14:33] <didrocks> * Workarounded with "manual discourse link" implemented on my blog post
[14:33] <didrocks> * The new Ubuntu Make maintainer asked for a little bit of help, did it. (reviews, suggestions, merges)
[14:33] <didrocks> * Some bug reviews (theme on the Shell)
[14:33] <didrocks> .
[14:34] <willcooke> thanks didrocks, can you ping me a RT link and I will ping
[14:34] <didrocks> sure
[14:34] <willcooke> ping ping a ping ping
[14:34] <willcooke> ta
[14:34] <willcooke> #topic duflu
[14:34] <willcooke> * Mutter/Xwayland
[14:34] <willcooke>   - Completed a few iterations of my fix to allow Xwayland to dump core when it crashes (instead of always hiding core/crash files): https://bugzilla.gnome.org/show_bug.cgi?id=789086
[14:34] <willcooke> * Totem stuttering (https://bugs.launchpad.net/bugs/1698270)
[14:34] <willcooke>   - Made a few attempts at fixing: https://bugzilla.gnome.org/show_bug.cgi?id=733780
[14:34] <willcooke>   - But eventually proposed the simplest solution (one line).
[14:34] <willcooke>   - Now we have fixes for all the totem stuttering issues and just need to work on landing/releasing them (see patch statuses below)...
[14:34] <willcooke> * Daily bug management across gnome-shell, mutter, gdm3, ubuntu-themes, bluez, pulseaudio, dkms and mir.
[14:34] <willcooke>   - Multiple days spent answering bug mail, thanks to the release.
[14:34] <willcooke> * Patches awaiting Ubuntu sponsorship (or needing refreshing for 18.04):
[14:34] <willcooke>   - https://code.launchpad.net/~vanvugt/gtk/fix-1698270/+merge/331846
[14:34] <willcooke>   - https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714459/comments/15
[14:35] <willcooke> * Patches awaiting upstream review:
[14:35] <willcooke>   - https://bugzilla.gnome.org/show_bug.cgi?id=645433
[14:35] <willcooke>   - https://bugzilla.gnome.org/show_bug.cgi?id=733780
[14:35] <willcooke>   - https://bugzilla.gnome.org/show_bug.cgi?id=787665
[14:35] <willcooke>   - https://bugzilla.gnome.org/show_bug.cgi?id=773453
[14:35] <willcooke>   - https://bugzilla.gnome.org/show_bug.cgi?id=787001
[14:35] <willcooke>   - and soon again: https://bugzilla.gnome.org/show_bug.cgi?id=789086
[14:35] <willcooke> * PulseAudio news regarding 17.10 - No real news, only four new bugs reported:
[14:35] <willcooke>   - A USB headset is dropping connection, but the user has already verified Pulse 11 fixes it.
[14:35] <willcooke>   - One new crash, occurred only once for one person.
[14:35] <willcooke>   - One VIA audio chip not showing up.
[14:35] <willcooke>   - One apparent user error.
[14:35] <willcooke> * Older PulseAudio bugs being talked about in 17.10:
[14:35] <willcooke>   - Kubuntu pulseaudio doesn't work. But the bug is really upstream, easy to fix and to workaround, plus a second redundant fix is coming when we disable the offending module in pulse 11: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519
[14:35] <willcooke>   - HSP really was being prioritized over A2DP, still! But it seems it doesn't manifest for many people so didn't showed up in our testing. Already fixed upstream in Pulse 12 and we'll patch it into 18.04 soonish. https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720684
[14:35] <willcooke> * BlueZ news regarding 17.10:
[14:35] <willcooke>   - No bluez bugs reported at all since release.
[14:35] <willcooke> #topic jbicha
[14:35] <jbicha> • forwarded https://bugzilla.gnome.org/show_bug.cgi?id=789254
[14:35] <jbicha> • fix uploaded for LP: #1725288
[14:36] <jbicha> • Added Provides: libsane to try to fix LP: #1707352 but that didn't work with versioned deps.
[14:36] <jbicha>  I think we need to add a transitional package libsane depending on libsane1 instead. Maybe we'll revert the rename for Bionic.
[14:36] <jbicha> • Uploaded gtk3 for LP: #1719043 but that caused a totem regression. Instead, we'll follow GNOME and cherry-pick the mutter revert to fix epiphany (!)
[14:36] <jbicha> • Proposing LP: #1726093
[14:36] <jbicha> • Helped a bit on forums with people upgrading to 17.10.
[14:36] <jbicha> eof
[14:36] <willcooke> thanks jbicha.  Let's talk about that MIR in AOB at the end
[14:37] <willcooke> #topic jamesh
[14:37] <willcooke> gnome-software: tracked down cause of bug #1724316: root cause is that
[14:37] <willcooke> SSO will refuse to refresh snapd's credentials if the user has changed
[14:37] <willcooke> their password.  To compound matters, snapd was forwarding this error
[14:37] <willcooke> as a generic "internal server error", making it difficult to
[14:37] <willcooke> intelligently recover.  Snapd changes submitted and reviewed (but not
[14:37] <willcooke> landed).  Corresponding snapd-glib and gnome-software changes in
[14:37] <willcooke> progress.
[14:37] <willcooke> snapd: followed up on default apps question: confined apps shouldn't
[14:37] <willcooke> be able to change defaults without user approval, so this is probably
[14:37] <willcooke> a job for xdg-desktop-portal in future (upstream bug filed).  mvo has
[14:37] <willcooke> put together a PR to provide an interim solution based on snapd-userd
[14:37] <willcooke> and zenity for the UI: will need to look at the security implications.
[14:37] <willcooke> I touched base with z_yga about the state of the mount namespace
[14:37] <willcooke> related work.  He is going to be working on the new content interface
[14:37] <willcooke> changes discussed at the sprint that will be needed for desktop theme
[14:37] <willcooke> support.  We also went over how I can get my user mounts branch to do
[14:37] <willcooke> its work through snap-update-ns.  I need to finish off those changes
[14:37] <willcooke> though.
[14:37] <willcooke> going to assume kenvandine[m][m] is not available
[14:37] <willcooke> #topic Laney
[14:38] <Laney> • Short week
[14:38] <Laney> • Worked on some gnome-software small bugs/features
[14:38] <Laney> ∘ Fixing apt:// to work again with the PK backend (not a big problem as we still have apturl)
[14:38] <Laney> ∘ Looking at the "shell extensions" category being empty because there are too many results, might be something to do to reduce the number shown
[14:38] <Laney> • Investigated / debugged the problem which was keeping gtk in artful-proposed, fixed in the software-properties test
[14:38] <Laney> • Reviewed / accepted some release fixes and random changes for others
[14:38] <Laney> • Some random release checklist things, mostly turning stuff off
[14:38] <Laney> • Helped a bit on arm64 testing, should be able to turn that on fully this week
[14:38] <Laney> 😈
[14:38] <willcooke> thanks Laney
[14:39] <willcooke> #topic oSoMoN
[14:39] <willcooke> • prepared SRU for bug #1718446 and got it published
[14:39] <willcooke> • promoted chromium snap (61.0.3163.100) from candidate to stable channel
[14:39] <willcooke> • updated chromium beta packages to 62.0.3202.62 for all supported
[14:39] <willcooke> releases, then stable (ready for publication, Chris currently
[14:39] <willcooke> validating)
[14:39] <willcooke> • built chromium snap 62.0.3202.62, published to candidate channel and
[14:39] <willcooke> issued call for testing
[14:39] <willcooke> • updated chromium dev packages to 63.0.3239.9 (artful, zesty,
[14:39] <willcooke> xenial), trusty requires more work
[14:39] <willcooke> • next up: libreoffice 5.4.2 SRU and snap, bug #1725238
[14:39] <willcooke> #topic seb128
[14:39] <seb128> would be good to verify that"
[14:39] <seb128> ups
[14:39] <seb128> * had one day off
[14:39] <seb128> * iso testing
[14:39] <seb128> * helped Didier testing gnome-shell revert debs to debug the ati/wayland issue
[14:39] <seb128> * loads of recently-reported-bugs triaging
[14:39] <seb128> * cleaned up gnome-software bugs and tagged snaps related issues
[14:39] <seb128> * sponsored the gdm/gnome-session/fallback SRU from Olivier

[14:40] <willcooke> thanks seb128
[14:40] <willcooke> #topic tkamppeter
[14:40] <tkamppeter> - UDEV/systemd: Got upstream answer from Lennart Poettering (original author of systemd?) and it seems that the fix of the escaping in the UDEV rules file does not solve the problem. There is still a problem with the escaping (https://github.com/systemd/systemd/issues/7109).
[14:40] <tkamppeter> - Google Summer of Code 2018: Started planning.
[14:40] <tkamppeter> - Got the flu and had some sessions at the dentist.
[14:40] <tkamppeter> - Bugs.
[14:41] <willcooke> hope you're on the mend tkamppeter
[14:41] <tkamppeter> Now its all OK with me, and the dentist was a long-standing issue, not acute pain.
[14:41] <willcooke> #toipic Trevinho
[14:41] <willcooke> good
[14:41] <willcooke> :)
[14:41] <willcooke> #topic Trevinho
[14:42] <willcooke> Notes for the upcoming meeting:
[14:42] <willcooke>  · Fixed regression in gtk2 theme
[14:42] <willcooke>  · Fixed theming for destructive-action buttons in headerbar
[14:42] <willcooke>  · Fixed theming for *-action buttons in headerbar when maximized
[14:42] <willcooke>  · c-lobrano theme fixes (thanks!) review
[14:42] <willcooke>  · Prepared landing for theme fixes and SRU bugs
[14:42] <willcooke>  · Debugging (and proposed fix, that I want to improve a bit yet)
[14:42] <willcooke>    the tricky st-icon blur/shadow crash
[14:42] <willcooke>    https://bugzilla.gnome.org/show_bug.cgi?id=788908
[14:42] <willcooke>  · Fixed a memory leak in mutter
[14:42] <willcooke>    https://bugzilla.gnome.org/show_bug.cgi?id=789227
[14:42] <willcooke>  · Renamed mutter API get_flatpack_id into
[14:42] <willcooke>    get_sandboxed_app_id (and updated gnome-shell)
[14:42] <willcooke>    https://bugzilla.gnome.org/show_bug.cgi?id=789277
[14:42] <willcooke>  · Found a way to debug crashes with proper C and JS backtrace
[14:42] <willcooke>    got from a gdb session launched from a normal terminal and
[14:42] <willcooke>    updated the GNOME wiki accordingly (https://is.gd/tddLmH)
[14:42] <willcooke>  · Made patches to make gnome-shell to report better debugging
[14:42] <willcooke>    infos on crashes (pointing out the bad JS code too)
[14:42] <willcooke>    https://bugzilla.gnome.org/show_bug.cgi?id=789237
[14:42] <willcooke>    and added functions to toggle such debugging from looking glass
[14:42] <willcooke>    https://bugzilla.gnome.org/show_bug.cgi?id=789377
[14:42] <willcooke>  · Triaging/debugging lots of various top-bugs in errors.u.c and
[14:42] <willcooke>    some GNOME upstream patches reviews
[14:42] <willcooke>  · Got nextcloud-client to the ubuntu snap store with automatic
[14:42] <willcooke>    travis deploy (edge) on new git revisions
[14:42] <willcooke>    https://github.com/nextcloud/client_theming/pull/215
[14:42] <willcooke>  · Fixed dash-to-panel extension that was causing gnome-shell
[14:42] <willcooke>    to crash https://github.com/jderose9/dash-to-panel/pull/263
[14:42] <willcooke>  · Last week here before 2 weeks of offline-vacation in Cuba!
[14:42] <willcooke> 🌴
[14:43] <willcooke> #topic robert_ancell
[14:43] <willcooke> - Short week - public holidays in NZ
[14:43] <willcooke> - GNOME Software snap bug diagnosing / fixing
[14:43] <willcooke> #topic AOB
[14:43] <willcooke> jbicha, want to remind us about the new package and the background there?
[14:44] <jbicha> LP: #1726093 doesn't need a MIR, it's a request for the ubuntu-desktop package to recommend a package to help traditional menu GNOME Shell extensions
[14:45] <jbicha> (& sru that to artful)
[14:46] <willcooke> I think adding it for 18.04 makes sense
[14:46] <willcooke> anyone got any thoughts about SRUing it?
[14:46] <willcooke> or general comments
[14:47] <didrocks> no objection for me
[14:48] <willcooke> oki, sounds like agreement then, but we can discuss more after the meeting if that's the not case
[14:48] <willcooke> any more for any more?  Going in 10...
[14:48] <willcooke> thanks all
[14:48] <willcooke> #endmeeting
[14:48] <meetingology> Meeting ended Tue Oct 24 14:48:56 2017 UTC.
[14:48] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2017/ubuntu-desktop.2017-10-24-14.30.moin.txt
[14:49] <didrocks> thanks!
[14:49] <seb128> sorry, got sidetracked
[14:49] <seb128> no objection from me to the gmenu gir
[14:49] <seb128> it's a small integration piece
[14:49] <didrocks> (and already in main)
[14:51] <Laney> sure, that seems good
[14:51] <Laney> is it the only case of this problem?
[14:52] <Laney> to put it differently - what happens when the next gir is required?
[14:52] <Laney> might be an upstream report for a better dependency mechanism :-)
[14:52] <Laney> gmenu seems to solve most of the cases we have now
[14:52] <jbicha> some system monitor extensions require gir1.2-gtop-2.0 like https://tracker.debian.org/pkg/gnome-shell-extension-system-monitor
[14:55] <jbicha> gmenu and gtop are the only 2 major ones I am aware of that aren't already pre-installed
[14:56] <Laney> I suppose people avoid writing extensions that rely on external stuff because there's no way to request it
[14:57] <didrocks> would make sense
[14:57] <Laney> maybe it would be terrible if they could :-)
[14:58] <didrocks> well, I wonder how bad you can hack a system via any extensions, what's the extense of the API you have access to
[14:59] <Laney> suppose you get most dangerous shit via glib already
[14:59] <seb128> it could make sense to have a way for them to declare depends
[15:00] <seb128> but not have any packaging management around
[15:00] <seb128> just not load/install the extension if the depends is missing
[15:00] <seb128> and maybe get a way to tell the user that it can't be installed because libbla.so is not installed on the system
[15:00] <Laney> like catch a failed import or something
[15:01] <seb128> yeah, ideally
[15:01] <seb128> maybe have a "check_requirement" function that does the imports/etc and report true/false
[15:01] <seb128> or I don't know
[15:02] <seb128> probably a "nice to have" that we are not going to be able to have resources to work on this cycle
[15:04] <didrocks> would make sense, especially for people installing extensions now from gnome-software
[15:09] <Laney> https://bugzilla.gnome.org/show_bug.cgi?id=789414
[15:10] <Laney> didrocks: hey, thanks for your g-c-c crash fix upload, got some small feedback on it for you - do you want them on irc or in the bug?
[15:12] <didrocks> Laney: as you prefer, here is fine
[15:12] <didrocks> you wanted to reuse the G_*_SWAPPED I guess?
[15:12] <didrocks> but I prefered to keep the delta small
[15:12] <didrocks> and redo that part next cycle
[15:12] <Laney> no, don't point that out to me, I didn't notice it :P
[15:12] <didrocks> ahah ;)
[15:12] <Laney> "you're here about the murder, officeR?"
[15:13] <Laney> *puts away your lost wallet that he found, gets out handcuffs*
[15:13] <didrocks> heh
[15:13] <didrocks> (still something to do next cycle, to simplify callback parameters for _ext)
[15:14] <Laney> ++ g_signal_connect_object (iconsize_adj, "value_changed",
[15:14] <Laney> I think that signal is called value-changed
[15:14] <Laney> (pre-existing issue?)
[15:14] <didrocks> hum, pre-existing issue, I'm surprised it works then
[15:15] <Laney> and on one of the _connect_object calls you pass NULL as the gobject, I think that means it doesn't get disconnected
[15:15] <Laney> it should be the thing to watch even if the callback doesn't use it
[15:15] <Laney> iiuc
[15:16] <didrocks> Laney: ah, true on the NULL one. yeah, on the other one, I don't think it's the callback as I'm updating the gsettings key on that callback, but yeah, worth a look
[15:18] <didrocks> I'll stage the fixes and simplification for bionic already
[15:18] <Laney> neat
[15:18] <didrocks> thx for looking!
[15:18] <Laney> do the widgets get destroyed when you switch away from the panel?
[15:18] <Laney> thanks for the fix!
[15:19] <didrocks> Laney: not immediately, I didn't check more but didn't find in an empiric way when they are disposed
[15:19] <didrocks> should probably look at the code for this, but I guess anyway those fixes were needed
[15:20] <bschaefer> hello, having some fun issues with not being able to log into a tty/vt? (log in and it auto kicks me off?) Happened with a recent update ~last month i would say
[15:20] <seb128> didrocks, btw I just tried, valgrind throws invalid read errors when playing with the settings and swithcing panels
[15:20] <seb128> I'm going to try again latter and check with your patch
[15:20] <Laney> seb128: any panel or the dock one?
[15:20] <seb128> see if that resolves those
[15:20] <seb128> Laney, dock
[15:20] <Laney> ah
[15:20] <seb128> which is what I was trying
[15:21] <seb128> maybe others have the issue as well though
[15:21] <seb128> I'm going to valgrind a bit more later
[15:21] <Laney> I guess you could check this bug by changing the gsettings after switching off the panel
[15:21] <seb128> just did a round on gnome-software and reported 2 invalid read bugs, next g-c-c, then calendar :p
[15:21] <seb128> right
[15:21] <seb128> I'm going to play a bit more with that
[15:22] <didrocks> thx! back in the old days, with you playing with valgrind and others fixing :)
[15:22] <seb128> lol, you got me :p
[15:22] <seb128> I can try helping fixing a few of those
[15:22] <seb128> but I'm less good than you guys with those async/callback/signal issues :-)
[15:23] <seb128> k, on that note I need to go and pick up the little one
[15:23] <seb128> back in half an hour, see you there or tomorrow
[15:24] <Laney> yeah doing ^- makes a critical happen
[15:24] <Laney> see you seb128
[15:40] <didrocks> actually, there is no good reason to use _SWAPPED, so straighforward fix
[15:41] <Laney> :3
[15:44] <willcooke> hi bschaefer, that's an odd one
[15:45] <willcooke> bschaefer, you can log in to a desktop session ok?  And a terminal inside that desktop sesson?
[15:45] <bschaefer> willcooke, yeah my sessions just fine, its just when i try to log into vt/tty
[15:45] <bschaefer> ive yet to try ssh'ing
[15:45]  * bschaefer tries
[15:45] <Laney> anything in the journal?
[15:46] <bschaefer> Laney, i just see a tty3stop/start
[15:46] <bschaefer> Oct 24 08:21:31 bschaefer-ThinkPad-T450s systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart.
[15:46] <bschaefer> Oct 24 08:21:31 bschaefer-ThinkPad-T450s systemd[1]: Stopped Getty on tty3.
[15:46] <bschaefer> Oct 24 08:21:31 bschaefer-ThinkPad-T450s systemd[1]: Started Getty on tty3.
[15:46] <bschaefer> willcooke, yeah i cannot ssh anymore .. access denied
[15:46] <willcooke> ?!
[15:46] <bschaefer> was looking at the Xauth...
[15:46] <bschaefer> and its in a different spot now but ... it seemed valid
[15:47] <willcooke> bschaefer, on 17.10?  And Wayland?
[15:47] <bschaefer> willcooke, 17.10 using ubuntu xorg
[15:47] <Laney> nothing before that?
[15:47] <bschaefer> Laney, yeah let me post the log not sure whats bad/good :)
[15:47] <Laney> I venture this isn't a desktop specific problem but let's see ;-)
[15:48] <bschaefer> Laney, i have ... a rough machine ive somehow kept together since 15.10 upgrading manually :)
[15:48] <bschaefer> Laney, http://paste.ubuntu.com/25810354/
[15:48]  * bschaefer suspects something ... with his overall setup
[15:49] <bschaefer> all i can see is pam seems to close it
[15:49] <bschaefer> but not a why or i dont see errors
[15:50] <Laney> is repowerd still a relevant thing?
[15:50] <bschaefer> hmm no, let me remove it
[15:50] <Laney> some weird messages from it there
[15:51] <mgedmin> bschaefer: what's your shell, according to /etc/passwd?
[15:52] <bschaefer> o actually yeah thats the issue... i has zh
[15:52] <bschaefer> but changed it back
[15:52] <bschaefer> bschaefer:x:1000:1000:bschaefer,,,:/home/bschaefer:/bin/zsh
[15:52] <bschaefer> but it still thinks its the shell?
[15:52] <bschaefer> vs /bin/bash (using chsh to change it)
[15:52] <bschaefer> i would suspect thats the issue (is it'll try /bin/zsh and it wont be there)
[15:53] <Laney> o rite
[15:53] <Laney> I thought you were getting a timeout
[15:53] <bschaefer> that was with ssh... could be a different issue :)
[15:53] <bschaefer> i login, then kicks me right away
[15:54] <Laney> good one mgedmin
[15:54] <bschaefer> mgedmin, there we go, thanks!
[15:54] <bschaefer> strangely i used chsh to change to zsh but i guess it didnt like changing back to bash...
[17:39] <willcooke> night all
[19:23] <oSoMoN> nighty night