[00:32] <Noskcaj> bluesabre-laptop, IT WORKS! :)
[00:33] <Noskcaj> Only issue is, the os.path.join fix wasn't complete. e.g. the .desktop says usr/binmenulibre
[01:16] <bluesabre-laptop> Noskcaj: great, so my latest commit should fix that
[01:16] <Noskcaj> Then we should be all good from the packaging side
[01:17] <bluesabre-laptop> fantastic
[01:17] <bluesabre-laptop> I'll do the release tonight and post a note about it here.  Thanks Noskcaj!
[01:18] <Noskcaj> no problem. It's good to know 14.04 is pretty much where we need it to e
[01:18] <Noskcaj> *be
[01:18] <Noskcaj> As long as i can find a DD
[01:26] <bluesabre-laptop> yeah, it does help that you are on the debian python apps team though
[04:09] <bluesabre-laptop> Noskcaj: If you get a chance, can you pull the latest revision and see if building still works?  I think I've ironed out all the wrinkles now
[04:16] <bluesabre-laptop> and I can set you up as an admin so that you can upload packaging to a menulibre ppa tomorrow
[04:16] <bluesabre-laptop> heading to bed, night all!
[04:18] <Unit193> Good night.
[04:18] <Noskcaj> g'night bluesabre-laptop.
[04:18] <Noskcaj> Testing now
[04:51] <Noskcaj> Current issues: .pot is generated at each build, no manpage, README is nearly empty, usr/share/menulibre/media/ is empty
[04:54] <Noskcaj> And there don't appear to be any tests or advanced doc (todo list rather than an immediate issue)
[08:08] <Noskcaj> bluesabre, you around?
[08:42] <Noskcaj> the power manager systemd fix is now in -proposed
[10:13] <knome>  
[10:14] <knome> hmm..
[11:07] <slickymaster> morning all
[12:22] <bluesabre-laptop> is Noskcaj were here, I'd say "manpage added, readme fixed, empty media is cleared, but I'm not sure how to keep the .pot file from updating on each build"
[14:53] <bluesabre-laptop> all thats left now is rearranging the menulibre launchpad page
[14:53] <bluesabre-laptop> and figuring out what to do with all the old releases that were number year.month.revision
[14:56] <slickymaster> hi bluesabre-laptop 
[14:57] <bluesabre-laptop> hey slickymaster
[14:57] <slickymaster> if you want to take a look at what I've done so far with the Mugshot docs: http://smdavis.us/doku/doku.php?id=mugshot-docs
[14:58] <slickymaster> ping me if you notice something that isn't correct and/or needs to be changed
[14:58] <bluesabre-laptop> looks great so far
[14:59] <slickymaster> good :)
[15:07] <bluesabre-laptop> Noskcaj: https://launchpad.net/menulibre/2.0
[15:08] <bluesabre-laptop> knome ^
[15:08] <bluesabre-laptop> I'll work with Noskcaj to get this into Debian/Ubuntu and a PPA for testing
[15:08] <bluesabre-laptop> elfy ^
[15:08] <bluesabre-laptop> :)
[15:10] <bluesabre-laptop> slickymaster: if you're interested, we can start the docs for menulibre here: http://smdavis.us/doku/doku.php?id=menulibre-docs
[15:14] <slickymaster> yeah, I saw it bluesabre-laptop. As soon as I'll finish Mugshot's I'll assign myself to it, if by then no one has started working on it
[15:55] <bluesabre-laptop> slickymaster: thanks, I'll do it first if I can get these updates released :)
[16:19] <elfy> bluesabre-laptop: thanks for letting me know :)
[16:48] <slickymaster> elfy, you around?
[16:55] <DanChapman> lderan, hey :-) how are you? would you be able to put each test into it's own MP it's easier to deal with that way ;-p
[16:56] <lderan> sure DanChapman :)
[16:56] <elfy> slickymaster: kind of 
[16:56] <slickymaster> hey DanChapman 
[16:56] <slickymaster> it's quick
[16:56] <knome> autopilot testing, eh? how's that coming along?
[16:56] <DanChapman> lderan, cheers mate
[16:57] <DanChapman> hey slickymaster
[16:57] <slickymaster> regarding 1256898
[16:57] <slickymaster> regarding bug 1256898
[16:57] <slickymaster> I'm assuming we're talking about xfce4-session 4.10.1-3ubuntu2
[16:57] <slickymaster> right?
[16:58] <lderan> knome, getting started with the basic tests, some apps like Mines and gimp are not playing nicely sp trying to see what can be done with them
[16:58] <lderan> s/sp/:P/
[16:58] <knome> lderan, aha, can we use autopilot testing with the xfce componenets at some point?
[16:58] <knome> -e
[16:59] <lderan> we can do very minimal testing at the moment with the xfce stuff, pretty much to see if they open.
[16:59] <knome> what does "at the moment" imply? their codebase needs to be changed before we can, or some other tools need to be written?
[17:00] <DanChapman> knome, anything Gtk2 based is not possible to do anything more than simply check window loads/visible and window title
[17:00] <knome> DanChapman, now that's stupid :P
[17:00] <lderan> can't even see if the window title changes :(
[17:02] <knome> bbl
[17:02] <knome> (thanks for the quick update!)
[17:03] <elfy> slickymaster: was that ^^ for me - if so it'll be whatever we are using, though I can't now even remember why we decided we needed it
[17:06] <slickymaster> elfy: yeah, that was for you
[17:06] <slickymaster> that's why I was pinging you
[17:06] <elfy> yea - saw the ping and then nothing else :) 
[17:07] <slickymaster> it seems to me that the existing test already covers what you wrote in the bug description
[17:07] <slickymaster> elfy: ^^^
[17:09] <elfy> I *think* I was thinking about suspend missing and the new lock business 
[17:10] <slickymaster> hmm, I think it would be best just to add those to the existing testcase, don't you?
[17:10] <elfy> not lock - ochosi wants light-locker testing 
[17:10] <ochosi> hey elfy 
[17:10] <elfy> needs a conversation
[17:10] <elfy> hi ochosi :)
[17:11] <ochosi> just returned
[17:11] <ochosi> what's up?
[17:11] <slickymaster> ochosi: my conversation with elfy ^^^
[17:11] <ochosi> suspend + lock in what where?
[17:11] <elfy> ochosi: it's all tied up with the discussion we need to have with knome 
[17:11] <brainwash> ochosi: yay, now I can bother you with theme glitches again :D
[17:11] <ochosi> aha
[17:12] <slickymaster> elfy, ochosi, I think I'll postpone bug 1256898 until you both discuss it with knome 
[17:13] <elfy> slickymaster: yep that's fine
[17:13] <slickymaster> in the meanwhile I'll continue to work on http://smdavis.us/doku/doku.php?id=menulibre-docs
[17:13] <elfy> yep 
[17:13] <ochosi> brainwash: haven't heard back from you about the powermenu patch in the greeter. however, i discussed this also briefly with bluesabre-laptop and knome and i think we'll just style the shutdown/reboot dialogs and add a notice that users are logged in
[17:13] <slickymaster> bah, wrong link
[17:14] <slickymaster> the correct one is http://smdavis.us/doku/doku.php?id=mugshot-docs
[17:15] <brainwash> ochosi: this patch is incomplete anyway, we need to check the permissions when the menu is actually opened
[17:15] <ochosi> brainwash: no, we don't. those permissions are only checked system-wide by lightdm afaik so they'll always be the same
[17:17] <ochosi> elfy: you still haven't told me what that "discussions with knome" will be really about :)
[17:17] <elfy> ochosi: the lightlocker testing - and whether to have suspend in the same test
[17:18] <brainwash> ochosi: remember the missing restart menu entry? the user session was still active for ~30sec after the user has already logged out
[17:18] <brainwash> this is still true for hibernate
[17:19] <ochosi> elfy: right, well there's only one aspect connecting light-locker with suspend, and that's to check whether the session is locked when you wake up the computer
[17:19] <ochosi> brainwash: ok, but how is that related?
[17:19] <brainwash> ochosi: it makes sense to check the permission to restart/shutdown/.. on the fly
[17:20] <ochosi> not really, it'll still mean if you open the menu in the first 30secs those entries will be missing
[17:20] <brainwash> yes, it's not perfect
[17:21] <ochosi> no, it's an ugly ugly workaround
[17:21] <ochosi> if it's only about hibernate, then it should get fixed the same way as reboot/shutdown got fixed imo
[17:22] <elfy> ochosi: so it makes sense to have suspend in the same testcase to you?
[17:22] <ochosi> elfy: what other testcases could/would it go in?
[17:24] <elfy> exactly - it used to be in the old post install test - at the moment it's missing
[17:24] <elfy> we don't actually have tests for any restart/power off afaik 
[17:24] <elfy> suspend was the only one we tested iirc
[17:26] <brainwash> ochosi: ok, different approach.. a local user logs out while a remote user is still active for 2min, after some more time the local user decides to shut down the pc
[17:27] <ochosi> elfy: well the problem is that there are a gazillion reasons for suspend to fail
[17:27] <ochosi> elfy: most of them light-locker unrelated...
[17:27] <elfy> mmmm 
[17:27] <brainwash> ochosi: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732623#188
[17:27] <ochosi> brainwash: have you tested to shutdown from within the session while another user is still logged in?
[17:30] <brainwash> ochosi: it preforms a shutdown?
[17:31] <ochosi> brainwash: i don't know, it was a question
[17:31] <brainwash> currently everything is possible, so shutdown
[17:32] <ochosi> so why should the greeter prevent any of that then, e.g. by hiding the powermenu?
[17:33] <brainwash> greeter != user session
[17:33] <ochosi> no idea how that's an argument
[17:33] <ochosi> anyhow, what's up with that debian bugreport
[17:34] <brainwash> dunno, I think they want the dynamic check
[17:34] <brainwash> patch also available
[17:34] <brainwash> 07-run_time_power_menu.patch
[17:34] <ochosi> yeah, but i thought we had just established that that's not really a fix
[17:35] <brainwash> yes, not for this particular case
[17:36] <brainwash> but what about my scenario with local + remote user?
[17:36] <brainwash> basically multi user environments 
[17:36] <ochosi> there are no remote sessions in xubuntu
[17:36] <ochosi> s/xubuntu/gtk-greeter/
[17:36] <ochosi> only unitygreeter handles that
[17:38] <ochosi> and i'm not sure i understand what you were getting at with your scenario
[17:38] <brainwash> ok, without proper case this seems to lead nowhere
[17:39] <brainwash> please mark bug 1264838 as invalid or so
[17:39] <ochosi> ok, my point is: with physical access you can always shut down a computer, no matter whether a user is logged in or whatever
[17:39] <ochosi> i can't, that's in debian
[17:39] <ochosi> but feel free to comment on it
[17:39] <brainwash> reported upstream
[17:39] <brainwash> LP report
[17:42] <knome> elfy, ochosi: you two are good to have the discussion, that's why ochosi/knome ;)
[17:42] <elfy> ok - then we've had it then
[17:42] <knome> okay
[17:42] <knome> :)
[17:42] <elfy> knome: so we're left with no suspend test :)
[17:43] <knome> okay
[17:43] <elfy> unless we do a whole power testcase I guess - or just add it back to the post install test
[17:43] <knome> a whole power testcase sounds better to me than add it bak
[17:43] <knome> +c
[17:43] <knome> my c-key is still borked
[17:43] <elfy> ok 
[17:44] <elfy> I completely lost Q once
[17:44] <elfy> then I couldn't change a password because it had q in it 
[17:44] <knome> my problem seems to be quick, light taps
[17:45] <elfy> mine ranged from those to thumping it with a mug ... 
[17:46] <elfy> slickymaster: ^^
[17:47] <brainwash> can the image highlight/dim effect be disabled for the xfce4-panel class only? https://github.com/shimmerproject/Greybird/blob/master/gtk-3.0/gtk-widgets.css#L82
[17:50] <knome> elfy, heh
[17:50] <knome> bbl again ->
[17:50] <slickymaster> elfy: hmm, so if I understand you guys correctly, the intention now is to make a Power test from scratch, right?
[17:51] <ochosi> bbiab
[17:51] <ochosi> brainwash: yeah, can be done i guess
[17:52] <slickymaster> elfy: if so, shouldn't bug 1256898 be closed as it has nothing to do with what is now intended?
[17:54] <elfy> slickymaster: yea - was on my list - done now
[17:54] <elfy> hi PaulW2U 
[17:55] <PaulW2U> hi elfy
[17:55] <slickymaster>  elfy ?! what is now done, closing the bug or the power testcase?
[17:55] <elfy> slickymaster: bug
[17:56] <slickymaster> elfy: ok. Are you going to open one for the power test?
[17:57] <elfy> I am 
[17:57] <slickymaster> ok
[18:01] <elfy> bug 1270911
[18:03] <elfy> slickymaster: not sure if you know - but I made you an admin on trello
[18:04] <slickymaster> yeah, you already told me
[18:04] <elfy> sigh ... 
[18:04] <elfy> I need sleep
[18:04] <slickymaster> I didn't remove that bug from Trello, because I assume you would do it
[18:04] <elfy> :)
[18:05] <ochosi> elfy: so if there's a separate power-test, put suspend there
[18:05] <ochosi> but if not, you can always pin it on light-locker
[18:05] <slickymaster> :) that makes two of us. Didn't sleep at all last night, due to a horrible, still afflicting, tooth ache 
[18:05] <elfy> :| I feel that pain
[18:06] <elfy> ochosi: yep - just did a bug for a new testcase to include suspend
[18:06] <elfy> which is really what we need anyway - was just looking for a shortcut :)
[18:11] <brainwash> ochosi: adding "-gtk-image-effect: none;" to .xfce4-panel .menu {} works fine here
[18:17] <ochosi> elfy: ok, so i presume that's resolved? :)
[18:17] <ochosi> brainwash: yup, wanna check how this affects other apps to see whether to disable it globally
[18:18] <brainwash> ochosi: the ubuntu themes don't use these effects at all, how can it be even checked?
[18:18] <elfy> ochosi: yep - always good for it to be a simple thing to deal with
[18:19] <ochosi> brainwash: you can use other gtk3 apps (like gedit or whatever uses a menu) and see whether it's there too
[18:19] <ochosi> and annoyingly so
[18:19] <brainwash> ochosi: do gtk2 apps use this effect?
[18:19] <ochosi> they can't
[18:19] <brainwash> oh
[18:19] <ochosi> unless someone writes an engine that does that effect
[18:23] <brainwash> the toolbar icons in gedit get highlighted slightly
[18:23] <brainwash> but not the icons in the menus
[18:24] <ochosi> weird
[18:24] <ochosi> cause they should be in a way
[18:24] <brainwash> or the change is so minimal
[18:24] <ochosi> or otherwise the menu in the indicators is some inheritance problem
[18:24] <brainwash> not noticeable at all
[18:25] <ochosi> so maybe an inheritance from buttons
[18:25] <brainwash> ochosi: the indicators menu work properly the first time you open it, but on the second time the highlight glitch occurs
[18:26] <ochosi> never happens on saucy, is all i can tell
[18:26] <brainwash> when you move the cursor between menu and indicator button in the panel
[18:26] <brainwash> you saw my screencast
[18:26] <ochosi> yeah, i saw your screencase
[18:26] <brainwash> cast
[18:26] <ochosi> i can't reproduce it though
[18:26] <brainwash> trusty only maybe
[18:26] <slickymaster> bluesabre-laptop: regarding http://smdavis.us/doku/doku.php?id=mugshot-docs:installation-preferences#preferences I don't see much material to work on doc wise speaking.
[18:26] <brainwash> gtk 3.10
[18:28] <brainwash> do we have anyone here who runs trusty + gtk3 indicator stack?
[18:28] <slickymaster> bluesabre-laptop: What I mean is you just install it and there's no specifics configurations you have to make, other than start using it. What do you think? I could probably be seeing it wrongly
[18:28] <slickymaster> Anyway gotta go now. bbl after dinner
[18:35] <ochosi> brainwash: i will by the end of the week, so no rush with this
[18:39] <sergio-br2> hello
[18:43] <ochosi> hey
[19:03] <Noskcaj> The systemd power manager fix and the light locker xflock4 fix should both in in -proposed now
[19:07] <ochosi> Noskcaj: awesome work!
[19:08] <Noskcaj> and bug 1246364 is semi-invalid now
[19:08] <brainwash> power-manager is already in trusty, not trusty-proposed
[19:08] <Noskcaj> yay
[19:09] <brainwash> so, now SRU for saucy :)
[19:11] <brainwash> ochosi: looks like we got an ugly issue in xfce, the session won't kill gpg-agent on logout and thus prevent logind from closing the session
[19:35] <brainwash> ochosi: here another scenario: user closes the graphical session and returns to the greeter, then he closes the console session (tty1), so no more user sessions are running, but the greeter will still hide the hibernate menu entry
[19:36] <brainwash> no hibernate for us ubuntu users, but other distros allow the user to hibernate without manually editing configs
[19:37] <brainwash> just in case you won't accept my "hibernate" scenario :)
[19:38] <brainwash> on top of that, the system maintainer is free to change the policykit rules for logind, so every power action could be affected
[19:44] <brainwash> Noskcaj: just wondering, light-locker is the 3rd option in xflock4, so xflock4 will first try to run xscreensaver or gnome-screensaver
[19:45] <brainwash> is that intended?
[19:47] <bluesabre-laptop> slickymaster: yeah, there are no preferences in mugshot, it just works
[19:59] <elfy> bluesabre-laptop: I always find that using tabcomplete makes me sure people are in the channel :p
[20:00] <bluesabre-laptop> elfy: I just hope they review the #xubuntu-devel public logs when they're not around :)
[20:00] <elfy> ha ha ha 
[20:11] <Noskcaj> brainwash, sort of, it's a temporary patch, although the order can be changed if it affects anything in a bad way
[20:12] <elfy> Noskcaj: thanks by the way
[20:12] <Noskcaj> no problem.
[20:12] <Noskcaj> gthumb 3.3.1 and settings 4.11.1 should both be up soon too. 
[20:14] <bluesabre-laptop> Noskcaj: good to hear
[20:15] <Noskcaj> bluesabre-laptop, When you next have some time, could you try and merge lightdm-gtk-greeter from debian? It's a bit of a waste for us to be maintaining it separately
[20:15] <bluesabre-laptop> Noskcaj: sure thing
[20:16] <Noskcaj> Thanks. I'd do it, but i don't understand the package well enough.
[20:16] <bluesabre-laptop> I'll take care of it
[20:16] <bluesabre-laptop> and if you have some time, I just made you a member of ~menulibre-dev
[20:17] <bluesabre-laptop> could you upload a trusty package for 2.0 to https://launchpad.net/~menulibre-dev/+archive/devel
[20:17] <Noskcaj> thanks. Should i wait for an official release or just go from the bzr branch?
[20:17] <Noskcaj> And did you see my list of issues yesterday?
[20:17] <bluesabre-laptop> I did a release a bit earlier today, I resolved all of the issues except the .pot updating on new builds
[20:18] <bluesabre-laptop> https://launchpad.net/menulibre/2.0
[20:18] <Noskcaj> ok. I have to go now, but is there an option  to disable the .pot thing i can use for debian?
[20:19] <bluesabre-laptop> you're welcome to add a small quilt patch to remove the .pot file, or if you would recommend, I can remove it from the source package
[20:21] <brainwash> Noskcaj: /close
[20:21] <brainwash> woops, wrong channel
[20:21] <brainwash> :)
[22:00] <sergio-br2> hey ochosi, this elementary icons are like tango icons, or not fully?
[22:01] <Noskcaj> bluesabre-laptop, Do you have any idea what dependancy i'm missing that causes http://paste.ubuntu.com/6788413/ ?
[22:06] <Noskcaj> Debian finally has a new version of blueman, merging now
[22:15] <ochosi> sergio-br2: yeah, they're a bit like a tango-refresh
[22:15] <ochosi> but not following all the tango guidelines, e.g. the colorscheme isn't the same
[22:16] <sergio-br2> ahhh ok
[22:17] <sergio-br2> but the guideline for highlights in the edges is one thing true to elemetary?
[22:17] <ochosi> brainwash: pushed your patch for the indicator-menus
[22:17] <sergio-br2> but the guideline for highlights in the edges is one thing true to elemetary?
[22:17] <sergio-br2> but the guideline for highlights in the edges is one thing true to elemetary?
[22:18] <ochosi> sergio-br2: are you referring to a specific document with icon-guidelines or just an observation of the existing icons?
[22:18] <sergio-br2> it's missing in package-x-generic
[22:18] <sergio-br2> well, bot
[22:18] <sergio-br2> both
[22:19] <sergio-br2> is there a specific guideline for elementary?
[22:19] <ochosi> i don't think that there are any written guidelines
[22:19] <ochosi> the icons were originally just created by one person only
[22:19] <ochosi> so no guidelines were necessary
[22:19] <ochosi> and i think still most icons are done by DanRabbit
[22:20] <ochosi> i submitted lots of icons in new sizes, but not that many new icons per se
[22:20] <brainwash> ochosi: thanks
[22:20] <ochosi> with respect to package-x-generic, that's true, but i'm not sure it'd really look nice there
[22:20] <ochosi> brainwash: any other theme-glitches?
[22:21] <brainwash> ah, speaking of icons.. I think we still need a high res icon for parole's about dialog
[22:21] <ochosi> hmright
[22:21] <ochosi> 128px?
[22:21] <sergio-br2> ok
[22:21] <brainwash> not sure, it's quite big
[22:22] <ochosi> brainwash: can you send me another screenshto?
[22:22] <ochosi> just to be sure...
[22:26] <brainwash> ok
[22:32] <brainwash> ochosi: http://en.zimagez.com/zimage/parole0.php
[22:34] <brainwash> and here's a pic of the animated pending icon in the software center, notice the solid grey area, it disappears only when you hover over the button
[22:34] <brainwash> http://en.zimagez.com/zimage/uscprogressbutton.php
[22:35] <brainwash> same issue with unity's theme, but almost not noticeable because of the coloring
[22:36] <brainwash> I'll try to fix that one, so don't bother :P
[22:42] <ochosi> ok nice
[22:42] <brainwash> ochosi: any thoughts on my hibernate menu entry scenario? ironically I've just encountered this situation
[22:42] <ochosi> i think the problem is that that's qt and not sure how that's handled
[22:42] <brainwash> no, gtk3
[22:42] <ochosi> one thing at a time, still drawing the 128px icon
[22:42] <brainwash> :)
[22:42] <ochosi> are you sure it's not qt->gtk3?
[22:43] <brainwash> ubuntu's software center?
[22:43] <ochosi> yeah
[22:43] <brainwash> it's python + gtk3
[22:44] <ochosi> then they should stop using those fugly custom widgets
[22:45] <brainwash> it's strange indeed, the animation is defined via a python function and some cairo magic is involved too I think
[22:45] <brainwash> gtkparasite points to the animation function
[22:46] <ochosi> i guess a regular gtkspinner didn't do it for them :/
[22:46] <ochosi> the whole toolbar looks terrible imo
[22:47] <brainwash> it's not that bad
[22:47] <ochosi> i guess those icons are also hardcoded
[22:47] <ochosi> it could be fixed by using more of the standard widgetry
[22:47] <brainwash> yeah, the icons are provided by the usc package
[22:48] <ochosi> but in a usc dir or in pixmaps or hicolor?
[22:49] <brainwash> /usr/share/software-center/ui/gtk3/art/icons/pending.png
[22:49] <ochosi> hmpf
[22:49] <ochosi> yeah, so hardcoded it is
[22:49] <ochosi> parole-appicon-patch pushed
[22:49] <brainwash> wow, awesome
[22:49] <ochosi> in case you can already test
[22:50] <ochosi> i need to re-read your hibernate scenario again, there were too many other things happening in between
[22:51] <ochosi> right, so what do you suggest? loading the menu "on the fly" is possible, but it won't really solve the problem
[22:51] <brainwash> got another tiny theme annoyance, greeter this time.. if you move the cursor to the top right and click, it won't activate the power menu
[22:52] <ochosi> we can just as well put an hourglass cursor there and a tooltip saying "wait for your power-actions to appear while your session finally is closign down"
[22:52] <brainwash> yeah, maybe
[22:53] <ochosi> hm, true, not sure where that 1px comes from
[22:53] <brainwash> some recent change most likely :)
[22:54] <ochosi> are you sure? i mean: did that ever work?
[22:57] <brainwash> strange, got the 1px too in saucy
[22:57] <brainwash> ah wait, using greybird git
[22:59] <brainwash> my mind is now blown.. so it was always like this? 1 px border? :D
[22:59] <ochosi> :)
[22:59] <ochosi> it's quite possible, i never tried that tbh
[23:00] <ochosi> i don't see anything in the theme-code that would cause this
[23:01] <brainwash> never mind then
[23:01] <ochosi> must be something in the themecode though
[23:01] <ochosi> doesn't happen with all themes, it seems
[23:02] <brainwash> and regarding the power menu, would building it on-the-fly come with any drawbacks?
[23:03] <ochosi> ok, locally fixed the top-corner-click problem
[23:03] <ochosi> well more (useless) system calls, the menu popping up with a delay
[23:04] <ochosi> i don't know what repercussions it would have, but as i said, it doesn't fix the issue as that isn't in the greeter
[23:04] <ochosi> i guess it should be discussed in the bugreport anyways
[23:05] <brainwash> lets focus on the greeter only
[23:05] <brainwash> mmh, right
[23:06] <ochosi> so basically the hibernate-issue that you have is also something that's only related to logind settings
[23:06] <ochosi> or am i wrong?
[23:07] <brainwash> very likely, not sure how it was handled before
[23:23] <brainwash> ochosi: it's actually a two way issue, you boot the pc, switch to tty1 and login.. now you return back to greeter and the hibernate menu entry will be still visible
[23:23] <brainwash> should be hidden now
[23:24] <brainwash> but what should be done, if the power menu is keep opened while switching between tty1 and vt7? :D
[23:24] <brainwash> kept opened
[23:26] <brainwash> in this case policykit simply won't let you hibernate the system
[23:26] <ochosi> i'm still reading this immensly long debian bugreport-discussion...
[23:27] <brainwash> they mainly focus on the gpg-agent issue which keeps the logind session alive
[23:28] <brainwash> pulseaudio does the same occasionally
[23:29] <brainwash> but this does not really justify the proposed change
[23:34] <brainwash> I don't mind delaying a final decision, maybe I'm just too exited about the release of trusty :)
[23:35] <ochosi> hehe
[23:35] <ochosi> do you have the link to the upstream logind policy change handy?
[23:35] <ochosi> (or at least the downstream merge-request @launchpad)
[23:35] <brainwash> the restart multi session one?
[23:36] <ochosi> yup
[23:36] <brainwash> google is not very helpful
[23:40] <brainwash> http://cgit.freedesktop.org/systemd/systemd/commit/src/login/org.freedesktop.login1.policy.in?id=299404a19f26aa4f203042d8285ee0b7afa5bf40
[23:41] <brainwash> the user is able to shutdown, reboot and suspend the system... but hibernate, no, that's evil :)
[23:43] <ochosi> well why don't you report another bug against systemd's default policies then?
[23:46] <brainwash> https://bugs.freedesktop.org/show_bug.cgi?id=70237
[23:46] <brainwash> won't fix :(
[23:48] <Unit193> I love it, clearly these people have heard of VNC, RDP, and the like. :)
[23:50] <ochosi> i really wonder why reboot is ok then
[23:50] <Unit193> Because it doesn't bring up the last session?
[23:50] <brainwash> or shutdown + suspend
[23:51] <brainwash> initially: shutdown + suspend -> OK,  restart + hibernate -> NO
[23:52] <brainwash> restart is OK now due to the change "forced" by us
[23:52] <ochosi> Unit193: right, but from the greeter it doesn't, it just brings you back to the greeter
[23:53] <ochosi> (or that's what it should do, anyhow i dont ever use hibernate so i wouldn't know)
[23:54] <brainwash> but this isn't the point actually, the system admin can change this rules and disallow every power action when multiple sessions are active
[23:54] <brainwash> they are just rules after all
[23:55] <brainwash> but lets wait for more input
[23:55] <brainwash> maybe ask robert
[23:59] <ochosi> hm, not sure he has much to say on this
[23:59] <ochosi> they use gnome-settings-daemon for all this