Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
KDE plasma / sddm - broken after update [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
davidm
Guru
Guru


Joined: 26 Apr 2009
Posts: 557
Location: US

PostPosted: Fri Apr 14, 2017 9:31 am    Post subject: KDE plasma / sddm - broken after update [SOLVED] Reply with quote

Hello has anyone else noticed a problem where upon boot sddm will display briefly then the screen will be black and flicker a bit and get stuck? Switching a virtual terminal works eventually, otherwise you can't do anything.

I also tried disabling sddm and using startx but KDE errors out. Starting fluxbox manually with startx works though so it seems to be a KDE related problem and not X.

Using nouveau and systemd if that matters.

Nothing obvious stood out in the journal but I will try to post some more log output later. I just wanted to see if this was only me having the problem. I've made no other changes other than system updates but it's been about three weeks since I last updated.


Last edited by davidm on Tue Apr 18, 2017 8:25 pm; edited 1 time in total
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6824
Location: Austria

PostPosted: Fri Apr 14, 2017 9:46 am    Post subject: Reply with quote

sddm is not a KDE product, if this issue is happening before you even log in to Plasma session this is completely unrelated. You can start Plasma-5 via startx as well.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
davidm
Guru
Guru


Joined: 26 Apr 2009
Posts: 557
Location: US

PostPosted: Fri Apr 14, 2017 3:25 pm    Post subject: Reply with quote

asturm wrote:
sddm is not a KDE product, if this issue is happening before you even log in to Plasma session this is completely unrelated. You can start Plasma-5 via startx as well.

Disabling sddm and using startx (with kde) was one of the first things I tried.

startx (with kde) errors out as well. But startx with fluxbox (using startx command line to manually start it) works.

I'll post some log output later when I next get a chance to reboot (am trying to install latest updates plus doing some work using fluxbox) and test it. It's possible the reason kde plasma does not work with startx is due to a configuration issue though from memory I had it working before from the cli without a display manager.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6824
Location: Austria

PostPosted: Fri Apr 14, 2017 5:51 pm    Post subject: Reply with quote

If there's errors with startx and flickering with sddm it seems there are multiple issues, but first and foremost I'd look at Xorg.0.log and dmesg, try the previous or a later version of mesa, etc...

davidm wrote:
(with kde)

I'm sure you actually mean Plasma. ;)
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
davidm
Guru
Guru


Joined: 26 Apr 2009
Posts: 557
Location: US

PostPosted: Tue Apr 18, 2017 6:13 pm    Post subject: Reply with quote

Yep, I meant Plasma. ;)

The only thing suspicious in Xorg.1.log is:

Code:

[   105.999] (II) NOUVEAU(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[   105.999] (II) NOUVEAU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   105.999] (II) NOUVEAU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[   105.999] (II) NOUVEAU(0): Modeline "1280x800"x0.0   71.00  1280 1328 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[   105.999] (II) NOUVEAU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   105.999] (II) NOUVEAU(0): Modeline "1440x900"x0.0   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
[   105.999] (II) NOUVEAU(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[   105.999] (II) NOUVEAU(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[   106.748] (EE)
[   106.748] (EE) Backtrace:


Odd? Looks like a crash but no hints are given. At least in this file. Using startx KDE/Plasma actually flickers and starts to load but disappears.

I doubt it is X because 'startx /usr/bin/startfluxboxworks' perfectly. I have a fully usable system now under fluxbox, but I like Plasma more.

This is a systemd system but here is .xinitrc:

Code:

exec /usr/bin/startkde


I just upgraded mesa and kwin I think once again after this already happened. It didn't fix it. I guess I can try downgrading further. I also tried downgrading sddm to stable (possible multiple issues...) and that did not fix it either.

I'll reboot again and take a photo of the screen when it crashes again. It has some messages but is highly garbled. Will post back.
Back to top
View user's profile Send private message
davidm
Guru
Guru


Joined: 26 Apr 2009
Posts: 557
Location: US

PostPosted: Tue Apr 18, 2017 6:23 pm    Post subject: Reply with quote

asturm,

Looks like it is possibily a nouveau issue. Another user is having similar problems here on Gentoo with the same card and with Plasma.

https://forums.gentoo.org/viewtopic-p-8057918.html
https://forums.gentoo.org/viewtopic-t-1062172.html


Last edited by davidm on Tue Apr 18, 2017 7:50 pm; edited 1 time in total
Back to top
View user's profile Send private message
davidm
Guru
Guru


Joined: 26 Apr 2009
Posts: 557
Location: US

PostPosted: Tue Apr 18, 2017 7:34 pm    Post subject: Reply with quote

I just tried downgrading mesa to 17.0.2. No luck.

One point which might be helpful in isolating this is that I haven't recently performed any kernel upgrades so it is likely not the nouveau code in the kernel. The other thread (see previous post for link) suggests it is X related. I haven't tried downgrading X yet.

Output from redirecting std error from terminal after doing 'startx'

Code:

xauth:  file /home/david/.serverauth.2343 does not exist


X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.9-gentoo x86_64 Gentoo
Current Operating System: Linux gentoot3400 4.9.9-gentoo #2 SMP Thu Mar 2 16:29:01 EST 2017 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.9-gentoo root=UUID=f7cba8d7-a8eb-4667-abbf-d70e145e3c77 ro dolvm rootfstype=ext4 init=/usr/lib/systemd/systemd
Build Date: 13 April 2017  04:32:59AM
 
Current version of pixman: 0.34.0
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Tue Apr 18 15:28:18 2017
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
resize called 1920 1080
Loading stage  "initial" 179
startkde: Starting up...
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
OpenGL vendor string:                   nouveau
OpenGL renderer string:                 Gallium 0.4 on NVC1
OpenGL version string:                  4.3 (Core Profile) Mesa 17.0.2
OpenGL shading language version string: 4.30
Driver:                                 Nouveau
GPU class:                              Unknown
OpenGL version:                         4.3
GLSL version:                           4.30
Mesa version:                           17.0.2
X server version:                       1.19.3
Linux kernel version:                   4.9.9
Requires strict binding:                yes
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
(EE)
(EE) Backtrace:
klauncher: Exiting on signal 1
xinit: connection to X server lost
Hangup
Service started, version:
XIO:  fatal IO error 6 (No such device or address) on X server ":1"
      after 195 requests (195 known processed) with 0 events remaining.
Could not connect to D-Bus server: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.

startkde: Shutting down...
kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__1) failed: : No such file or directory
Error: Can not contact kdeinit5!
xprop:  unable to open display ':1'
xprop:  unable to open display ':1'
startkde: Done.


dbus IS running:

Code:

 $ systemctl status dbus
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since Tue 2017-04-18 15:19:53 EDT; 13min ago
     Docs: man:dbus-daemon(1)
 Main PID: 1921 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─1921 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Apr 18 15:19:53 gentoot3400 dbus[1921]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Apr 18 15:19:53 gentoot3400 dbus[1921]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 18 15:19:53 gentoot3400 dbus[1921]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Apr 18 15:19:53 gentoot3400 dbus[1921]: [system] Successfully activated service 'org.freedesktop.hostname1'
Apr 18 15:19:53 gentoot3400 dbus[1921]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Apr 18 15:19:53 gentoot3400 dbus[1921]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Apr 18 15:20:15 gentoot3400 dbus[1921]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Apr 18 15:20:15 gentoot3400 dbus[1921]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Apr 18 15:20:15 gentoot3400 dbus[1921]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Apr 18 15:20:15 gentoot3400 dbus[1921]: [system] Successfully activated service 'org.freedesktop.UPower'
Back to top
View user's profile Send private message
davidm
Guru
Guru


Joined: 26 Apr 2009
Posts: 557
Location: US

PostPosted: Tue Apr 18, 2017 8:22 pm    Post subject: Reply with quote

Got it! :)

Downgrading to x11-libs/libdrm-2.4.75 results in a bootable system again with working KDE/Plasma.

Looks like we found a bug. So far two Gentoo users see this on a GeForce GT 730 when using nouveau. Does anyone else see it on different hardware?
Back to top
View user's profile Send private message
jfo
n00b
n00b


Joined: 07 Sep 2015
Posts: 37

PostPosted: Wed Apr 19, 2017 1:33 am    Post subject: Reply with quote

davidm -

Good work ! and thank you ! I will give a libdrm downgrade a try when I have a moment, but it is very likely that libdrm is the culprit.
That would explain why the proprietary nvidia driver works ... afaik it has no libdrm dependencies.

Here is what I see on my system

Code:

qlop -l | grep libdrm

Mon Dec  5 19:45:30 2016 >>> x11-libs/libdrm-2.4.74
Sat Jan 28 09:40:53 2017 >>> x11-libs/libdrm-2.4.75
Wed Mar 29 19:14:50 2017 >>> x11-libs/libdrm-2.4.76
Sat Apr   8 10:03:47 2017 >>> x11-libs/libdrm-2.4.77
Sun Apr  9 09:54:42 2017 >>> x11-libs/libdrm-2.4.79


So there were 3 successive updates about a week ago.
Back to top
View user's profile Send private message
davidm
Guru
Guru


Joined: 26 Apr 2009
Posts: 557
Location: US

PostPosted: Mon May 15, 2017 12:21 pm    Post subject: Reply with quote

Just wanted to note that upon upgrading to libdrm-2.4.80 the problem also goes away for me. So if someone masked the newer versions of libdrm as a workaround for this bug then they might want to remove the mask and give it a try again. :)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum