Bug 24008 - cannot log in to plasma desktop from GDM greeter
Summary: cannot log in to plasma desktop from GDM greeter
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-15 09:38 CET by Ben McMonagle
Modified: 2019-02-04 23:17 CET (History)
3 users (show)

See Also:
Source RPM: gdm, plasma
CVE:
Status comment:

Attachments
journal.txt when attempting to login to Plasma from GDM (123.81 KB, text/plain)
2018-12-20 07:15 CET, Ben McMonagle 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ben McMonagle 2018-12-15 09:38:45 CET 
Description of problem: in a multi DE installation, I changed DM (using # drakdm) from sddm to gdm to check a network manager function in Gnome. logged out of gnome. choosing plasma (it is indicated as selected) presents gnome desktop. logging out to the greeter shows that plasma is still selected. logged back into gnome, changed DM back to sddm, logged out and then could log in to the pre-selected plasma desktop


Version-Release number of selected component (if applicable):


How reproducible: every time


Steps to Reproduce:
1. install at least gnome and plasma desktops into a single system
2. login to plasma, change DM to gdm and log out.
3. try to log back in to plasma
Marja Van Waes 2018-12-16 16:45:58 CET

Source RPM: gdm => gdm, plasma
CC: (none) => gnome, kde, marja11

Comment 1 Marja Van Waes 2018-12-19 08:35:37 CET 
Hi Ben,

Right before changing your DM, please switch to a VT (tty3 or so), log in, become root and run:

   journalctl -f 2>&1 | tee journal.txt

keep it running and reproduce the issue.

Then attach journal.txt to this report.

After that, reboot to see whether you can log in to Plasma after a reboot.

If you cannot, then run as root:

  journalctl -b > bootlog.txt

and attach bootlog.txt to this report.

Btw, isn't it possible to start Gnome from SDDM? I'm lagging behind and missed lots of information about which exact DMs (and DEs) can currently cope with Wayland and which can't, only know that Gnome needs it.

Keywords: (none) => NEEDINFO

Comment 2 Ben McMonagle 2018-12-20 07:14:36 CET 
(In reply to Marja Van Waes from comment #1)

> 
> Btw, isn't it possible to start Gnome from SDDM?

yes, but I was checking something in Gnome on Wayland
Comment 3 Ben McMonagle 2018-12-20 07:15:58 CET 
Created attachment 10586 [details]
journal.txt when attempting to login to Plasma from GDM
Comment 4 Marja Van Waes 2018-12-22 12:11:02 CET 
In attachment 10586 [details] there's a lot of 

> localhost.localdomain /usr/libexec/gdm-wayland-session[16329]: Activated
> service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1
> exited with status 1

don't know whether that's related


after that, there's

> Dec 20 19:07:04 localhost.localdomain /usr/libexec/gdm-wayland-session[16329]:
> Activating service name='org.a11y.Bus'
> Dec 20 19:07:04 localhost.localdomain /usr/libexec/gdm-wayland-session[16329]:
> Successfully activated service 'org.a11y.Bus'

so I assume Wayland is still used (instead of falling back to Xorg)

and later there's

> plasmashell[16396]: Could not connect to any X display.

I assume "X" here is Xorg and excludes Wayland?

First assigning to KDE team, to hear whether Plasma should work with Wayland. 

@ KDE team

It won't harm to read the log, I may have missed something. Please reassign to the Gnome maintainers if this should be fixed on their side.

Assignee: bugsquad => kde
Keywords: NEEDINFO => (none)

Comment 5 Ben McMonagle 2019-02-04 23:17:40 CET 
fixed for :

Mageia-7-beta2-x86_64
DATE.txt: Wed Jan 30 22:33:06 CET 2019

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.