[Bug 987900] New: selecting Wayland with Plasma 5 (plasma5-session-wayland) from sddm produces black screen and then returns to login screen
http://bugzilla.opensuse.org/show_bug.cgi?id=987900 Bug ID: 987900 Summary: selecting Wayland with Plasma 5 (plasma5-session-wayland) from sddm produces black screen and then returns to login screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: rainer.klier@gmx.at QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 683225 --> http://bugzilla.opensuse.org/attachment.cgi?id=683225&action=edit journald log with unsuccessfull wayland session i am using openSUSE x86_64 Tumbleweed on a notebook with a geforce gtx 765m with the latest proprietary nvidia driver 367.27. Xorg is working fine without problems. today i updated to latest kde framework 5.7.0, and had the idea of trying out wayland, as i read that kde framework 5.7.0 should at least support wayland in some way. but it does not work at all. if i select the Wayland plasma session from the wayland sessions from sddm (the one which comes from the config file /usr/share/wayland-sessions/plasmawayland.desktop which comes from the package plasma5-session-wayland) and trying to login, i only see a black screen for some seconds, and then i am back at the sddm greetings screen. i have attached the part of journald logs where the unsuccessfull login happens: at 17:18:04 you can see the attempt to start new session using /usr/share/wayland-sessions/plasmawayland.desktop. at about 17:18:11 you can see that it was not successfull and then i selected the normal Xorg based session /usr/share/xsessions/kde-plasma.desktop and loged in successfully. what did i wrong? why does it not even start the session? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
Rainer Klier
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
http://bugzilla.opensuse.org/show_bug.cgi?id=987900#c1
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
http://bugzilla.opensuse.org/show_bug.cgi?id=987900#c2
--- Comment #2 from Rainer Klier
Please don't change the priority, this is for the developers/maintainers to prioritize the bugs they are working on.
oh, sorry about that. i didn't know.
Regarding your problem: I don't think Plasma/Wayland can work with the nvidia driver.
:-(
NVidia did add Wayland support to their driver a few months ago, but AFAICT from Google it seems to only work with Weston as compositor and requires special patches to Weston (provided by NVidia).
ah, ok.
If you don't want to uninstall nvidia, you can use a Krypton LiveCD instead: http://download.opensuse.org/repositories/KDE:/Medias/images/iso/ See also: https://www.dennogumi.org/2016/06/two-in-one/
thanks for the hints.
In any case, Plasma/Wayland is still more or less experimental and unfinished.
yes, this i knew.
I don't think we (openSUSE) really accept bug reports about it.
ok.
It should start though, and did here when I last tried (on Krypton) if the graphics driver supports it.
sorry, but i didn't really understand this last sentence. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
http://bugzilla.opensuse.org/show_bug.cgi?id=987900#c3
--- Comment #3 from Wolfgang Bauer
(In reply to Wolfgang Bauer from comment #1)
It should start though, and did here when I last tried (on Krypton) if the graphics driver supports it.
sorry, but i didn't really understand this last sentence.
I meant that it should basically work if you use a graphics driver that has proper Wayland support, like radeon, intel, or nouveau. Even fbdev or vesa should do, but note that having nvidia installed breaks Mesa's OpenGL support, (including its software renderer), so Plasma won't start at all in that case. You'd need to uninstall nvidia, as mentioned. There may be other problems/missing features or even crashes (might depend on the actual driver in use), but you should at least be able to login. I just booted Krypton on my radeon system here and it worked (it even felt more stable than a few weeks ago when I last tried). I tried on an intel system in the past as well, and it started there as well. As Krypton is a LiveCD based on Tumbleweed (with the latest unstable KDE packages though), it should work on Tumbleweed as well though I cannot explicitly try that at the moment. There's also a "stable" variant of Kryption btw, which comes with Plasma 5.7.0 (again on top of Tumbleweed). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
http://bugzilla.opensuse.org/show_bug.cgi?id=987900#c4
--- Comment #4 from Rainer Klier
(In reply to Rainer Klier from comment #2)
(In reply to Wolfgang Bauer from comment #1)
It should start though, and did here when I last tried (on Krypton) if the graphics driver supports it.
sorry, but i didn't really understand this last sentence.
I meant that it should basically work if you use a graphics driver that has proper Wayland support, like radeon, intel, or nouveau. Even fbdev or vesa should do, but note that having nvidia installed breaks Mesa's OpenGL support, (including its software renderer), so Plasma won't start at all in that case. You'd need to uninstall nvidia, as mentioned.
ok, verstanden.
There may be other problems/missing features or even crashes (might depend on the actual driver in use), but you should at least be able to login.
ok.
As Krypton is a LiveCD based on Tumbleweed (with the latest unstable KDE packages though), it should work on Tumbleweed as well though I cannot explicitly try that at the moment.
There's also a "stable" variant of Kryption btw, which comes with Plasma 5.7.0 (again on top of Tumbleweed).
ok, danke für die aufklärung. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
http://bugzilla.opensuse.org/show_bug.cgi?id=987900#c5
Sergio Lindo Mansilla
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
http://bugzilla.opensuse.org/show_bug.cgi?id=987900#c6
--- Comment #6 from Wolfgang Bauer
Reproducible on snapshot 20190201.
I get the same error message in journal as the attached log:
And why do you think it is the same problem 3 years afterwards? The original reporter used the proprietary nvidia driver which doesn't support Wayland. Is that your case too? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
http://bugzilla.opensuse.org/show_bug.cgi?id=987900#c7
--- Comment #7 from Sergio Lindo Mansilla
And why do you think it is the same problem 3 years afterwards?
Only because they have the same symptoms.
The original reporter used the proprietary nvidia driver which doesn't support Wayland. Is that your case too?
No, it is happening on a qemu virtual machine using this qcow2: https://openqa.opensuse.org/tests/844617/asset/hdd/opensuse-Tumbleweed-x86_6... Should I open a new ticket, then? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
http://bugzilla.opensuse.org/show_bug.cgi?id=987900#c8
Sergio Lindo Mansilla
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
http://bugzilla.opensuse.org/show_bug.cgi?id=987900#c9
--- Comment #9 from Wolfgang Bauer
New ticket created: https://bugzilla.opensuse.org/show_bug.cgi?id=1124294
Thank you, that's probably the best in a case like this. Btw, regarding the proprietary nvidia driver (i.e. the original problem here), work finally has started (by NVIDIA) to add proper support for it in kwin_wayland: https://marc.info/?l=kwin&m=154205907402787&w=3 https://phabricator.kde.org/D18570 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=987900
http://bugzilla.opensuse.org/show_bug.cgi?id=987900#c10
--- Comment #10 from Rainer Klier
Btw, regarding the proprietary nvidia driver (i.e. the original problem here), work finally has started (by NVIDIA) to add proper support for it in
great! nice! i am looking forward testing it, when it is available. thanks for the info wolfgang. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com