[00:00] <xnox> ali1234: it's easier to parse files /usr/share/unity/indicators/*, make a list of processes and exec all of them / sigterm and kill them.
[00:00] <xnox> ali1234: also, without dbus activation there is nothing to activate indicators with if they auto shutdown.
[00:01] <xnox> ali1234: honestly using upstart for indicators is a massive overkill.
[00:05] <ali1234> i don't really care as long as it works :/
[00:05] <ali1234> we use upstart for session init anyway, and it seems to work okay there with the workaround
[00:21] <xnox> ali1234: real session init is different, as the startup and shutdown events are different and there is more of them.
[00:22] <xnox> ali1234: for "indicator-session" tedg crippled that work a fair amount.
[05:28] <pitti> Good morning
[05:29] <Mirv> darn, with arm64 the 10GB size limit of the PPA came to full
[05:29] <Mirv> and morning
[06:28] <darkxst> pitti, hey
[06:29] <darkxst> ok to change gnome-session instance to use XDG_CURRENT_DESKTOP instead of DESKTOP_SESSION?
[06:29] <darkxst> the current code makes no sense, given only gnome + gnome-classic should be using g-s-d
[06:31] <pitti> hey darkxst
[06:32] <pitti> darkxst: hm, I don't think I can give a qualified answer to that immediately
[06:32] <pitti> DESKTOP_SESSION=ubuntu
[06:32] <pitti> XDG_CURRENT_DESKTOP=Unity
[06:32] <pitti> darkxst: you mean $XDG_CURRENT_DESKTOP is an "official" one, and $DESKTOP_SESSION is an Ubuntu-ism?
[06:33] <darkxst> DESKTOP_SESSION is just the session name
[06:33] <pitti> which components set these? I guess lightdm/gdm are involved with that?
[06:33] <darkxst> u-s-d is start on INSTANCE=ubuntu
[06:33] <pitti> or is that just purely {gnome,ubuntu}-session?
[06:33] <darkxst> but other sessions will need u-s-d
[06:33] <darkxst> yes they are set by lightdm/gdm
[06:34] <pitti> darkxst: i. e. you are running /usr/share/xsessions/$DESKTOP_SESSION.desktop ?
[06:34] <pitti> and lightdm/gdm set that?
[06:35] <darkxst> pitti, mitya57 has (or is in the process of) switched gnome-flashback to XDG_CURRENT_DESKTOP=Unity
[06:35] <darkxst> but it still starts g-s-d, rather than u-s-d
[06:35] <darkxst> due the gnome-session instance in upstart being based of DESKTOP_SESSION
[06:36] <pitti> darkxst: so $DESKTOP_SESSION is set by the login manager, while $XDG_C_D is set by gnome/ubuntu-session itself?
[06:36] <darkxst> they are both set by login manager, but desktop_session is just the session name
[06:36] <darkxst> XDG_C_D will either be Unity or GNOME
[06:37] <pitti> Exec=gnome-session --session=ubuntu
[06:37] <pitti> TryExec=unity
[06:37] <pitti> ooh
[06:37] <pitti> i. e.  ubuntu.desktop actually starts unity, and never gnome
[06:37] <pitti> I had expected this to say Exec=ubuntu-session now, after the split?
[06:38] <pitti> darkxst: so /usr/share/xsessions/ubuntu.desktop says --session=ubuntu, what does that mean?
[06:39] <pitti> darkxst: it sounds a bit recursive :)
[06:41] <pitti> darkxst: anyway, you understand this a lot more than I do, so if it's the right thing to do and doesn't break anything existing, go ahead
[06:41] <darkxst> pitti, ubuntu-session only provides the desktop file, that is called by --session=ubuntu
[06:41] <pitti> (I'm just curious how it works these days)
[06:41] <pitti> darkxst: right, my question is why --session=ubuntu is *in* ubuntu.desktop -- at this point we already know that we want the ubuntu session
[06:42] <pitti> i. e. that --session=ubuntu obviously does something else than selecting a session .desktop
[06:42] <darkxst> there are two different session desktop files
[06:42] <darkxst> one for xsession and one for gnome-session
[06:42] <pitti> aah, /usr/share/gnome-session/sessions/ubuntu.session
[06:43] <pitti> DesktopName=Unity
[06:43] <pitti> darkxst: so lightdm/gdm read /usr/share/xsessions/, the user chooses "ubuntu", /u/s/xsessions/ubuntu.desktop starts gnome-session --session=ubuntu
[06:43] <darkxst> XDG_C_D (in upstart jobs) is set from X-LightDM-DesktopName
[06:44] <pitti> darkxst: and this reads /usr/share/gnome-session/sessions/ubuntu.session and thus starts u-settings-daemon, compiz, and sets XDG_CURRENT_DESKTOP=<DesktopName>, i. e. "Unity"?
[06:44] <pitti> does that sound right?
[06:44] <darkxst> pitti, nope, upstart jobs don't see gnome-session variables
[06:45] <pitti> darkxst: right, I mean just in terms of how the session is choosen and started (ignoring upstart jobs)
[06:45] <darkxst> well yes, although u-s-d and g-s-d are started by upstart
[06:46] <darkxst> compiz, gnome-shell etc get start via gnome-session
[06:46] <pitti> ah yes; the above clearly wasn't complicated enough yet :-)
[06:46] <pitti> darkxst: thanks for the heads-up
[06:46] <pitti> darkxst: so X-LightDM-DesktopName=Unity is the thing which gets exported to $XDG_CURRENT_DESKTOP, and that's what upstart jobs see?
[06:46] <darkxst> yup
[06:47] <pitti> (is it just me, or does that whole thing contain about two more layers of indirection than one can grasp?)
[06:48] <pitti> instance $DESKTOP_SESSION
[06:48] <pitti> exec gnome-session --session=$DESKTOP_SESSION
[06:48] <pitti> ok, so it seems this circumvents/overrides what's in /usr/share/xsessions/ubuntu.desktop?
[06:50] <darkxst> seemingly, but regardless the 'instance' is unrelated to the exec
[06:52] <darkxst> but DESKTOP_SESSION still comes from /usr/share/xsessions/ubuntu.desktop
[09:20] <Sweetshark> seb128: I just closed bug 739184 as "wontfix" in LibreOffice as the last comment clearly indicates its an issue in indicator-appmenu. This was the hightest heat bug in LibreOffice and still is the second highest heat bug in indicator-appmenu now and has been around since 2011 ...
[09:20] <ubot2`> Launchpad bug 739184 in unity (Ubuntu) "[Libreoffice] Mnemonics do not work in Unity" [Undecided,Triaged] https://launchpad.net/bugs/739184
[09:21] <seb128> Sweetshark, ok, thanks
[09:21] <Sweetshark> seb128: anything possible to maybe priotize this? it seems to be one of these "wont touch this" things ...
[09:22] <Sweetshark> (TBH I dont think it will be solved for LTS, but still ...)
[09:23] <seb128> Sweetshark, it's supposed to be fixed in trusty I think, seems to work for me
[09:24] <Sweetshark> seb128: oh? yey! ;)
[09:25] <seb128> Sweetshark, it was fixed in https://launchpad.net/ubuntu/+source/unity/7.1.2+14.04.20140214.1-0ubuntu1
[09:27] <Sweetshark> seb128: cool, anyone wanting to claim ownership of the bug and collect the karma for the fix? (its still in state confirmed/triaged in unity/indicator-appmenu on launchpad)
[09:28] <seb128> Sweetshark, I just close it
[09:28] <Sweetshark> seb128: ok.
[09:28] <seb128> but karma goes to attente who fixed it ;-)
[09:28] <seb128> you can assign to him to reflect that
[09:28]  * Sweetshark hugs attente.
[09:31] <Sweetshark> seb128: done
[09:31] <seb128> Sweetshark, thanks
[09:35] <pitti> hey seb128
[09:36] <pitti> moin moin seb128
[09:36] <Sweetshark> moin moin pitti ;)
[09:36] <seb128> pitti, hey, wie gehts?
[09:36] <pitti> gut, danke!
[09:49] <seb128> larsu, mdeslaur, others annoyed by that: https://launchpad.net/~ci-train-ppa-service/+archive/landing-001/ has a compiz version supposed to fix the "shrinking" windows, if somebody want to test it
[09:49] <seb128> https://launchpad.net/~ci-train-ppa-service/+archive/landing-008/ has "unity as lock screen"
[09:49] <seb128> which might be another good one
[09:50]  * seb128 opts in for both
[10:42] <seb128> dpm, hey
[10:43] <seb128> dpm, how are you?
[10:43] <dpm> hey seb128, good, good, and you?
[10:43] <seb128> dpm, if I go to http://developer.ubuntu.com/api/devel/ubuntu-13.04/qml/ui-toolkit/overview-ubuntu-sdk.html and click on "resources" in the top titles that gives me a page not found error, is that known?
[10:43] <seb128> dpm, I'm good thanks
[10:45] <dpm> seb128, those urls are deprecated. We're keeping them because things like scopes documentation haven't been imported into d.u.c yet. Try using http://developer.ubuntu.com/apps/qml/api/ instead
[10:45] <seb128> oh
[10:45] <dpm> we should be taking down the deprecated ones, yes
[10:45] <seb128> it's unfortunate because those are the first results in google for "ubuntu ui toolkit"
[10:46] <seb128> the first and only one on the first page
[10:47] <dpm> yeah :/
[10:47]  * dpm notes down a point for discussion in the docs session at UDS
[10:51] <dpm> seb128, updated the WIs on https://blueprints.launchpad.net/ubuntu/+spec/appdev-1403-dev-doc-next-steps
[10:51] <seb128> dpm, thanks
[11:34] <seb128> bregma, Trevinho: silo 1 (the compiz fix) looks good to me (been running it for some hours), you guys should land it ;-) (the lockscreen has some issues though, cf my email, so maybe not that one yet)
[11:36] <bregma> seb128, I'm getting an unusually high number of AP test failures with that landing, I'm moving testing to a different machine and rerunning to see if it's just a messed-up test environment
[11:36] <seb128> bregma, the compiz one or the unity one?
[11:36] <bregma> seb128, I have both, which means rerunning with just the compiz one on a cleaner machine
[11:37] <seb128> k
[11:37] <seb128> I wouldn't be surprised if the unity one had issues
[11:37] <bregma> on the other hand, the lock screen seems to work when tested manually
[11:37] <seb128> the minimize animation looks different to me for example
[11:38] <seb128> but maybe that one is just me, I don't minimize often, I hit it by error a bit earlier
[11:38] <seb128> lock screen works nicely indeed ;-)
[11:42] <mdeslaur> seb128: new compiz seems great, thanks! (thanks Trevinho!)
[11:42] <seb128> good
[12:12] <Saviq> seb128, you knowing the desktop... it seems like some windows (nautilus, xchat-gnome for me) again shrink on opening, most probably due to menu bar going away (into the global bar)
[12:12] <Saviq> I remember that bug from days back, it seems to be here again
[12:13] <seb128> Saviq, https://launchpad.net/~ci-train-ppa-service/+archive/landing-001/+sourcepub/4010774/+listing-archive-extra
[12:13] <seb128> bug 1204307
[12:13] <ubot2`> Launchpad bug 1204307 in Compiz "Regression: The size of all windows grows by the size of the decoration each time Compiz gets restarted" [Medium,In progress] https://launchpad.net/bugs/1204307
[12:14] <Saviq> seb128, I'm not sure that's that...
[12:14] <seb128> the bug referenced is wrong
[12:15] <Saviq> http://people.canonical.com/~msawicz/screencast_00000.mp4
[12:15] <seb128> Saviq, well, if if what you describe is "windows shrink by their decoration height", that's fixed in that ci train landing
[12:15] <Saviq> seb128, ok
[12:15]  * Saviq gets that
[12:15] <seb128> Saviq, you can install compiz and verify ;-)
[12:15] <seb128> Saviq, eperm on that url
[12:15] <Saviq> I'm doing just that :)
[12:21] <Trevinho> mdeslaur: yw... Sorry for delay, but I've a list full of things, and deadlines approaching :P
[12:23] <mdeslaur> Trevinho: np, I know how it is :)
[12:31] <Saviq> seb128, grr, anyway, it's fixed
[12:32] <seb128> Saviq, why "grrr" then? ;-)
[12:32] <Saviq> seb128, grrr for perms ;)
[12:32] <seb128> oh
[12:32] <seb128> good it's fixed ;-)
[12:33] <Saviq> seb128, how about nautilus hanging on opening new window when gvfs times out? i.e. gvfs-mounted ssh connection goes away for whatever reason, clicking the nautilus icon results in the "hourglass" icon indefinitely
[12:33] <Trevinho> seb128: ah I've a question for you: what is the most safe way to detect a guest session?
[12:34] <seb128> Saviq, I don't know about this one, feel free to open a bug with a stacktrace of the hang
[12:35] <seb128> Trevinho, I've no idea, that's one for robert_ancell rather ;-)
[12:35] <Trevinho> seb128: ok, thanks, as for now I've used the "guest-" prefix trick... but not the best thing probably
[12:36] <Saviq> seb128, well, it's not actually hanging... it's just waiting for gvfs... I did apport-bug --hanging and bug #1290835 is the result
[12:36] <seb128> Saviq, thanks (I see what you mean)
[12:48] <Trevinho> seb128: do we also want to see the switch to guest in the locker?
[12:56] <seb128> Trevinho, no strong opinion on this one, it's available from the greeter
[13:02] <Trevinho> seb128: unfortunately not to patch all the indicators to support a new kind of indicator, for now we've to use a workaround in unity: we load indicators in lockscreen_mode if any is available, otherwise we fallback to greeter mode, but is not the nices solution
[13:03] <seb128> Trevinho, that seems a good way to deal with the transition
[13:03] <Trevinho> seb128: yeah it would have been nicer if indicator_ng_new_for_profile would have returned a null if the profile is not available, but it doesn't seem to be the case... :/
[13:05] <Trevinho> larsu: ^ I guess you don't want to do that as the profile might be available anyway or is it a bug?
[13:07] <larsu> Trevinho: indicatorng has a failable constructor, it should return NULL when it can't find the profile
[13:07] <larsu> if not, that would be a bug
[13:07] <Trevinho> larsu: it doesn't :(
[13:08] <Trevinho> larsu: it always returns a valid indicator...
[13:08] <larsu> Trevinho: ah indeed. It fails when it can't load the file, but not if it can't load the profile
[13:08] <larsu> I think that's dumb. Let me see why I did it that way (and change it if I can)
[13:08] <Trevinho> larsu: thanks
[13:09] <larsu> Trevinho: hm, there's a comment in there that non-existant profiles are handled by returning a valid indicator but leaving it empty
[13:10] <larsu> and I think I did that because otherwise panels would have to deal with that
[13:10] <Trevinho> larsu: mh, probably but... the fact is that also valid indicators are not empty, so it's hard do get which one is valid or not
[13:10] <Trevinho> I mean, they get filled by signals..
[13:10] <Trevinho> generally
[13:10] <larsu> Trevinho: why do you want to know?
[13:11] <Trevinho> larsu: since I want to add a new lockscren profile, but falling back to greeter if that is not avaialbe
[13:11] <Trevinho> (not to patch all the indicators)
[13:12] <Trevinho> larsu: i guess all the panels handle possible null values on return I think, btw...
[13:12] <Trevinho> as indicators might always not be installed
[13:12] <larsu> right
[13:12] <larsu> but I don't like the idea of panels implementing fallbacks
[13:12] <larsu> then we'd have them in two places
[13:12] <larsu> why don't you just patch the indicator files?
[13:13] <Trevinho> larsu: yeah, so... is it that enough or should I also patch the code?
[13:14] <larsu> Trevinho: no, I prefer to keep it this way now that I remember why I did it. Feel free to ping me with the MRs for quick approval (I can also help out if you don't have the time. let me know)
[13:14] <larsu> MRs for indicator files, I mean ;)
[13:15] <Trevinho> larsu: ok, thank... an help would be appreciated, yes :P
[13:16] <Trevinho> larsu: probably some custom modes should be applied to indicator keyboard (that is showing all the things always) and indicator-session (on which I'm working on now)
[13:16] <larsu> Trevinho: simply have a [lock_screen] profile which points to [greeter]? For which indicators?
[13:17] <Trevinho> larsu: all :)
[13:17] <Trevinho> a part from messaging
[13:17] <larsu> Trevinho: dude.
[13:17] <Trevinho> bluetooth...
[13:17] <larsu> if I apply the fallback to all, just use the other profile
[13:17] <Trevinho> larsu: yes, sure...
[13:17] <Trevinho> larsu: I meant that for indicator-session I need to make the desktop_lockscreen profile a little different
[13:18] <Trevinho> that's what I'm doing now
[13:18] <larsu> okay
[13:18] <Trevinho> larsu: so, just need datetime, keyboard power and sound
[13:19] <larsu> Trevinho: okay, will do.,
[13:19] <Trevinho> (keyboard to be fixed later, btw)
[13:19] <Trevinho> larsu: thanks a lot
[13:19] <larsu> Trevinho: I wonder if we should have a default ObjectPath, so that keyboard can have the same thing on all profiles
[13:20] <larsu> probably not worth it though, as most indicators will be slightly different on the profiles
[13:20] <Trevinho> larsu: keyboard need not to show some options in lockscreen mode (the ones to open options)...
[13:20] <larsu> ah okay
[13:20] <larsu> there you go :)
[13:21] <Trevinho> larsu: is currently doing that in greeter, but not showing since.. well it's thte greeter :)
[13:22] <larsu> Trevinho: lockscreen or lock_screen?
[13:22] <seb128> Trevinho, larsu: speaking of sound, what should be the behaviour on the lock screen? Having the play/pause controls is somewhat nice, but having the players listed means anyone can start those...
[13:22] <Trevinho> larsu: I've called it desktop_lockscreen
[13:22] <larsu> Trevinho: okay
[13:22] <Trevinho> seb128: probably showing the one playuing only
[13:22] <larsu> seb128: is there a bug about that?
[13:23] <seb128> larsu, not yet, I just noticed, I'm going to open one
[13:23] <larsu> cool, I'll fix it later
[13:30] <larsu> Trevinho: MRs are up
[13:30] <Trevinho> larsu: cool, approving in a sec
[13:33] <Trevinho> bregma: we'd need also these http://pastebin.ubuntu.com/7073548/ in the ppa, and soon to rebuild unity...
[13:41] <Trevinho> seb128: as for the session indicator, do we want a list of users (as it happens with  desktop) or just a way to switch to greeter to select user?
[13:41] <seb128> Trevinho, I'm not a designer :p I'm happy with any of those solutions
[13:41] <seb128> I still think that design is wrong btw
[13:41] <seb128> imho we need an element next to the password entry to send to the greeter
[13:42] <seb128> it's really unconvenient to go all the way to the menu for that
[13:42] <Trevinho> seb128: mh well, it might be, but it wouldn't be consistent with desktop still
[13:43] <Trevinho> imho the lockscreen should be user-centric, switching is just something that might happen
[13:43] <seb128> desktop doesn't have a password entry in the middle :p
[13:43] <seb128> yeah, maybe
[13:45] <attente> Trevinho: hey, about https://code.launchpad.net/~attente/compiz/1284532/+merge/208908/comments/495199, is that unity profile also used for flashback?
[13:53] <Trevinho> attente: no, but the gsettings are shared between profiles by default
[13:54] <Trevinho> attente: so basically the gsettings defaults should have all we need, then you can use migration scripts to add/remove things per profile
[13:54] <Trevinho> not the best thing, but what we've to deal with
[13:57] <attente> Trevinho: ok, thanks
[14:00] <Trevinho> seb128: we should probably handle differnetly the case where w've multiple users: in that case we show a "Lock/Switch Account…" label... and that's fine, but  I think we should use a different callback then (so use unity greeter by default)
[14:02] <seb128> om26er, there?
[14:02] <om26er> seb128, hello
[14:03] <seb128> om26er, hey
[14:03] <seb128> om26er, could you rebase https://code.launchpad.net/~om26er/ubuntu-system-settings/pep8_pyflakes_fix/+merge/207966 on https://code.launchpad.net/~laney/ubuntu-system-settings/migration-script-no-crash/+merge/210005 ?
[14:03] <seb128> om26er, I'm trying to do a landing, we have a bunch of changes in the queue, but those 2 conflicts
[14:04] <seb128> om26er, should be a trivial change, but Laney is off on holidays so yours need to be rebased
[14:04] <om26er> seb128, will do that in 20mins, in a standup. is that fine ?
[14:04] <seb128> om26er, sure, thanks
[14:07] <Trevinho> larsu: here you are https://code.launchpad.net/~3v1n0/indicator-session/lockscreen-mode/+merge/210415
[14:07] <larsu> Trevinho: charles maintains session. I'd be happier if he did the review
[14:07] <larsu> (looks good to me though)
[14:08] <Trevinho> larsu: ah sure... I can wait charles review then :)
[14:08] <Trevinho> charles: let me know if you prefer to move things in a different function, instead of these "ifs" based on profile...
[14:18] <seb128> sil2100, didrocks, pitti, others: want to test https://launchpad.net/~ci-train-ppa-service/+archive/landing-009/ ? should fix unity grabbing the keybinding from your command line IRC clients
[14:24] <pitti> seb128: ah, I remember that I once had that problem (grabbing alt+left/right/up), but I don't remember any more how I worked around it
[14:24] <pitti> seb128: i. e. what do I need to do to undo this workaround?
[14:24] <seb128> pitti, dunno, that bug is new from trusty, if your workaround is old it's probably not the same issue
[14:25] <pitti> seb128: it happened maybe three weeks ago or so?
[14:25] <seb128> pitti, the issue there is things like "ctrl-<letter>" activating a menu item rather than the feature they are mapped to in e.g irssi
[14:25] <seb128> pitti, right
[14:25] <sil2100> seb128: oh, it's built, testing then!
[14:25] <seb128> did you remap your keybindings? or disabled the integrated menu?
[14:25] <pitti> ah, I noticed that alt+b now opens the terminal menu instead of my previous keybinding to put the window to the back
[14:25] <pitti> seb128: I remapped that wm function to ctrl+b
[14:26] <pitti> I didn't think that was a bug
[14:26] <pitti> it definitively grabbed alt+cursor as well, but I can't say any more what the workaround was
[14:26] <seb128> pitti, that seems different from conflict with local commands and menu
[14:26] <seb128> hum, k
[14:33] <slowcon> hey guys. looking to downgrade from unity to lxde
[14:33] <slowcon> would you suggest rebuilding the server?
[14:33] <seb128> slowcon, hey, wrong channel, #ubuntu for user questions
[14:34] <slowcon> thanks seb128
[14:34] <larsu> seb128: is bug #1290067 about there not being a "New Empty Document" thing anymore?
[14:34] <ubot2`> Launchpad bug 1290067 in nautilus (Ubuntu) "New File menu in nautilus (ubuntu session) is missing option to create a 'New Document'" [Low,Confirmed] https://launchpad.net/bugs/1290067
[14:35] <seb128> larsu, yes
[14:35] <larsu> okay
[14:35] <sil2100> seb128: tested it quickly locally on guest session and it seems to fix the issue \o/
[14:36] <sil2100> seb128: unity-gtk-module that is
[14:36] <seb128> sil2100, thanks, landing that then (I tested with other apps/normal usecases here)
[14:37] <sil2100> :)
[14:37] <sil2100> seb128: thank you!
[14:38] <seb128> sil2100, credits go to attente for doing all the work, I'm just doing the landing
[14:39] <sil2100> attente: thanks for fixing, it's so good to have irssi working nicely with my terminal again
[14:41] <attente> sil2100: seb128: thanks for landing ;)
[14:41] <seb128> attente, yw! I didn't block on the one desrt started reviewing, we can do another for that one when it's ready
[14:43] <attente> seb128: yeah, not worried since it's low priority
[14:44] <desrt> the use_underline one?
[14:47] <attente> desrt: yeah
[14:48] <desrt> attente: replied again
[14:48] <xnox> new wallpapers are up on the bug report =) \o/
[14:48] <desrt> my brain is not working well this week :(
[14:48] <seb128> xnox, nice, who is uploading?
[14:48] <seb128> xnox, btw did you manage to help mpt with his upgrade issues?
[14:49] <mpt> seb128, we’re still in the middle of upgrading
[14:49] <seb128> mpt, I though you were done upgrading but the machine wouldn't boot anymore
[14:49] <xnox> seb128: no idea, the tarball is up on the bug report https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1275798 I've never done fresh series of wallpapers.
[14:49] <ubot2`> Launchpad bug 1275798 in ubuntu-wallpapers (Ubuntu) "14.04 wallpapers package" [Undecided,New]
[14:49] <xnox> seb128: we are booted into trusty
[14:49] <mpt> seb128, that was because the upgrade got stuck part-way
[14:49] <seb128> oh :/
[14:49] <seb128> "great"
[14:50] <mpt> “yeah”
[14:50] <seb128> kenvandine, who does wallpapers updates nowadays? still you? ;-) see ^
[14:50] <kenvandine> sure :)
[14:50] <xnox> seb128: yeah, new kernel wasn't installed, grub was out-of-sync and most packages were unpacked but not configured =/ a complete mess. and ifupdown did a confffile prompt =/
[14:51] <seb128> kenvandine, thanks ;-)
[14:51] <mpt> seb128, so I was right about the conf file prompt after all
[14:51] <seb128> mpt, seems so
[14:53] <om26er> seb128, i merged with that branch but pep8 fails on the migrator script with: http://paste.ubuntu.com/7073921/
[14:53] <om26er> I had to: from __future__ import print_function
[14:53] <om26er> is that fine to keep that in ?
[14:58] <seb128> om26er, seems fine to me, if that makes it happy
[14:59] <charles> Trevinho: if the changes were bigger, it would make more sense to split the new profile out into separate code... but I'm ok with the if's you've got in that MR
[14:59] <Trevinho> charles: nice :)
[14:59] <charles> Trevinho: thanks for the patch :)
[15:00] <Trevinho> charles: yw
[15:03] <om26er> seb128, btw a first attempt to improve those tests is also ready. https://code.launchpad.net/~om26er/ubuntu-system-settings/fix_tests/+merge/210102
[15:05] <ritz_> cyphermox,  hi, https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1116317 . planning to push the debian patch in ?
[15:05] <ubot2`> Launchpad bug 1116317 in network-manager-applet (Ubuntu Raring) "[ffe] allow option to create user connections by default" [Medium,In progress]
[15:06] <seb128> om26er, yeah, I saw, it's a lot of changes, would be nice to have smaller merge proposal with limited scope
[15:06] <om26er> its still 25% of it ;)
[15:07] <seb128> still, you mix different improvements and it's not easy to understand where you are going/why you are changing things
[15:08] <om26er> I tried to differentiate everything in each commit
[15:09] <om26er> seb128, I can try to divide it, though most of it is only changing the test_about which I think makes sense to change together
[15:09] <seb128> om26er, ok, I guess I'm going to try to spend time understanding where you are going and why then
[15:09] <seb128> om26er, it would help if you would put that in the description
[15:10] <seb128> om26er, hum, did the pyflake merge request url change? did you superseed the previous one?
[15:10] <seb128> om26er, what is invalid on https://code.launchpad.net/~om26er/ubuntu-system-settings/pep8_pyflakes_fix/+merge/207966 ?
[15:10] <om26er> seb128, https://code.launchpad.net/~om26er/ubuntu-system-settings/pep8_pyflakes_fix/+merge/210430
[15:11] <om26er> seb128, I had to do a resubmit because didn't find a way to add laney's branch as prerequisite for already proposed branch
[15:11] <seb128> om26er, right, that's really annoying, I had the old URL in a CI train landing silo, I need to ask for a silo reconfiguration if you change the url
[15:11] <seb128> oh
[15:11] <seb128> that's fine then, I'm keeping the old one
[15:11] <seb128> they merge in order
[16:09] <seb128> tedg, attente: indicator-keyboard doesn't seem to have an upstart script or autostart, is that wanted?
[16:09] <seb128> (I guess it's working through dbus activation)
[16:10] <tedg> seb128, Yeah, MR proposed, waiting for silo.
[16:10] <seb128> tedg, oh ok, you included it with the start changes?
[16:10] <tedg> seb128, Yeah, makes every indicator the same. :-)
[16:11] <tedg> Welcom
[16:11] <tedg> Oops
[16:20] <mpt> xnox, those erlang packages were used by couchdb, which I guess was left over from Ubuntu One
[16:21] <xnox> mpt: =)
[16:21] <seb128> we need to do a better job at cleaning stuff on upgrade
[16:28] <mpt> xnox, the new person to review visual design changes is Jouni Helminen
[16:29] <xnox> mpt: cool.
[16:38] <xnox> seb128: Laney: experiencing high-dpi on markm's machine is cool. So it's bare-metal now, and after scaling gnome and unity all is good, but we don't have a scaling web-browser. Both firefox and chromium use gtk2?! and webbrowser-app/qt5 is not picking up scaling either =(
[16:39] <xnox> ooh, i'll try out epiphany-browser, maybe that would work?!
[16:39] <seb128> xnox, qengho is working on hidpi support in chromium, he has a ppa for it
[16:39] <Trevinho> larsu: I saw you've an ubuntu-themes patch waiting, I?ve one that is going to be ready in few minutes as well, I guess we can just make one landing together, isn't i?
[16:40] <xnox> seb128: oh, cool. Link? i'd like markm to try that out.
[16:40] <seb128> xnox, https://launchpad.net/~cmiller/+archive/chromium-browser-dev-daily
[16:40] <larsu> Trevinho: yes. There'll be another one coming as well
[16:41] <seb128> Trevinho, yeah, don't worry, no theme landing today, we can do one tomorrow or later in the week
[16:41] <Trevinho> seb128: well, it's UIF coming, and this needs to go in before, isn't it: https://code.launchpad.net/~3v1n0/ubuntu-themes/borderless-decorations
[16:42] <seb128> Trevinho, right, UIF is thursday, so still some days to land
[16:42] <seb128> Trevinho, we already did a theme landing today, we can do another one tomorrow
[16:42] <Trevinho> also today is my last day for this week, so... Although I might be somewhat available, I'm not here by day
[16:44] <seb128> Trevinho, oh, urg, I hope the lockscreen is in shape/others unity member can get it through
[16:44] <seb128> Trevinho, enjoy your days off!
[16:44] <seb128> Trevinho, can you get somebody to review/approve the theme change btw? maybe a designer?
[16:46] <Trevinho> seb128: the lockscreen is in shape I think... and andyrock could check it in case anyway. Anyway, if there are problems I'll surely check what happens in the evening (I'm going to ski, so... in the eveing there's always time for some rest :P)
[16:46] <seb128> Trevinho, ;-)
[16:46] <Trevinho> seb128: as for the theme changes, I've done them with jounih
[16:46] <seb128> ok, good
[16:46] <seb128> so just get him to approve it ;-)
[16:46] <Trevinho> I should probably mention it on the MR
[16:55] <seb128> bregma, so what's the landing status for the lockscreen? do you need help?
[16:56] <seb128> bregma, Laney said it needs to land by wednesday for the ffe to be valid, I don't see that happening if we don't make a push for it
[16:59] <bregma> seb128, I'm redoing the AP tests, now that the compiz landing is out of the way ... takes a couple of hours for a complete run
[16:59] <seb128> bregma, well, we know that we are going to need to add indicators to that landing slot, we should do that now and ask for a reconfigure
[17:00] <seb128> bregma, there is no point to wait for the autopilot results to do that
[17:00] <bregma> mmm, true
[17:00] <seb128> that would get use closer from testing a full set
[17:00] <seb128> even if we need another round when you get the results of the tests
[17:02] <seb128> bregma, http://paste.ubuntu.com/7074536/ imho
[17:02] <bregma> seb128, how can you answer questions I'm typing before I even hit enter?
[17:02] <seb128> ;-)
[17:40] <Trevinho> lol, well I also pasted that before... probably it got lost :)
[17:57] <Trevinho> bregma: the lockscreen packages were building because the commit message missing. I've fixed them
[18:00] <seb128> Trevinho, seems like he already kicked a retry ;-)
[18:19] <bregma> some indicators are getting a depwait on ppc64el: missing liburl-dispatcher1-dev
[18:22] <seb128> bregma, that's fine, it's normal state in the archive as well
[18:23] <seb128> it boils down to qt5 missing on those archs, britney is going to be fine with it since it's not a regression
[18:23] <bregma> that britney, she's such a sport sometimes
[18:23] <bregma> usually she is not my friend at all
[18:24] <seb128> yeah that happens when you are not nice to her... ;-)
[18:35] <bregma> seb128, my AP test runs with the lockscreen silo on a clean(er) machine look good: assuming the latest indicator changes conform, will we be OK to land this change?
[18:36] <seb128> bregma, seems good to me yes, I've been running that ppa all day and I didn't notice issues (out of the indicators which are building atm)
[18:40]  * didrocks waves good evening and good night!
[18:42] <BigWhale> Borderless gnome terminal will hurt my productivity. Just so you ALL know this. ;)
[18:43] <seb128> Trevinho, ^
[18:44] <Trevinho> BigWhale: just open a tab and you'd get borders :P
[18:45]  * BigWhale bursts into tears.
[18:45] <BigWhale> :>
[18:45] <Trevinho> :)
[18:45] <seb128> lol, I don't even notice the difference, tell how much I care about details ;-)
[18:46] <Trevinho> seb128: only because you're not running it... I *KNOW* that you'll find any bug at any pixel once relased (or just before) :)
[18:46] <seb128> haha
[18:46] <BigWhale> When we had borderless windows in 10.11? 11.04? I had a lot of trouble with overlapping terminal windows.
[18:47] <seb128> Trevinho, I'm running it, I build your branch before approving the change
[18:47] <seb128> built
[18:47] <ali1234> i can highly recommend terminator as a replacement for gnome-terminal
[18:47] <Trevinho> seb128: ah, ok then :)
[18:47] <seb128> Trevinho, it's in a landing slot now btw
[18:47] <Trevinho> seb128: ah, cool :)
[18:47] <BigWhale> ali1234, google is useless for this... :> All I get are cyborgs.
[18:48] <ali1234> it's in the respositories
[18:48] <ali1234> or however you spell it :)
[18:48] <seb128> Trevinho, but yeah, it feels weird, I'm noticing it on nautilus more ;-)
[18:48] <BigWhale> ali1234, I have to see the screenshots first! :))
[18:48] <Trevinho> seb128: that's your spot...
[18:49] <Trevinho> seb128: ah, I see the silo failed because gnome-screensaver... should we add the  MR instead?
[18:50] <seb128> Trevinho, dunno, that seems like a bug in the CI script, gnome-screensaver is listed in the "sources"
[18:50] <ali1234> BigWhale: http://gnometerminator.blogspot.co.uk/p/introduction.html
[18:50] <Trevinho> seb128: is that blocking anything or can be considered a "warning"?
[18:51] <seb128> Trevinho, we can overwrite it, seems a buggy warning
[18:52] <Trevinho> seb128: also in the ppa there are some dep-wait for ppc64el...
[18:52] <BigWhale> ali1234, it does look interesting
[18:52] <BigWhale> running it now
[18:52] <ali1234> the window splitting is very useful
[18:52] <seb128> Trevinho, yeah, qt5 is missing on those archs, same in trusty, not an issue
[18:53] <seb128> Trevinho, who change unity/compiz in a way that made update-manager not resizable? ;-)
[18:53] <Trevinho> seb128: I've no idea... who was that bad guy?!
[18:53]  * Trevinho ops...
[18:53] <seb128> lol
[18:54] <seb128> why?!?!?!
[18:54] <seb128> do you hate us? ;-)
[18:54] <Trevinho> seb128: well, no really I don't know
[18:54] <Trevinho> seb128: ah, well the fact is that window is not resizable in terms of hints
[18:55] <seb128> right, but compiz used to ignore that (I think)
[18:55] <Trevinho> seb128: well, more than non-resizalbe is non-maximizable
[18:55] <Trevinho> mh, it looks like a bug :P
[18:56] <Trevinho> I never use it, so i didn't notice :P
[18:56] <seb128> haha
[19:09] <captainflammy> .
[19:12] <Trevinho> seb128: funny thing is taht if you maximize the update-manager (double clicking on the decoration), then once restored is resizable
[19:12] <Trevinho> seb128: so, I guess it's something like that it doesn't notify us properly when it changes its alowed actions
[19:12] <Trevinho> or, we don't update when it asks (afaik I ignored some changes that were duplicated)
[19:33] <bregma> seb128, indicator changes in the lockscreen seem good now, have you tested them too?
[19:41] <seb128> bregma, hey, just had dinner, let me upgrade
[19:52] <seb128> bregma, Trevinho: so, I updated, looks fine, out of the fact that indicator-sound|power|keyboard lets you run some apps from the locked screen (they open behind the lock but you can spam the session)
[19:53] <seb128> bregma, Trevinho: I wouldn't block landing on that (we had too much delay) but that's something that should be addressed in the next days if you can (I know Trevinho is off until eow)
[19:53] <seb128> bregma, Trevinho: +1 from me for landing assuming somebody is going to follow up on those (we can help if needed)
[19:54] <bregma> I see that from the keyboard, but sound just has volume for me
[19:54] <seb128> does it has any player in your session?
[19:55] <seb128> if no, start rhythmbox or totem and close it, they get added the first time you run them ;-)
[19:55] <bregma> ah, OK, I don't have a player on that system
[19:56] <seb128> but that's a bug for us, larsu said he would have a look, I need to open a bug about it
[19:56]  * larsu will have a look tomorrow
[19:56] <seb128> larsu, you shouldn't be around anymore!
[19:56] <seb128> larsu, you fixed too many bugs for a day, go enjoy your evening ;-)
[19:57] <Trevinho> seb128: yeah, let's land it now :)
[19:57] <larsu> seb128: I am (as much as I can with my knee). What are you still doing here?
[19:57] <Trevinho> seb128: the indicator things are easily fixable now
[19:57] <Trevinho> seb128: since all needs to define custom states for desktop_lockscreen
[19:57] <seb128> larsu, hum, me? let's pretend I didn't say anything :p
[19:58] <Trevinho> and larsu can do it :P
[19:58] <Trevinho> (or we can also :))
[19:58]  * larsu hides
[19:58] <seb128> lol
[19:58] <Trevinho> ehehe
[19:58] <seb128> in fact indicator-power opens gnome-power-manager on the greeter as well
[19:58] <seb128> I though charles fixed that one
[19:59] <seb128> bregma, Trevinho: let's land it
[19:59] <Trevinho> seb128: yeah
[19:59] <seb128> Trevinho, don't worry about indicators, those are minors issue we can sort for you
[19:59] <charles> hurm, I don't think I've seen that ticketed before
[19:59] <seb128> Trevinho, enjoy the skiing ;-)
[19:59] <bregma> seb128, I'm just doing a quick sanity test on the phone, because of the ABI change
[19:59] <Trevinho> seb128: thanks :)
[19:59] <seb128> bregma, that makes sense
[19:59] <charles> seb128: the fixed one you're thinking of is "Add Event..." opening evolution in the datetime indicator
[19:59] <bregma> didrocks made me
[20:00] <charles> seb128: could you ticket the indicator-power one?
[20:00] <seb128> charles, like https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1256872 that I opened on 2013-12-02. ;-)
[20:00] <ubot2`> Launchpad bug 1256872 in indicator-power (Ubuntu) "shouldn't open battery statistics dialog on the greeter" [High,New]
[20:01] <seb128> charles, I though you guys picked them all/fixed the "open on greeter" issues for some reason, sorry for not checking earlier
[20:01] <seb128> charles, I think you fixed at least the session running g-c-c, I didn't check if that was true for the other ones
[20:02] <charles> seb128: !
[20:02] <charles> thank you
[20:02] <seb128> charles, yw ;-)
[20:02] <seb128> oh, robert_ancell just joined
[20:03] <seb128> robert_ancell, hey
[20:03] <robert_ancell> hello
[20:03] <seb128> robert_ancell, we are talking about landing https://launchpad.net/~ci-train-ppa-service/+archive/landing-008 to distro (unity lock screen) ... +1 0 -1 ?
[20:04] <robert_ancell> I didn't run it locally but +1 for the concept
[20:04] <seb128> lol
[20:04] <seb128> bregma, k, click the button, if it goes wrong just blame it on robert_ancell, he gave a +1
[20:04] <robert_ancell> yeah, I'll just fix it quick before you wake up :)
[20:05] <seb128> robert_ancell, done with lightdm fixes? ;-)
[20:05] <robert_ancell> never done...
[20:05] <robert_ancell> seb128, have you noticed an improvement in user switching?
[20:05] <seb128> do you still have some stuff that are important there?
[20:06] <robert_ancell> seb128, there's an odd bug that's occuring in SuSE that I want to fix in-case it's hitting some of our users
[20:06] <seb128> robert_ancell, did you see my email? the "wipe your session" issue is fixed ;-)
[20:06] <robert_ancell> cool
[20:06] <seb128> oh, which one?
[20:06] <robert_ancell> seb128, the session ends up with a different Xauthority to the server
[20:06] <seb128> is that one of those "can't login anymore"?
[20:07] <robert_ancell> bug 1260220
[20:07] <ubot2`> Launchpad bug 1260220 in Suse "Greeter and other clients cannot connect to X server" [Medium,Confirmed] https://launchpad.net/bugs/1260220
[20:07] <seb128> doesn't seem nice
[20:07] <robert_ancell> yeah
[20:07] <robert_ancell> Never seen it myself
[20:07] <seb128> I don't think I've seen ubuntu reports about that
[20:08] <robert_ancell> seb128, me neither. But it might be something that's just less likely in Ubuntu so would like to find the cause
[20:08] <seb128> right
[20:08] <robert_ancell> seb128, oh, I found out why we weren't showing up in "last" - we weren't writing to wtmp/btmp. Man those interfaces are awful
[20:08] <robert_ancell> So that one's in the queue
[20:08] <seb128> that didn't make it to your upload today?
[20:08] <robert_ancell> no, that will be in the next one
[20:08] <seb128> I saw the mps and the upload, but I didn't look at the times
[20:08] <seb128> ok
[20:09] <seb128> can you comment on the GNOME bug I pointed you at/close it?
[20:09] <robert_ancell> yeah, I will do. Tell them to remove that hack :)
[20:09] <seb128> I need to drop the change from u-c-c I guess, it makes every sudo session being listed
[20:09] <seb128> they didn't take it
[20:09] <robert_ancell> yes, the pts thing is really wrong
[20:09] <robert_ancell> but it's really all heuristics trying to interpret what utmp records actually mean
[20:10] <seb128> we are the only ones who have it, Laney made me add it because otherwise the history was empty
[20:10] <robert_ancell> because there's no standard
[20:10] <seb128> yeah :/
[20:10] <robert_ancell> seb128, oh, I was wondering what should replace it, since CK had a history but it seems like logind has nothing
[20:10] <robert_ancell> have you heard of any new "session history" service?
[20:10] <seb128> no I didn't
[20:11] <seb128> you should ask lennart ;-)
[20:11] <robert_ancell> It seems to me that the login history should come from logind and the failed login records should come from PAM
[20:11] <robert_ancell> and utmp/wtmp/btmp should all die a fiery death
[20:12] <seb128> that would work for me, I don't even know why we have so many similar but different files to start with
[20:14] <bregma> seb128, phone seems sane enough, I shall press the button
[20:15] <robert_ancell> seb128, so they can all get out of sync of course!
[20:15] <seb128> bregma, doit!
[20:15] <seb128> robert_ancell, yeah :/
[20:15] <bregma> well, that was disappointing
[20:15] <seb128> robert_ancell, btw, did you see https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1255558/comments/53 ?
[20:15] <ubot2`> Launchpad bug 1255558 in unity-greeter (Ubuntu) "Can't type my password after cold boot" [High,Triaged]
[20:15] <robert_ancell> seb128, yeah, looking at u-g now. Fixing the double authenticate bug at the moment
[20:17] <robert_ancell> bregma, btw, is someone going to fix the hud opening all the time when pressing alt-d in a browser? or alt-b in jed? So annoying...
[20:18] <robert_ancell> It seems to be any alt key combination that is not exposed as a menu
[20:18] <seb128> robert_ancell, when did that start?
[20:18] <robert_ancell> seb128, when the LIM was enabled I think
[20:18] <bregma> sounds like sonething attente would be involved in, alt-key grabbing?
[20:18] <seb128> robert_ancell, hum, I would think it's likely "when we moved key grabbing from g-s-d to unity"
[20:19] <seb128> which attente did this cycle
[20:19] <robert_ancell> ah
[20:20] <seb128> well, some people complained also that super-<something> started opening the dash again( which apparently was fixed in previous cycle)
[20:20] <seb128> those "make the difference between a tap and a combinaison" are not really reliable :/
[20:21] <bregma> it's difficult to discern a user's intent
[20:29] <ochosi> seb128: seems like adding the user to the "audio" group is enough to keep music playback alive when using the greeter as lockscreen (i.e. with VT switch)
[20:31] <seb128> ochosi, nice ;-)
[20:33] <ochosi> seb128: we'll do a new dev-release of light-locker which will help a bit for now, it'll lock the session but only switch to the greeter once you "wake it up", i.e. by touching the mouse or so. so only then would the music stop (without the audio-group)
[20:34] <seb128> ochosi, that sounds like a cool hack, though it might lead to some weird effects (like things not being consistent between "I didn't touch the computer for 10 minutes" and "I moved the mouse and then didn't touch it for 10 minutes again" for example)
[20:35] <seb128> but those are issues we identified with the greeter as lock screen anyway
[20:35] <ochosi> seb128: yup true, which is why it's only optional
[20:35] <seb128> like the "suspend after idle" user settings not being respected
[20:35] <seb128> still unsure what I like more
[20:36] <ochosi> mmm
[20:36] <seb128> it seems we are going for the "lock screen being the greeter" on ubuntu touch, but as a side effect people start pushing code that "write user datas to accountsservice so the greeter can read those"
[20:36] <seb128> like we are soon pushing the current playing though there
[20:36] <seb128> so the greeter can display it
[20:37] <ochosi> right
[20:37] <seb128> or the sound status (so if you mute from the greeter the session is silent as well on login)
[20:42] <ochosi> seb128: so that's not becoming ambigious with multiple running user-sessions?
[20:42] <ochosi> i mean, will you have to update the indicators to actually reflect the accountsservice information from the currently selected user on the greeter?
[20:43] <seb128> ochosi, that's a bit weird, but the datas are by user, same way we current have the wallpaper matching the selected user
[20:44] <ochosi> seb128: so, just a random scenario. two users (A, B) are logged in. A has music playback, locks session, then B logs in -> music playback of A stops (i would assume)
[20:44] <ochosi> then B starts music playback, locks the session
[20:44] <ochosi> whose music is playing? I would presume B's because he was the "last"
[20:44] <ochosi> then user A is selected in the user-list/combobox
[20:45] <ochosi> music-playback of B pauses and A's recommences?
[20:45] <charles> does anyone in-channel have a bluetooth keyboard or mouse whose battery shows up in the power indicator? If so, could you pastebin me the output of "upower --dump" ?
[20:45] <ochosi> (i.e. greeter DJ?)
[20:45] <ochosi> charles: i assume "(not present)" doesnt count?
[20:46] <charles> :)
[20:46] <cyphermox> charles I can get that for you tonight possibly
[20:47] <kenvandine> charles, i do
[20:47] <seb128> ochosi, yeah, those scenarios are a bit undefined...
[20:47] <kenvandine> http://paste.ubuntu.com/7075683/
[20:48] <kenvandine> charles, ^^ that's with a wireless mouse
[20:48] <charles> kenvandine: thank you!
[20:48] <kenvandine> np
[20:48] <ochosi> seb128: which is why i think that stopping music-playback on lock is generally not such a bad idea on a system with >1 users
[20:48] <seb128> right "on system with > 1 users"
[20:49] <seb128> but you end up on "lock screen and greeter are not the same thing, on system with 1 user you would only ever see the lock screen"
[20:49] <TheMuso`> I remind you guys of this, WRT audio: https://wiki.ubuntu.com/Audio/TheAudioGroup?highlight=%28audio%29%7C%28group%29
[20:49] <seb128> which is in session
[20:51] <dobey> oh what beauty are these appropriately sized windows
[20:51] <ochosi> TheMuso`: yeah, adding myself to the audio group enabled contineous audio-playback when locking with light-locker for me
[20:51] <TheMuso`> ochosi: I guess my point was we shouldn't be using the audio group.
[20:52] <TheMuso`> I thought that giving that link would explain things somewhat more concisely than I could.
[20:52] <attente> robert_ancell: i can't seem to replicate that problem
[20:57] <robert_ancell> attente, so if you open chrome/firefox and press alt-d it always focusses the URL entry?
[20:57] <attente> robert_ancell: i get a dialog that says "Open Web Location" in firfox
[20:58] <attente> robert_ancell: in jed, it pops up the buffers menu
[20:59] <robert_ancell> hmm, not for me
[20:59] <robert_ancell> any settings I can reset?
[20:59] <seb128> robert_ancell, attente: the jed case might be the fix from unity-gtk-module that landed today
[20:59] <attente> robert_ancell: chromium-browser focuses the URL entry
[20:59] <robert_ancell> I'll try the update
[21:00] <seb128> the update is not going to resolve firefox issues though
[21:00] <TheMuso`> I know for one that if you disable alt shortcut keys for the menus in gnome-terminal, using alt + E etc to go to menus still works...
[21:00] <attente> i guess if u-g-m fixes it, then it wouldn't open the hud, but open a menu instead?
[21:00] <seb128> oh, that's good point :/
[21:00] <seb128> ignore me then
[21:00] <attente> sounds like it's at the compiz level unfortunately... :(
[21:01] <seb128> robert_ancell, does it happen in a guest session?
[21:01] <TheMuso`> Bug 1289089
[21:01] <ubot2`> Launchpad bug 1289089 in Unity "Menus still accessible via keyboard shortcut even when keyboard shortcuts for menus in gnome-terminal are disabled." [Undecided,New] https://launchpad.net/bugs/1289089
[21:02] <robert_ancell> hmm, guest not working it seems
[21:04] <seb128> the guest session, or alt-d in firefox in guest? (if that's supposed to do something, doesn't in french locale)
[21:05] <robert_ancell> the guest session
[21:05] <robert_ancell> alt-d focusses the url entry
[21:15] <attente> robert_ancell: do you have anything set in /org/gnome/desktop/input-sources/xkb-options?
[21:16] <robert_ancell> attente, looking
[21:16] <robert_ancell> attente, it's set, but to []
[21:17] <robert_ancell> attente, just playing with it now, it only happens if you press alt-d quickly. If I do alt (wait) d it works fine
[21:57] <seb128> Trevinho, bregma: hum, just a note, the theme update is slightly buggy, if you use the light theme the wm decorations show black for like a fraction of second before being being decorated with their normal color
[21:57] <seb128> Trevinho, that doesn't happen without your changes from today :/
[22:17] <seb128> bregma, the unity ppc64el retry worked, seems like you can publish the silo
[22:19] <Trevinho> seb128: that's already fixed in a branch I've
[22:20] <seb128> Trevinho, theme one or unity?
[22:20] <Trevinho> seb128: https://bugs.launchpad.net/unity/+bug/1287464
[22:20] <ubot2`> Launchpad bug 1287464 in Unity "Fake decorations on spread flickers the first time they've been selected" [Medium,In progress]
[22:20] <robert_ancell> attente, confirmed the jed issue is fixed with update. Still seeing it in Chrome though
[22:20] <Trevinho> that's the same isue, fixed in unity some days ago, but I had to wait the lockscreen to land
[22:21] <seb128> Trevinho, that's happening on the normal session every time the windows gets the focus and it wasn't happening before your theme update, are you sure it's the same issue?
[22:21] <seb128> Trevinho, ok
[22:21] <Trevinho> tooltips / QL shadows should be tuned also
[22:21] <Trevinho> seb128: yes
[22:21] <seb128> bregma, land the lockscreen so you can another one with the fixes then ;-)
[22:23] <attente> robert_ancell: a bit strange, i'm not sure why that would've fixed jed
[22:23] <robert_ancell> attente, the unity-gtk3-module as seb128 suggested?
[22:24] <attente> robert_ancell: yeah, but that fix was for preventing the menu bar from activating, not for anything related to hud
[22:25] <seb128_> Trevinho, sorry, I'm not on a stable connection atm ... good to see those fixes lined up, you should merge propose them though, so they can be landing after the lockscreen one ;-)
[22:25] <Trevinho> seb128_: mh I planeed to add something else there... but ok, I see if I can
[22:26] <seb128_> thanks