Bug 355843

Summary:	plasma hangs at kdeinit5 when starting a wayland session
Product:	[Plasma] plasmashell	Reporter:	Patrick Auernig <patrick.auernig>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	anakin.cs, bshah, darkbasic, jsardid, kde, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.4.95
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	the process tree .wayland-errors

Description Patrick Auernig 2015-11-24 14:50:10 UTC

When starting a wayland plasma session via sddm the screen goes black for some seconds, then the mouse cursor appears followed by the qml loading screen.
The progress bar of the loading screen is not moving at all (or is not visible).
After some time (maybe 30 seconds, could be longer), the loading screen disappears and the user is left with a black screen.

When I checked the running processes in another tty I saw that kdeinit5 forked multiple subprocesses and there was one zombie process named "start_kdeinit_w" (also as subprocess of kdeinit5).

According to the .wayland-errors logfile there is also a problem connecting to systemd.

I'm using the latest Archlinux packages from the kde-unstable repository
and Intel integrated graphics (4400).

Reproducible: Always

Steps to Reproduce:
1. Start Plasma (wayland) with sddm
2. Wait for the login screen to disappear
3. Find yourself before a black screen


Expected Results:  
The plasma desktop is displayed

Comment 1 Patrick Auernig 2015-11-24 14:50:39 UTC

Created attachment 95699 [details]
the process tree

Comment 2 Patrick Auernig 2015-11-24 14:51:17 UTC

Created attachment 95700 [details]
.wayland-errors

Comment 3 Kai Uwe Broulik 2015-11-24 15:51:58 UTC

Looks like the OOM protection thing.

Comment 4 AnAkkk 2015-11-24 20:57:16 UTC

Why is Plasma 5.5 shipped with a "Plasma on Wayland" session and the OOM thing turned on if it's known to make it unusable?

Comment 5 Patrick Auernig 2015-12-10 13:37:05 UTC

It works when using the kinit-nooom package (https://aur4.archlinux.org/packages/kinit-nooom) from the AUR.

It seems that this bug is a Duplicate of https://bugs.kde.org/show_bug.cgi?id=356175

*** This bug has been marked as a duplicate of bug 356175 ***

Comment 6 AnAkkk 2015-12-10 13:38:19 UTC

This is not a duplicate. In the other bug it says that he's already using kinit-noom and has a different issue.

Comment 7 avlas 2016-07-11 18:53:12 UTC

I solved an issue in my system that seems like this bug to me by installing qtwayland5 and its dependencies libqt5waylandclient5 and libqt5waylandcompositor5 (using neon). Hope it helps to others...