[00:00] <ochosi> i sometimes see this issue as well, or something similar, and i wonder if it's x11 because if i do a manual VT switch the session wakes up again (that's without light-locker or any other screensaver apart from the x11 mit screensaver extension)
[00:08] <TJ-> I've never been able to get the DPMS to be enabled in that way, once its off its off
[00:09] <TJ-> ochosi: I added a delay loop and it didn't help
[00:10] <TJ-> I've added a report of what the X error is from gdk_x11_display_error_trap_pop
[00:15] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: Disable xfce4-screensaver lock screen in the live session @ http://git.launchpad.net/xubuntu-default-settings/commit/?id=650fd90df8d1e3e7b15fd789907fa47e9e2f68e5 (by Sean Davis)
[00:22] <TJ-> Well, the error is 8 but cannot figure out where to decode that; can't see an obvious error.h 
[00:24] <TJ-> hmmm, seems to be "#define BadMatch           8    /* parameter mismatch */ "
[00:36] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: Add Super+L shortcut to lock the screen. Replace Ctrl+Alt+D with Super+D to show the desktop @ http://git.launchpad.net/xubuntu-default-settings/commit/?id=4f8124a0669462a5ff86017043ab4cc068ae4b1e (by Sean Davis)
[00:37] <bluesabre> Unfortunate that xfwm4 doesn't support multiple keybindings and doesn't have an interface for it's commands (I think)
[00:39] <bluesabre> TJ-: yeah, I've definitely seen instances where DPMS gets turned on, and not back off without swapping VTs and killing it (more than just with light-locker)
[00:40] <bluesabre> ochosi: do you have a strong opinion on: [TEAM VOTE] The GIMP: Shipping with GTK theme by default ?
[01:00] <Eickmeyer> bluesabre: ack
[01:14] <bluesabre> Finally got the emoji email out. Hopefully we get some +1s :)
[01:17] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-cpugraph-plugin 1.0.91 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-cpugraph-plugin-1-0-91-released-tp54273.html (by André Miranda)
[06:57] <ochosi> bluesabre: maybe we can simulate the problem by enabling dpms on a secondary monitor and then trying to configure it with xrandr. if thats the problem we may just havr to add a dpms call to xfsettingsd (if it doesnt do that already)
[06:57] <ochosi> regarding gimp, i'd go for non-dark theme. the dark theme of gimp osnt really that nice (its more dark greyish) and the monochrome icons dont help a11y imo
[08:46] <knome> hmm, should update the team factoid
[10:15] <bluesabre> ochosi: I think dpms is all monitors or none
[10:15] <bluesabre> ochosi: thanks for the vote :)
[10:15] <bluesabre> ochosi: now vote on emoji ;)
[11:14] <ochosi> bluesabre: ah right, possible that affects all displays because its a single x call
[11:15] <ochosi> but with a timeout one could still easily simulate this
[11:15] <ochosi> dpms on -> sleep 3000 -> xrandr --auto
[11:15] <ochosi> or something along those lines
[13:06] <TJ-> bluesabre: I did a test with the daily 19.10 amd64; the live env suffers the same on the 2nd cycle of lid-close suspend>resume too. Updated bug report to reflect that. As before, monitoring the output's dpms node in sysfs shows it being turned off when the GUI TTY is active
[13:44] <bluesabre> TJ-: some possibly good news for 19.10... will be swapping out light-locker for xfce4-screensaver today or tomorrow. Major difference between the 2 is that the latter doesn't use vt-switch for user locking. At least for me, this means I am able to suspend/resume my laptop normally and it always comes back
[13:44] <bluesabre> (ofc, we still need to get the LTS into a reasonable state)
[13:56] <TJ-> but neither of those are used in the Live environ are they?
[22:42] <jphilipz> hi all, i want to do QA testing primarily on the upcoming xfce 4.14 components and wondered if i should get the daily iso or the 19.04 iso and add the qa staging ppa on top of it
[22:54] <guiverc2> jphilipz, I'm no expert, but I'd suggest eoan daily from http://iso.qa.ubuntu.com/qatracker/milestones/ as it allows you to record your QA-tests, have have a place for comments and to report bugs (if found) in a manner that's more easily tracked  (they go on launchpad anyway; but it has test/bug tracking)  my 2c
[22:56] <jphilipz> guiverc2: thanks. when you say 'record your QA-tests', can you elaborate on that
[22:57] <guiverc2> if you open the provided link, it'll take you to http://iso.qa.ubuntu.com/qatracker/milestones/404/builds/195174/testcases/1303/results  (for live qa-tests); where you can currently see some recent logs  (i forgot were there)
[23:01] <guiverc2> jphilipz, i would have pushed that less if I'd realize my logs were there, but take note of button "Add a test result"  it has places for critical bugs, bugs & comments, you can amend your reports ...  from launchpad you can view all qa-tests (from iso.qa.ubuntu.com) that involve a specific bug etc
[23:09] <jphilipz> guiverc2: thanks
[23:11] <jphilipz> i see here there are various test cases, but what about reporting bugs not related to these - http://iso.qa.ubuntu.com/qatracker/milestones/404/builds/195174/testcases
[23:11] <guiverc2> report those normally thru launchpad.   the iso.qa site is specific to those tests, and should NOT limit your testing :)
[23:12] <guiverc2> record comments as you see appropriate (or useful to you) 
[23:12] <guiverc2> useful to you & others
[23:17] <jphilipz> i've reported a few bugs on launchpad before for ubuntu mate, so lets see how this goes