| Summary: | Wayland session does not launch using the login screen when using fish shell | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | pewkrause |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | nate, ngompa, plasma-bugs-null |
| Priority: | LO | Keywords: | wayland-only |
| Version First Reported In: | 5.23.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| URL: | https://github.com/sddm/sddm/pull/1360 | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=450639 | ||
| Latest Commit: | https://github.com/sddm/sddm/commit/bc5a18f34c0881929a6b2e5d3993971c4f692f4f | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
pewkrause
2021-12-03 18:38:36 UTC
That's odd: Nov 26 10:30:08 vision sddm[993]: Session started Nov 26 10:30:08 vision sddm-helper[2114]: [PAM] Closing session Nov 26 10:30:08 vision sddm-helper[2114]: pam_unix(sddm:session): session closed for user peter Nov 26 10:30:08 vision sddm-helper[2114]: [PAM] Ended. Nov 26 10:30:08 vision sddm[993]: Auth: sddm-helper exited with 1 It just means the session failed to run and SDDM worked perfectly in that case. Please include output of ~/.local/share/sddm/wayland-session.log and reopen (In reply to David Edmundson from comment #2) > It just means the session failed to run and SDDM worked perfectly in that > case. > > Please include output of ~/.local/share/sddm/wayland-session.log and reopen The log file only contains a single statement: '/tmp/xsess-env-gx5RNd: Zeile 39: PROFILEREAD: Schreibgeschützte Variable.' Couldn't find that file, so obviously it gets deleted automatically. I checked the file '/tmp/xsess-env-...' right after the wayland session login gets stuck and line 39 says EXPORT PROFILEREAD="true". Just found out, that the problem is caused by the fact that I am running 'fish' as my default shell. Maybe fish tries to read a different config file than bash does. Hope I can figure that out. Thanks for your support anyway! So it works when you're using bash? (In reply to Nate Graham from comment #6) > So it works when you're using bash? Yes, it does. Unfortunately, fish is not POSIX compatible and is, obviously, not meant to be used in the non-interactive login shell, as it does not read the .bashrc. I guess I need to add a few details: As of today, none of the shells seem to work anymore with launching a wayland session, although I am sure it was working with bash before. Also, logging in as a freh defined new user, I can easily switch between the shells using 'chsh -s' and the login persistantly works with bash and won't work using fish. So, it looks like there still is something else blocking the wayland login to my default user. I will check the journal output once again. The Wayland-related output of the system.journal after booting with bash reads: Dez 14 19:17:08 vision ksmserver-logout-greeter[2997]: The Wayland connection broke. Did the Wayland compositor die? Dez 14 19:17:08 vision kded5[2364]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Dez 14 19:17:08 vision kwalletd5[2637]: The Wayland connection broke. Did the Wayland compositor die? Dez 14 19:17:08 vision kded5[2364]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Dez 14 19:17:08 vision kactivitymanagerd[2397]: The Wayland connection broke. Did the Wayland compositor die? Dez 14 19:17:08 vision kded5[2364]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Dez 14 19:17:08 vision kaccess[2381]: The X11 connection broke (error 1). Did the X11 server die? Dez 14 19:17:08 vision pulseaudio[2462]: X11 I/O error exit handler called, preparing to tear down X11 modules Dez 14 19:17:08 vision pulseaudio[2462]: X11 I/O error handler called Dez 14 19:17:08 vision gmenudbusmenuproxy[2454]: The X11 connection broke (error 1). Did the X11 server die? Dez 14 19:17:08 vision xembedsniproxy[2385]: The X11 connection broke (error 1). Did the X11 server die? Dez 14 19:17:08 vision ksmserver[2367]: The X11 connection broke (error 1). Did the X11 server die? Dez 14 19:16:59 vision ksmserver-logout-greeter[2997]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dez 14 19:16:59 vision ksmserver-logout-greeter[2997]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dez 14 19:16:59 vision dbus-daemon[2299]: [session uid=1000 pid=2299] Successfully activated service 'org.kde.LogoutPrompt' Dez 14 19:16:59 vision dbus-daemon[2299]: [session uid=1000 pid=2299] Activating service name='org.kde.LogoutPrompt' requested by ':1.10' (uid=1000 pid=2367 co> Dez 14 19:16:25 vision plasmashell[2800]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop de> Dez 14 19:16:25 vision plasmashell[2800]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop de> Dez 14 19:16:25 vision plasmashell[2800]: trying to show an empty dialog Dez 14 19:16:25 vision plasmashell[2800]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Is there a Qt Issue? Sorry, guys, my fault. Last time I ran a Wayland session with bash being the default shell I disabled the laptop screen in order to use the second screen only and was not aware of the fact, that this would not apply to the X11 session. On the other hand the issue of Wayland not booting with fish being the default shell has not been fixed yet. I am currently using a workaround now by stting bash as the default shell and starting fish only the moment I start a terminal. This works fine for me. maybe it's mainly an issue of the fish shell. This is fixed in upstream SDDM and openSUSE will need to backport it: https://github.com/sddm/sddm/pull/1360 Awesome! |