[06:19] <flocculant> bluesabre: thought I'd best remind you of that parole/some mkv files issue
[06:22] <flocculant> tried to install parole from daily ppa and got some dependency issue with gstreamer1.0-clutter 
=== Hallo32 is now known as Justanick
=== Hallo32 is now known as Justanick
=== davmor2_ is now known as davmor2
=== Justanick1 is now known as Justanick
=== Justanick1 is now known as Justanick
[19:31] <a1fa> hello - i hit a strange resume bug with xfce in xubuntu 17.04 not wanting to unlock after resuming
[19:31] <a1fa> anyone else hit that?
[19:33] <flocculant> a1fa: only seen resume after lock issues when I've locked accidentally and quickly tried resuming
[19:33] <flocculant> with nvidia
[19:34] <flocculant> best thing you can do is report it ubuntu-bug light-locker then you can report that bug number in here
[19:34] <a1fa> this is a laptop with intel gpu - i waited 10 min between resumes
[19:34] <flocculant> people able to test will try and confirm that 
[19:34] <a1fa> should i do launchpad bug report?
[19:35] <flocculant> didn't see it when I was using intel on the desktop - but laptop/desktop issues often vary 
[19:35] <flocculant> a1fa: use ubuntu-bug and it will grab all the things it needs from your system
[19:35] <a1fa> let me try again
[19:36] <a1fa> btw - liking the new defaults in 17.04
[19:36] <flocculant> a1fa: also the xubuntu-devel mailing list is a good place to catch people using dev version
[19:37] <a1fa> flocculant: how long should i wait before resume? 30s?
[19:37] <a1fa> < 
[19:37] <flocculant> when I've managed to fail it - it was less than the time it takes to enter a password - so 30s should be fine :)
[19:38] <a1fa> ok. 50s.. i get "This session is locked" 
[19:38] <a1fa> so i get prompted for password, i unlock it, it goes to black screen with "This session is locked"
[19:38] <flocculant> mmm
[19:38] <flocculant> we saw that before cycle or so back
[19:39] <flocculant> not tried lately - might be back in a bit too long ...
[19:39] <a1fa> so far the workaround is to restart lightdm
[19:41] <a1fa> should i open a bug for light-locker?
[19:42] <flocculant> you can or I can now I've had a go ...
[19:42] <flocculant> I'll dig out the old bug
[19:44]  * flocculant checks one of the previous symptoms
[19:45] <a1fa> were you able to replicate it?
[19:45] <flocculant> yup 
[19:45] <flocculant> and the old symptom
[19:46] <flocculant> a1fa: thanks for bringing it up :)
[19:47] <a1fa> no problem - glad it will get some attention
[19:48] <a1fa> i'm also testing btrfs on root on this machine
[19:48] <a1fa> its a laptop with dual msata disks
[19:49] <flocculant> bluesabre: so we appear to have lock issues again - very similar to bug 1622303
[19:49] <ubottu> bug 1622303 in xfce4-session (Ubuntu) "Fails to unlock/ resumes to black screen" [Undecided,In progress] https://launchpad.net/bugs/1622303
[19:49] <flocculant> which last time was down to pitti change to x-d-s - but guessing not that as we've got same package still
[19:50] <flocculant> I'm seeing slightly different than last time - lock with music playing, unlock and momentarily can hear music - which then stops again - cursor flashing in top right on tty8 as it tries to unlock
[19:51] <flocculant> I guess it would be best to report anew for this cycle? 
[19:51] <flocculant> and \o/ for it not being the middle of April ;)
[19:53] <a1fa> want me to report it?
[19:54] <flocculant> a1fa: probably - but also maybe not as we have the bug linked just above from the 16.10 cycle
[19:54] <flocculant> a1fa: would be useful to know if you saw it in 16.10?
[19:55] <a1fa> i did
[19:55] <a1fa> but it unlocked after 2nd time
[19:55] <flocculant> oh really 
[19:55] <flocculant> odd
[19:55]  * flocculant will try tomorrow at booting with intel driver and checking that too
[19:56] <a1fa> https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399
[19:56] <ubottu> Launchpad bug 1656399 in light-locker (Ubuntu) "Unable to unlock Xubuntu XFCE session after suspend." [Undecided,New]
[19:56] <flocculant> a1fa: you didn't run ubuntu-bug from a terminal? just manually reported it? 
[19:57] <a1fa> manually :X
[19:58] <a1fa> dont have the interwebs on that laptop
[19:58] <flocculant> right 
[19:58] <a1fa> can i run it into a file, and attach it?
[19:58] <flocculant> yea - trying to remember how :)
[20:00] <a1fa> here i got interwebs up now
[20:00] <a1fa> lets see
[20:01] <flocculant> a1fa: https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_offline_or_using_a_headless_setup
[20:03] <a1fa> ok i think i associated the report
[20:09] <flocculant> a1fa: thanks :)
=== Justanick1 is now known as Justanick
[21:31] <a1fa> flocculant: i got some more news.. same behaviour after idle screen
[21:42] <flocculant> a1fa: pretty sure that's the same light-locker
[21:55] <a1fa> yeah and if you click lock, same thing happens -_X
[22:01] <flocculant> yup
[22:09] <flocculant> bluesabre: luckily I can confirm all this lock issue on a vm so no need to install to see it
[22:10] <flocculant> well - when I say luckily I have tongue in cheek - what would be really lucky would be a cycle without light-locker coming up again
[22:10] <flocculant> (unless it's lightdm ofc)
[22:12] <flocculant> also - pretty sure I wasn't seeing this for the whole cycle - at some point in the last couple of months I've suspended and it's been ok