Arch Linux

cr3h

Member

Registered: 2015-01-21

Posts: 1

[KDE] Failed to properly resume session after tty switch or suspend.

Hello!
I have problem with resuming my X session after i switched console with ctrl+alt+F.., or after wake up from suspend/hibernate. In the first situation i can see my cursor and parts (triangles) of desktop which dynamically changes while moving my mouse. I can control my pc - its just a display issue. In second case are usually some static artefacts, for example affecting conky, but rest of desktop behaves normally. The only way for me to solve it is to change tty once again and kill X server, then it brings me automatically to kdm and then work fine, but it makes suspend/hibernate and changing ttys useless.

Edit: I found this error in /var/log/Xorg.0.log:

[ 13476.840] (EE) systemd-logind: failed to get session: PID 1699 does not belong to any known session

Return of ps -ef:

root      1699   290  3 12:37 tty7     Ss+    0:20 /usr/bin/Xorg.bin -br -novtswitch -quiet :0 vt7 -nolisten tcp -auth /var/run/xauth/A:0-IWmbl

Versions:

[cr3h@archlinux ~]$ kde4-config -v
Qt: 4.8.6
KDE: 4.14.3
kde4-config: 1.0

[cr3h@archlinux ~]$ X -version
X.Org X Server 1.16.3
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.18.1-1-ARCH x86_64 
Current Operating System: Linux archlinux 3.18.2-2-ARCH #1 SMP PREEMPT Fri Jan 9 07:37:51 CET 2015 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=79d42580-4069-42e7-84ce-db999184bf6f rw resume=/dev/sda4
Build Date: 29 December 2014  01:09:58PM
 
Current version of pixman: 0.32.6
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.

[cr3h@archlinux ~]$ lspci | grep VGA
02:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)

Last edited by cr3h (2015-01-22 11:56:28)

whoops

Member

Registered: 2009-03-19

Posts: 891

Re: [KDE] Failed to properly resume session after tty switch or suspend.

You probably figured this out yourself by now, but just in case google sends anyone else here:

This is a problem with compositing. A workaround is to switch it off and on again with [alt+shift+F12] every time this happens.

( Still looking for a real solution btw, that's how I ended up here. )

edit: this seems to work: (for nvidia prop driver) https://forum.kde.org/viewtopic.php?f=111&t=121590
options nvidia NVreg_RegisterForACPIEvents=1 NVreg_EnableMSI=1
( no, it didn't - not totally at least. Probably was just lucky the problem didn't - happen the first 3 times I tested  )

Last edited by whoops (2015-08-05 09:16:21)