Hiya,
I've recently noticed that my system doesn't always get to GDM on boot. I'm not sure what's causing it, but looking at the boot messages, it seems to get stuck around something to do with "User id 42". I'm trying to get more info off journalctl but it doesn't have any. Any suggestions?
Oh, booting into run level 3 and then running startx seems to work.
Happened with both an F22 upgraded to F23 and now a fresh F23 (I thought maybe something had broken in the upgrade, but that doesn't seem to be the case).
This is only happening on my dell laptop which I power off and reboot frequently. The other machines seem to be fine, but I don't reboot them often so I can't really be 100% sure about this.
On Sat, Oct 03, 2015 at 03:44:58PM +0100, Ankur Sinha wrote:
I've recently noticed that my system doesn't always get to GDM on boot. I'm not sure what's causing it, but looking at the boot messages, it seems to get stuck around something to do with "User id 42".
You can check what is "User id 42" by typing
id -n -u 42
(or by looking at id numbers in /etc/passwd). Unless you were forcing some id changes on your system you will most likely find that the answer is "gdm". Surprise!
I'm trying to get more info off journalctl but it doesn't have any. Any suggestions?
systemctl -l status gdm
It is really hard to guess without any information what troubles you may have and why.
Oh, booting into run level 3 and then running startx seems to work.
How about 'telinit 5' instead here? 'systemctl default' should do the same (one would hope so).
Michal
On Sat, 2015-10-03 at 10:05 -0600, Michal Jaegermann wrote:
On Sat, Oct 03, 2015 at 03:44:58PM +0100, Ankur Sinha wrote:
I've recently noticed that my system doesn't always get to GDM on boot. I'm not sure what's causing it, but looking at the boot messages, it seems to get stuck around something to do with "User
id 42".
You can check what is "User id 42" by typing
id -n -u 42
(or by looking at id numbers in /etc/passwd). Unless you were forcing some id changes on your system you will most likely find that the answer is "gdm". Surprise!
Should've guessed that..
I'm trying to get more info off journalctl but it doesn't have any. Any suggestions?
systemctl -l status gdm
It is really hard to guess without any information what troubles you may have and why.
Oh, booting into run level 3 and then running startx seems to work.
How about 'telinit 5' instead here? 'systemctl default' should do the same (one would hope so).
I know, but when gdm fails, the system just hangs and I can't access a virtual terminal or anything - journalctl doesn't seem to store data about this boot at all :/
For the time being, I've changed my login manager to lightdm and that appears to work fine. I'll keep testing this from time to time and see if I can get some logs or error info.
-
Ankur Sinha -
Michal Jaegermann