You are not logged in.
Hi everyone, since the last update and restart, my login is stuck on "Reached target graphical interface".
I'm on a Dell XPS 13, gdm and i3.
I still have access to try with Ctrl + ATL + F2
Any idea ?
Last edited by slashome (2018-04-12 10:36:41)
Offline
Welcome to the arch linux forums slashome. So what exactly was in the last update for your system? You did not provide the pacman.log for it.
You also did not include the status of gdm.service or the its journal output from a boot after the last update.
Edit:
You might also want to change the title to include mention of gdm and remove the assertion that boot is freezing.
Last edited by loqs (2018-04-11 20:50:44)
Offline
I have the same problem after performing pacaur - Syu
It also updated my kernel to 4.15.15
systemctl status gdm says:
gdmDisplay: display lasted 0.939 seconds
child process -486 was already dead
Child process 474 was already dead
Unable to kill session worker process
Offline
Sorry I was on my phone, hard to type a log
So, here is pacman.log
Here is the gdm service status :
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2018-04-12 10:10:33 CEST; 43min ago
Main PID: 412 (gdm)
Tasks: 3 (limit: 4915)
Memory: 4.7M
CGroup: /system.slice/gdm.service
└─412 /usr/bin/gdm
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I don't know how to specificaly get gdm log journalctl sorry
And thank you very much for your help !
Offline
What is going on with all these --noconfirms and partial updates? https://wiki.archlinux.org/index.php/Sy … nsupported
Which exact command are you using to update your system?
Also the fact that your gdm log gets immediately rotated might mean two things. You either set a small journal size or your root partition is full, neither are desirable situations. Check your root partitions size and clear out potential cruft, a long time uncleaned pacman cache might accumulate over time, or verify that no file grows out of control (use df -h and something like ncdu to figure out biggest offenders)
After that properly run a
sudo pacman -Syu
and check and make sure that you are not using an outdated mirror.
Offline
Hi V1del, thanks a lot for helping ! I fixed my problem !
I did a clean pacman upgrade as you said, then I had to fix some npm existing files issues, then restarted and TADAAAAAA !
My sweet machine purr like a charm !
Offline
And as is hopefully evident through this, stop running everything as --noconfirm that really isn't an option you should casually use like that. And you are likely running that through some wrapper where you do not see the output pacman generates. That isn't a good basis for proper system maintenance, system updates do require you to look at their output and make conscious decisions as to what should be happening sometimes.
Offline