[12:38] <bluesabre> Freshly installed eoan on my laptop
[12:38] <bluesabre> Noticed the flicker in the whiskmenu folks have mentioned
[12:39] <bluesabre> Also noticed we're not currently building xfce4-settings with the colord support... I'm thinking we probably want that
[13:33] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfmpc 0.3.0 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfmpc-0-3-0-released-tp54268.html (by André Miranda)
[14:02] <knome> yes please :)
[14:48] <bluesabre> ochosi: what packages are required for colord to find my monitors? In eoan, I'm just getting "No devices found."
[14:48] <bluesabre> It detected my scanner, briefly, earlier
[14:49] <bluesabre> Or is this possibly some nvidia-linked issue?
[14:53] <bluesabre> https://imgur.com/NBNJfcS.png is what I'm seeing
[19:02] <ochosi> bluesabre: you need xiccd for that, it's an additional daemon
[19:02] <ochosi> yuck, the no devices found is misplaced, i thought that one expands
[19:02] <ochosi> i mean it could be worse, but it should be centered
[19:02] <ochosi> (vertically)
[19:05] <ochosi> actually it's all summed up and explained here: https://simon.shimmerproject.org/2019/02/19/color-profile-support-for-xfce/
[19:06] <ochosi> (also the xiccd dependency)
[20:01] <TJ-> bluesabre: when you have time, could you give an opinion on the findings in comments #16 onwards in Bug #1759950  - the Lid-Close-Suspend-Resume-DPM-off issue - I've traced it down through to libxrandr but not being familiar with this area of functionality not sure what to make of it
[20:22] <brainwash> TJ-: I have no input, but did you test with 19.10 dev yet?
[20:23] <TJ-> brainwash: no, not so far
[20:23] <brainwash> or 19.04 + xubuntu experimental PPA
[20:24] <TJ-> I'll fetch the 19.10 daily and try that
[20:25] <TJ-> really annoys me that all the -dev images have the same name no matter which flavour; almost overwrote the Lubuntu image!
[23:25] <bluesabre> ochosi: thanks, that does the trick
[23:29] <bluesabre> TJ-: that's interesting, but I really don't know where to go from there since I'm not particularly well versed in randr either :(
[23:32] <TJ-> bluesabre: 3 issues are strange; 1) first close-suspend-open-resume is fine, but subsequent cycles fail, 2) the fact I added a delay and it still doesn't recover suggests it isn't a race condition 3) as this doesn't affect other flavours my suspicion is its something xfsettingsd is {not,} doing  
[23:36] <bluesabre> !team | uploaded colord-enabled xfce4-settings to eoan. Should build and be available a bit later.
[23:37] <bluesabre> https://launchpad.net/ubuntu/+source/xfce4-settings/4.13.6-0ubuntu2
[23:37] <bluesabre> Eickmeyer: FYI ^
[23:38] <bluesabre> TJ-: is there any other non-Xfce desktop that we could test by dropping light-locker/xfce4-settings into?
[23:40] <TJ-> bluesabre: not sure to be honest! I have a tentative theory... you know that both the first and second cycles both report "xfsettingsd-CRITICAL **: <timestamp>: Failed to apply display settings" ... what if thatfailure after the 1st resume is the cause of the 2nd cycle then failing (not updating some internal state possibly ?)
[23:41] <bluesabre> TJ-: that sounds like as good a theory as any :)
[23:41] <TJ-> hehehe grasping at straws :)
[23:41] <TJ-> I've not focusing on that aspect as yet, but I guess I ought to since we'd rather not have any failures
[23:42] <TJ-> It's sure easier than trying to figure out libx11 and libxrandr
[23:44] <TJ-> seems to come from  if (gdk_x11_display_error_trap_pop (gdk_display_get_default ()) != 0)
[23:44] <TJ-> so I presume gdk_display_get_default() is where to focus
[23:47] <TJ-> ahhh, and that looks to be one of yours :)  c6c7ca212
[23:56] <TJ-> hmmm, so, if I understand correctly, one of the function calls between the push and the pop is failing
[23:58] <ochosi> maybe x11/gdk isnt ready when xfsettingsd is asking for the display