[01:03] <Unit193> Oh look, xfce4-equake-plugin 1.3.5 released.
[01:32] <bluesabre> Unit193: evince vs evince-gtk whats the diff?
[01:34] <Unit193> Mmm.  Guess you don't know then.  One is more gnome based.
[01:34] <Unit193> Try installing -gtk and see if you notice any missing functionality?  It'd be for Vapid Vampire anyway.
[01:36] <bluesabre> Seems identical, I'd have to sit down with it
[01:36] <bluesabre> good to know that there is probably some distinction though
[12:12] <elfy> ochosi: what's going with the screensaver times - I've had to resest it to 0 again today
[12:15] <ochosi> elfy: well you tell me, what *is* going on with them? 
[12:17] <ochosi> did the xfpm settings change?
[12:18] <ochosi> or were the displayed values in xfpm settings not the same as in X?
[12:18] <ochosi> (bottom line: i really need more info...)
[12:33] <elfy> sorry meant to post this http://pastebin.com/K81VtX1h
[12:34] <elfy> xset when it blanked, when I'd upped them and then once I'd set them to 0 again
[12:48] <ochosi> hm, strange, we didn't change anything in the blanking department for a while
[13:01] <ochosi> elfy: so this happens just sometimes?
[13:01]  * ochosi wonders whether anyone else has experienced that...
[13:02] <ochosi> i admit to not having checked the logic of how xfpm sets/resets these times, i just added new functionality (blanking) on top of the existing DPMS support
[13:02] <ochosi> since there were no bugreports claiming that that doesn't work (and since it seemed to work just fine for me), i'm a bit puzzled by this issue
[13:19] <elfy> yea - not had it since the last time though which was after update of x-d-s 
[13:20] <elfy> only odd thing I've done since then and today was play about with saving session and logging into that
[13:22] <ochosi> the session doesn't remember the values for blanking
[13:22] <ochosi> which was the main reason to implement this feature in xfpm
[13:22] <elfy> no idea then
[13:22] <ochosi> but i've heard that there are some bugs with session management
[13:22] <ochosi> so it might be related to that
[13:23] <ochosi> did you check what values xfpm displayed in its settings when you experienced the blanking?
[13:23] <ochosi> (just to know whether it was reset to its own defaults or whether it was simply out of sync with the X11 settings)
[13:23] <elfy> unless updates to power manager and/or data are doing it - had updates to data yesterday
[13:24] <ochosi> that was just a tiny patch to fix lid-close suspending
[13:24] <elfy> I did check - xfpm was reporting what I had set it for - 0 all across the board
[13:24] <ochosi> right
[13:24] <ochosi> in that case it was out of sync with X11, because the session management or something else tampered with those settings
[13:24] <ochosi> which is a known issue in 1.4, unfortunately
[13:25] <elfy> ochosi: yes - but if it is resetting things to 'default' regardless of what got fixed
[13:25] <ochosi> haven't had time to check that yet, it's unfortunately more complicated to fix than it sounds...
[13:27] <elfy> ok - well if I see it again I'll try and take more notice of what's going on at around the same time
[13:29] <ochosi> thanks, that'd be great
[13:29] <ochosi> i'd really like to get this sorted
[13:30] <elfy> you and me both - when it catches me unawares it's usually just at the wrong time :p
[13:30] <ochosi> heh, yeah :)
[13:31]  * ochosi wonders what the right time would be
[13:31] <elfy> ha ha ha 
[13:43] <brainwash> bluesabre: just noticed something related to "Black screen on resume in Xubuntu 14.04.1"
[13:44] <brainwash> from the report: "Black screen on resume when using standby on close lid is confirmed on Dell Latitude D400 on completely new install of Xubuntu 14.04.1 32 bit."
[13:44] <brainwash> now take a look at bug 1254131
[13:44] <ubottu> bug 1254131 in linux (Ubuntu) "[Dell Latitude D505] Lubuntu suspend via lid close causes freeze" [Low,Confirmed] https://launchpad.net/bugs/1254131
[13:44] <brainwash> Dell Latitude in both cases
[13:46] <brainwash> appears to be the exact same problem
[13:46] <brainwash> black screen + mouse cursor visible and system completely frozen
=== LazyUser69 is now known as LazyUserBNC
[15:29] <brainwash> bluesabre: should we backport the fixes for bug 1347272 to trusty?
[15:29] <ubottu> bug 1347272 in xfce4-volumed (Ubuntu) "Several XFCE applications appear unresponsive after communicating with a daemon" [High,Triaged] https://launchpad.net/bugs/1347272
[15:30] <brainwash> Noskcaj: ^
[15:31] <brainwash> "Nominated for Lucid" :D
[15:35] <brainwash> Noskcaj: do you keep an eye on this meta report?
[16:24] <pleia2> elfy: I shall tweet
[16:25] <elfy> pleia2: thanks :)
[16:25] <elfy> it's an early warning ;)
[16:25] <elfy> probably as pointless as the last one - but as long as I've done what I can *shrug*
[16:26] <pleia2> I appreciate it, I'm conferencing again next week, but it's local so I can download things and make time, now I won't forget!
[16:27] <ochosi> +1
[16:32] <elfy> ty pleia2 :)
[19:54] <Noskcaj> brainwash, not really, but i can
[19:56] <brainwash> Noskcaj: the fixes will land at some point in ubuntu, but I'm not sure if sru'ing them is really necessary
[19:56] <brainwash> too much paper work :/
[20:12] <Noskcaj> I'd not worry about an SRU unless we get a bunch of crash bug reports
[20:16] <brainwash> like over 1000 bug heat? :>
[20:17] <brainwash> it is sru worthy
[20:30] <Noskcaj> ok
[20:30] <Noskcaj> then as long as the fix works in utopic, we should backport it
[22:41] <bluesabre> hey everyone
[22:42] <bluesabre> brainwash: yeah, the list of things to backport is growing
[22:42] <ochosi> hey bluesabre 
[22:42] <ochosi> about to go to bed
[22:42] <ochosi> how're things?
[22:43] <Unit193> bluesabre: Timed out 10 minutes before you said that.
[22:44] <bluesabre> things are good
=== LazyUserBNC is now known as LazyUser69