[05:30] <Unit193> knome: There, happy?  I also maaaay have had help with the answers.  I cheated. :3
[06:59] <Unit193> https://wiki.xubuntu.org/devel/ppa is wrong. :3
[07:15] <Unit193> https://wiki.xubuntu.org/releases/18.04/release-notes?do=diff&rev2%5B0%5D=1521701811&rev2%5B1%5D=1522307655&difftype=sidebyside ?
[15:24] <hilpv> hey there... I'm using xubuntu 17.10, and I've found that light-locker won't let me unlock my screen after a recent update. I traced this down to a failure where the seat path for systemd is NULL, and light locker can't do much to recover from there it seems. Is this a known issue?
[17:10] <flocculant> bluesabre: ^^ - also - on bionic after suspend I get a dead desktop - had to go back a version to see desktop
[17:14] <flocculant> not been in long - got stuff to do - then I'll try and look at it a bit logically
[17:15] <flocculant> ochosi: just to cheer you up - and just before release (again) lightdm turns into devil child :p
[18:26] <flocculant> well - I really hate this thing every cycle :(
[18:45] <TJ-> I've got an unusual blank/black/off tty issue on resume from suspend for the user session with 18.04. Looks to be related to XFCE, is this the correct channel to discuss/explore it? *only* when doing S3 suspend via lid-close, on resume lightdm greeter/lock shows and I authenticate. Immediately it switches to the user session the screen blanks (no sign of backlight). Can switch away to other TTYs and
[18:45] <TJ-> the console displays fine. switch back to GUI and 'black'
[18:46] <TJ-> I've been trawling logs watching it remotely over SSH and so far no clues as what is going on. xrandr says the output is connected and active, DPMS is off
[18:47] <flocculant> TJ-: yea it is the right channel - but currently you'll be talking to me only ;)
[18:53] <flocculant> TJ-: I did purge ppa's - still seeing bizarre things - and no network after suspend
[19:15] <TJ-> It's so weird it's making me laugh. I just returned from dinner, pressed a key, bluetooth connects, greeter/lock shows, authenticate and 'blam!' black screen again (it didn't resume so it's 'remembered' this 'off' setting for the user session
[19:16] <flocculant> so that's light-locker
[19:26] <TJ-> interesting! If I 'systemctl suspend' then after it's suspended close the lid. Open the lid, it resumes, greeter > auth > user session is fine
[19:32] <TJ-> this suggests the Lid Close event is handled but not cancelled when resuming
[19:33] <flocculant> https://i.imgur.com/5qYRfNj.png
[19:33] <flocculant> I get this when coming back from suspend - some times
[19:34] <TJ-> that looks like the wrong texture is being restored
[19:34] <flocculant> also the systemctl suspend made no difference to no network
[19:35] <TJ-> Interestingly, in auth.log up until March 25th when I d-r-u-ed to 18.04 there are "systemd-logind: Lid closed/opened" pairs ... since then, none
[19:36] <flocculant> (xfwm4:1316): xfwm4-WARNING **: 20:32:11.168: GL not available
[19:36] <flocculant> bluesabre: ^^
[19:36] <TJ-> which network device is it? dmesg should reveal something
[19:42] <TJ-> according to 'man logind.conf' HandleLidSwitch=suspend is the default but usually a GUI will take-over handling with an inhibito lock handle-lid-switch 
[19:43] <TJ-> this points the finger at xfce4-power-manager I think
[19:43] <flocculant> TJ-: dmesg had a lot of https://paste.ubuntu.com/p/rMnpkXR8hZ/
[19:44] <TJ-> flocculant: that's framebuffer (fb) DRM so definitely a video driver issue; what GPU/driver ?
[19:44] <flocculant> GeForce 210 using nouveau
[19:45] <TJ-> I've seen nouveau do that on 16.04 but it seems to depend on which GPU
[19:52] <TJ-> looks like x-p-m has also regressed in other areas; it no longer reports the Bluetooth keyboard battery status
[19:52] <flocculant> TJ-: took a few goes to get just no network > https://paste.ubuntu.com/p/yjmY5Tnz5y/
[19:54] <TJ-> I disable x-p-m Security > "Lock screen when system is going to sleep" and the problem didn't occur. Need to test it a few more times though
[19:56] <TJ-> oh, was wrong about no auth.log Lid closed/opened messages; grep thought the file was binary after March 25th. With 'grep -a' it sees the messages for 18.04
[19:59] <TJ-> and Bluetooth keyboard battery state is kernel issue; /sys/class/power_supply/hid-XXXXX/ nodes show the same values
[20:01] <flocculant> TJ-: I've got to afk now - hopefully someone helpful will be along 
[20:54] <Unit193> One could test via downgrading xfpm.
[21:11] <TJ-> I've found the problem and reverted the offending code. https://github.com/the-cavalry/light-locker/issues/108
[22:05] <Unit193> knome: You didn't review? :3
[22:05] <knome> review what?
[22:06] <knome> the slideshow? :P
[22:06] <Unit193> I pasted wiki link.
[22:06] <knome> hmm
[22:07] <knome> i approve the wiki change
[22:07] <Unit193> OK, thanks.
[22:47] <Unit193> knome: Oh, there's also the PPA wiki page. :>
[22:49] <knome> yes
[22:49] <knome> so what about that is wrong?
[22:52] <Unit193> 1. xfce4-gtk3 doesn't exist.  2. experimental may kind of be right, but it's basically "All Xfce development releases."  3. staging is basically "Backports to $currentRelease".
[22:53] <knome> ok, so why not update the page?
[22:53] <knome> it's a wiki for a reason... :)
[22:57] <Unit193> 1. Words are haaaard.  2. Yes, just making sure I'm not "going off and doing my own thing" :)
[22:57] <Unit193> Eg, communicating!
[22:57] <knome> tbh i'm not the right person to talk about the PPA descriptions
[22:58] <knome> i can help with the words things