[02:04] <bluesabre> beta testcases are up, http://iso.qa.ubuntu.com/qatracker/milestones/402/builds
[06:24] <flocculant> bluesabre: I'll try and get a couple done tonight
[13:57] <ochosi> flocculant: that really looks like a whiskermenu issue with the version of garcon we have in ubuntu. did it really crash the whole panel or just the one plugin?
[16:34] <knome> ochosi, around?
[17:21] <flocculant> ochosi: just crashes whisker from what I can see - it restarted properly after the second go this last time - previously I lost it completely and my customisation of it
[17:22] <flocculant> ochosi: also - I have everything I can think of telling the system to not run a screensaver nor any blanking from the power settings - it still seems to blank the screen
[17:22] <flocculant> lightlocker is removed
[17:30] <flocculant> not laptop of course
[17:35] <flocculant> knome: hi there - always with an issue of late - did you know the wiki was dead? 
[17:35] <flocculant> or did I miss some mail somehow ...
[18:25] <flocculant> ochosi: https://streamable.com/ppy3t
[18:43] <flocculant> presentation mode does at least work
[18:55] <knome> flocculant, hmm, no, it should be up
[18:55] <knome> but have to go now, will look at it tomorrow
[18:55] <knome> thanks for the heads up
[19:25] <flocculant> knome: no worries
[22:21] <ochosi> flocculant: you probably have to *enable* display power management, otherwise the X11 default settings are used for screen blanking
[22:22] <ochosi> you can query those settings with "xset -q" in the terminal (check for DPMS and Screen Saver)
[22:22] <Unit193> FWIW, regarding the panel I do not have whisker.
[22:22] <ochosi> well it sounded more like flocculant had an issue with whisker, not with the whole panel (unless i misunderstood his latest messages)
[22:23] <ochosi> so i think you're seeing different issues
[22:23] <ochosi> can you reproduce your bug?
[22:24] <Unit193> I'd have presumed so as well, and not in a reliable way.
[22:27] <ochosi> maybe you can check xsession-errors or some other hint?
[22:27] <ochosi> alternatively compile the panel with debug=full and run it for some time and try to reproduce?
[22:28] <Unit193> Indeed, there wasn't much there.
[22:29] <ochosi> :/
[22:29] <ochosi> so i guess without a little more to go on i'm not sure how much i can do...
[22:33] <Unit193> Last update caused the window buttons plugin to freeze, and kill didn't work without -9. :/  Oh yes, I'm not really saying you can, just figured it'd be remiss if I didn't bother to mention it at all, in case someone else had it as well.
[22:34] <ochosi> and that's a plain install of 19.04?
[22:41] <Unit193> Well, not precisely, no.  But it is 19.04