[05:14] <didrocks> good morning
[05:37] <jibel> morning
[05:37] <jibel> Hey didrocks
[05:38] <didrocks> hey jibel
[06:47] <duflu> Morning didrocks, jibel
[06:48] <seb128> good morning desktopers
[06:48] <seb128> hey duflu, how are you?
[06:49] <flexiondotorg> Morning France
[06:49] <seb128> duflu, we finally got the ubuntu-restricted change unblocked, thanks to jbicha for the upload
[06:49] <seb128> hey flexiondotorg
[06:49] <flexiondotorg> And duflu
[06:49] <duflu> seb128, going well. I possibly just finished the final form of the clutter-gtk CPU fix. Upstream will have to decide what form of patch they like, but it's also still waiting for a separate smoothness fix
[06:49] <seb128> ah, nice
[06:49] <duflu> seb128, how are you?
[06:50] <seb128> I'm good, could have done with a bit more sleep though
[06:50] <seb128> I was up hacking on g-c-c until 1:30
[06:50] <duflu> Fun
[06:51] <seb128> indeed
[06:51] <seb128> well at least I got things working
[06:51] <seb128> I've a new panel in 3.25 for the dock settings
[06:51] <seb128> now up to Didier to deal with the backend side
[06:52] <duflu> Cool. Users love settings. I vaguely recall we had a lot more to play with in Gnome 2.x
[06:52] <duflu> and never recovered fully
[06:53] <duflu> In the old days you could set refresh rates and subpixel orders ;)
[06:55] <duflu> Interesting thought - Any machine with <= half the power of my desktop would have been too underpowered to be able to redraw a FHD 60Hz totem window. The user experience for plenty of people should improve soon
[07:04] <seb128> great
[07:45] <andyrock> seb128, didrocks on artful just after the login the deskop icons apper behind the dock
[07:45] <seb128> andyrock, yes, known issue
[07:45] <seb128> until it refreshes
[07:45] <andyrock> is anyone working on it?
[07:46] <seb128> andyrock, it you want to work on a patch that would be great
[07:46] <seb128> no
[07:46] <andyrock> kk
[07:46] <seb128> andyrock, https://bugzilla.gnome.org/show_bug.cgi?id=760651
[07:46] <ubot5`> Gnome bug 760651 in Desktop "Desktop icon under top panel" [Normal,New]
[07:49] <didrocks> andyrock: FYI, I implemented this + intellihide behavior in 2011
[07:49] <didrocks> andyrock: you might want to check there
[07:50] <didrocks> andyrock: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1711377 has more info
[07:50] <ubot5`> Ubuntu bug 1696621 in nautilus (Ubuntu) "duplicate for #1711377 Desktop icons slip under the top bar and dock" [Medium,Confirmed]
[07:50] <didrocks> (even if dupped)
[07:50] <didrocks> there is the first refresh issue
[07:51] <didrocks> + the fact that nautilus should learn about the icon size in intellihide mode (which isn't the STRUT, has we still want apps to maximize fullscreen)
[07:51] <andyrock> didrocks: thanks
[07:57] <seb128> didrocks, andyrock, the duplicate status is wrong imho, Didier's report included 2 issues, one is a dup and an upstream bug (the fact that it needs a refresh to do the correct layout) and one is a feature request (handling the dynamic behaviour)
[07:57] <andyrock> indeed
[07:57] <seb128> I should perhaps have renamed/retargetted to the second issue when I commented
[07:57] <andyrock> I would prefer to focus on the upstream bug
[07:57] <seb128> right,I was going to say that
[07:58] <seb128> it's the default config/the most noticable one
[08:06] <Laney> moin
[08:07]  * Laney has been to the dentist
[08:07] <willcooke> morning desktoppers
[08:07] <willcooke> Laney, was it ok?
[08:08]  * willcooke has the man from Lenovo coming today to replace the keyboard
[08:08] <Laney> got to go to the hygeinist next week /o\
[08:08] <Laney> otherwise yeh
[08:08] <Laney> wisdom teeth man
[08:08] <willcooke> :((
[08:08] <willcooke> Mine were growing well in to my 30s I think
[08:09] <davmor2> Laney: don't have them pulled out they contain all your wisdom man ;)
[08:09] <seb128> hey willcooke Laney
[08:09] <willcooke> but at least there was room for them
[08:09] <Laney> they're horizontal or something
[08:09] <willcooke> morning seb128 davmor2
[08:09] <davmor2> Morning all
[08:09] <Laney> hey seb128
[08:09] <Laney> hey davmor2!
[08:09] <Laney> can I borrow yours?
[08:09] <Laney> my wisdom is lacking
[08:11] <jibel> Morning davmor2
[08:11] <davmor2> hey jibel
[08:12] <didrocks> hey Laney, willcooke
[08:12] <willcooke> morning didrocks
[08:13] <didrocks> good luck Laney, once this all is done, remember me to tell you about some horrible story I have with my widsom teeth :)
[08:13] <Laney> hey didrocks
[08:13] <Laney> heh
[08:13] <Laney> we're not at the stage of doing anything yet :P
[08:15] <Laney> WAT, me ubiquity uploads failed to build
[08:15] <didrocks> on ALL archs
[08:16] <Laney> but I test built it :(((((((((((((((((((((((((((((((((((((
[08:16] <didrocks> so dbus-update-activation-environment was enough?
[08:16] <Laney> putting it earlier was the secret
[08:16] <didrocks> Laney: ah ok ;)
[08:16] <Laney> not that I tested the actual debs
[08:16] <didrocks> Laney: from the failure, I would say missing bzr add :p
[08:17] <Laney> maybe
[08:17] <Laney> but that computer is off now and I'm in the library so can't know today :P
[08:17] <Laney> cd upub
[08:17] <Laney> wtf
[08:17] <Laney> tilix ias gone mental
[08:17] <didrocks> <missing password> ;)
[08:17] <Laney> I could see both tabs at the same time
[08:20] <seb128> does anyone have a simple example of single instance checking code?
[08:20] <seb128> I should say non-gtk one
[08:20] <seb128> or non-gapplication
[08:20] <seb128> like command line unix style :p
[08:22] <didrocks> depends on your language, but most of the time you write an <app_name>.pid in a temp fixed location and write the pid in it
[08:22] <didrocks> then, if the file exists, you check if the current pid is still running
[08:22] <didrocks> if so, exit
[08:22] <didrocks> or you overwrite it with your own pid
[08:23] <didrocks> (and try to clean it when shutting down, ofc, the first case is to handle crashes ^)
[08:23] <seb128> thanks
[08:23] <seb128> it's C, and I was trying to avoid do all that work
[08:24] <Laney> what's seb128 doing?
[08:24] <Laney> sounds intriguing
[08:24] <seb128> trying to get update-notifier to not segfault under wayland
[08:24] <didrocks> seb128: you have the run-once or so wrapper script from kirkland
[08:24] <seb128> I might just disable the single instance code
[08:24] <seb128> I can't be bothered to handle things properly
[08:24] <seb128> it currently uses the X clipboard for that
[08:25] <seb128> we have a contributor patch
[08:25] <seb128> https://launchpadlibrarian.net/332753117/0001-Replaced-up_get_clipboard-with-a-pidof-hack.patch
[08:25] <seb128> I could just apply it pretending it's fine :p
[08:25] <seb128> hackish hack day!
[08:26] <seb128> we currently have no update-notifier under wayland, which means no apport prompting for issues
[08:26] <seb128> which is not a good thing, we want feedback
[08:26] <didrocks> (/me whistles)
[08:27] <pitti> oh, are we still using update-notifier for that
[08:27] <didrocks> hey pitti!
[08:27] <seb128> hey pitti
[08:27] <pitti> bonjour didrocks et seb128 !
[08:27] <pitti> isn't that the kind of thing that coudl be replaced with a session-systemd path unit
[08:27] <seb128> pitti, yeah, the apport maintainer never added a remplacement solution :p
[08:27] <seb128> you tell me :-)
[08:27] <pitti> that guy sucks!
[08:28] <didrocks> he's probably writing javascript nowdays :)
[08:28]  * didrocks hugs pitti
[08:28] <Laney> sec
[08:29] <seb128> pitti, also no pkexec for system reports under wayland...
[08:30] <pitti> urgh, we use pkexec a lot, don't we
[08:30] <seb128> sort of yes :-/
[08:30] <pitti> due to its efforts to grab the focus/keyboard?
[08:30] <pitti> (which is X only?)
[08:30] <pitti> I thought g-shell had a builtin polkit agent
[08:31] <seb128> sorry, in fact it seems it's only when .desktop use pkexec
[08:31] <seb128> https://bugzilla.gnome.org/show_bug.cgi?id=763531
[08:31] <ubot5`> Gnome bug 763531 in overview "pkexec in .desktop no longer works" [Critical,Reopened]
[08:32]  * seb128 looks more at why system reports don't wokr
[08:36] <Laney> seb128: https://paste.ubuntu.com/25476960/ maybe that's useful to you
[08:37] <Laney> update-notifier already has the path units AFAICS
[08:37] <Laney> but probably not hooked up atm
[08:40] <didrocks> Laney: but if the process crash, you don't have it cleaned up, correct?
[08:40] <seb128> Laney, thanks, I found that/considered it but was unsure if the predictable filename was an issue since something else could decide to hijack it
[08:40] <Laney> doesn't matter, it's not locked then
[08:40] <seb128> or take the lock
[08:40] <Laney> ok, as you wish
[08:41] <seb128> but I guess it can't do much damage
[08:41] <seb128> well, I'm just unsure
[08:41] <seb128> I'm not a security guy
[08:43] <Laney> what was the protection against that for the clipboard method, out of interest?
[08:43] <seb128> I guess none, you have a point :-)
[08:44] <seb128> Laney, thanks!
[08:44] <seb128> shrug
[08:44] <seb128> $ pkexec /usr/share/apport/apport-gtk /var/crash/_usr_lib_gdm3_gdm-wayland-session.1000.crash
[08:44] <seb128> Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Impossible de se connecter : Connection refused
[08:44] <seb128> Erreur de segmentation (core dumped)
[08:44] <seb128> $ pkexec sleep 1; /usr/share/apport/apport-gtk /var/crash/_usr_lib_gdm3_gdm-wayland-session.1000.crash
[08:44] <seb128> works
[08:44] <Laney> fun
[08:44] <seb128> indeed :-/
[08:46] <pitti> you mean the "connection refused" thing was from pkexec, not apport? the second command runs apport-gtk as user, so no surprise if that works
[08:47] <seb128> ah, crap
[08:47] <seb128> thanks for pointing that out
[08:48] <seb128> I'm trying to figure out how to get a backtrace
[08:49] <seb128> ah, apport has the dump
[08:49] <seb128> even if unpack hits
[08:49] <seb128> ValueError: ['UserGroups'] has no binary content
[08:52] <seb128> #0  0x00007f9f8a172c99 in _gtk_style_provider_private_get_settings (
[08:52] <seb128>     provider=0x0) at ././gtk/gtkstyleproviderprivate.c:123
[08:57] <willcooke> duflu, koza seb128 - otp still, will be a bit late / won't make it to BT meeting.  Is there much to discuss today?
[09:00] <duflu> willcooke, running late too. Nothing I know of other than Pulse 11 is interesting
[09:01] <seb128> willcooke, duflu, koza, oh sorry, I'm in the middle of hacking and forgot about that one again
[09:01] <seb128> let's skip?
[09:01] <duflu> +1
[09:01]  * duflu wonders if koza is in there alone
[09:01] <duflu> jibel, ? ^
[09:03] <jibel> duflu, ah sorry, owm
[09:04] <jibel> duflu, or just skip :)
[09:04] <jibel> koza is not even in the room
[09:05] <seb128> let's skip then
[09:05] <seb128> duflu, pulseaudio 11 is for next cycle imho, I agree with what you wrote on the trello board
[09:05] <koza> jibel sorry
[09:06] <duflu> And good news... bluez has not released recently
[09:06] <koza> jibel seb128 duflu terribly sorry, I have been reading BT spec and did not realize it is 11 already
[09:06] <jibel> koza, nw duflu was wondering if you were in the meeting alone, and you were not :)
[09:07] <duflu> Best excuse ever for missing the BT meeting
[09:07] <koza> :)
[09:07] <seb128> koza, we decided to skip, there is not much to share and everybody is busy
[09:07] <koza> exactly, same situation on my side - not much to share, busy with other BT stuff
[09:08] <koza> (everyone now wants to use Bluetooth, this is crazy)
[09:08] <Laney> I should try this Bluetooth thing some time
[09:08] <duflu> seb128, still should PPA sooner
[09:34] <seb128> Laney, your suggestion works fine, https://code.launchpad.net/~seb128/update-notifier/work-under-wayland/+merge/330271
[09:35] <seb128> Laney, thanks again ;-)
[09:35] <seb128> now to debug the under pkexec segfault
[09:37] <Laney> seb128: didn't want to check errno?
[09:37] <Laney> I guess you just exit anyway so maybe you don't care
[09:38] <Laney> good stuff
[09:43] <seb128> Laney, right, I don't want to enter into the business of dealing with situations were things in a weird state
[09:43] <seb128> just exit for now
[09:52] <seb128> so it's basically "can't use gtk under sudo/pkexec"
[09:52] <seb128> if you do that on eog or gedit it tells you it can't open the display and bails out
[09:52] <seb128> it's just that python code/apport is handling errors less well
[09:58] <seb128> k, I'm offline for a bit for debuggign&lunch, bbl
[11:10] <willcooke> man from Lenovo will be here in a mo to replace my keyboard \o/
[11:19] <willcooke> oki, bbl
[12:09] <willcooke> yay, keyboard fixed!
[12:10] <seb128> willcooke, it was still the space bar not working on the right issue?
[12:10] <willcooke> seb128, yeah
[12:10] <seb128> good that they fixed it :-)
[12:11] <willcooke> The space bar is much more positive now, you can tell that you're pressing it
[12:11] <willcooke> The engineer runs Ubuntu too :)
[12:12] <Laney> nice
[12:13] <jbicha> did you get the spacebar heating option? ;)
[12:13] <pitti> willcooke: oh wow, they sent someone? I also had the extra 24/7 worldwide plan, but they just fedexed me a replacement
[12:13] <pitti> not that I'm complaining, it's easy enough to replace; I'm just surprised
[12:13] <pitti> jbicha: indeed - winter's coming! :-)
[12:14] <willcooke> pitti, yeah, bloke came out and did it for me.  It was quite involved on this X270, he had to take the main board out, and the battery, and the hdd
[12:15] <pitti> willcooke: oh, wow; took me 5 mins to replace on my x240,  keyboard was pretty much the first thing that came off
[12:15] <pitti> maybe the design changed quite a bit
[12:17] <willcooke> Ha, I offered him a cup of tea when he got here (natch) and the first thing he asked was "which model is it?" - and suggested that if it was a 240 then there wouldnt have been time to boil the kettle :)
[12:18] <pitti> hah - so, this is much more expensive for them, teaches them right to not make the design worse :)
[12:20] <andyrock> seb128, didrocks: I got a fix
[12:20] <andyrock> mutter's fault
[12:20] <seb128> andyrock, woot
[12:20] <seb128> well done
[12:20] <andyrock> I'll propose a fix upstream
[12:21] <seb128> andyrock, send...excellent
[12:21] <andyrock> it's 1 line
[12:21] <seb128> don't forget to reassign the bug in bugzilla
[12:45] <popey> Ooh, suddenly a dropbox icon appears at the top of my 17.10 panel
[12:45] <popey> but it's not clickable :(
[12:46] <popey> (known bug?)
[12:47] <didrocks> Trevinho: ^
[12:47] <didrocks> andyrock: that's nice! the env var trick worked I guess for debugging?
[12:47] <didrocks> jbicha: btw, did you get the FFe lined up for g-c-c?
[12:47] <andyrock> didrocks: yep
[12:47] <didrocks> great ;)
[12:50] <jbicha> didrocks: yes, use LP: #1712797
[12:50] <ubot5`> Launchpad bug 1712797 in gnome-control-center (Ubuntu) "FFe: gnome-control-center 3.26" [Undecided,Confirmed] https://launchpad.net/bugs/1712797
[12:51] <didrocks> jbicha: excellent! I just have some debug stack to get in the UI, and we'll be good to go!
[12:51] <jbicha> did you guys happen to fix LP: #1712104 with this patch set?
[12:51] <ubot5`> Launchpad bug 1712104 in gnome-control-center (Ubuntu) "Add Hot Corner switch to Dock Settings" [Wishlist,New] https://launchpad.net/bugs/1712104
[12:51] <didrocks> I don't know if we want to add this, do we?
[12:51] <didrocks> right now, ubuntu session is "no hot corner", vanilla is "hot corner"
[12:51] <jbicha> it's a popular feature for some people
[12:52] <didrocks> but it's a good point, seb128, willcooke, Laney, what do you think about surfacing this option? ^
[12:52] <didrocks> (with off by default in the ubuntu session, not selectable in the vanilla one)
[12:52] <jbicha> I think most people that have already been using GNOME have gotten used to the hot corner and it's frustrating if it's not there
[12:52] <jbicha> why not selectable?
[12:52] <willcooke> didrocks, I think off by default is the right way to go, I dont have any strong preference for making it an optional thing
[12:52] <didrocks> jbicha: well, it will be upstream vanilla experience in the GNOMEsession, so on by default there
[12:52] <Laney> why is that a dock setting?
[12:53] <didrocks> Laney: where did we say it's a dock settings?
[12:53] <didrocks> oh
[12:53] <didrocks> that's the bug
[12:53] <didrocks> no, it would be in a different frame
[12:53] <didrocks> same panel
[12:53] <jbicha> or I could add it to the Tweaks app > Top Bar if you don't want it in g-c-c right now
[12:53] <didrocks> (which shouldn't be entitled "Dock")
[12:54] <Laney> I woudn't do it as a distro patch, but that might just be me
[12:54] <didrocks> I think a settings with off by default isn't that crazy, in the same panel
[12:54] <jbicha> I think there are people who don't mind the Ubuntu session but like the hot corner and telling them to use dconf-editor or gsettings directly isn't great
[12:54] <Laney> tweaks would be ok
[12:54] <didrocks> Laney: not a distro patch, but as we disable it by default…
[12:54] <didrocks> and it's a separate panel, where we have our dock settings also
[12:54] <Laney> I think the argument applies to people who don't like it enabled by default and would want to disable it
[12:54] <Laney> the GSetting is upstream too
[12:55] <didrocks> nope
[12:55] <jbicha> the gsettings is not upstream yet :(
[12:55] <didrocks> it's a patch made by upstream
[12:55] <didrocks> but not in tree
[12:55] <Laney> sure
[12:55] <Laney> but if they take it then it makes sense to expose it
[12:56] <andyrock> seb128: should I open a new bug for mutter
[12:56] <andyrock> or can I just send the patch file in the nautilus bag
[12:56] <andyrock> I cannot re-target it
[12:57] <didrocks> however, it's some place where we reverted the upstream behavior due to our dock, I guess it's sensible to expose a way to put that gesture back in, but that's just IMHO
[12:57] <didrocks> let's see what seb128 thinks about it as well once he's back
[12:58] <jbicha> if upstream could commit that patch to gnome-shell, then it makes sense in Tweaks>Top Bar upstream too
[13:13] <seb128> andyrock, reassign the bug to the right component as I said earlier
[13:14] <seb128> andyrock, why not?
[13:14] <andyrock> seb128: how can I reassign
[13:14] <seb128> didrocks, jbicha,no strong opinion, unsure how the hot corner fits with a dock, you are likely to trigger it by error when going over the most used/top icon
[13:14] <andyrock> or the ui is really bad
[13:15] <andyrock> or I'm not allowed
[13:15] <andyrock> :D
[13:15] <seb128> andyrock, the product should be a combo
[13:15] <seb128> just select another value
[13:15] <seb128> on the top of the page, second item
[13:15] <seb128> or first rather
[13:15] <didrocks> ok, looks like more for Tweaks thus
[13:16] <seb128> +1
[13:16] <didrocks> (can be conditional if the key is there)
[13:16] <didrocks> let me record that on the bug report
[13:16] <seb128> we can always add it next cycle if the user feedback tells us it's a wanted option
[13:17] <andyrock> I'm not allowed to do that https://usercontent.irccloud-cdn.com/file/bWbgePvT/Screenshot%20from%202017-09-06%2015-17-05.png
[13:17] <didrocks> sounds good to me
[13:17] <seb128> andyrock, ok, let me reassign for you
[13:19] <andyrock> seb128: it's mutter not gnome-shell
[13:19] <seb128> andyrock, I got an error with mutter so picked the other one
[13:19] <andyrock> kk thanks
[13:19] <seb128> those are the same people looking at both
[13:19] <seb128> so should be fine
[13:19] <jbicha> https://git.gnome.org/browse/gnome-tweak-tool/commit/?id=29073dd8a70e5
[13:19] <seb128> jbicha, nice
[13:20] <jbicha> that's on git master, I need to ask the translators if I can commit to the 3.26 branch
[13:26] <willcooke> seb128, jbicha - I realised I never got round to testing the power button stuff, do I need to add some PPAs etc to see it?
[13:26] <seb128> I don't know, power/suspend handling is crap for me atm
[13:27] <seb128> I need to debug that but I'm waiting for 3.26 to land
[13:27] <seb128> also I had the suspend button extension which stopped working
[13:27] <jbicha> willcooke: if you don't want to use dconf-editor or gsettings, you need gnome-control-center 3.25.92 which is in the GNOME3 Staging PPA right now
[13:27] <seb128> quite annoying :-/
[13:27] <willcooke> jbicha, I can dconf-editor, that's fine
[13:29] <jbicha> gsettings set org.gnome.settings-daemon.plugins.power power-button-action 'interactive'
[13:30] <willcooke> jbicha, works great! ship it!
[13:30] <seb128> lol
[13:31] <willcooke> seb128, are you having issues with that setting then? ^
[13:31] <Saviq> Hey all, where does unity store the display settings? I can't get it to start proper, only clue is a dialog saying it can't restore display config
[13:31] <willcooke> urgh, sounds familiar ^ ?
[13:31] <willcooke> is this the monitors.xml thing again?
[13:32] <popey> yeah, ditch (or move) the .config/monitors.xml
[13:32] <Saviq> Also gnome-shell only starts when I have my ext monitor connected...
[13:32] <willcooke> Saviq, you reckon it might be this?  https://bugzilla.gnome.org/show_bug.cgi?id=786660
[13:32] <ubot5`> Gnome bug 786660 in general "3.25.91: Unable to log in: invalid monitor configuration, Logical monitors not adjecent" [Critical,New]
[13:33] <Saviq> Ok ditching monitors.xml helped with the dialog, but unity still doesn't start :'/
[13:33] <Saviq> No window decor, runs a few secs and exits
[13:34] <didrocks> willcooke: jbicha: the settings "interactive" doesnt work for me
[13:34] <didrocks> ah, you have to press for more than 0.5s
[13:34] <didrocks> (or 1s)
[13:35] <Saviq> "Fatal: Couldn't open display :0"
[13:35] <willcooke> didrocks, that's hardware dependent I think.  When does it generate the ACPI event
[13:35] <didrocks> I don't remember to have that delay on unity
[13:35] <didrocks> but I might be wrong :)
[13:35] <willcooke> didrocks,  on X220 - yeah, I does
[13:35] <didrocks> jbicha: shouldn't that be our default for the ubuntu session?
[13:35] <willcooke> lemme check
[13:35] <didrocks> willcooke: if you have it on, yeah :) I normally press that button only when I'm upset, so not often (hem ;))
[13:36] <Saviq> But yeah, gnome-shell now starts, so monitors.xml helped here
[13:36] <jbicha> didrocks: there are a few issues with it being default but since it's in Settings>Power, it's easy for users to opt in to
[13:36] <didrocks> jbicha: do we have logs of those issues?
[13:37] <willcooke> didrocks, confirmed, same on u7
[13:37] <didrocks> willcooke: ok, "good" then :) (and thanks for checking!)
[13:37] <didrocks> willcooke: and you know what, my screen is still really readable and clean! :)
[13:37] <jbicha> I don't like having the behavior of the Power Button be different if you log in to GNOME or log in to Ubuntu
[13:37] <willcooke> Saviq, I think Trevinho is your best bet for help there
[13:38] <didrocks> jbicha: that's not really an "issue" as per deficiency
[13:38] <jbicha> what should happen if no one is logged in?
[13:38] <didrocks> like, in gdm? I don't think the settings impacts gdm here, does it? (as it's per user)
[13:38] <jbicha> it's possible to lose work if something accidentally hits the Power button and you don't notice for 60 seconds
[13:39] <jbicha> shouldn't the behavior be the same though?
[13:39] <didrocks> wasn't that the case in unity and installing ubuntu gnome?
[13:39] <didrocks> you had different behaviors
[13:39] <didrocks> and I don't think the multiple session thing is something people will switch back and forth
[13:41] <jbicha> are you sure that Unity defaults to power off when power button is pressed?
[13:41] <seb128> willcooke, sorry, GNOME fail I don't get pings notifications :-/ no, no issue with that setting, just GNOME behaves crap regarding to power manager here, like it suspend when it should, can't configure the lid close behaviour, sometime doesn't suspend when it should
[13:41] <didrocks> TBH, I think it will be more common to have people installing Tweaks and trying to enable/disable mod extensions like crazy, sounds something more important
[13:41] <didrocks> jbicha: yes
[13:41] <popey> ooh! I had that today. My laptop didn't suspend on lid close, just sat there getting warm
[13:42] <seb128> didrocks, jbicha , I didn't follow the whole discussion but unity default to display the dialog with all the action on power button event
[13:42] <jbicha> didrocks: ok, I'd like the same settings for power button action for both GNOME and "Ubuntu"
[13:43] <didrocks> jbicha: I don't think we want to change any upstream default in the vanilla session
[13:43] <didrocks> that's the point of this session
[13:45] <jbicha> hmm, maybe
[13:51] <seb128> Trevinho, you should maybe add X-Ubuntu-Use-Langpack: yes to debian/control for unity so it keeps getting its translations included in langpacks
[13:52] <Trevinho> seb128: oh, yeah... if I could just get it built in 17.10 after gcc change.... I'll be back on this soon, but having no failures in my archs makes things a bit more complicated
[13:53] <Trevinho> I might try with some qemu though
[14:20] <seb128> willcooke, those weird visual glitches don't happen only on unlock for me but also when starting e.g firefox
[14:20] <seb128> which opens maximized here
[14:20] <seb128> unsure but could be xwaylands apps only
[14:20] <willcooke> I'm seeing it under X as well
[14:21] <seb128> it's pretty recent here I think
[14:21] <seb128> it was not bothering me before
[14:21] <seb128> I wonder if that's a gnome-shell 3.25 regression
[14:21] <willcooke> I thought it might be to do with the launcher
[14:21] <willcooke> or a combination
[14:21] <seb128> it could
[14:21] <willcooke> so, that rather neatly raises this...
[14:21] <seb128> but it was not doing it with 3.24 I think
[14:22] <willcooke> andyrock, While you're poking around inside mutter, could you see if you can work out what's going on there ^
[14:22] <willcooke> you can recreate the issue in question by:
[14:22] <willcooke> maximizing a window
[14:22] <willcooke> lock
[14:22] <willcooke> unlock
[14:22] <willcooke> see the window do a little wiggle
[14:23] <andyrock> willcooke: i'll take a look
[14:23] <willcooke> thanks!
[14:33] <seb128> kenvandine, hey, I tested eog snap yesterday and it shows the thumbnails for me
[14:39] <Saviq> Trevinho: any idea about snapped remmina complaining that it can't open :0 display? I'm on wayland atm, so maybe something not working with XWayland? the app isn't shown in the gnome-shell launcher, so meh...
[14:39] <kenvandine> seb128, awesome, thanks
[14:40] <Trevinho> Saviq: mh, no I've not tried that...
[14:40] <Trevinho> Saviq: I mean, I did try that some time ago
[14:40] <kenvandine> seb128, one thing i'm noticing though, we don't get window icons for snaps
[14:40] <Trevinho> but... Not recently
[14:40] <kenvandine> if you uninstall the eog deb
[14:40] <kenvandine> then run the snap, you won't get the window icon
[14:40] <Trevinho> Saviq: it's using the snap preload though, so maybe I should fix it to use new technologies
[14:40] <kenvandine> i think we need snapd to copy out the icon like it does the desktop file
[14:41] <kenvandine> and we need to add whatever directory it's copied to for theme icons?
[14:41] <seb128> Saviq, Trevinho, https://github.com/snapcore/snapd/pull/3398 for the "snaps not listed under wayland" (which is different of your display issue)
[14:41] <Saviq> seb128: ack, thanks
[14:47] <Saviq> Trevinho: can confirm it's a wayland issue, the snap works fine under Xorg
[14:49] <Trevinho> Saviq: mh, i see... I'll give it a look in next days, but there shouldn't be much different between real x and actual xwayland
[14:49] <Trevinho> Saviq: have you tried it in devmode to see where the failure is?
[14:49] <Trevinho> or if it run in that mode?
[14:50] <Saviq> Trevinho: I don't think there's a denial
[14:50] <Saviq> actually
[14:50] <Saviq> Trevinho: [ 4937.076699] audit: type=1400 audit(1504709436.461:198): apparmor="DENIED" operation="connect" profile="snap.remmina.remmina" name="/run/user/1000/wayland-0" pid=23505 comm="remmina" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[14:52] <Trevinho> mh, it might be somewhat related to some XDG_RUNTIME
[14:52] <Trevinho> it segfaults to me then, but still
[14:53] <Saviq> Trevinho: yeah segfault here, too
[14:54] <jibel> that's new, my laptop changes the brightness on its own and turns the screen off
[14:54] <jibel> exciting
[14:56] <Trevinho> Saviq: it seems setting the GDK_BACKENd doesn't change much
[14:56] <kenvandine> jibel :-D awesome
[14:56] <Trevinho> I mean to be x11
[14:56] <jibel> *something* calls /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness ...
[14:57] <jibel> but not me
[14:57] <jibel> that's really annoying, time for a reboot
[15:00] <didrocks> Laney: oh btw, while running, I think I got why you needed to set the env variable early
[15:00] <didrocks> it's actually before you start g-s-d
[15:00] <didrocks> as it's on X (don't know how it works under wayland)
[15:00] <didrocks> but it doesn't read the theme from gsettings
[15:00] <didrocks> but rather it's a xprop set by g-s-d
[15:00] <didrocks> so, you need the env var before starting it :)
[15:03] <Laney> right, it gets inserts into Net/ThemeName
[15:03] <seb128> Saviq, Trevinho, kenvandine has been fixing snaps to work under wayland, maybe he can help you
[15:35] <bdmurray> Why would I have no screensaver / lockscreen on one of my artful systems?
[15:35] <bdmurray> I looked for missing recommends and found none.
[15:35] <gQuigs> bdmurray: lightdm vs gdm, gnome-shell only works locking with gdm (AFAICT)
[15:36] <gQuigs> and then other environments don't seem to work with gdm (LXDE)
[15:38] <bdmurray> gQuigs: Do you know how I switch between them?
[15:39] <gQuigs> bdmurray: sure - sudo dpkg-reconfigure gdm3 IIRC
[15:40] <gQuigs> then it will prompt to choose the default - then reboot and see if lock screen works
[15:41] <jbicha> bdmurray: what desktop are you using?
[15:42] <jbicha> what are you doing to try to lock your screen? (keyboard shortcut, waiting a few min. etc)
[15:44] <bdmurray> jbicha: gnome, keyboard shortcut and waiting and suspending
[15:45] <jbicha> which keyboard shortcut?
[15:45] <bdmurray> jbicha: switching to gdm3 seems to have fixed it
[15:46] <bdmurray> jbicha: super+L seems to work again so that
[15:46] <jbicha> could you file a bug against gnome-shell?
[15:47] <jbicha> I think at least the lock button in the system status menu in the right of the top bar should have been working
[15:47] <bdmurray> jbicha: sure
[15:48] <jbicha> Ubuntu's GNOME Shell carries a few lightdm patches
[15:53] <jdstrand> Saviq: you need to plug the wayland interface
[15:54] <jdstrand> Saviq: don't worry about XDG_RUNTIME_DIR, the desktop part launcher is accounting for all of that
[15:55] <jdstrand> Saviq: you need 2.28 to get the wayland interface though
[15:55] <kenvandine> it's been working well for me with core from edge
[15:55] <kenvandine> all of my snaps now work with wayland
[15:56] <kenvandine> i had to add the opengl plug to quadrapassel as well
[15:56] <jdstrand> kenvandine: fyi, you should start plugging desktop and desktop-legacy now that they are committed (also 2.28)
[15:56] <jdstrand> https://github.com/snapcore/snapd/wiki/Interfaces#desktop
[15:56] <kenvandine> jdstrand, i'll add those to my wayland branches
[15:56] <jdstrand> Saviq: that goes for you too ^
[15:56] <kenvandine> i have branches for all of them adding wayland
[15:56] <jdstrand> cool
[15:56] <kenvandine> just not merged yet
[15:57] <jdstrand> I will be writing up some documentation in the forum for this and submitting a patch for the desktop part to advertise it
[15:57] <kenvandine> thx
[15:57] <jdstrand> just haven't gotten to it yet (2.28 isn't out yet, so that's ok)
[15:57] <kenvandine> since it'll all be in 2.28 i'll just do all of those changes in the same branches as wayland
[15:57] <kenvandine> jdstrand, when should 2.28 be out?
[15:57] <kenvandine> i thought i had heard this week
[15:58] <jdstrand> kenvandine: I think they are preparing it now
[15:58] <kenvandine> cool
[15:58] <jdstrand> kenvandine: probably a week or so
[15:58] <kenvandine> the wayland interface is working great for me :)
[15:58] <jdstrand> kenvandine: glad to hear! :)
[15:59] <jdstrand> kenvandine: I'm curious what else you did with the snaps to make them work with wayland beyond plugging the interface and using the updated desktop part
[16:00] <kenvandine> i had to add opengl to quadrapassel
[16:00] <kenvandine> that's it
[16:00] <jdstrand> ok
[16:00] <kenvandine> along with the unity7 interface of course
[16:00] <kenvandine> does desktop include opengl?
[16:00]  * kenvandine kind of thinks it should :)
[16:00] <jdstrand> oh, I think the segfaults I saw was that the gnome-24 content snap didn't work on 26.04
[16:01] <kenvandine> clutter apps need it
[16:01] <jdstrand> err
[16:01] <jdstrand> 16.04
[16:01] <jdstrand> kenvandine: so, I'd be really interested if you could drop the unity7 interface in favor of desktop and desktop-legacy
[16:01] <kenvandine> jdstrand, i can test that this week
[16:01] <jdstrand> that said, you probably want to still plugs unity7
[16:02] <jdstrand> but if you disconnect it, it would be interesting to see what denials pop out
[16:02] <jdstrand> (also disconnect x11 if you are plugging it)
[16:03] <jdstrand> in this manner we can make desktop and desktop-legacy better
[16:03] <jdstrand> kenvandine: ok, so to be clear, keep plugging unity7, but in your testing, disconnect it first
[16:04] <jdstrand> kenvandine: unless you don't expect these apps to run on unity7, then you can just drop it in favor of the other two
[16:04]  * jdstrand needs to write this forum post so everything is clear
[16:11] <bdmurray> jbicha: the lock button does work with lightdm, shall I still file a bug re keystroke and no time based locking?
[16:13] <kenvandine> jdstrand, ok, thx
[16:15] <kenvandine> jdstrand, for now i should use both desktop and desktop-legacy right?
[16:15] <kenvandine> for a11y
[16:16] <jbicha> bdmurray: yes, thanks
[16:17] <jbicha> most people using GNOME have been using GDM but there are some people who installed GNOME on Xenial who kept lightdm
[16:58]  * dobey misses unity8
[17:01] <kenvandine> dobey!
[17:02] <dobey> yup :-/
[18:10] <willcooke> night all
[18:43] <jdstrand> kenvandine: yes, both desktop and desktop-legacy
[18:44] <kenvandine> jdstrand, thx
[18:44] <jdstrand> kenvandine: desktop is 'safe' (eg, like wayland) where 'desktop-legacy' is 'transitional' (eg, like x11)
[18:44] <kenvandine> understood
[18:44] <jdstrand> kenvandine: desktop-legacy has the things that aren't safe yet, ibus, fcitx, a11y, etc
[18:45] <jdstrand> as they become safe, we'll adjust 'desktop' to have the safe accesses
[18:45] <kenvandine> cool
[19:32] <kenvandine> jdstrand, quadrapassel works with wayland, desktop, and desktop-legacy with x11 and unity7 disconnected :)
[19:33] <kenvandine> jdstrand, i do see this warning though
[19:33] <jdstrand> nice!
[19:33] <kenvandine> (quadrapassel:3338): Gdk-WARNING **: /build/gtk+3.0-GC0UmG/gtk+3.0-3.22.15/./gdk/x11/gdkwindow-x11.c:5573 drawable is not a native X11 window
[19:33] <kenvandine> which makes sense to some degree :)
[19:34] <kenvandine> ok, i get that with x11 connected as well
[19:34] <jdstrand> yeah. seems like maybe a bug in gdk
[19:34] <kenvandine> i hadn't rememberd that
[19:34] <kenvandine> yeah
[19:34] <jdstrand> thanks for testing :)
[19:34] <kenvandine> np
[19:35] <kenvandine> jdstrand, if i run into any issues i'll let you know
[19:35] <jdstrand> kenvandine: great, thanks! :)
[19:47] <gQuigs> should I remove "Flash" from the translations of ubiquity while I'm at it? (I know they will have to be retranslated anyway)
[19:47] <gQuigs> (or maybe my translation will count)
[20:08] <dmj_s76> andyrock: Trevinho: How much do you know about how Unity does backlight brightness?
[20:08] <Trevinho> dmj_s76: it's all in unity-settings-daemon
[20:10] <dmj_s76> I finally nailed down an issue we've been working around on nvidia systems to xbacklight and /sys/class/backlight getting out of sync.
[20:34] <infinity>  2978 adconrad  20   0  835048  44476  27716 S 198.3  0.2 531:02.32 gnome-software
[20:34] <infinity> Fun.
[21:49] <flexiondotorg> Trevinho WHat is happening with this ticket?
[21:49] <flexiondotorg> https://bileto.ubuntu.com/#/ticket/2848#audit_log
[21:49] <flexiondotorg> I'm hoping to work on landing the theme fixes while at UbuCon this weekend.
[21:50] <Trevinho> flexiondotorg: I was waiting my branch to be approved in order to publish
[21:50] <Trevinho> it should be the case now
[21:50] <flexiondotorg> Ideally I'd like to based on your merged fixes :-)
[21:50] <Trevinho> flexiondotorg:  nope https://code.launchpad.net/~3v1n0/ubuntu-themes/better-destructive-action/+merge/329392
[21:51] <Trevinho> flexiondotorg: we can merge it for now and we can fix the issue later
[21:52] <flexiondotorg> OK. As I'm looking at themes I can take a look.
[21:52] <flexiondotorg> So, merge and then fix up.
[21:52] <flexiondotorg> OK, I have to be up in 4 hours. So catch you tomorrow :-)
[22:04] <Trevinho> flexiondotorg: can you approva that MP?
[22:05] <flexiondotorg> No, I don't have those powers