| Summary: | GDM: Couldn't login as normal user, only as root (keyboard layout US while keyboard is Swedish) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jan Pihlgren <jan> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Jan Pihlgren
2016-11-23 13:20:35 CET
Hi Jan,
Thanks for filing this report.
The issues with SDDM and GDM might have different causes, which means we might have to clone this bug report for the GDM issue.
Can you please set SDDM as display manager again and then boot until it goes wrong, switch to e.g. tty2 by pressing rightCtrl + F2 and run, as root:
journalctl -ab > SDDM.txt
After that, could you please switch back to GDM, reboot, try to login, see it fail and run as root:
journalctl -ab > GDM.txt
and attach both SDDM.txt and GDM.txt to this bug report.
Btw, where did logging in as root work?CC:
(none) =>
marja11 In reply to your mail, which I saw by some lucky coincidence. (I receive hundreds of valid [so non-spam] mails per day, which is much more than I can handle. Mailing me in private is not the way to get an answer. It is better to ask general questions in the forums or on discuss ml: the chance that someone will see your question and answer it, is very much greater) At the moment, to select which DM to use, an easy way is to use drakdm, which can be started from the command line. After selecting a display manager there, so that it's highlighted, and OK'ing, on reboot the selected DM will be used. I forgot to ask you for some more needed information. If you manage to also answer as many as possible of the questions that Lewis asked here: https://bugs.mageia.org/show_bug.cgi?id=19782#c0 that would be fabulous :-D Don't get overwhelmed ;-) If this is too much, then just give the feedback and attachments that you're currently capable of giving :-) Btw, was it GDM where you logged in as root, or SDDM, or ...? Keywords:
(none) =>
NEEDINFO Marja van Waes Sorry about mailing you personaly. Here is some answer: Btw, where did logging in as root work? Before I did the latest update, kernel 4.8.10-desktop-3.mga6 Btw, was it GDM where you logged in as root, or SDDM, or ...? It was GDM where I loged in as root I think that one reason that I couldn't logg in as user is that the keyboard layout is still US, I use Swedish layout. My hardware: x86_64 on 64bit host ISO = Mageia-6-sta1-x86_64-DVD.iso date=2016-07-02 BIOS boot error after installation uppdate kernelversion = 4.8.10-desktop-3.mga6 ================================================= 2016-11-25 11:31 Just try a new boot and succeded after change to GDM. kernel = 4.8.10-desktop-3.mga6 Logged in as user. :) :) Now I am very happy!!! ================================================= Reboot 4.8.10-desktop-3.mga6 Logged in as user. OK Can't access mcc. administrator/root password will not start mcc changed to user root, than I could access mcc ================================================== Reboot kernel = 4.8.10-desktop-3.mga6 Logged in as user. OK ================================================== For now it's OK (In reply to Jan Pihlgren from comment #3) > > I think that one reason that I couldn't logg in as user is that the keyboard > layout is still US, I use Swedish > layout. > Adjusting summary accordingly > Can't access mcc. administrator/root password will not start mcc > changed to user root, than I could access mcc MCC not starting, unless as user root, could be bug 16764 Please check the "Steps to Reproduce" in that report. If that's exactly what you see, then please report _there_ that you hit that bug in *cauldron*. If you do _not_ see the same, then please ask for help in the forums to determine whether a separate bug report should be filed. > Reboot > kernel = 4.8.10-desktop-3.mga6 > Logged in as user. OK > For now it's OK I understand logging in with GDM as user works fine, now. The SDDM issue is most likely still present, but the same as bug 19834. Let's keep bug 19834 for the SDDM issue, and keep this one for GDM. If the GDM issue emerges again, then please reopen this report. Keywords:
NEEDINFO =>
(none) |