Bug 445735 - wayland login results in black screen with mouse
Summary: wayland login results in black screen with mouse
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.23.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-19 08:04 UTC by Kwon-Young Choi
Modified: 2022-01-11 10:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kwon-Young Choi 2021-11-19 08:04:31 UTC
SUMMARY

Hello,
I've just upgraded from plasma 22 to plasma 23 in fedora 35 and when I try to login with wayland, I just obtain a black screen with my mouse still responsive.
I've also noticed some blue effect on the corners of the screen.


STEPS TO REPRODUCE
1. login in sddm with wayland

OBSERVED RESULT

Immediately shown black screen with mouse still moving.

EXPECTED RESULT

normal plasma desktop is shown

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 35
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.14.17-301.fc35.x86_64 (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i9-10885H CPU @ 2.40GHz
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

ADDITIONAL INFORMATION

My laptop is a dell precision with a 4k screen, which I normally set to 1920p in x11 because I can't specify different scaling factor for different monitors.
Comment 1 Kwon-Young Choi 2021-11-19 08:51:23 UTC
tried with a freshly created user, results in the same problem with only black screen and mouse
Comment 2 Kwon-Young Choi 2021-11-22 16:07:57 UTC
updated to:

Operating System: Fedora Linux 35
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.14.18-300.fc35.x86_64 (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i9-10885H CPU @ 2.40GHz
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

Still the same problem happens when login to wayland with a freshly created user
Comment 3 Zamundaaa 2021-11-23 11:40:31 UTC
Sounds like KWin works fine but plasmashell doesn't start. Can you make any windows appear, for example by pressing ctrl+alt+t for Konsole?
Comment 4 Kwon-Young Choi 2021-11-23 11:58:17 UTC
Yes ! Doing ctrl-alt-t opens konsole. Don't know why I haven't thouht of doing that
Comment 5 Kwon-Young Choi 2021-11-23 11:59:47 UTC
Here is the output of trying to launch plasmahsell:

```
☧~ plasmashell --replace
kf.plasma.quick: Applet preload policy set to 1
qt.svg: <input>:303:258: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:303:463: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:303:659: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:303:913: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:303:1049: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:303:1251: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:303:1453: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:303:1631: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:303:1739: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:303:1980: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:303:2223: Could not add child element to parent element because the types are incorrect.
trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height"
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
[destroyed object]: error 7: importing the supplied dmabufs failed
The Wayland connection experienced a fatal error: Protocol error
```
Comment 6 Kwon-Young Choi 2021-11-23 12:06:26 UTC
From the error message, I've found this bug: https://github.com/NVIDIA/egl-wayland/issues/40

My laptop has an two card, intel and nvidia. By default, I believe everything should be using the intel card, no ?
Comment 7 Kwon-Young Choi 2021-11-23 12:11:55 UTC
Maybe this will also help
```
☧~ dnf info egl-wayland 

Installed Packages
Name         : egl-wayland
Version      : 1.1.9
Release      : 2.fc35
Architecture : i686
Size         : 66 k
Source       : egl-wayland-1.1.9-2.fc35.src.rpm
Repository   : @System
From repo    : updates
Summary      : Wayland EGL External Platform library
URL          : https://github.com/NVIDIA/egl-wayland
License      : MIT
Description  : Wayland EGL External Platform library
```
Comment 8 Kwon-Young Choi 2021-11-23 12:29:42 UTC
I've tried to downgrade egl-wayland as suggested in the previously linked bug report and got a working plasmashell session.
I don't really understand if it is nvidia or qt that should be patched but I'll wait for more updates to come :)
Comment 9 Kwon-Young Choi 2021-12-13 08:26:53 UTC
Hello,

I have upgraded to:

Operating System: Fedora Linux 35
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.6-200.fc35.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i9-10885H CPU @ 2.40GHz
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

And the wayland session and plasmashell is starting correctly.
I think we can now close this bug.
However, I have noticed a very heavy stuttering in the settings app (I'll try to open a new bug for that).
The rest of the desktop seems normal.