Bug 412152 - [Wayland] cannot start session on anything other than proprietary NVIDIA drivers
Summary: [Wayland] cannot start session on anything other than proprietary NVIDIA drivers
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-wayland (show other bugs)
Version: 5.16.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2019-09-21 09:58 UTC by Seqularise
Modified: 2019-10-23 06:49 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Wayland-session log (12.00 KB, text/x-log)
2019-09-24 06:45 UTC, Michael D
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Seqularise 2019-09-21 09:58:51 UTC
SUMMARY
When i try to start session from sddm it just goes to black screen.
startplasma-wayland from tty gives me this:

No backend specified through command line argument, trying auto resolution
kglobalaccel-runtime: Failed to register service org.kde.kglobalaccel
"/usr/bin/kwin_wayland" ("--xwayland", "--libinput", "--exit-with-session=/usr/lib/startplasma-waylandsession") exited with code 11
startplasmacompositor: Shutting down...
startplasmacompositor: Done.



SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version:
Comment 1 Seqularise 2019-09-23 14:30:01 UTC
I tried it in openSUSE Krypton, same issue.
Maybe this is hardware related? i have a HD 6850, maybe kwin have not been tested with old radeon drivers
Comment 2 Michael D 2019-09-24 06:45:23 UTC
I have Intel hardware (Kabylake) and get the same black screen. The cursor is visible but I can't see windows. If I press ctrl+alt+delete and enter, I can log out, so the session seems to be working but nothing is visible.

I have an external display hooked up to my laptop through hdmi. I'm attaching my wayland-session.log.
Comment 3 Michael D 2019-09-24 06:45:42 UTC
Created attachment 122830 [details]
Wayland-session log
Comment 4 Pawel 2019-10-10 13:29:03 UTC
I don't know, that my problem with Plasma-Wayland session is the same, but my system is going to black screen, too with Plasma 5.17 beta.
System - Arch Linux
GPU - AMD GCN 2nd with amdgpu (radeon.cik_support=0 amdgpu.cik_support=1 applied for kernel).
Plasma 5.16.5 starts well.
Comment 5 David Edmundson 2019-10-10 13:49:56 UTC
try with 


export `dbus-launch`

before starting kwin
Comment 6 Pawel 2019-10-10 15:23:52 UTC
(In reply to David Edmundson from comment #5)
> try with 
> 
> 
> export `dbus-launch`
> 
> before starting kwin

If I should change line Exec= in /usr/share/wayland-sessions/plasmawayland.desktop to Exec=dbus-launch /usr/bin/startplasma-wayland then it doesn't works. The main difference is that after I choose plasma-wayland in SDDM it starts and return to login screen.
Comment 7 Seqularise 2019-10-10 16:07:43 UTC
with export `dbus-launch`

dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files
Warning: QT_AUTO_SCREEN_SCALE_FACTOR is deprecated. Instead use:
   QT_ENABLE_HIGHDPI_SCALING to enable platform plugin controlled per-screen factors.
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
QCommandLineParser: already having an option named "v"
No backend specified through command line argument, trying auto resolution
Icon theme "gnome" not found.
"/usr/bin/kwin_wayland" ("--xwayland", "--libinput", "--exit-with-session=/usr/lib/startplasma-waylandsession") exited with code 11
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
Comment 8 Pawel 2019-10-11 08:26:18 UTC
Maybe it will be useful. It's from gdb when I try to start kwin_wayland in embedded mode (in X11 Plasma session):

Starting program: /usr/bin/kwin_wayland 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7f884722a700 (LWP 10432)]
No backend specified through command line argument, trying auto resolution
[New Thread 0x7f88469ac700 (LWP 10433)]
[New Thread 0x7f8844993700 (LWP 10434)]
[New Thread 0x7f883e9ee700 (LWP 10435)]
[New Thread 0x7f883e1ed700 (LWP 10436)]
[New Thread 0x7f883d9ec700 (LWP 10437)]
[New Thread 0x7f883d1eb700 (LWP 10438)]
[New Thread 0x7f883c9ea700 (LWP 10439)]
[New Thread 0x7f88331c0700 (LWP 10440)]
[New Thread 0x7f88325bf700 (LWP 10441)]
OpenGL vendor string:                   X.Org
OpenGL renderer string:                 AMD KABINI (DRM 3.33.0, 5.3.5-1-pb, LLVM 9.0.0)
OpenGL version string:                  4.5 (Core Profile) Mesa 19.2.1
OpenGL shading language version string: 4.50
Driver:                                 RadeonSI
GPU class:                              Sea Islands
OpenGL version:                         4.5
GLSL version:                           4.50
Mesa version:                           19.2.1
Linux kernel version:                   5.3.5
Requires strict binding:                no
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
[New Thread 0x7f8831dbe700 (LWP 10442)]
[New Thread 0x7f88315bd700 (LWP 10443)]
[New Thread 0x7f880bfff700 (LWP 10444)]

Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault.
0x00007f88506b5ec0 in KWayland::Client::Compositor::operator wl_compositor*() ()
   from /usr/lib/libKF5WaylandClient.so.5

I'll try with KF5.63rc but I have to build it.
Comment 9 Pawel 2019-10-11 14:13:45 UTC
There's the same error with KF 5.63rc
Comment 10 Pawel 2019-10-13 17:26:41 UTC
And on 5.63, too.
Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault.
0x00007fe0ef5ebec0 in KWayland::Client::Compositor::operator wl_compositor*() ()
   from /usr/lib/libKF5WaylandClient.so.5
Comment 11 Pawel 2019-10-14 09:05:22 UTC
And maybe this will be useful:
1. There's info on bugs.archlinux.org, then KWin has missing qt5-script dependency. So I've build it with it (it's in my system, already), but without success. KWin_wayland doesn't start.
2. When I try to start i.e. gwenview in wayland embeded session, I noticed such information: "This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem."
And info from gdb:
"Program received signal SIGABRT, Aborted.
0x00007ffff5cc0f25 in raise () from /usr/lib/libc.so.6"
3. I've just installed weston, and I can open session with it.
4. I've even build (on Qt 5.14b1) another Qt5 Wayland based DE - Liri and it cannot start session, too. I don't know that it's Qt5 or Liri related, because it's still WIP and sometimes it starts, sometimes not.
5. Output from gdb with new building KWin is the same as previous:
"Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault.
0x00007f14f98a6ec0 in KWayland::Client::Compositor::operator wl_compositor*() ()
   from /usr/lib/libKF5WaylandClient.so.5"
6. I know, that there's at least one person who can run kwin_wayland (5.16.90 on Arch Linux) session without any problem.
7. I try to run wayland session on my personal config of Plasma and on completly clear new user session and the result is the same. Only black screen (with cursor only).
8. The problem occurs with Qt5.13.x, too. I haven't any problem with starting Plasma Wayland session on Plasma 5.16.x even with KF5.63rc (and of course on previous verision of KF5, too).

Please ask about any informations interesting you.
Comment 12 Pawel 2019-10-15 18:48:05 UTC
There isn't any progress with 5.17.0. Still only black screen.
Comment 13 alggwp 2019-10-15 21:23:27 UTC
I have the same problem also on Arch.
I'd like to add that it works fine with the proprietary nvidia drivers but fails with the nouveau drivers.

 I have the exact same problems as described here so appearently it is not caused by the drivers themselves (since I am on Nvidia, others Intel here) but we all get the exact same error messages (""/usr/bin/kwin_wayland" ("--xwayland", "--libinput", "--exit-with-session=/usr/lib/startplasma-waylandsession") exited with code 11")
Comment 14 Alexandre Pereira 2019-10-18 01:38:49 UTC
strangely i have this bug if i boot with amdgpu_dc=0.
with amdgpu_dc=1, kwin loads the wayland session.

can anyone test ?
Comment 15 Pawel 2019-10-18 05:03:47 UTC
(In reply to Alexandre Pereira from comment #14)
> strangely i have this bug if i boot with amdgpu_dc=0.
> with amdgpu_dc=1, kwin loads the wayland session.
> 
> can anyone test ?

I tested on two kernels (my own, and linux-zen) with both: amdgpu_dc=0 and amdgpu_dc=1 but without any success. Still only black screen.
Comment 16 alggwp 2019-10-19 04:48:49 UTC
So I spun up an additional machine with Void Linux and there I have the same exact problem. I get the same exact error message and the same exact behaviour shown so it's definitely caused by Plasma.
Comment 17 alggwp 2019-10-19 04:51:59 UTC
I changed the title since it seems obvious the error is on Plasmas side. Everyone here is getting the exact same error messages while some are using AMD, others Intel and others Nouveau.
Comment 18 Alexandre Pereira 2019-10-19 13:57:50 UTC
Pawel and everyone, sorry!!! made a typoo, its not amdgpu_dc=1 , its amdgpu.dc=1.

for reference, here is my grub kernel boot parameters:

radeon.cik_support=0 radeon.si_support=0 amdgpu.dpm=1 amdgpu.dc=1 amdgpu.si_support=1 amdgpu.cik_support=1
Comment 19 Pawel 2019-10-19 14:23:21 UTC
(In reply to Alexandre Pereira from comment #18)
> Pawel and everyone, sorry!!! made a typoo, its not amdgpu_dc=1 , its
> amdgpu.dc=1.
> 
> for reference, here is my grub kernel boot parameters:
> 
> radeon.cik_support=0 radeon.si_support=0 amdgpu.dpm=1 amdgpu.dc=1
> amdgpu.si_support=1 amdgpu.cik_support=1

Yes, I can confirm - it works for me, too.
Comment 20 alggwp 2019-10-19 18:10:09 UTC
Well then the missing question is what is up with the people not having an AMD gpu.
Comment 21 Pawel 2019-10-20 07:14:03 UTC
Yes, maybe it's a workaround for Plasma Wayland session on AMDGPU, but with this parameters my Plasma (rather applications) are unstable now. I know, that amdgpu.dc=1 is rather not for my GCN2 GPU. With many applications crash often. There're many freezes of Plasma and applications. I cannot see mails in KMail etc.
Comment 22 Pawel 2019-10-20 07:20:09 UTC
Sorry, I forgot. Comment above is about Plasma Wayland session.
Comment 23 Seqularise 2019-10-22 10:28:03 UTC
i was able to start session with kwin from master, thanks to D24829 :)
Comment 24 alggwp 2019-10-22 18:39:19 UTC
Can confirm upstream kwin starts. It crashes nonetheless but at least it starts now so that's another bug meaning this bug is probably fixed.
Comment 25 Pawel 2019-10-23 05:37:48 UTC
I can confirm too. With 5.17.1 Wayland session starts, but there're many other bugs like high CPU usage, unstable applications (maybe it's that high CPU usage related), and I cannot logout. Everything looks like it's subject for another thread.
Comment 26 Méven Car 2019-10-23 06:49:12 UTC
https://phabricator.kde.org/D24829 and KWin 5.17.1 will fix this according to bug reporters.
Marking as resolved.

Regarding high CPU usage, this may relate to https://bugs.kde.org/show_bug.cgi?id=413305 "[Wayland] 100% cpu usage, system lagging, radeon amdgpu"