After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 760613 - GDM is unable to start plasma-wayland sessions
GDM is unable to start plasma-wayland sessions
Status: RESOLVED NOTABUG
Product: gdm
Classification: Core
Component: general
3.18.x
Other All
: Normal major
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks: WaylandRelated
 
 
Reported: 2016-01-14 08:37 UTC by Christian Stadelmann
Modified: 2018-03-09 10:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Stadelmann 2016-01-14 08:37:29 UTC
Steps to reproduce:
1. run gdm (with wayland backend as configured by default on Fedora 23)
2. try to login into a plasma-wayland session

What happens:
Session immediately returns to GDM

What should happen:
Ordinary login to plasma-wayland sessions.

This issue is not present with plasma/X11 sessions. This issue is not present when starting `dbus-launch --exit-with-session /usr/bin/startplasmacompositor` manually from a tty. This is the `Exec=` value in /usr/share/wayland-sessions/plasmawayland.desktop. There is no crash at all, nothing to report by abrt/libreport.
Comment 1 Strangiato 2017-12-15 12:10:04 UTC
confirmed on Arch Linux, gdm 3.26.2.
Comment 2 bernie 2017-12-24 03:18:18 UTC
Also present on Fedora 27 (gdm-3.26.2.1-3.fc27, plasma-workspace-wayland-5.11.4-1.fc27.x86_64).

The user journal contains:

Dec 18 17:48:19 giskard /usr/libexec/gdm-wayland-session[14439]: startplasmacompositor:
Could not start D-Bus. Can you call qdbus?
Dec 18 17:48:19 giskard /usr/libexec/gdm-wayland-session[14439]: startplasmacompositor:
Starting up...

I endured qdbus is in the path, so the issue must be something else.
Comment 3 Andreas Linz 2018-02-13 09:30:52 UTC
I can confirm this problem on Arch Linux 4.15.2-2 with GDM 3.26.2.1-1, plasma-wayland-session 5.12.0-1 and plasma-desktop 5.12.0-1.
Comment 4 bernie 2018-03-05 12:08:45 UTC
Can one of the GDM maintainers please comment?
Comment 5 Ray Strode [halfline] 2018-03-05 13:43:26 UTC
just a guess...

Exec=dbus-launch --exit-with-session

seems wrong since the X server isn't started until Xwayland is started and that happens somewhere down the chain of calls from startplasmacompositor.  --exit-with-session means "exit when the X server goes away" but there's no X server yet.

also gdm starts dbus for the session, so it should be wholly unnecessary.

Maybe try:

Exec=/usr/bin/startplasmacompositor

in the file instead?

Anyway, I don't think this is a GDM problem.
Comment 6 Christian Stadelmann 2018-03-06 21:51:58 UTC
(In reply to Ray Strode [halfline] from comment #5)
> just a guess...
> 
> Exec=dbus-launch --exit-with-session
> 
> seems wrong since the X server isn't started until Xwayland is started and
> that happens somewhere down the chain of calls from startplasmacompositor. 
> --exit-with-session means "exit when the X server goes away" but there's no
> X server yet.
> 
> also gdm starts dbus for the session, so it should be wholly unnecessary.
> 
> Maybe try:
> 
> Exec=/usr/bin/startplasmacompositor
> 
> in the file instead?
> 
> Anyway, I don't think this is a GDM problem.

You were right about this. This is not a bug in GDM but in the .desktop file. Thank you very much for looking into it!