[00:17] <brainwash> ochosi: your system is just.. awesome :D
[00:19] <brainwash> your screen gets locked automatically via dbus, right? or via xfce4-session and xflock4 (light-locker-command)?
[00:25] <ochosi> acutally it gets locked via X11's builtin screensaver
[00:25] <ochosi> brainwash: ^
[00:25] <ochosi> light-locker does automatic time-based locking based on whatever is set in "xset s"
[00:25] <brainwash> on suspend?
[00:27] <brainwash> and does the version trusty already support the time-based locking?
[00:29] <ochosi> not sure what version there is
[00:29] <ochosi> 1.1.0 supports it
[00:29] <ochosi> on suspend it autolocks, yes
[00:29] <ochosi> light-locker listens to the suspend command and locks the screen
[00:29] <ochosi> there's not even a switch currently to turn that off
[00:30] <brainwash> yeah, I know that :)
[00:30] <brainwash> 1.0.0 in trusty
[00:32] <knome> bbl, back sometime...
[00:33] <brainwash> ochosi: ok, so both systems here run 1.0.0
[00:34] <ochosi> i can see that we do a new stable release soon
[00:34] <ochosi> there aren't really any more features we want for now i think
[00:35] <brainwash> uhm, what about the ability to show screensavers? xD
[00:36] <brainwash> so no plans for a GUI settings window or something like that?
[00:36] <ochosi> that certainly is out of the scope of light-locker
[00:36] <ochosi> well a gui for settings, i hope yes
[00:36] <ochosi> but ideally it'll get integrated in other settings dialogs
[00:36] <ochosi> no need for specific light-locker settings tbh
[00:37] <ochosi> ppl need to be able to set the X11 screensaver for blanking
[00:37] <ochosi> and maybe enable/disable the time-based locking
[00:37] <ochosi> and that's about it
[00:37] <brainwash> mmh, you still need a GUI which is DE independent
[00:38] <brainwash> or at least a conf file
[00:38] <ochosi> the conf is done by the distributors atm
[00:38] <ochosi> by setting the startup command
[00:39] <ochosi> thing is that UI would literally contain a checkbox or two and a gtkspinbutton for setting the timeout
[00:39] <brainwash> it somehow feels a bit incomplete for a LTS release, or?
[00:40] <brainwash> incomplete/basic
[00:40] <ochosi> i'm not sure what's missing
[00:40] <ochosi> i always wanted it to be basic
[00:40] <ochosi> it's not called "fancy-locker" for a reason
[00:40] <brainwash> the average user wants to be able to control it
[00:41] <ochosi> yeah, but ideally they will be able to
[00:41] <ochosi> via setting timeouts in powermanager-settings
[00:41] <ochosi> that needs fixes for logind anyway, adding a way of enabling the X11 screensaver and setting its timeout shouldn't be too hard
[00:41] <brainwash> doe we have a test case for light-locker?
[00:42] <ochosi> not sure
[00:42] <brainwash> it might cause some unexpected failures
[00:47] <brainwash> ochosi: is a request needed to upgrade to 1.1.0?
[00:48] <brainwash> this is the initial packaging request bug 1237134
[00:49] <ochosi> i think we need to release a new stable version in order to get ubuntu folks to update it
[00:49] <ochosi> since it's an LTS release, i would expect them to want something that's also labelled stable
[00:49] <ochosi> even if there won't be additional fixes
[00:50] <brainwash> I see
[00:50] <brainwash> "Preparing to release 1.1.0"
[00:50] <ochosi> anyway, if you wanna write a tiny app that sets the screensaver values, that'd be welcome
[00:50] <ochosi> i personally don't have any time to take care of that, too many other things (and christmas) coming up
[00:51] <brainwash> with my amount of knowledge and experience it would take weeks
[00:52] <brainwash> finding the right way to do it
[00:52] <brainwash> or a "good" way
[00:53] <ochosi> i think ubuntu handle it all via their session
[00:53] <ochosi> so no additional settings dialog is needed there
[00:54] <rowboatn1ck> wouldnt you just need to change .xscreensaver?
[00:55] <brainwash> ochosi: right, because it's familiar with gnome-screensaver
[00:56] <ochosi> rowboatn1ck: no, that's for xscreensaver
[00:56] <rowboatn1ck> there's a new one?
[00:56] <ochosi> i was talking about X11's screensaver extension (aka libxss)
[00:56] <ochosi> we're planning to replace xscreensaver with light-locker
[00:57] <ochosi> which blanks the screen with X11 and un/locks it via lightdm's greeter
[00:57] <rowboatn1ck> ah
[00:59] <brainwash> ochosi: make xfce4-session aware of light-locker (and not care that much about other DEs)?
[00:59] <ochosi> brainwash: there's a misunderstanding here: there's no need for awareness of light-locker specifically, only of X11's screensaver extension
[00:59] <ochosi> light-locker only listens to libxss
[01:00] <ochosi> and reacts to blanking by locking shortly thereafter
[01:00] <ochosi> so basically anything that manages X11's settings works with light-locker
[01:00] <brainwash> and to dbus messages
[01:00] <ochosi> that's we're a bit reluctant to create a UI for it i guess
[01:00] <ochosi> +why
[01:00] <ochosi> yeah, to those as well
[01:01] <ochosi> xflock will be patched, so manual locking will work fine
[01:01] <brainwash> but I mean, xfce4-session locks the screen on suspend/hibernate via xflock4 if the users activates it
[01:01] <brainwash> deactivating it won't work as of now
[01:02] <ochosi> yeah, not with light-locker 1.0
[01:02] <brainwash> but with 1.1.0?
[01:03] <brainwash> with the current available snapshot I mean
[01:03] <ochosi> with the daily PPA, it'll auto-lock on suspend
[01:03] <ochosi> not sure it'll do anything on hibernate
[01:04] <ochosi> it could also be that you have your issue because the session does something wrong when locking via xflock
[01:04] <ochosi> i'm really not sure, i've never used it like that tbh
[01:04] <brainwash> we should threat suspend and hibernate equally =S
[01:04] <ochosi> yeah, but hibernate isn't enabled in ubuntu by default
[01:04] <brainwash> no, xflock4 does not even get called
[01:04] <ochosi> hence the same is true for xubuntu
[01:04] <ochosi> so it's already not treated the same way
[01:04] <brainwash> it's via session/dbus
[01:04] <ochosi> ah ok
[01:05] <ochosi> maybe there's the problem, i don't know the session-code
[01:05] <brainwash> xflock4 isn't even patched yet
[01:06] <ochosi> wasn't there a merge-request?
[01:07] <brainwash> ochosi: one last question, your system switches to vt8 after you resume the system, right?
[01:07] <ochosi> i specifically remember someone from ubuntu-devel asking me about the MR and i "approved" it
[01:07] <ochosi> yeah
[01:07] <brainwash> not before the system enters the suspend sate
[01:07] <brainwash> state
[01:07] <brainwash> ok
[01:07] <ochosi> before i suspend, i see the light-locker-screen show for a sec or so, then nothing
[01:08] <ochosi> when it wakes up, the screen is blank (because that's what the greeter now does by default when it's in locker-state)
[01:08] <ochosi> then i move my mouse or hit a key, enter my password and i'm logged in again
[01:08] <brainwash> https://code.launchpad.net/~noskcaj/ubuntu/trusty/xfce4-session/light-locker
[01:09] <brainwash> yes
[01:11] <ochosi> i don't know enough about debian packaging, but to me it's weird that there's the patch and it's also already applied
[01:11] <ochosi> but maybe that's how it's supposed to be
[01:11] <ochosi> other than that it looks ok
[01:12] <ochosi> so i hope Noskcaj follows up on it
[01:13] <brainwash> I guess he knows how this stuff works
[01:14] <brainwash> so it's the quilt patch + the actual patched code
[01:15] <ochosi> yup
[01:15] <brainwash> mmh, any news regarding bug 1222021 ?
[01:18] <brainwash> I'll try to get the importance level raised to high, because the user might lose data if the system performs a shutdown on button press (no dialog) or when the system tries to suspend on a system which does not support it properly
[01:19] <brainwash> on top of that, it affects many users
[01:19] <ochosi> yeah, but it won't help i guess
[01:19] <ochosi> unless someone writes a patch
[01:19] <ochosi> (i mean the importance level alone)
[01:20] <ochosi> that would be one alternative, have a simple systemd settings app that also controls the screensaver
[01:20] <brainwash> true, not even "critical" would change anything =S
[01:20] <ochosi> then we dont need the powermanager anymore
[01:21] <ochosi> rowboatn1ck: wanna write some UI code again? ;) ^
[01:21] <brainwash> power manager also controls screen brightness and other settings
[01:22] <brainwash> and different profiles for battery and AC mode
[12:22] <elfy> ochosi: finally got around to adding lightlocker/ removing xscreensaver - seems the shortcut to it is ctrl+alt+L - not working for me here
[12:35] <brainwash> elfy: did you also patch xflock4?
[12:35] <elfy> no - why should I have
[12:36] <elfy> https://lists.ubuntu.com/archives/xubuntu-devel/2013-December/009478.html
[12:36] <brainwash> because the shortcut calls xflock4
[12:37] <elfy> doesn't say anything about fiddling about, if it's nto prod ready that's fine - just assumed it was
[12:37] <brainwash> https://code.launchpad.net/~noskcaj/ubuntu/trusty/xfce4-session/light-locker
[12:38] <brainwash> so a branch does already exist, merging and packaging takes some time =S
[12:38] <elfy> thanks - brainwash - I'll wait for that to land then
[12:39] <elfy> yep - indeed :)
[12:39] <elfy> just trying to make sure this machine has everything installable we hope to land in April actually installed
[12:41] <brainwash> right, the new stuff should be included asap I think
[12:41] <elfy> yep
[12:41] <brainwash> and we got plenty of changes and new features
[12:44] <elfy> I think the only 'new' stuff not installed here is menulibre and mugshot
[12:44] <brainwash> gtk3 indicator support
[12:45] <brainwash> the mentioned light-locker integration
[12:45] <brainwash> and the patches for the smooth background transition
[12:45] <elfy> yea
[12:45] <brainwash> whisker menu
[12:45] <elfy> though I've got both installed atm
[12:45] <elfy> and that
[12:46] <brainwash> and the panel layout loader/saver tool
[12:46] <brainwash> :D
[12:46] <elfy> no idea about that
[12:47] <elfy> if people doing these things don't actaully say on the mailing list then they get missed
[12:48] <elfy> bbl
[12:48] <brainwash> bye
[12:48] <elfy> have a good day brainwash :)
[13:16] <elfy> bluesabre: is there a trusty source for mugshot yet?
[13:16] <elfy> the daily ppa appears to not have one
[15:25] <elfy> ochosi: side effect here with removing xscreensaver and installing lightlocker - now affected by Bug 1193716
[15:44] <knome> oh yay!
[15:44] <knome> i has internets!
[15:48] <GridCube> yay!
[15:48] <GridCube> :D
[15:52] <bluesabre> elfy: good point, I've added a trusty build, should finish shortly
[15:56] <bluesabre> elfy, please see my comment on that bug
[16:49] <elfy> bluesabre: k - cheers and I saw the comment :)
[16:49] <elfy> knome: always useful :)
[16:53] <brainwash> doesn't the power manager allow to configure the timer for screen blanking?
[16:54] <brainwash> elfy: can you please suspend/hibernate your system and after resume check if the login greeter displays the "Log In" or "Unlock" button?
[16:56] <elfy> I tried suspend a short while ago - when I was looking at the lock screen thing - coming out of suspend - just goes straight to where I suspended from
[16:56] <elfy> no login nor unlock
[16:57] <brainwash> show while ago? after installing light-locker / making it the default?
[16:58] <brainwash> short
[16:58] <elfy> yea - after lightlocker install
[16:58] <elfy> I'm not really here atm
[16:59] <brainwash> so it should automatically lock your session every time you suspend/hibernate the system
[16:59] <brainwash> via session menu
[17:03] <elfy> of course
[17:08] <brainwash> ochosi: still don't understand this, lightdm reports that the greeter is not being used as lock screen (lock_hint not set)
[17:09] <brainwash> ochosi: but it works if I manually lock the session before triggering suspend/hibernate
[17:22] <knome> elfy, yep...
[17:32] <bluesabre> elfy, did you restart, or run light-locker?
[17:32] <bluesabre> the process has to be running to listen to suspend/hibernate/light-locker -l
[17:33] <bluesabre> its added to autostart, but not started automatically until you've logged out or run "light-locker"
[17:39] <elfy> no - no restart done - I'll check tomorrow then - but then I also applied setterm -blank 0 -powerdown 0 now
[17:49] <ochosi> elfy: yeah, you have to set that timeout via "xset s $seconds" in the terminal atm
[17:50] <ochosi> we'll have to fix that somehow, not sure yet how/where
[17:50] <bluesabre> ochosi: create a lightweight alternative to the xscreensaver settings
[17:51] <ochosi> bluesabre: yeah, or just fix powermanager to be able to set those values
[17:51] <bluesabre> but then what about the lubuntu folks?
[17:51] <ochosi> i thought they also use the powermanager?
[17:51] <bluesabre> maybe
[17:52] <bluesabre> we need to figure out what to do with this, want to create a wiki page or lp blueprint?
[17:52] <ochosi> one sec, i'm actually trying to follow up on the panel issues atm
[17:52] <ochosi> (alpha and bg issues i mean)
[17:53] <bluesabre> ok, cool
[17:56] <brainwash> bluesabre: do you test/use light-locker?
[17:57] <bluesabre> yeah, or I have in the past, haven't set it up on my new laptop yet
[17:58] <bluesabre> but I can answer any questions about it
[17:58] <brainwash> does the gtk greeter show the "log in" or "unlock" button after resuming from suspend/hibernate? :P
[17:59] <bluesabre> should show "unlock"
[17:59] <bluesabre> because it locks the screen when it suspends
[17:59] <brainwash> right, but lightdm does report a wrong status (lock_hint not set)
[17:59] <brainwash> for me (2 different systems)
[18:00] <bluesabre> so lightdm shows Log in for you then?
[18:00] <brainwash> yes
[18:01] <brainwash> but it works properly if I manually lock the screen and the suspend/hibernate
[18:01] <bluesabre> hm
[18:01] <bluesabre> ochosi ^
[18:02] <brainwash> ochosi cannot confirm this :/
[18:03] <brainwash> so I'm trying to find someone to confirm this issue
[18:03] <bluesabre> are you running saucy or trusty?
[18:04] <brainwash> one system is saucy, the other one is trusty
[18:04] <bluesabre> ah
[18:04] <bluesabre> covering all the bases ;)
[18:04] <brainwash> one can only suspend, the other one only hibernate :D
[18:04] <ochosi> so...
[18:04] <brainwash> basically they are totally different
[18:04] <ochosi> not covering all the bases ;)
[18:05] <bluesabre> I'm not familiar with the code, but I might take a look and see if anything sticks out to me
[18:05] <brainwash> if I manually lock the session, I will get redirected to vt8 _before_ entering the suspend state
[18:06] <brainwash> but automatically via dbus _after_ resuming
[18:06] <ochosi> my guess is that xfce4-session locks only after coming back from suspend
[18:07] <ochosi> light-locker locks it before going into suspend
[18:07] <ochosi> (because it seemed safer)
[18:07] <brainwash> xfce4-session does nothing actually, only triggering the suspend process
[18:07] <brainwash> xflock4 is not called
[18:08] <ochosi> might be a bug in the session then
[18:10] <bluesabre> not really a session bug, it doesn't lock by default on suspend
[18:11] <bluesabre> light-locker's lock activates when it detects the suspend-signal
[18:11] <bluesabre> but thats probably too late
[18:11] <bluesabre> so it locks when it comes back
[18:11] <bluesabre> is my guess
[18:11] <bluesabre> :D
[18:11] <ochosi> not sure, it locks on time here
[18:11] <ochosi> when i hit suspend, i see the lockscreen of light-locker for a split-second
[18:11] <bluesabre> probably a race condition
[18:12] <ochosi> maybe, but it has been working consistently here for a long while
[18:12] <ochosi> anyway, it wouldn't hurt to let the session take care of that
[18:12] <bluesabre> maybe we can upstream it with nick, or add an ubuntu-patch
[18:13] <ochosi> yeah
[18:13] <ochosi> i'm not at all familiar with the session code though
[18:13] <ochosi> also: the powermanager also handles that
[18:13] <ochosi> so duplocate functionality
[18:13] <ochosi> i think the powerman calls xflock
[18:14] <ochosi> (but it doesn't work with logind)
[18:14] <ochosi> it's a huge mess, imo
[18:20] <bluesabre> yeah
[18:20] <bluesabre> "modularity"
[18:22] <ochosi> :/
[18:22] <ochosi> imo we should fix the powermanager
[18:22] <ochosi> first ubuntu-patch it
[18:22] <ochosi> or convince nick that it needs patching
[18:22] <ochosi> but we really need a fix for that for 14.04
[18:22] <ochosi> at least proper logind support
[18:29] <brainwash> https://build.opensuse.org/package/show/X11:xfce/xfce4-power-manager
[18:29] <brainwash> patches do exist
[18:32] <brainwash> gnome-screensaver shows the "unlock" button after resume
[18:32] <ochosi> we should try to get those patches then...
[18:33] <brainwash> contact the ubuntu package maintainer
[18:37] <bluesabre> prtty sure that would be "Xubuntu Developers"
[18:37] <bluesabre> :)
[18:39] <ochosi> yup
[18:46] <forestpiskie> ok - see lock screen on way to suspending - comes back to login screen
[18:47] <forestpiskie> screen still blanking after 10 minutes - I assume that'll get sorted eventually
[18:47] <forestpiskie> back tomorrow
[18:50] <ochosi> forestpiskie: did you move your mouse?
[18:50] <ochosi> ah
[18:50] <ochosi> screen still blanking means: use "xset s $timeout" in your running session
[18:51] <ochosi> this setting doesn't get restored
[18:51] <ochosi> so you'd have to add it to your autostarted apps
[19:04] <brainwash> welcome back to 1999 :D
[19:05] <brainwash> ochosi: does the background of gtk3 indicator panel item become transparent occasionally?
[19:06] <brainwash> like full transparent
[19:11] <ochosi> no, not atm
[19:32] <jjfrv8> brainwash, hi. Did you ever file a bug for the Abiword ruler issue? I'm seeing it with the current daily.
[19:33] <ochosi> and if you do, please file it against abiword :)
[19:33] <brainwash> jjfrv8: not yet
[19:33] <jjfrv8> did you still plan to or do you want me to?
[19:34] <brainwash> open an extra window like the about dialog one and it will restore the ruler
[19:34] <brainwash> oh, the about dialog is missing an icon
[19:34] <ochosi> really?
[19:34] <brainwash> yeah, feel free to report it
[19:34] <ochosi> can you show me a screenshot of it?
[19:34] <ochosi> or is it one that abiword would usually provide
[19:35] <brainwash> it's showing the "image not available" one
[19:35] <ochosi> hm
[19:35] <ochosi> weird
[19:35] <jjfrv8> yes
[19:35] <brainwash> the usual abiword strangeness
[19:37] <ochosi> brainwash: when you get back from hibernation, other than the lock-hint missing you can re-login to your session, right?
[19:38] <brainwash> yes, everything seems to work properly
[19:38] <ochosi> ok, so only the lock-hint is missing
[19:38] <ochosi> i'm talking to robert_ancell in #ubuntu-devel atm
[19:38] <brainwash> lightdm responds with "(null)"
[19:38] <ochosi> mind to join quickly and report your exp?
[19:39] <ochosi> just in two sentences or so
[19:48] <brainwash> we just need some people to test this scenario :/
[19:48] <jjfrv8> Abiword bug 1261203
[19:48] <brainwash> jjfrv8: did you test other themes?
[19:49] <jjfrv8> no, I didn't think it mattered much if you get it on a fresh install
[19:49] <brainwash> it seemed to work ok in Unity and Lubuntu
[19:49] <brainwash> but in Xubuntu/Xfce all/most themes were affected
[19:50] <brainwash> I will need to verify this
[19:51] <jjfrv8> just tried a couple; default, bluebird. problem still there.
[19:53] <brainwash> which icon theme do you use?
[19:53] <brainwash> this is a screenshot of my abiword http://en.zimagez.com/zimage/abiword.php
[19:53] <jjfrv8> the default, elementary Xfce darker
[19:56] <brainwash> mine looks slightly different
[19:56] <jjfrv8> my first screenshot looked just like yours - I put it in the bug. Now I'm getting a slightly different one
[19:57] <brainwash> I cannot recall that I've changed it to something other than xfce darker
[19:57] <ochosi> brainwash: are you using the shimmer-daily PPA?
[19:57] <brainwash> no
[19:57] <ochosi> cause i removed the gnome-icon theme dependency there to trigger all missing icons
[19:57] <ochosi> so i can add them
[19:58] <jjfrv8> ochosi, I am
[19:58] <brainwash> you mean the abiword about dialog icon?
[19:58] <ochosi> yup
[19:59] <brainwash> ok, so the change needs to be reverted?
[20:00] <ochosi> no, since you're not using the PPA, the bug is somewhere else
[20:00] <brainwash> but why isn't abiword showing its own icon/symbol? o.o
[20:00] <brainwash> maybe a general abiword bug
[20:01] <ochosi> yup
[20:01] <ochosi> dinner-time, bbiab
[20:02] <jjfrv8> I'm off for a bit too
[20:45] <skellat> Anybody have time to take a peek at LP Bug #1211933 perhaps?
[20:51] <Haythem> heeey
[20:51] <Haythem> anyone here ?