FS#56138 - [plasma-wayland-session] Plasma Wayland session does not start correctly

Attached to Project: Arch Linux
Opened by Kirill Bobyrev (omtcyfz) - Friday, 27 October 2017, 13:11 GMT
Last edited by Antonio Rojas (arojas) - Monday, 30 October 2017, 21:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: plasma-wayland-session does not seem to launch properly. When I boot into plasma-wayland-session, I only get the black screen, my mouse is frozen and can not be moved. Since I followed all the instructions on Arch Wiki known to me, I believe it might affect the others.

Additional info:
* Version: 5.11.2-1
* I am using Nouveau open-source drivers as recommended by the KDE wiki entry: https://wiki.archlinux.org/index.php/KDE#Starting_Plasma
* I have two monitors if that's important. One monitor loads the wallpaper, the other one remains black.
* Trying to enter TTY(1 | 2 | ...) does result in anything.

Steps to reproduce:

* Install plasma-wayland-session
* Boot into SDDM
* Login to Plasma (Wayland) session
This task depends upon

Closed by  Antonio Rojas (arojas)
Monday, 30 October 2017, 21:03 GMT
Reason for closing:  Upstream
Comment by Johan Klokkhammer Helsing (johanhelsing) - Friday, 27 October 2017, 13:14 GMT
What happens if you run startplasmacompositor directly in a tty?
Comment by Kirill Bobyrev (omtcyfz) - Friday, 27 October 2017, 14:41 GMT
If I run

$ startplasmacompositor

I enter a working plasma session, which acts really weird, though. As I mentioned, I have two monitors, these are mirrored in the starting session, but windows seem to appear on the second screen while being clickable but not visible, e.g. I can drag a window from the second screen to the first one if I am able to guess where the window bar is and drag it...
Comment by Antonio Rojas (arojas) - Monday, 30 October 2017, 21:03 GMT
Not a packaging problem, please report this upstream to KDE giving as many details as possible (logs, error, GPU details). Nothing Arch can do about this.

Loading...