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