Description of problem: Mageia6 sta2 After starting MCC by the user from the menu, then selecting "Hardware -> Configuring the graphic server -> Test -> Yes" after the performed testing the owner of the .Xauthority file of the user will be root. And in the next boot the user can not enter the DE session because of the rights restriction to this file. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Run MCC from the menu, run test in the 'Configuring the graphic server' from the 'Hardvare' section 2.See your ~/.Xauthority file was owned by root 3.Reboot ant try to log in into DE
Created attachment 9294 [details] journalctl output Confirming the issue with a test user: In /home/u/ there was: -rw------- 1 u u 54 apr 25 12:12 .Xauthority After starting an XFCE session with "u" and running the graphic server test from MCC (but no settings changed) there was: -rw------- 1 root root 108 mei 13 09:37 .Xauthority -rw------- 2 u u 0 mei 13 09:38 .Xauthority-c -rw------- 2 u u 0 mei 13 09:38 .Xauthority-l and after logging out it was indeed impossible to log in again. After running "chown u: .Xauthority" (which was probably bound to fail to solve the issue, since the file had twice the original size) logging in was stil impossible. I then noticed that the contents of that file had been deleted -rw------- 1 u u 0 mei 13 09:39 .Xauthority -rw------- 2 u u 0 mei 13 09:38 .Xauthority-c -rw------- 2 u u 0 mei 13 09:38 .Xauthority-l After deleting all three .Xauthority* files, logging in worked fine again and the newly created .Xauthority had the correct size. Attaching the output of journalctl -a --since="2017-05-13 09:35" --until="2017-05-13 09:41" I have _not_ tried whether this bug is also valid when you actually change your configuration before testing it. @ Yuri Did you?
CC: (none) => marja11
Assignee: bugsquad => mageiatoolsSource RPM: (none) => drakx-kbd-mouse-x11Keywords: (none) => NEEDINFO
If I changed the configuration of the Graphic Card before "testing", everything is seems fine with this file then.
I encountered this bug on two recently installed boxes with Mageia 6 64-bit and Mate desktop. Solved it by changing user and group on .Xautority from "root" to normal user.
CC: (none) => pernel
@tv: As this happens pretty often to novice users when using the "Test" button in drakx11 - would it be difficult to implement a failsafe to chown any ~/.Xauthority* file in that users home folder to that user if it belongs to root ? That should probably go here, although I'm not that good at perl: http://gitweb.mageia.org/software/drakx-kbd-mouse-x11/tree/lib/Xconfig/test.pm#n137
CC: (none) => doktor5000, thierry.vignaud
I believe NEEDINFO got satisfied by comment 2. This trap have been present since long time.
CC: (none) => friKeywords: NEEDINFO => (none)Whiteboard: (none) => MGA8TOO
Our GUI tool for novices makes novices locked out - pretty serious. Raising severity and priority.
Priority: Normal => HighSeverity: normal => major
I see yet another user now needed help on forum with this.
Cant we just remove that test button...?
As users naturally experiment with drivers maybe this should be an errata item
Keywords: (none) => FOR_ERRATA9
Summary: User can't login into DE session because of user's .Xauthority file was owned by root => After drakx11 "test", user can't login into DE session because of user's .Xauthority file is owned by root
Some sad tests: _False negative Another reason to remove the test button is that it can also give false negatives. My system is happily using nvidia R535 on my GTX750. I just now launched drakx11 and pressed the test button and screen went blaxk maybe five seconds then back to desktop with drakx11 showing: An error occurred: (EE) Fatal server error: Try to change some parameters Nothing in journal Just pressing the button again, screen went black, then successfully show the rainbow test. _Regarding file ownership I ran the test answering Yes one time and No another time in the question on the rainbow test screen, and it did in neither case change the ownership of .Xauthority. So have this somehow got fixed? Or is the problem only arising under some circumstances? Above, i had started mcc from konsole with: LC_ALL=C mcc My user is member of wheel _Hard freeze Yet a reason to remove the dreaded test Next, i launched mcc from plasma menu, and in popup question selected my test user (also member of wheel btw) the test displayed the rainbow, but i could not select yes/no buttons, i saw no mouse pointer (maybe there was but that is a design problem, hard to see tiny on a 4K screen rainbow...) but i also dod not find keyboard working until it timed out. -- and after timing out it returned to a plain black desktop with frozen mouse pointer. Also ctrl-alt-F3 did not work (i verified earlier that it worked, bug 31994), not even REISUB. Had to use reset button. I end my tests... --- Added to errata https://wiki.mageia.org/en/Mageia_9_Errata#Graphics Updated https://wiki.mageia.org/en/Setup_the_graphical_server#Selecting_drivers
Keywords: FOR_ERRATA9 => IN_ERRATA9
(In reply to Morgan Leijström from comment #8) > Cant we just remove that test button...? Yes, please! I just wasted several hours trying to understand why I couldn't log in anymore! I finally reinstalled Mageia but I kept my /home partition alone, which means that the permissions on .Xauthority were left unchanged and so I did all this painful work for nothing.
CC: (none) => LpSolit
Target Milestone: --- => Mageia 10Whiteboard: MGA8TOO => MGA8TOO, MGA9TOO
For anyone needing help to rescue a system with failing GUI login: https://wiki.mageia.org/en/Rescue:_disable_GUI_at_boot HTH
CC: (none) => paul.blackburn
How does this wiki article help with the problem of this bug? The solution (until the test button is removed) is already pointed clearly out by Marja in comment 1.