[08:46] <Unit193> DanChapman: Howdy.
[08:46] <DanChapman> Howdy Unit193, and happy new year :-)
[08:47] <Unit193> Happy new year indeed.
[17:03] <jarnos> If I suspend by the log out dialog or by Action buttons, xflock4 is not called. What code is used, instead? What code xfce4-power-manager uses to lock?
[17:08] <brainwash> xflock4 is used if you tell xfce4-settings to do so
[17:10] <brainwash> jarnos: settings > session and startup > last tab
[17:34] <jarnos> brainwash, I see. However, if gnome-screensaver daemon is running, screen will be locked by it, if you have decided not to lock before sleep in settings.
[17:34] <brainwash> so? that's not a Xfce issue
[17:35] <brainwash> you need to configure gnome-screensaver
[17:37] <jarnos> brainwash, I don't see how you could do it.
[17:37] <brainwash> usually via dconf
[18:00] <jarnos> brainwash, but if you suspend using xfce4-power-manager, and you have chosen in its preferences not to lock, it won't lock even if gnome-screensaver daemon is running.
[18:57] <brainwash> jarnos: so it does not suspend via logind and calls upower directly I would assume
[19:00] <brainwash> so what is the actual problem? xubuntu does not ship with gnome-screensaver
[19:01] <brainwash> if you encounter the same issue with light-locker (fork of gnome-screensaver), please file a bug report on launchpad
[19:12] <jarnos> brainwash, is Xubuntu T going to be using light-locker in xflock4 ?
[19:12] <brainwash> jarnos: yes
[19:13] <brainwash> patch for xflock4 does already exist, but the branch needs to be merged
[19:14] <jarnos> brainwash, is the script going to be changed for xfce, too, or just xubuntu?
[19:14] <brainwash> you mean upstream?
[19:14] <jarnos> brainwash, yes
[19:15] <brainwash> don't know
[19:16] <jarnos> brainwash, light-locker depends on lightdm, but I guess xfce can be used with other display managers, as well.
[19:17] <jarnos> brainwash, where can I see the patch for xflock4?
[19:19] <brainwash> xflock4 simply tries to trigger known screen locker, and light-locker is kinda new
[19:20] <brainwash> jarnos: bug 1254366
[19:24] <jarnos> brainwash, thanks, I have been working on a patch for xflock4 in upstream, and I could try to take that into account.
[19:26] <brainwash> sounds great :)
[19:29] <brainwash> gottcode: hey, I've noticed something strange after upgrading to whisker menu 1.3, editing or changing .desktop files somehow crashes the panel plugin
[19:30] <brainwash> it happened while I was editing one file via text editor and also while apt-get was applying package updates
[19:31] <brainwash> I'll try to get some debugging information later
[20:31] <knome> i'm back.
[20:31] <knome> had a nasty stomach illness meanwhile, i hope you all were at least a bit better...
[20:37] <gottcode> brainwash: I will look into that shortly
[20:52] <jarnos_> I have been  trying light-locker in Saucy using this PPA: http://www.webupd8.org/2013/08/lightdm-session-locker-light-locker.html
[21:03] <jarnos_> I wonder, if there is some purpose in the light-locker daemon, which does not run on background btw. "light-locker-command -l" seems to work regardless of the daemon.
[21:05] <jarnos_> Whereas "gnome-screensaver-command --lock" starts its respective daemon, if one is not running.
[21:12] <brainwash> jarnos_: the daemon locks the session on suspend
[21:12] <brainwash> when suspend is triggered via logind
[21:13] <brainwash> and it also allows timed locking (after 10min)
[21:14] <brainwash> this feature requires a recent version of light-locker
[21:15] <jarnos_> brainwash, Do you mean it will lock screen only if you resume from suspend after e.g. 10 min?
[21:17] <brainwash> the daemon locks the screen on suspend OR after 10min of inactivity (according to the screen saver extension of the X server)
[21:22] <jarnos_> brainwash, oh, I see. I think xflock4 should then check, if the daemon is running, and use "light-locker-command -l "only then. I am going to address this in the bug report.
[22:49] <jarnos_> brainwash, now, there it is: bug 1254366
[23:13] <brainwash> jarnos_: ok, I'll test it as soon as I get access to my test system
[23:13] <jarnos_> brainwash, good
[23:14] <brainwash> currently everything is going slow, so it might take some time until the changes actually land in trusty
[23:55] <jarnos_> brainwash, so I have not yet tested light-locker in trusty, but I think it is the same version as in the PPA I have been using. In short tests I have seen at least to issues:
[23:56] <jarnos_> brainwash,  light-locker cannot fork, i.e.  "light-locker" runs just as "light-locker --no-daemon"
[23:56] <jarnos_> brainwash,  if I lock by it and change to different tty and back, desktop is shown short time.
[23:57] <jarnos_> Can anyone comfirm these in trusty?
[23:59] <jarnos_> Not much issues reported, yet: https://github.com/the-cavalry/light-locker/issues
[23:59]  * jarnos_ goes to sleep.