Bug 472459 - No desktop if user has a non bash shell
Summary: No desktop if user has a non bash shell
Status: RESOLVED UPSTREAM
Alias: None
Product: plasma-wayland-protocols
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 1.10.0
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-21 08:20 UTC by Rafael Linux User
Modified: 2023-08-05 16:54 UTC (History)
2 users (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 Rafael Linux User 2023-07-21 08:20:33 UTC
SUMMARY

Recently, I decided to give a try to Wayland, so I selected "Wayland" in SSDM desktop switcher and click "Accept" to log in, but instead Plasma desktop, a black screen was all I got. After a lot of googling around, someone mentioned that something similar had happened to him and found out that it was related to the shell I had installed. Indeed, I had the fish-shell l installed and, after uninstalling it and rebooting, I was able to get past the black screen. So I didn't try to install again fish-shell.

Yesterday, another openSUSE user, related same issue en an openSUSE forum. He had installed fish-shell too and after uninstall it, issue with Wayland disapeared. Someone told us that is POSIX related, but as users, we only can uninstall fish-shell.

STEPS TO REPRODUCE
1. Install "fish-shell" shell
2. Reboot
3. Try to login using Wayland to Plasma

OBSERVED RESULT
Black screen

EXPECTED RESULT
To show Plasma desktop after login

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20230718
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.3-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2

ADDITIONAL INFORMATION
Here are some related links, but sure there are more.
https://forums.opensuse.org/t/wayland-session-not-working/167751/9
https://www.reddit.com/r/openSUSE/comments/vm4a3b/plasma_wayland_session_stopped_working_after/

Thread that I opened on the fish-shell site to report the issue
https://github.com/fish-shell/fish-shell/issues/9906

And this is a related issue in KDE bugs (yet solved):
https://bugs.kde.org/show_bug.cgi?id=87671
https://github.com/fish-shell/fish-shell/issues/9906
Comment 1 Nicolas Fella 2023-08-05 16:54:53 UTC
This is an SDDM "issue". See https://github.com/sddm/sddm/issues/1592 / https://github.com/sddm/sddm/issues/1391

But also it's kind of not an SDDM issue. fish is not a POSIX compliant shell. Using a non-POSIX compliant login shell is likely to cause issues like this