[04:08] <katnip> lot of updates today :)
[04:08] <lotuspsychje> :p
[07:36] <Faux> Oh no!
[08:12] <sacarde> hi
[08:13] <sacarde> I installed ubuntu-daily dev version 18.04
[08:15] <sacarde> in /etc/os-release I view: development-branch
[08:15] <sacarde> if I will upgrade system when it will be released...
[08:16] <ducasse> !final
[08:16] <sacarde> ah.. ok
[08:18] <sacarde> thanks
[08:29] <Faux> > The display composition pipeline went through a major overhaul in release 390. As a side effect, it is now re-compositing the screen on every vblank. That's likely the cause of the GPU load you're seeing. We're working on optimizing it to reduce the overhead (tracking bug 2085439) but in the meantime, you can force the driver to use the old composition pipeline by setting.
[08:30] <Faux> Hating this driver more and more every day.
[10:00] <TJ-> Seem to have found a bug with lightdm/XFCE4. After resume from S3 sleep and having authenticated via the lock-screen greeter the user GUI session on vt7 remains black. Expected user-session processes, lightdm, Xorg are still runing with no indications in any log-file that something is wrong. Switching to a console works fine, switching back - console black. Intel HD 5300 GPU, no hybid. Trying to think of
[10:00] <TJ-> some more diagnosis I could do
[16:45] <Boyette> Hi
[16:46] <Boyette> I need some help debugging a very strange bug
[16:50] <lotuspsychje> !ask | Boyette 
[16:53] <Boyette> When I press the Prt SC button .. prtsc is not activated but mostly after 2 minutes system shutsdown 
[16:54] <lotuspsychje> Boyette: can you open a: tail -f /var/log/syslog and try that to see errors?
[16:56] <Boyette> https://pastebin.com/Mh6zzncJ
[16:58] <lotuspsychje> Boyette: system has shutdown?
[16:58] <Boyette> it just happend 5-10 minutes ago last time
[16:58] <lotuspsychje> Boyette: keep your tail open until it does, and see what happens
[16:58] <Boyette> it will just turn off a few minutes after i press that button
[16:59] <Boyette> well now offcourse the button does work
[16:59] <Boyette> but im sure in syslog i can find errors with freedesktop
[16:59] <Boyette> i noticed before
[16:59] <lotuspsychje> Boyette: did you clean install 18.04 daily?
[17:01] <Boyette> when
[17:02] <Boyette> i just dist-upgrade daily. thats not good?
[17:02] <lotuspsychje> Boyette: i mean did you install daily or upgrade from a version?
[17:02] <Boyette> dist-upgrade daily
[17:02] <Boyette> but this issue is there already for a while
[17:03] <lotuspsychje> Boyette: cool, let us know when you get more syslog errors on shutdown
[17:04] <Boyette> i have also xorg0.log xorg1.log
[17:04] <Boyette> syslog is very big 
[17:04] <Boyette> cant read
[17:04] <lotuspsychje> Boyette: i mean on your tail, in realtime check the errors before shutdown
[17:05] <Boyette> ok
[17:06] <Boyette> no way to read the syslog which for sure should have logged something 20 minutes ago
[17:06] <lotuspsychje> Boyette: you didnt play with any other program to assign a command to prtscr?
[17:07] <Boyette> no
[17:07] <Boyette> and the issue comes and goes
[17:07] <lotuspsychje> Boyette: press prtscr now, see if it does something in your tail?
[17:07] <Boyette> now it works fine
[17:07] <Boyette> Mar 29 19:05:06 HQ systemd[1]: Starting Hostname Service...
[17:07] <Boyette> Mar 29 19:05:06 HQ dbus-daemon[816]: [system] Successfully activated service 'org.freedesktop.hostname1'
[17:07] <Boyette> Mar 29 19:05:06 HQ systemd[1]: Started Hostname Service.
[17:07] <Boyette> Mar 29 19:07:20 HQ dbus-daemon[816]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.105' (uid=1000 pid=3373 comm="mate-screenshot " label="unconfined")
[17:07] <Boyette> Mar 29 19:07:20 HQ systemd[1]: Starting Hostname Service...
[17:07] <Boyette> Mar 29 19:07:21 HQ dbus-daemon[816]: [system] Successfully activated service 'org.freedesktop.hostname1'
[17:07] <lotuspsychje> Boyette: you sure its related to prtscr?
[17:08] <lotuspsychje> Boyette: mate-screenshot? where did you get that
[17:10] <lotuspsychje> !paste | Boyette 
[17:10] <Boyette> im on 18,04 mate
[17:11] <flocculant> TJ-: mmm - I've had to go back to lightdm 1.25.2-0ubuntu1 to get working suspend here
[17:11] <flocculant> and that's not great - 2 logins to get to desktop
[17:12] <flocculant> will have to do a bit more testing - then I'll report a bug
[17:12] <Boyette> so i think mate 18,04 comes with mate-screenshot
[17:12] <flocculant> just got home 
[17:13] <lotuspsychje> Boyette: ah kk, never worked with mate before
[17:13] <lotuspsychje> evening flocculant :p
[17:14] <flocculant> hi lotuspsychje :)
[17:14] <Boyette> its not so different
[17:14] <Boyette> just the skin i guess
[17:15] <Boyette> can it be related to something like this
[17:15] <Boyette> https://bugs.launchpad.net/ubuntu/+source/mate-utils/+bug/1615740
[17:17] <TJ-> flocculant: the last lightdm upgade bumps the version to 1.26 but only says it dropped a build-depend
[17:18] <TJ-> flocculant: looks like the 'Fix incorrect use of ConsoleKit CanSuspend/Hibernate API' may be related in 1.25-2
[17:25] <flocculant> yea read that - but haven't done much more than put the kettle on ;)
[17:30] <TJ-> ah, no, that's just to check it's possible. The issue I'm seeing is nothing to do with that. The Xorg vt just stays black, consoles are OK
[17:31] <flocculant> TJ-: what I was seeing prior to fiddling with versions was : suspend - unsuspend - login - see desktop - back to login - desktop but unusable
[17:31] <flocculant> biab
[17:31] <TJ-> A manual suspend doesn't cause it either... I'm wondering if it's related to suspend triggered by lid close
[17:33] <TJ-> Yes! that's the issue. When it resumes the greeter/lock-screen log-in is shown correctly but as soon as I've auth-ed it goes black
[17:35] <flocculant> TJ-: ok - thanks - not got laptopt to test that atm
[17:36] <flocculant> TJ-: I assume that's with 1.26?
[17:36] <TJ-> Yes
[17:36] <flocculant> ok - cheers
[17:36] <TJ-> it looks like an Xorg issue
[17:37] <TJ-> the only clue I see (no timestamp so possibly unrelated) is in $HOME/.xsession-errors with "Failed to configure CRTC 63" - seeing as the GPU only has 3 CRTCs that could be a problem
[18:04] <flocculant> TJ-: well - not only do I get issues with suspend - but after beating my way back to desktop - no network seemingly? Could you see if you have network?
[18:07] <TJ-> flocculant: everything else is fine, the only issue is no user-session GUI output afte lid-close triggered suspend :)
[18:11] <flocculant> ok cheers - none here after suspend :p I do have the xubuntu team ppa's installed - will purge those before doing more
[18:11] <Bashing-om> TJ-: Just arrived .. nvidia ? newly patched drivers are now in the PPA .
[18:18] <TJ-> Bashing-om: no, intel
[18:19] <Bashing-om> TJ-: :) was but a thought .
[18:19] <TJ-> My current theory is the user session receives the lid-closed message and used DPMS to turn the display off, but doesn't get the lid-opened message after resume so when switching to the user session it disables the output again!