[05:26] <jibel> morning
[06:09] <oSoMoN> good morning desktoppers!
[06:19] <duflu> Morning jibel, oSoMoN
[06:20] <oSoMoN> good afternoon duflu
[06:21] <oSoMoN> salut jibel
[06:27] <didrocks> good morning
[06:32] <duflu> Morning didrocks
[06:32] <didrocks> hey duflu
[06:33] <didrocks> duflu: I commented on the gdm bug, I wonder if the patch to revert the priority list was what triggered the bug
[06:33] <didrocks> like 2 lists that aren't synced
[06:33] <didrocks> did you see any cases where the selected session didn't work out now with new gdm?
[06:33] <didrocks> (I didn't/couldn't test enough yet to be certain)
[06:34] <duflu> didrocks, Oh I didn't see. Yes it sounds like things aren't synced. Possibly the real list that gets used if the popup never appeared is a different order to the popup GUI list
[06:34] <ricotz> hey desktopers :)
[06:35] <ricotz> afaics eog-plugins is suppose to pull in all plugins after the split, but it doesnt depend on any
[06:37] <didrocks> hey ricotz
[06:37] <ricotz> didrocks, hi
[06:39] <duflu> didrocks, bonus though - my upstream fix remains because it was independent of your change :)
[06:39] <oSoMoN> good morning didrocks, ricotz
[06:39] <didrocks> duflu: your upstream fix? sorry, didn't follow along
[06:39] <didrocks> hey oSoMoN!
[06:40] <duflu> didrocks, my old upstream gdm fix for Wayland sessions. Twas triggered by your change (now removed) but I designed the upstream fix to not conflict. So no merge problems
[06:40] <ricotz> oSoMoN, hi, something went wrong here? https://launchpad.net/ubuntu/+source/libreoffice/1:5.4.0-0ubuntu1
[06:41] <duflu> TLDR - everything is good
[06:42] <duflu> Maybe there's another upstream ordering bug but we might have just worked around it, so hopefully won't notice any more
[06:43] <didrocks> duflu: ah nice, so let's see ;)
[06:48] <oSoMoN> ricotz, ever seen this "Build for superseded Source" message? I haven't
[06:52] <oSoMoN> I guess we'll have to wait for seb to get online to shed some light on this
[06:54] <ricotz> oSoMoN, yeah, no idea, looks like the packages built, but the source never made it into the archive which seems to be the reason to reject the binaries
[07:13]  * didrocks restarts, brb
[07:18] <oSoMoN> good morning seb128, do you know what happened with https://launchpad.net/ubuntu/+source/libreoffice/1:5.4.0-0ubuntu1 ?
[07:19] <seb128> good morning desktopers
[07:20] <seb128> oSoMoN, yes, I screwed, I didn't find a .changes so I tried to copy-ppa instead of dputing but turns out you need to send to artful-proposed and not artful like for uploads, there is no redirection for copies
[07:20] <seb128> so I directly put the update to artful
[07:20] <seb128> deleting the old version
[07:20] <seb128> then I try to revert/go back to what we had
[07:20] <seb128> but I think didn't fully worked out
[07:20] <oSoMoN> do we need a 1:5.4.0-0ubuntu2 to fix things?
[07:20] <seb128> I ended up going to bed and letting things to be sorted out this morning
[07:21] <seb128> oSoMoN, that would be nice, with a .changes I can dput this time would even be better
[07:26] <seb128> hum
[07:27] <seb128> so post updates (few days pending) logout/login logged me into a GNOME session (like adwaita theme)
[07:27] <seb128> where I was using ubuntu wayland
[07:28] <seb128> brb, restarting in an ubuntu one
[07:31] <seb128> bah, Ubuntu Wayland is what is selected in gdm
[07:31] <seb128> but that's not what it gives me :/-
[07:31]  * seb128 looks at didrocks 
[07:31] <didrocks> seb128: still the gdm bug
[07:31] <didrocks> maybe?
[07:32] <seb128> I though it would be fixed once wayland is default?
[07:32] <didrocks> what made you think it will be fixed?
[07:32] <seb128> what I understood from the irc conversation
[07:32] <didrocks> it may be fixed, that's why I infer, and should be tested afterwards
[07:32] <seb128> so probably just misunderstanding from my side
[07:32] <didrocks> and I told it didn't deserve more testing before reverting that change
[07:32] <didrocks> you are welcome to debug…
[07:33] <didrocks> you know I've been slacking all the time for the past weeks/months
[07:33] <didrocks> and that I'm not doing anything either today…
[07:33] <didrocks> so, I clearly have time to debug that before FF, because all other features are on their way, correct?
[07:33] <oSoMoN> seb128, I had a similar issue earlier this morning, my session abruptly closed under me, and when I logged back in, I was in a gnome session instead of ubuntu
[07:33] <didrocks> also, as I have extra time, I'm please to have this alt regression that starts to occurs after upgrade
[07:33] <seb128> waouh, starting easily this morning
[07:34] <didrocks> seb128: not pleasant after working 50h+ to be told "looks at you"
[07:34] <didrocks> like "what have you done?"
[07:34] <seb128> didrocks, it was not meant as a criticism
[07:34] <didrocks> sounded like it
[07:35] <didrocks> and the "I though it would be fixed once wayland is default?"
[07:35]  * didrocks looks at logs
[07:35] <didrocks> as it's the only thing that matter now
[07:35] <seb128> sorry it was not meant that way
[07:35] <seb128> it was an honest question
[07:35] <didrocks> seb128: also, unsure why this is on me
[07:35] <oSoMoN> seb128, I’m preparing a 1:5.4.0-0ubuntu2, and I’ll use that to enhance the changelog with more details about new build deps and runtime deps
[07:35] <didrocks> anyone can also look at it?
[07:35] <didrocks> don't think I introduced this bug…
[07:36] <seb128> didrocks, it's not, don't get started the wrong way
[07:36] <seb128> it's just a bug
[07:36] <didrocks> well, we have a lot of those
[07:36] <seb128> I mentioned your name because we discussed it a few weeks back
[07:36] <seb128> right
[07:36] <didrocks> the "looks at" isn't the right way to mention anyone's name
[07:37] <didrocks> also, do you have this alt + left/right key triggering tty changes?
[07:37] <seb128> oSoMoN, thanks, but just do what is the easiest, the archive is screwed so we need the new version uploaded
[07:37] <seb128> didrocks, that was meant as some teasing, sorry it went the wrong way
[07:37] <seb128> :-(
[07:38] <seb128> no, alt-left/right changes channels in hexchat here
[07:38] <seb128> I've the current console-setup from x_nox with the upstart job removal
[07:38] <seb128> but I only session restarted, not rebooted
[07:38] <didrocks> sorry to have taking in that way, but I would like to have a working machine first to be able to work, as there is now this indicator thing to be done ASAP (and could have been anticipated)…
[07:38] <didrocks> ah
[07:38] <seb128> let me reboot
[07:38] <didrocks> maybe it's because you didn't reboot
[07:38] <didrocks> thanks
[07:42] <seb128> didrocks, oSoMoN, session fixed after reboot
[07:42] <seb128> gdm wasn't restart and the list of session between ui and disk was out of sync I think
[07:42] <didrocks> oh, you didn't restart gdm?
[07:42] <didrocks> so, didn't revert the gdm patch
[07:42] <seb128> it had gnome/gnome wayland/ubuntu/ubuntu wayland with ubuntu wayland selected
[07:42] <seb128> right
[07:42] <didrocks> and gdm doesn't reload the list dynamically
[07:42] <seb128> now after reboot it has "on xorg"
[07:42] <didrocks> yeah
[07:43] <seb128> right
[07:43] <didrocks> ok, at least, it's still **potentially** fixed
[07:43] <seb128> alt-left/right still switch hexchat channels
[07:43] <didrocks> grrr, I had a debconf question
[07:43] <didrocks> kept the default
[07:43] <didrocks> to switch keyboard layout
[07:43] <didrocks> and then rebooted
[07:43] <didrocks> and now, I can't do anything useful with alt :(
[07:44] <didrocks> I tried wayland and xorg (currently back to xorg)
[07:44] <seb128> try to maybe dpkg-reconfigure console-setup
[07:45] <seb128> I didn't have a debconf session
[07:45] <didrocks> tried this
[07:45] <didrocks> you have multiple keyboard layout, correct?
[07:47] <didrocks> sounds quite common: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146
[07:48] <seb128> I've fr and en
[07:48] <Tribaal> hi all! Just switched to wayland, and it mostly seems to work, except my touchpad now misses a "right click" possibility. How can I help debug/fix?
[07:49] <Tribaal> (the touchpad has physical clicks when depressed bottom left or bottom right. The bottom right click registers as "main" click as well)
[07:58] <didrocks> succeeded in disabling alt + arrow keys thx to a workaround on that post, but weechat still not working on alt + number to switch channels
[08:00] <didrocks> seb128: if you set a shortcut in gnome-terminal, like "switch to tab x" to alt + 1, what do you get printed?
[08:00] <didrocks> I only have "1" printed
[08:00] <didrocks> (and then, crash)
[08:02] <Laney> moinoinoin
[08:02] <willcooke> morning all
[08:03] <didrocks> hey Laney, willcooke
[08:06] <Laney> hey willcooke hey didrocks
[08:06] <Laney> what's up
[08:07] <didrocks> trying to understand why after today's update, alt + number doesn't work on my weechat
[08:07] <didrocks> otherwise good
[08:07] <didrocks> yourself?
[08:07] <Laney> what got updated?
[08:07] <Laney> yeah i'm okay
[08:08] <didrocks> a bunch of things, didn't update yesterday
[08:08] <didrocks> or rather, reboot between updates
[08:08] <didrocks> first was alt + arrow keys shifted me to tty
[08:08] <didrocks> (sounds like a repeated regression)
[08:08] <Laney> been there
[08:08] <didrocks> and now, everything "works" apart from alt + number (that I only use in weechat, unsure what else is using this)
[08:09] <Laney> is it going to the terminal emulator itself?
[08:09] <didrocks> alt + j + numbers works for higher buffer
[08:09] <didrocks> Laney: unsure, this is the issue
[08:09] <didrocks> how could I konw?
[08:10] <Laney> something like xev but in the terminal
[08:10] <Laney> then press the keys and see if they get to it
[08:11] <Laney> or check the keybinding list and see if "switch to tab N" got remapped back by a bug ;-)
[08:11] <didrocks> Laney: well, xev isn't in the terminal, which is my issue…
[08:11] <didrocks> but in xev, I see the 4 events, of course
[08:11] <Laney> yes
[08:11] <didrocks> which isn't the terminal env :p
[08:12] <Laney> not xev itself of course
[08:12] <didrocks> I checked the keybinding list, nothing…
[08:12] <Laney> something that does that kind of thing but in a terminal
[08:12] <didrocks> I don't know of any, do you?
[08:12] <Laney> I would have to research
[08:13] <didrocks> how did you fix the alt + left/right btw? Just the workaround to reflush? As it happened again for multiple people, we should fix it the right way IMHO
[08:13] <Laney> I didn't have it on this laptop I don't think
[08:14] <didrocks> but on the other one, when you got it? Did you change anything in the archive or workarounded it locally? (just curious)
[08:14] <Laney> I think I remember finding an upstream bug that described what I had
[08:15] <Laney> but probably just rebooted to fix it
[08:15] <Laney> did talk about it on  IRC at the time
[08:15] <seb128> hey Laney willcooke
[08:15] <didrocks> interesting, so alt + number works in other apps
[08:15] <didrocks> but terminal
[08:15] <didrocks> I didn't get any g-t update though
[08:17] <Laney> hey seb128
[08:17] <Laney> how's it going?
[08:17] <seb128> good! though I screwed artful yesterday night :-/
[08:17] <Laney> my phone battery sucks these days
[08:17] <Laney> 84% and I only read a few news articles
[08:17] <seb128> turns out that copy-package to artful isn't a good idea
[08:17] <Laney> oho
[08:17] <seb128> it doesn't redirect to proposed
[08:17] <seb128> so I sent libreoffice directly to artful
[08:17] <Laney> yeah archive admins and release team don't have the safety net there
[08:17] <seb128> then tried to demote-proposed and copy back the old version
[08:18] <seb128> but that failed
[08:18] <seb128> so artful has no libreoffice-l10n atm
[08:18] <Laney> there's weird bugs around operating on the same package with copies
[08:18] <Laney> you have to sometimes wait a publisher cycle
[08:18] <oSoMoN> seb128, https://people.canonical.com/~osomon/libreoffice-5.4.0/
[08:18] <Laney> not sure when exactly
[08:18] <seb128> oSoMoN, thanks
[08:20] <Laney> did you try something like "copy-package --from=ubuntu --to=ubuntu --from-suite=artful --force-same-destination --include-binaries --version=1:5.3.4-0ubuntu1 libreoffice-l10n"?
[08:20] <seb128> $ ./copy-package -b --from=ubuntu -s artful --to=ubuntu --force-same-destination -e  1:5.3.4-0ubuntu1 libreoffice-l10n
[08:20] <seb128> is what I tried
[08:20] <seb128> the same command worked for libreoffice itself
[08:20] <Laney> just errored?
[08:21] <seb128> I didn't get an error or anything for l10n
[08:21] <seb128> it said it was copying
[08:21] <seb128> but I never saw a result
[08:21] <Laney> weird
[08:21] <Laney> maybe launchpad guys can look in the logs
[08:21] <Laney> that's the same command I just pasted which I think is right
[08:27] <didrocks> ok, workarounded for now with alt + number-without-shift remapping in weechat
[08:29] <seb128> didrocks, did you try downgrading console-setup to make sure it's the one creating the issue?
[08:30] <didrocks> tried it
[08:30] <didrocks> didn't work, even after reboot
[08:30] <didrocks> and in the same length, Alt + Ctrl + Shift + up/down doesn't work
[08:30] <didrocks> I wonder if the issue isn't related to alt + shift
[08:33] <didrocks> I guess my best bet would be to list all debconf database
[08:34] <jibel> didrocks, with today's iso the theme is not right when you select 'install ubuntu'
[08:34] <jibel> didrocks, it's a light theme
[08:36] <didrocks> jibel: ah, that's what I expected
[08:36] <didrocks> jibel: ok, will get to it just after FF
[08:36] <didrocks> (I guess it was already in yesterday's image though)
[08:37] <seb128> jamesh, hey, did you see my msgs about connectivy portal?
[08:38] <jibel> didrocks, and after installation it's x11, did the change to default to wayland landed on time for this build?
[08:38] <jibel> apparently so
[08:40] <didrocks> jibel: an, this one is interesting
[08:40] <didrocks> anyway, log bugs, we will need to get through them whenever we can
[08:46] <seb128> oSoMoN, ricotz, libreoffice situation should be sorted out, restore old packages in artful and got the new ones in artful-proposed
[08:46] <seb128> oSoMoN, thanks for the packages ready to sponsor
[08:46] <didrocks> and another keyboard reconfigure (setting something else, and reresetting worked)
[08:46] <didrocks> phew
[08:47] <seb128> didrocks, \o/
[08:47] <didrocks> seb128: still annoying though we get things like this :/
[08:47] <didrocks> seb128: ok, so back to business
[08:47] <didrocks> appindicators
[08:47] <didrocks> do we have a great default apps using it that I can test/showcase?
[08:49] <seb128> transmission
[08:49] <seb128> vino
[08:50] <seb128> tomboy but it's not default
[08:51] <didrocks> will give it a try with transmission
[08:55] <flexiondotorg> Morning Desktopers
[08:57] <didrocks> seb128: anything needed to be done for transmission? Downloading an iso, no appindicator
[08:57] <didrocks> I got the second "pulseaudio" indicator though
[08:57] <seb128> hey flexiondotorg
[08:58] <seb128> didrocks, maybe the extension is not working?
[08:58] <seb128> try with the appindicator tool binary?
[08:58] <didrocks> seb128: well, it should work, or I wouldn't have had the second pulseaudio icon I think
[08:58] <didrocks> but let's try with the tool
[08:59] <seb128> didrocks, tomboy otherwise?
[08:59] <didrocks> hum, install mono for one test? :p
[08:59] <seb128> good point
[08:59] <didrocks> finding the appindicator tool…
[09:01] <seb128> didrocks, try installing indicator-keylock otherwise
[09:01] <didrocks> installed, should I get anything after running it?
[09:02] <didrocks> oh right
[09:02] <didrocks> num lock
[09:02] <didrocks> works
[09:02] <didrocks> so transmission may be broken?
[09:02] <didrocks> Trevinho: mind testing transmission with appindicator extension? ^
[09:03] <didrocks> not sure it's wise to add indicator-keylock as an example
[09:03] <Trevinho> didrocks: ok
[09:03] <didrocks> hey Trevinho ;)
[09:03] <Trevinho> hi didrocks
[09:03] <Trevinho> and seb128
[09:03] <didrocks> Trevinho: with what applications are you testing generally btw?
[09:03] <Trevinho> and others :)
[09:03] <didrocks> like? Anything interesting for an example ?
[09:03] <seb128> (in an hangout but looking more after)
[09:04] <didrocks> and I need to find why having online source in pulseaudio shows up in the indicator
[09:04] <Trevinho> didrocks: I've been using the example app from libappindicaotor with some random hacks, qt systray apps...
[09:04] <didrocks> Trevinho: is it the same for you? ^
[09:04] <Trevinho> and electron apps with forced desktop
[09:04] <didrocks> could use clementine
[09:04] <didrocks> as an example
[09:17] <didrocks> Trevinho: is that expected that if I remove indicator-application, kill the user service, then indicator-keylock still shows up in the indicator part?
[09:17] <didrocks> I was thinking that we'll need to reseed indicator-application but I'm unsure now (or was that just for unity panel proxy and the extension doesn't use it?)
[09:17] <Trevinho> didrocks: no,indicator-application isn't needed at this point.
[09:18] <Trevinho> didrocks: the extension create the dbus server to the applications will connect to now
[09:18] <didrocks> ok, that was the unity proxy
[09:18] <didrocks> great!
[09:18] <didrocks> Trevinho: keep us posted for transmission
[09:19] <Laney> OH
[09:20] <Laney> i have the alt-arrows bug too!
[09:20] <didrocks> do we get any badge?
[09:20] <didrocks> or need to create a launchpad team
[09:21] <Laney> this is annoying when you use a tiling terminal
[09:21] <Laney> that's how you switch between them :P
[09:22] <didrocks> yeah, and I guess you are not affecting with alt + numbers because you don't need to use the shift keys
[09:22] <didrocks> even after reconfiguring, it's funky
[09:22] <didrocks> like alt + shift + number works
[09:22] <didrocks> (in order)
[09:22] <didrocks> but shift + alt + number doesn't
[09:24] <Laney> azerty
[09:24] <didrocks> well, software bug :p
[09:24] <didrocks> used to work
[09:25] <Laney> zorks for ,e
[09:25] <Laney> sorry1
[09:25]  * Laney added azerty
[09:25] <didrocks> ;)
[09:25] <oSoMoN> :)
[09:25] <Laney> alt-shift-1234567890 and shift-alt-1234567890 work properly
[09:25] <didrocks> how do you test?
[09:25] <Laney> irssi
[09:26] <didrocks> interesting, I doubt weechat regressed without updating
[09:26] <didrocks> but there is clearly something wrong in this console-conf update (or something wrong for a long time triggered by this update)
[09:27] <seb128> Laney, so the pocket copy worked yesterday but it was in sourceNEW and nothing told me
[09:27] <Laney> oho
[09:27] <seb128> Laney, I noticed this morning when I went to review something else
[09:28] <Laney> https://bugs.launchpad.net/launchpad/+bug/830614
[09:28] <didrocks> oh great, deja-dup update removed all my server settings for backing up
[09:28] <didrocks> quality©
[09:28] <Laney> ah, we just missed its bug birthday!
[09:29] <didrocks> (and reverted to cloudnext)
[09:31] <seb128> Laney, thanks
[09:32] <Laney> guessing that it's not going to be fixed any time soon ;-)
[09:33] <seb128> didrocks, there is a migration code but maybe you need to restart
[09:34] <didrocks> seb128: for deja-dup?
[09:34] <seb128> yes
[09:34] <didrocks> I did update on Friday
[09:34] <didrocks> and rebooted multiple times since
[09:35] <didrocks> I don't have the nautilus entries anymore, just "network server"
[09:37] <didrocks> so, reentered manually the address
[09:38] <seb128> :-/
[09:38] <seb128> mteeeerry
[09:41] <Laney> just reinstalling console-setup makes this bug happen
[09:42] <Laney> probably something the postinst does
[09:44]  * Laney knows what it is
[09:44] <andyrock> jbicha: mooorning
[09:44] <andyrock> jbicha: sorry for the ping :D
[09:45] <seb128> hey andyrock, how are you?
[09:45] <Laney> elif [ -d /lib/debian-installer ] || \
[09:45] <Laney>      expr "$(fgconsole 2>/dev/null || true)" : '[1-6]$' >/dev/null; then
[09:45] <Laney>     setupcon --force
[09:46] <Laney> guess what the fgconsole is now that it wasn't before
[09:46] <Laney> :)
[09:46] <andyrock> hey seb128 good good
[09:52] <Laney> this is an ubuntu delta
[09:52] <Laney> weird
[09:56] <Laney> cyphermox: xnox: can you halp with this console-setup thing?
[09:56] <xnox> Laney, what's up?
[09:56] <Laney> setupcon --force is now running because we have gnome-shell on vt2
[09:56] <xnox> argh
[09:56] <Laney> which is breaking that condition I just pasted up there
[09:57] <Laney> what's the right way out?
[09:57] <Laney> ask logind what's running on that vt?
[09:57] <Laney> or, what's this bit of delta for and is it still necessary?
[09:57] <xnox> that sounds reasonable. (logind)
[09:58] <xnox> yeah, no clue, need to dig into history to find that out
[09:58] <xnox> also i'm not sure if that is relevant anymore
[09:58] <xnox> also 1-6 bit looks odd to me
[09:58] <Laney> seems like it might be a bit crusty
[10:02] <Laney> https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/93338
[10:03] <Laney> old skool
[10:08] <Trevinho> didrocks: transmission, once i enabled the icon in settings it's working to me..
[10:11] <seb128> didrocks, Trevinho, oh right it's a setting, I though that was enabled by default
[10:12] <Trevinho> I've to say that the setting doesn't seem to work well when toggled
[10:12] <Trevinho> so it might be something to look at anyway
[10:14] <jamesh> seb128: sorry, missed your ping.  I've got a patch ready.  I don't think I've got access to our network-manager packaging git repo, but I can send you the patch.
[10:16] <Laney> hey jamesh
[10:16] <jamesh> hi Laney
[10:16] <Laney> you good?
[10:17] <jamesh> yes.
[10:18] <Trevinho> didrocks, seb128: I guess that the setting was somewhat enabled by default in unity.. But not sure.
[10:18] <Trevinho> anyway indeed there's a problem when toggling it, so I'll look into that too
[10:22] <seb128> jamesh, that would nb
[10:22] <seb128> jamesh, that would be good thanks
[10:22] <jamesh> seb128: I've just emailed you the patch (this is against the network-manager/ubuntu repo, with the other packaging changes
[10:22] <seb128> thx
[10:31] <flexiondotorg> I was testing isos last night, no DNS resolution in the daily images. Can other desktopers confirm?
[10:32] <Laney> See #ubuntu-devel, it's being worked on atm
[10:32] <Laney> flexiondotorg:
[10:33] <flexiondotorg> Laney ty
[10:34] <jamesh> oSoMoN: btw, I started a conversation about the fonts issue with snaps yesterday: https://forum.snapcraft.io/t/desktop-allow-access-to-host-system-fonts/1796
[10:36] <jamesh> oSoMoN: I think we can get this supported in one of the existing interfaces so it eventually just works for all apps
[10:38] <oSoMoN> jamesh, thanks, I'll be following that conversation closely
[10:51] <seb128> back
[10:53] <seb128> Trevinho, andyrock, so I was wondering how doable it would be to use the same "source" (which I guess is libmessaging-menu) that unity was using to make the dock displays unread-count indications
[10:55] <Trevinho> seb128: no that wasn't libmessaginmenu
[10:56] <Trevinho> seb128: applications interacting with launcher were using libunity...
[10:56] <Trevinho> or just simple dbus (they only have to implement an interface of the c.c.Unity.Launcher) that gives infos such as `{'count': 2551L, 'urgent': False, 'progress-visible': False, 'count-visible': True, 'progress': 0.0}`
[10:57] <Trevinho> seb128: anyway... implementing that shouldn't be hard
[10:58] <Trevinho> maybe together with defining a new API that could other apps using without relying in libunity later
[10:58] <seb128> right
[10:58] <seb128> having a proper API would be nice, that's going to take more time though
[10:59] <Trevinho> well, I think our API is already fine... just adding an alias to something like com.ubuntu.Launcher maybe or something even more generic
[10:59] <Trevinho> or.. .actually there were already some efforts fore that
[11:01] <Trevinho> seb128: so dockmanager API was defined some years ago... we could just tell people to use that in future, as it's basically compatible already
[11:01] <Trevinho> http://wiki.go-docky.com/index.php?title=Writing_Helpers#DockManager_DBus_Interface_Specification
[11:02] <seb128> Trevinho, that would be nice
[11:02] <Trevinho> so together with implementing the libunity one, we can support both
[11:02] <Trevinho> it shouldn't be too much effort (if we already want one)
[11:05] <ricotz> Trevinho, hmm
[11:06] <ricotz> Trevinho, I didn't even came around to add dockmanager support to plank, since I was outruled by LauncherEntry
[11:10] <seb128> Trevinho, well, if andyrock wants to look at that I wouldn't say no :-)
[11:11] <andyrock> seb128: kk I'll take a look
[11:11] <Trevinho> ricotz: yeah... well, we can still support both, or just rename that as something less unity-dependent
[11:12] <Trevinho> sure :)
[11:27] <andyrock> seb128: do you know the url of the xenial branch of update-notifier? I cannot find it under https://code.launchpad.net/update-notifier
[11:27] <seb128> andyrock, I'm not sure there is one
[11:28] <andyrock> so do I need to send the debdiff on the bug to SRU it later on?
[11:29] <seb128> yes
[11:31] <andyrock> kk
[11:47] <ricotz> Trevinho, are you aware of any dockmanager API user besides docky?
[11:48] <ricotz> let me rephrase, ... any maintained application?
[11:49] <Trevinho> ricotz: i thought plank was using it, but if not..... well then no.
[11:50] <ricotz> Trevinho, I see, I remember awn and docky
[11:50] <Trevinho> ricotz: also cairo dock was, but yeah... nothing really in use
[11:51] <ricotz> so renaming the unity LauncherEntry interfaces to something more generic seems reasonable
[11:51] <Trevinho> ricotz: we can still continue in keeping our APIs just supporiting a more unity-less namespace
[11:51] <Trevinho> ok
[11:51] <ricotz> and having a more common trigger-DBus-service
[11:52] <ricotz> e.g. not only "com.canonical.Unity"
[11:52] <Trevinho> agree
[11:53] <Trevinho> maybe the best thing to  do in the new namespace would be getiting rid of dbusmenu for the quiclists, supporing gmenu
[11:53] <Trevinho> but that's a different story
[11:55] <ricotz> having libunity exposing/supporting the gmenu would be great
[11:56] <ricotz> seems better to move this gmenu parser of gnome-shell code into glib or gtk+
[12:09] <Laney> xnox: it got a bit out of hand https://paste.ubuntu.com/25369254/
[12:15] <xnox> Laney, you didn't want to use e.g. $ loginctl --no-legend list-sessions?
[12:15] <xnox> and then parse and do: loginctl show-session c14 | grep Type
[12:15] <xnox> or what not?
[12:16] <xnox> $ loginctl -p Type show-session c14
[12:16] <xnox> Type=x11
[12:16] <Laney> haha
[12:16] <xnox> Laney, i read that as sarcasm as in "silly xnox, no, you see this and that happens when calling loginctl"
[12:16] <xnox> =)
[12:16] <Laney> I didn't fancy parsing that stuff
[12:17] <Laney> but if there's a way to get it in an easy to read way
[12:17] <Laney> that would be better
[12:17] <Laney> it was a journey that led to a strange place
[12:18]  * Laney sees --no-legend
[12:18] <tjaalton> is the keyring known to not work under wayland?
[12:18] <xnox> yeah, but there is still whitespace
[12:19] <Laney> should be ok with awk
[12:21] <xnox> yeah, i'd preffer: loginctl --no-pager --no-legend list-sessions; and then loginctl -p Type show-session $session
[12:21] <xnox> and probably compare != "Type=tty" or some such
[12:22] <xnox> although busctl is nice =)
[12:22] <farhad> sorry to ask here, but in ubuntu channel no body knows this question. is there any way to autohide or remove top panel in ubuntu 16.04? maybe via unity.css file?
[12:30] <GunnarHj> willcooke, seb128: Saw that the trello card "GNOME and fcitx" has been moved to 18.04 proposed, and want to remind of the need to make a decision on the default IM framework for CJKV languages in Ubuntu 17.10.
[12:32] <Laney> xnox: http://paste.debian.net/982518/ ?
[12:34] <GunnarHj> There has been some discussion in the list thread which started with this message:
[12:34] <GunnarHj> https://lists.ubuntu.com/archives/ubuntu-desktop/2017-May/004935.html
[12:34] <xnox> Laney, nice
[12:34] <xnox> me like
[12:35] <Laney> I think I can eliminate the second call
[12:35] <Laney> sec
[12:38] <didrocks> jbicha: hey! Do you plan updating gnome-shell today? I would have another upload in the pipe and would prefer basing it on 2.25.90 design
[12:39]  * Laney stabs sh
[12:56] <didrocks> Trevinho: it was probably a distro patch to set it on by default, it's not a gsetting key
[12:56] <didrocks> (for transmission)
[12:56] <didrocks> the default is hardcoded in code
[12:56] <Trevinho> ah... ok
[12:58] <didrocks> so, we don't really have good examples by default
[12:58] <didrocks> vino isn't going to work on wayland
[12:58] <didrocks> and transmission indicator isn't that interesting
[12:59] <didrocks> (and skype doesn't work yet), I wonder what we can screenshot
[13:00] <didrocks> would revert to the keyload I guess
[13:12] <seb128> jbicha, hey, jam_esh got a n-m debdiff, can you have a look/merge it?
[13:35] <cyphermox> Laney: did you file a bug about this?
[13:35] <Laney> cyphermox: not yet
[13:35] <cyphermox> (your console-setup bug)
[13:35] <Laney> i'll file a bug with patch if you want to review it
[13:35] <cyphermox> sure, ok
[13:35] <Laney> found another bug though
[13:37] <cyphermox> ah?
[13:37] <Laney> run setupcon --force -k in a wayland session
[13:37] <Laney> then it gets into some messed up mode where ctrl-c kills gnome-shell
[13:37] <Laney> /o\
[13:38] <seb128> ah
[13:38] <seb128> so you confirmed that weird bug :p
[13:38] <Laney> sounds like bug #1710637
[13:38] <Laney> but I don't think that's something you run multiple times per day
[13:38] <seb128> that one indeed
[13:38] <cyphermox> well, it's pretty obvious that anything setupcon is likely to break things if run on an X console
[13:38] <Laney> sooooooooooooooooooooooooooooooooooo probably not this
[13:38] <seb128> :-/
[13:38] <cyphermox> that's why X was going to tty7 before...
[13:38] <Laney> the postinst of keyboard-configuration is running this
[13:39] <Laney> not behind any guard or anything
[13:39] <cyphermox> right
[13:39] <Laney> -k doesn't break stuff on x
[13:42] <cyphermox> k attempts to muck with keymaps. Anything like that happening on a console that is used for graphics is kind of wrong
[13:42] <kenvandine> Trevinho, we have a fix submitted for a theme bug I filed, would you mind reviewing it?  https://code.launchpad.net/~c-lobrano/ubuntu-themes/bug-1708141/+merge/328927
[13:43] <Laney> it explicitly calls setupcon --force -k if it sees $DISPLAY
[13:43] <Laney> so this is intentional
[13:43] <cyphermox> (as X or Wayland or whatever else changes the console's mode anyway, and is supposed to handle keys and all by itself
[13:43] <kenvandine> Trevinho, i think it looks fine, but my gtk theme css foo is rusty :)
[13:43] <cyphermox> Laney: sounds like a bug
[13:43] <Laney> ok, feel free to just delete it then
[13:43] <didrocks> jbicha: if you don't plan to update to G-S this week, I can go on with 3.24, but do you mind updating the bzr branch? (it only has -0ubuntu5)
[13:43] <cyphermox> Laney: the fact that it worked before doesn't mean it was correct :)
[13:44] <Laney> it's simpler to delete it than to figure out why it is broken
[13:44] <kenvandine> Trevinho, specifically i think it's consistent with other buttons, so should be fine
[13:46] <Trevinho> kenvandine: yeah I saw them, I just had to test them all :)
[13:46] <cyphermox> Laney: I agree
[13:46] <cyphermox> if we can't figure out whether the console is safe to configure, skip it
[14:00] <Trevinho> anyone can check this for me https://code.launchpad.net/~3v1n0/ubuntu-themes/radiance-headerbar-buttons-fix/+merge/324516 ?
[14:00] <Trevinho> too?
[14:07] <Laney> cyphermox: bug #1712356 - please review
[14:07] <Laney> untested, unbuilt, need to go have lunch :-)
[14:08] <cyphermox> I was just about to suggest /run/systemd/system
[14:08] <cyphermox> AGH
[14:08] <Laney> what
[14:08] <cyphermox> a copy-pasta fail
[14:08] <cyphermox> http://paste.ubuntu.com/25369833/
[14:09] <Laney> that breaks if you're sshed in and someone else is logged into x doesn't it?
[14:10] <cyphermox> no, that checks the current ession
[14:10] <Laney> that's the point
[14:10] <Laney> you need to check any session
[14:10] <cyphermox> hum
[14:13] <cyphermox> won't your patch have the same issue?
[14:14] <Laney> nope, I look at all sessions, check if their tty is the foreground one and if it is type=tty
[14:15] <cyphermox> sure, you look at all sessions, when you run the fg one, you check if it's a tty and then run setupcon
[14:15] <Laney> yep
[14:15] <Laney> that's the intention of the code afaik
[14:16] <cyphermox> you'd break X the same way as my change, if setupcon affects all VTs
[14:16] <cyphermox> the changes are equivalent, AFAICT.
[14:16] <Laney> no they aren't
[14:17] <Laney> you look at the current session of the user that's running the postinst
[14:17] <cyphermox> sure.
[14:17] <Laney> I look at all sessions that anyone has open on the machine at the time
[14:17] <cyphermox> yes; in the for loop of all the sessions, you /find/ the current one. ie.     if [ -n "${vtnr}" ] && [ "${vtnr}" -eq "${FGCONSOLE}" ]; then
[14:17] <Laney> that current one might not be the one that's doing this package upgrade
[14:18] <Laney> you only find it if that is the case
[14:19] <cyphermox> in what case would you not find the session running the upgrade?
[14:21] <Laney> SSH to a machine, run the upgrade, XDG_SESSION_ID is a tty, run setupcon, break the active gnome-shell
[14:21] <Laney> or: SSH to a machine, run the upgrade, fgconsole gives you the TTY of gnome-shell, look at all sessions, find that TTY, see that it is Type=wayland, don't run setupcon
[14:22] <Laney> see you shortly
[14:31] <seb128> bbiab, changing location and stopping for some errands on the way
[14:38] <popey> oSoMoN: getting reports that the chromium snap is broken on nvidia proprietary drivers
[14:38] <popey> (it's broken here)
[14:40] <cyphermox> Laney: sorry, I had a thinko on what fgconsole was doing. that said, now I'm starting to think we should really fix setupcon rather than working around this
[14:43] <oSoMoN> popey, darn, I’ll look into that, any useful output?
[14:43] <cyphermox> for now though I guess we'll upload that, no sense in blocking console-setup longer
[14:44] <popey> oSoMoN: sadly not, I know flexiondotorg has debugged some of these, and has fixed them, perhaps he can help
[14:48] <oSoMoN> flexiondotorg, your expertise is needed! ^
[14:52] <popey> oSoMoN: can you point me at the yaml?
[14:54] <oSoMoN> popey, https://git.launchpad.net/~osomon/+git/chromium-snap/tree/snap/snapcraft.yaml?h=stable
[14:58] <didrocks> cyphermox: speaking of keyboard, since this update, I have some weird effect: like Alt + Shift + number (in order) works as expect
[14:58] <didrocks> cyphermox: but Shift + Alt + number (in this order) doesn't
[14:58] <didrocks> like it's printing the digit as if I didn't press Alt
[14:58] <didrocks> so modifier order sounds like important
[15:01] <cyphermox> didrocks: since what update?
[15:01] <didrocks> cyphermox: console-setup
[15:01] <didrocks> and this command ran on my GNOME session
[15:01] <cyphermox> it hasn't been updated in any meaningful way
[15:02] <didrocks> well, it did screw up my alt + arrow keys
[15:02] <didrocks> as for Laney
[15:02] <didrocks> and various alt + number behaviors
[15:02] <kenvandine> Trevinho, i built that themes branch in bileto, silo 2913
[15:02] <cyphermox> yeah, that might be the bug that Laney was fixing, but I can't do more than that
[15:03] <didrocks> cyphermox: do you know how I can debug and restore so that alt + shift + number is equivalent to shift + alt + number?
[15:03] <cyphermox> no
[15:03] <cyphermox> I would close the session and reopen it
[15:03] <didrocks> did that
[15:03] <didrocks> rebooted
[15:03] <didrocks> didn't work
[15:03] <cyphermox> then it's not setupcon
[15:03] <didrocks> (both on wayland or xorg)
[15:03] <cyphermox> something else must have been changed.
[15:04] <didrocks> well, running that command did change quite a lot of things in my session, and other updates in the same transaction don't seem relevant
[15:04] <cyphermox> sure, but not across a reboot
[15:04] <cyphermox> it's not like it's going to change settings.
[15:05] <didrocks> I had the alt + arrow keys issue persistent between reboots
[15:05] <didrocks> another user is fine, so at least, it's not system-wide
[15:05] <didrocks> (the other user wasn't connected during the upgrade)
[15:05] <didrocks> but I don't even know where that config could be
[15:06] <cyphermox> yes, but you're talking about a tool that is meant for TTYs, not graphical sessions
[15:06] <didrocks> but this tool was ran on graphical sessions by error if I understand the bug correctly
[15:06] <didrocks> due to tty2
[15:06] <cyphermox> it's not impossible that gnome-settings-daemon might have noticed changes and mucked with the settings on its end for them to be persistent, but that seems unlikely
[15:07] <didrocks> any idea where I should start debugging from? That sounds annoying
[15:08] <didrocks> (I only find debug info on systemd-localed, which we don't use)
[15:10] <cyphermox> compare gsettings between the session that works and the one that doesn't
[15:11] <didrocks> cyphermox: what I already did, nothing in gsettings, I bet it's in an obscure .conf file
[15:11] <cyphermox> if it was setupcon, then it would have to affect all terminals
[15:11] <didrocks> what it did, for running users
[15:11] <cyphermox> but you rebooted since
[15:11] <didrocks> yep
[15:12] <cyphermox> so if now it's not affecting all users, it's not the cause of the issue
[15:12] <didrocks> which is still a strange coincidence, you will admit
[15:12] <cyphermox> otherwise maybe try to reboot, login to the user that "works" first, see if then it's not good
[15:13] <didrocks> hum, good idea
[15:13] <didrocks> will try this
[15:13] <didrocks> so that this user goes to tty2
[15:13] <cyphermox> no, it's not, it's something to be expected when changing VTs like that
[15:13] <cyphermox> the possibility here is that setupcon runs at boot (as it always did) and races with gdm/your session
[15:16] <didrocks> hum, no, first user session is correct with the other one
[15:16] <didrocks> so, it's something that was picked on the upgrade and persisted
[15:16] <didrocks> but what? good question
[15:16] <jbicha> Laney: what do you think about gjs' failing autopkgtests? https://bugzilla.gnome.org/786572
[15:17] <jbicha> can we ignore the test failure this time? it looks like it's a new test
[15:21] <seb128> re
[15:21] <seb128> didrocks, thanks for the feedback/replies on the desktop list!
[15:22] <cyphermox> didrocks: that couldn't be caused by console-setup, sorry
[15:22] <cyphermox> didrocks: I have no idea where to look except for gsettings
[15:22] <didrocks> seb128: yw!
[15:23] <didrocks> cyphermox: no worry, let's see if someone else is getting this
[15:23] <didrocks> cyphermox: weird that modifiers press order could give different results
[15:24]  * seb128 shrugs at https://bugzilla.gnome.org/show_bug.cgi?id=753678
[15:24] <seb128> mdeslaur is going to like that one
[15:24] <didrocks> never saw similar issues before :)
[15:25] <seb128> well at least we fixed them in lightdm/unity
[15:25] <seb128> that one is open for some years with a CVE assigned
[15:26] <seb128> :-(
[15:26] <popey> oSoMoN: ok, i have fixed chromium. it launches now
[15:26] <mdeslaur> seb128: hopeless :P
[15:26] <oSoMoN> popey, cool, so what was it?
[15:27] <popey> some env vars missing in your launcher
[15:27] <popey> am just rebuilding one more time to test again
[15:28] <oSoMoN> great!
[15:28] <oSoMoN> popey, LIBGL_DRIVERS_PATH ?
[15:30] <Laney> jbicha: will look after meeting
[15:30] <Laney> cyphermox: ok, thanks for the brainstorm, are you reviewing/uploading or want me to?
[15:31]  * Laney finds the list of meeting names quickly
[15:31] <kenvandine> o/
[15:31] <kenvandine> :-D
[15:31] <cyphermox> Laney: reviewing, I'm doing a console-setup merge....
[15:32] <Laney> righto
[15:32] <seb128> hey
[15:32] <Laney> well it would be good to do this sooner rather than later
[15:32] <Laney> as it breaks the session
[15:32] <jbicha> o/
[15:32] <Laney> ALRIGHTTTTTTTTT
[15:33] <Laney> #startmeeting desktop team meeting
[15:33] <meetingology> Meeting started Tue Aug 22 15:33:23 2017 UTC.  The chair is Laney. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:33] <meetingology> Available commands: action commands idea info link nick
[15:33] <Laney> andyrock (out), dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel, heber, kenvandine, laney , oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)
[15:33] <didrocks> hey
[15:33] <oSoMoN> o/
[15:34] <dgadomski> o/
[15:34] <andyrock> I'm here actually
[15:34] <Laney> ooooooooooooooho
[15:34] <Laney> less pasting for me
[15:34] <Laney> #topic andyrock
[15:35] <andyrock> # holidays most of last week
[15:35] <andyrock> # reviwing some Marco's code
[15:35] <andyrock> # proposed an MP for update-notifier on artful
[15:35] <andyrock> # preparing MPs for update-notifier on X and T
[15:35] <andyrock> # updating patches to update-manager to catch up with new design
[15:35] <andyrock> # eow
[15:35] <Laney> merci
[15:35] <Laney> #topic dgadomski
[15:37]  * Laney meows
[15:37] <Laney> he just waved
[15:38] <dgadomski> hey
[15:38] <dgadomski> * implemented a fix to bug #1702529, will offer it upstream and prepare SRUs after proper testing
[15:38] <dgadomski> * did some research in the field of disabling WiFi Direct functionality. There's no option for it in NM (I think) and there's a bug in iwlwifi preventing to disable it with wpa_cli. I started a discussion about it in linux-wireless ml, will prepare a lp bug.
[15:38] <dgadomski> * looking into python performance regression (bug #1638695)
[15:38] <dgadomski> * testing my fix to bug #1638695
[15:38] <dgadomski> eof
[15:38] <Laney> aaaaaaaaaaaha
[15:38] <dgadomski> my irc client froze I guess
[15:39] <Laney> thanks dgadomski
[15:39] <Laney> good to see the python thing getting fixed
[15:39] <Laney> #topic didrocks
[15:39] <didrocks> hey
[15:39] <didrocks> * Did a lot of changes to ubuntu and GNOME Shell vanilla sessions:
[15:39] <didrocks>  - Separate between a vanilla and GNOME session.
[15:39] <didrocks>  - Uploaded glib changes for per-session override.
[15:39] <didrocks>  - Cleaned up overrides per session (global, gdm, ubuntu, unity) ones. That way, we have 2 sessions with vanilla having GNOME's default.
[15:39] <didrocks>  - Make the vanilla session more vanilla by having GNOME themes and font. Rewrote the way we patched the Shell theme to keep in sync while still shipping 2 versions.
[15:39] <didrocks>  - Use non symbolic icons in the appmenu for our ubuntu session while still having upstream using the symbolic ones.
[15:39] <didrocks>  - Implement a Gnome Shell ubuntu mode, enabled only in the ubuntu session with our changes.
[15:39] <didrocks>  - Worked with dash to dock upstream to add our "ubuntu" branch there, renaming and slight changes with different defaults. Implemented some settings we want users to have access in GNOME Control Center and wrote as well the transition from the unity settings to ubuntu dock ones. Pushed some changes to the master dash to dock upstream branch.
[15:39] <didrocks>  - Switched our ubuntu & gnome sessions to wayland by default.
[15:39] <didrocks>  - Fixed sound above 100% menu in a compatible way with upstream vanilla session. Opened a discussion with GNOME design team.
[15:39] <didrocks>  - Fixed our battery indicator by using upstream one, while still using our own icon themes for other icons and making corresponding changes in unity-power (+ awesome tests update fun).
[15:39] <didrocks> * Wrote about all those changes with rationale in blog posts:
[15:39] <didrocks>  - https://didrocks.fr/2017/08/14/ubuntu-gnome-shell-in-artful-day-1/
[15:40] <didrocks>  - https://didrocks.fr/2017/08/15/ubuntu-gnome-shell-in-artful-day-2/
[15:40] <didrocks>  - https://didrocks.fr/2017/08/16/ubuntu-gnome-shell-in-artful-day-3/
[15:40] <didrocks>  - https://didrocks.fr/2017/08/17/ubuntu-gnome-shell-in-artful-day-4/
[15:40] <didrocks>  - https://didrocks.fr/2017/08/18/ubuntu-gnome-shell-in-artful-day-5/
[15:40] <didrocks>  - https://didrocks.fr/2017/08/21/ubuntu-gnome-shell-in-artful-day-6/
[15:40] <didrocks>  - thanks to Will for rereading and typo fixes before publish!
[15:40] <didrocks> * Engaging on those via twitter, google+, numerous comments on my blog (more than 100 in total) as well french forum.
[15:40] <didrocks> * Misc:
[15:40] <didrocks>  - review some mate uploads in gtk unity module?
[15:40] <didrocks>  - review some gjs new packages and help transition.
[15:40] <didrocks> .
[15:40] <oSoMoN> wow
[15:41] <seb128> indeed oow :-)
[15:41] <seb128> wow
[15:42] <Laney> thx, nice one
[15:42] <Laney> #topic duflu
[15:42] <Laney> someone tell me when this is done (bluez ...) please
[15:42] <Laney> * Totem performance: Investigating and profiling... - https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1698270 - https://bugs.launchpad.net/ubuntu/+source/clutter-gst-3.0/+bug/1698282 - Completed an initial/partial fix: https://bugs.launchpad.net/ubu
[15:42] <Laney> ntu/+source/totem/+bug/1698282 - ... but more work is still required. Ongoing.
[15:42] <jackpot51> Discussion about Pop! OS right now, right here: https://chat.pop-os.org/community/channels/town-square
[15:42] <Laney> * Video acceleration: - Trello card (and public announcement) still blocked on the final
[15:43] <Laney> checklist item, awaiting sponsorship:
[15:43] <Laney> https://bugs.launchpad.net/ubuntu/+source/ubuntu-restricted-
[15:43] <Laney> addons/+bug/1709166
[15:43] <Laney> * PulseAudio: xenial SRU still blocked awaiting sponsorship: - https://bugs.launchpad.net/pulseaudio/+bug/1539209
[15:43] <Laney> * Daily bug management across gnome-shell, gdm, ubuntu-themes, bluez,
[15:43] <Laney> pulseaudio and mir. - Also completed another backlog expiry review, this time for
[15:43] <Laney> yakkety-specific bugs.
[15:43] <Laney> * BlueZ 5.46 released to artful this week.
[15:43] <didrocks> Laney: done
[15:43] <seb128> I did the pulseaudio/xenial sponsoring from duflu today
[15:43] <Laney> thanks didrocks
[15:44] <Laney> seb128: nice one
[15:44] <Laney> #topic jbicha
[15:44] <jbicha> • Lots of GNOME 3.25.90 work. Some of the bigger pieces landed:
[15:44] <jbicha> ◦ Evolution
[15:44] <jbicha> ◦ webkit2gtk & epiphany
[15:44] <jbicha> ◦ gnome-calendar (now supports recurring events)
[15:44] <jbicha> ◦ tracker2 (split source package means we'll probably be able to sync this with Debian from now on)
[15:44] <jbicha> ◦ nautilus now offers full-text search for indexed files if you have tracker running
[15:44] <jbicha> ◦ gjs (in artful-proposed)
[15:44] <jbicha> • Reported pango regressions, cherry-picked a fix for one from bugzilla, and reverted to building with autotools for the other
[15:44] <jbicha> • LocutusofBorg fixed the s390x build for geary so the git snapshot using webkit2gtk is now in artful
[15:44] <jbicha> • empathy now uses webkit2gtk too. If we didn't care about boinc or gnucash, we could probably complete remove old webkitgtk from 17.10.
[15:44] <jbicha> • Uploaded the 3 new library source packages for GNOME Builder 3.26 to Debian & Ubuntu new queues
[15:44] <jbicha> eof
[15:45] <Laney> thx
[15:45] <Laney> good to see more tomboy users
[15:45] <didrocks> jbicha: are you going to update to GNOME Shell 2.25.90 soon?
[15:45] <seb128> and g-c-c 3.25?
[15:45] <jbicha> didrocks: I kinda want to see gjs migrate out of proposed first
[15:46] <didrocks> jbicha: ok, I have a change for G-S tomorrow and there is the fit and finish sprint on Thursday/Friday, so maybe next week?
[15:46] <didrocks> (as I'll probably upload some theme changing on Friday after the sprint)
[15:46] <seb128> I guess gcc is part of the gnome-session/g-s-d migration you mentioned yesterday?
[15:46] <jbicha> the sprint should probably be working on 3.25 instead
[15:46] <didrocks> jbicha: well, sounds like maybe not, upstream may revert the transparent bar by default
[15:47] <jbicha> when I rebuilt gnome-session for the gsd transition, it's now complaining about the gnome-session s390x binaries
[15:48] <jbicha> I could just upload all the remaining pieces instead of trying to separate transitions now
[15:48] <didrocks> (please don't do G-S then for now)
[15:49] <jbicha> gnome-control-center 3.26 requires new mutter for the Display panel to work I believe…
[15:49] <seb128> k
[15:50] <Laney> ok, thanks, moving on
[15:50] <Laney> #topic jamesh
[15:50] <Laney> didn't get a status from you, so maybe you are still here to give one
[15:50] <seb128> he tends to forget
[15:51] <seb128> and probably late for him
[15:51] <Laney> I know, but we'll see.
[15:51] <Laney> k, jamesh please mail your status to us
[15:51] <Laney> #topic jibel heber
[15:52] <jbicha> didrocks: btw, your Dock panel needs to be rewritten for g-c-c 3.26
[15:52] <didrocks> jbicha: don't have time for this right now, but will welcome any help
[15:53] <Laney> :/
[15:54] <Laney> #topic kenvandine
[15:54] <kenvandine> * Short week for me, on vacation friday -> monday
[15:54] <kenvandine> * oSoMoN and I discussed a strategy for our snap publisher and support.  Documented as a wiki page on the forum and added links to all the branches and snaps.  https://forum.snapcraft.io/t/snaps-officially-supported-by-canonical/1719
[15:54] <kenvandine> * Added a couple of collaborators to all of my snaps, the active collaborators will actually persist after we change the publisher.
[15:54] <kenvandine> * Changed owner of all the branches and snaps to ~ubuntu-desktop in LP
[15:54] <kenvandine> * Finished up the simple-scan classic snap and got it published in the store.  I also committed the snapcraft.yaml upstream.
[15:54] <kenvandine> * Worked on strict confinement for simple-scan, not quite working yet but according to snappy-debug the policy should actually be working.  Need to figure that out still.
[15:54] <kenvandine> * Tested theme fix for vertically linked buttons, would like to get that landed this week.
[15:54] <kenvandine> EOF
[15:54] <Laney> nice
[15:55] <Laney> Trevinho or me can probably review the theme if you request us on it
[15:55] <kenvandine> yeah, i pinged Trevinho this morning
[15:55] <Trevinho> kenvandine: yeah, I checked them
[15:55] <Trevinho> I've a bileto silo ready...
[15:55] <kenvandine> oh... :)
[15:55] <kenvandine> i'll kill mine then
[15:56] <Laney> what's a few CPU cycles between friends
[15:56] <Laney> #topic laney
[15:56] <Laney> • short week
[15:56] <Laney> • tracked down glib test problems, got them running again/made them pass, uploaded to unstable
[15:56] <Laney> • debugged systemd autopkgtest timeouts, buggy disabling of KillUserProcesses with meson switch
[15:56] <Laney> • some more random autopkgtest administration - lxd workers getting stuck (wrote a script to help with that maybe), lxc workers running out of space, ...
[15:56] <Laney> • looked at ubiquity/console-setup ftbfsing so we can get the g-s-d launching code in, uploaded that...
[15:56] <Laney> • ...triggered a bug in the console-setup postinst that was calilng setupcon on gnome-shell sessions, breaking the keyboard, proposed a patch there which cyphermox is taking from me to upload hopefully soon
[15:56] <Laney> • did some gnome-software bugfixes upstream
[15:56] <Laney> <imagine an emoji here>
[15:57] <Laney> I assume that is done now
[15:57] <Laney> #topic oSoMoN
[15:57] <oSoMoN> hey
[15:57] <oSoMoN> • wrote call for testing chromium snap, got some useful feedback and pushed fixes
[15:57] <oSoMoN> • published chromium snap to stable channel, updated beta channel
[15:57] <oSoMoN> • just got more fixes from popey for nvidia, will push a new version to the candidate channel in a moment
[15:57] <oSoMoN> • created doc on forum for snaps officially supported by Canonical
[15:57] <oSoMoN> • shared chromium GCC-specific patches (still in use for trusty builds) with other chromium packagers, took an action item to upstream them where relevant
[15:57] <oSoMoN> • continued experimenting with is_official_build=true and is_component_build=false for chromium builds, which would get us much closer to official chrome packages (but with the chromium branding of course), everything builds and runs fine except trusty armhf (ld gets OOM)
[15:57] <oSoMoN> • libreoffice 1:5.4.0-0ubuntu2 in artful-proposed (still building), thanks Rico and Seb
[15:57] <oSoMoN> • built libreoffice 5.4.0 snap but seeing at least one important issue, will push to edge channel and continue investigating
[15:57] <oSoMoN> EOF
[15:58] <Laney> thanks oSoMoN, nice stuff
[15:58] <Laney> #topic seb128
[15:58] <seb128> * travelled for a meeting on an national holiday, swapped a day back in exchange
[15:58] <seb128> * sponsoring (intel-vaapi-driver, mpv, gstreamer-vaapi, pulseaudio, poppler, bluez, totem, * libreoffice, pulseaudio for xenial)
[15:58] <seb128> * NEW review for gnome-shell-extension-ubuntu-dock and gnome-shell-extension-appindicator
[15:58] <seb128> * screwed libreoffice in artful by copying to the wrong pocket, did some archive admin dance
[15:58] <seb128> to fix the situation
[15:58] <seb128> * tested new g-c-c shell UI
[15:58] <seb128> * rhythmbox-plugin-alternative-toolbar by default
[15:58] <seb128> * replied to snapcraft discussions about gnome platform
[15:58] <seb128> * reported some GNOME bugs upstream
[15:58] <seb128> * uploaded xdg-user-dirs without pkgbinarymangler tweak to get translations imported
[15:59] <seb128> * reviewed trello board status and updated some cards
[15:59] <seb128> * followed up on the mailing list about desktop apps selection
[15:59] <seb128> * chassed up some feature work to get things landing before ff this week

[15:59] <Laney> weeeeee
[16:00] <seb128> haha
[16:00] <Laney> are those gstreamer patches being worked upstream?
[16:00] <Laney> well, not your work I guess
[16:00] <Laney> thanks!
[16:00] <Laney> #topic tkamppeter
[16:01] <seb128> he's getting reviews so seems to go in the right direction
[16:01] <tkamppeter> - cups-filters: Switched to C/C++ 11 standards, silenced all compiler warnings, configurable timeouts for legacy CUPS broadcasting/browsing, corrections in README, 1.16.3 release. Prepared cups-browsed for PCLm support (Mopria and Wi-Fi Direct driverless printing).
[16:01] <tkamppeter> - Google Summer of Code 2017: Student project coordination and mentoring. GSoC ends this week. Final video meeting with the 5 print dialog students, they have done well. Test of the dialog, works, needs some polishing. PCLm printing tests. PCLm (Mopria and Wi-Fi Direct driverless printing) support will make it into Ubuntu before Feature Freeze. All 7 students will pass.
[16:01] <tkamppeter> - Bugs.
[16:02] <Laney> 5 people working on the print dialog!
[16:02] <Laney> thanks tkamppeter
[16:02] <Laney> #topic Trevinho
[16:02] <Trevinho> · Analisys, testing and hacking of indicators / tray with Top Icons and AppIndicator extensions
[16:02] <Trevinho> · Reviewed some theme changes
[16:02] <Trevinho> · Fixed an issue in mutter with fractional scaling and stretched wallpaper
[16:02] <Trevinho> · More gcc7/cmake-3.9 fixes in nux/compiz (got a porter box to check some sigc signal issues in some archs)
[16:02] <Trevinho> · Working in StWidgets scaling
[16:02] <Trevinho>  - EOF
[16:03] <tkamppeter> Yes, 2 on a Qt dialog, 1 on a CUPS backend and backend/frontend lib, 1 on LibreOffice patches and 1 on Google Cloiud Print backend.
[16:03] <Laney> ah, St, fun
[16:03] <Laney> thanks Trevinho
[16:03] <Laney> hmm, did I have a status from robert_ancell
[16:04] <Laney> don't think so, ok
[16:04] <Laney> #topic AOB
[16:06] <Laney> k, thanks!
[16:06] <Laney> #endmeeting
[16:06] <meetingology> Meeting ended Tue Aug 22 16:06:23 2017 UTC.
[16:06] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2017/ubuntu-desktop.2017-08-22-15.33.moin.txt
[16:06] <seb128> thanks Laney, good meeting!
[16:06] <seb128> I'm surprised jbicha didn't bring any ffe or landing discussion in the aob :-)
[16:06] <oSoMoN> thanks all
[16:07] <jbicha> we kinda talked about those a bit already
[16:09] <jbicha> seb128: should we temporarily keep installing the old g-c-c for testing if we upload 3.25.90?
[16:09] <seb128> jbicha, that would be useful
[16:10] <jbicha> ok
[16:11] <GammaDraconis> Hello, the notifications will be top right on Arful ?
[16:11] <didrocks> GammaDraconis: you will get news about it tomorrow in my next blog post :)
[16:12] <didrocks> (would be indicators)
[16:12] <ogra_> they will probably bottom right and upside down :P
[16:12] <ogra_> *+be
[16:12] <jbicha> not to be confused with the notifications in the clock menu which is staying in the center top right, right?
[16:12]  * didrocks adds the "if user_name == ogra", as usual
[16:12] <didrocks> yep ;)
[16:12] <ogra_> :D
[17:14] <willcooke> night all
[17:44] <Laney> nn
[17:47] <cyphermox> Laney: change looks good, works fine, I'm running one last test (I managed to find a way to reduce this to something even simpler), and if it works I'll upload that, otherwise upload your version
[19:13] <Trevinho> kenvandine: can you please have  a look to https://code.launchpad.net/~3v1n0/ubuntu-themes/radiance-headerbar-buttons-fix/+merge/324516 ?
[19:15] <kenvandine> Trevinho, looking
[19:16] <kenvandine> Trevinho, was it using the ambiance button before?
[19:16] <Trevinho> kenvandine: yep
[19:21] <kenvandine> Trevinho, tested and approved
[19:22] <Trevinho> thanks
[19:22] <kenvandine> np
[19:22] <kenvandine> that looked really bad in radiance
[19:22] <kenvandine> which i never use :)
[19:52] <Trevinho> kenvandine: also https://code.launchpad.net/~3v1n0/ubuntu-themes/better-destructive-action/+merge/329392
[19:52] <Trevinho> yeah me too :)
[19:53]  * Trevinho (an example destructive action is when shift+delete on a file in nautilus)
[19:54] <kenvandine> Trevinho, ok, i'll take a look
[20:06] <kenvandine> Trevinho, this branch isn't built into the silo yet right?
[20:06] <Trevinho> kenvandine: not yet
[20:06] <Trevinho> kenvandine: it's building right now
[20:07] <kenvandine> cool, so i can ca see what it looks like currently