/srv/irclogs.ubuntu.com/2014/09/18/#xubuntu-devel.txt

Unit193Oh look, xfce4-equake-plugin 1.3.5 released.01:03
bluesabreUnit193: evince vs evince-gtk whats the diff?01:32
Unit193Mmm.  Guess you don't know then.  One is more gnome based.01:34
Unit193Try installing -gtk and see if you notice any missing functionality?  It'd be for Vapid Vampire anyway.01:34
bluesabreSeems identical, I'd have to sit down with it01:36
bluesabregood to know that there is probably some distinction though01:36
elfyochosi: what's going with the screensaver times - I've had to resest it to 0 again today12:12
ochosielfy: well you tell me, what *is* going on with them? 12:15
ochosidid the xfpm settings change?12:17
ochosior were the displayed values in xfpm settings not the same as in X?12:18
ochosi(bottom line: i really need more info...)12:18
elfysorry meant to post this http://pastebin.com/K81VtX1h12:33
elfyxset when it blanked, when I'd upped them and then once I'd set them to 0 again12:34
ochosihm, strange, we didn't change anything in the blanking department for a while12:48
ochosielfy: so this happens just sometimes?13:01
* ochosi wonders whether anyone else has experienced that...13:01
ochosii 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 support13:02
ochosisince 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 issue13:02
elfyyea - not had it since the last time though which was after update of x-d-s 13:19
elfyonly odd thing I've done since then and today was play about with saving session and logging into that13:20
ochosithe session doesn't remember the values for blanking13:22
ochosiwhich was the main reason to implement this feature in xfpm13:22
elfyno idea then13:22
ochosibut i've heard that there are some bugs with session management13:22
ochosiso it might be related to that13:22
ochosidid 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
elfyunless updates to power manager and/or data are doing it - had updates to data yesterday13:23
ochosithat was just a tiny patch to fix lid-close suspending13:24
elfyI did check - xfpm was reporting what I had set it for - 0 all across the board13:24
ochosiright13:24
ochosiin that case it was out of sync with X11, because the session management or something else tampered with those settings13:24
ochosiwhich is a known issue in 1.4, unfortunately13:24
elfyochosi: yes - but if it is resetting things to 'default' regardless of what got fixed13:25
ochosihaven't had time to check that yet, it's unfortunately more complicated to fix than it sounds...13:25
elfyok - well if I see it again I'll try and take more notice of what's going on at around the same time13:27
ochosithanks, that'd be great13:29
ochosii'd really like to get this sorted13:29
elfyyou and me both - when it catches me unawares it's usually just at the wrong time :p13:30
ochosiheh, yeah :)13:30
* ochosi wonders what the right time would be13:31
elfyha ha ha 13:31
brainwashbluesabre: just noticed something related to "Black screen on resume in Xubuntu 14.04.1"13:43
brainwashfrom 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
brainwashnow take a look at bug 125413113:44
ubottubug 1254131 in linux (Ubuntu) "[Dell Latitude D505] Lubuntu suspend via lid close causes freeze" [Low,Confirmed] https://launchpad.net/bugs/125413113:44
brainwashDell Latitude in both cases13:44
brainwashappears to be the exact same problem13:46
brainwashblack screen + mouse cursor visible and system completely frozen13:46
=== LazyUser69 is now known as LazyUserBNC
brainwashbluesabre: should we backport the fixes for bug 1347272 to trusty?15:29
ubottubug 1347272 in xfce4-volumed (Ubuntu) "Several XFCE applications appear unresponsive after communicating with a daemon" [High,Triaged] https://launchpad.net/bugs/134727215:29
brainwashNoskcaj: ^15:30
brainwash"Nominated for Lucid" :D15:31
brainwashNoskcaj: do you keep an eye on this meta report?15:35
pleia2elfy: I shall tweet16:24
elfypleia2: thanks :)16:25
elfyit's an early warning ;)16:25
elfyprobably as pointless as the last one - but as long as I've done what I can *shrug*16:25
pleia2I 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:26
ochosi+116:27
elfyty pleia2 :)16:32
Noskcajbrainwash, not really, but i can19:54
brainwashNoskcaj: the fixes will land at some point in ubuntu, but I'm not sure if sru'ing them is really necessary19:56
brainwashtoo much paper work :/19:56
NoskcajI'd not worry about an SRU unless we get a bunch of crash bug reports20:12
brainwashlike over 1000 bug heat? :>20:16
brainwashit is sru worthy20:17
Noskcajok20:30
Noskcajthen as long as the fix works in utopic, we should backport it20:30
bluesabrehey everyone22:41
bluesabrebrainwash: yeah, the list of things to backport is growing22:42
ochosihey bluesabre 22:42
ochosiabout to go to bed22:42
ochosihow're things?22:42
Unit193bluesabre: Timed out 10 minutes before you said that.22:43
bluesabrethings are good22:44
=== LazyUserBNC is now known as LazyUser69

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!