Bug 24699 - multi-DE install does not login to XFCE from GDM
Summary: multi-DE install does not login to XFCE from GDM
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Jani Välimaa
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-22 07:04 CEST by Ben McMonagle
Modified: 2021-01-29 08:24 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
install report (221.55 KB, application/x-xz)
2019-04-22 07:05 CEST, Ben McMonagle
Details
output of journalctl -a -b1 (234.98 KB, text/plain)
2019-04-22 07:20 CEST, Ben McMonagle
Details

Description Ben McMonagle 2019-04-22 07:04:36 CEST
Description of problem: unable to login to XFCE from GDM in a multi  DE install, however login is ok from sddm


Version-Release number of selected component (if applicable):
Mageia-7-beta3-i586.iso
DATE.txt: Fri Apr 12 01:10:58 CEST 2019

How reproducible:


Steps to Reproduce:
1.install all DE in a single install from above .iso
2.attempt to login to xfce from GDM
3.
Comment 1 Ben McMonagle 2019-04-22 07:05:52 CEST
Created attachment 10965 [details]
install report
Comment 2 Ben McMonagle 2019-04-22 07:20:29 CEST
Created attachment 10966 [details]
output of journalctl -a -b1
Comment 3 Lewis Smith 2019-04-22 09:48:38 CEST
I note this bug is for 32-bit again. I have changed the hardware designation, but
@Ben: please change it back if you disagree.

M7beta3 x64 Classic ISO real h/w Radeon video all desktops...
 GDM -> Xfce (with the iffy transition, bug#24134) works, I am using it to write this. 
@ Ben: I rather think that you already confirmed the same (all desktops launch from all DMs) for 64-bit?
Assigning this to Jani because bug#24134 is already with him, and this one also is an Xfce login problem.

CC: (none) => lewyssmith
Hardware: All => i586
Assignee: bugsquad => jani.valimaa

Comment 4 Martin Whitaker 2019-04-22 09:57:02 CEST
I observed this in VirtualBox, I think for both 32-bit and 64-bit installs. It only happened on the first boot after install, rebooting appeared to cure the problem. Go figure...

CC: (none) => mageia

Comment 5 Ben McMonagle 2021-01-29 08:24:52 CET
long fixed

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.