Bug 19568

Summary: When trying to login to Cinnamon, MATE or GNOME Classic, you get automatically logged out, but GNOME with Wayland works
Product: Mageia Reporter: Kristoffer Grundström <lovaren>
Component: RPM PackagesAssignee: GNOME maintainers <gnome>
Status: RESOLVED WORKSFORME QA Contact:
Severity: major    
Priority: Normal CC: lovaren, marja11, olav, thierry.vignaud
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: gdm CVE:
Status comment:
Attachments: Here's the ouput from journalctl -a
install.log
A replay of my installation
stage1.log
report.bug.xz

Description Kristoffer Grundström 2016-10-12 04:06:26 CEST 
Description of problem: I created a VM of Mageia 6 (Cauldron) and as I booted for the first time I got to the login screen of GDM, but as soon as I tried to login to MATE, Cinnamon or GNOME or GNOME Classic I got logged out almost instantly. However if I choose to login to GNOME with Wayland it works.

I checked the content of /etc/sysconfig/desktop using nano and there was only one row stating:

DISPLAYMANAGER=gdm

I installed lightdm and sddm and tried switching from gdm to any of thoose, but that ended up with this result when rebooting: http://www.ladda-upp.se/bilder/almbldjmigtewg/

I also compared with the content in /etc/sysconfig/desktop for Mageia 5 and I saw 2 rows like this:

DISPLAYMANAGER=kdm
DESKTOP=KDE4

so I added DESKTOP=Cinnamon to my VM and rebooted, but got the same crash once again.

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

How reproducible: All the time.

Steps to Reproduce:
1. Download the full DVD iso for Mageia 6 (Cauldron). 
2. Create a new VM in Virtualbox.
3. Start the installation of Mageia 6 (Cauldron).
4. Choose MATE, GNOME and Cinnamon as Desktop Environments.
5. Reboot.
6. Once you get to the login screen for GDM enter your user password and press Enter.
7. Voila! You'll be automatically logged out instantly.
8. Change to login to any of the other Desktop Environments and try to login.
9. Voila! Same thing will happen again.
Comment 1 Kristoffer Grundström 2016-10-12 04:10:38 CEST 
Created attachment 8516 [details]
Here's the ouput from journalctl -a

CC: (none) => hamnisdude

Comment 2 Kristoffer Grundström 2016-10-12 04:11:32 CEST 
Created attachment 8517 [details]
install.log
Comment 3 Kristoffer Grundström 2016-10-12 04:12:10 CEST 
Created attachment 8518 [details]
A replay of my installation
Comment 4 Kristoffer Grundström 2016-10-12 04:12:34 CEST 
Created attachment 8519 [details]
stage1.log
Comment 5 Kristoffer Grundström 2016-10-12 05:07:26 CEST 
Created attachment 8520 [details]
report.bug.xz
Comment 6 Kristoffer Grundström 2016-10-12 05:10:01 CEST 
To uncomment WaylandEnable=false in /etc/X11/gdm/custom.conf doesn't give me a working login window. The kernel stops before.
Comment 7 Kristoffer Grundström 2016-10-12 05:24:47 CEST 
I made a misstake when adding the proper Cauldron medias after the first reboot so I fixed my typo now and got over 900 updates to install. I'll check if any of those solve this issue or not.
Comment 8 Kristoffer Grundström 2016-10-12 05:43:25 CEST 
Hmmmmmmmmmm. Apparently theese updates created an I/O error since I can no longer boot into a working login window.
Comment 9 Marja Van Waes 2016-10-13 12:04:20 CEST 
(In reply to Kristoffer Grundström from comment #7)
> I made a misstake when adding the proper Cauldron medias after the first
> reboot so I fixed my typo now and got over 900 updates to install. I'll
> check if any of those solve this issue or not.

But this bug occurred before you updated _anything_, so it is at least valid for the 6sta1 traditional iso, correct?

Do you mind trying again with a cauldron network install?

CC: (none) => marja11
Assignee: bugsquad => gnome

Comment 10 Olav Vitters 2016-10-13 19:04:24 CEST 
It looks like it is not finding any screens/modules. So pointing to e.g. kernel/X11/Xorg.

CC: (none) => olav, thierry.vignaud

Comment 11 Kristoffer Grundström 2017-07-03 17:10:06 CEST 
On a fresh RC install I can confirm this issue once again.

It happens on all Desktop Environments.
Comment 12 Kristoffer Grundström 2017-07-03 21:06:39 CEST 
I tried switching to another DM, but non would login in.

XDM told me that $HOME had permission problem so I therefor decided to delete my user account and make a new one. Had to login as root and open userdrake and created a new user. When I switched back from XDM and booted into SDDM and clicked on Login everything worked just fine.

Don't know if an updated caused my first user account to become broken, but problem is solved for now.
Comment 13 Kristoffer Grundström 2017-07-20 23:34:50 CEST 
We can close this bug as I can't reproduce it anymore. If someone else experiences this issue feel free to reopen it again with further information.

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