FS#47355 - [kinit] startplasmacompositor - "/usr/lib/startplasma" - hangs at "start_kdeinit_wrapper"

Attached to Project: Arch Linux
Opened by James (thx1138) - Sunday, 13 December 2015, 01:34 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 15 December 2015, 18:45 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Please see
https://bugs.kde.org/show_bug.cgi?id=356580

"startplasmacompositor" from the new plasma-workspace 5.5.0-4, which creates a Wayland-based KDE session, cannot be run without disabling KDEINIT_OOM_PROTECT, due to an unresolved bug in src/kdeinit/kinit.cpp, src/start_kdeinit/start_kdeinit.c, or src/start_kdeinit/start_kdeinit_wrapper.c. Nobody has tracked-down this bug yet.

The "quick fix" is to manually unset KDEINIT_OOM_PROTECT in "kinit-5.17.0/src/CMakeLists.txt", changing
set(KDEINIT_OOM_PROTECT 1)
to
set(KDEINIT_OOM_PROTECT)
until the OOM problem, triggered with start_kdeinit_wrapper, can be resolved.

Without modifying the kinit package, for now, kwin_wayland and startplasmacompositor are not usable.
This task depends upon

Closed by  Antonio Rojas (arojas)
Tuesday, 15 December 2015, 18:45 GMT
Reason for closing:  Fixed
Additional comments about closing:  plasma-workspace 5.5.1
Comment by Antonio Rojas (arojas) - Sunday, 13 December 2015, 07:53 GMT
There's a kinit-nooom package in AUR as a workaround for this. Note that you should be able to start a Wayland session as long as there isn't an X server running already.
Comment by James (thx1138) - Sunday, 13 December 2015, 16:07 GMT
Thanks for that. I see that package is hard-coded for kinit-5.16.0, not 5.17. AUR users should figure this out, but really, the question is, should kinit-5.17.0 "break" some element of the plasma-workspace-5.5.0 and kwin-5.5.0 packages, in particular "startplasmacompositor"? Yes, this is an "upstream" issue. I consider it "sloppy" that KDE has not addressed this issue after knowing about it for six months - and then making a new realease. But still, is the "Arch Experience" to be "works out of the box" or "cut to fit, paint to match"? Hmm - I really could see people arguing that either way...
Comment by Antonio Rojas (arojas) - Sunday, 13 December 2015, 17:53 GMT
Given that the Plasma wayland session is currently just a technical preview and not really usable, I think it's not a big problem that users have to fiddle with packages in order to use it. In any case there's not much we can do until upstream figures out what the problem is.
Comment by Antonio Rojas (arojas) - Tuesday, 15 December 2015, 18:45 GMT
Plasma wayland sessions should work now in 5.5.1

Loading...