You are not logged in.
Hey,
I've run into a weird issue here: when I reboot my laptop, it gets stuck after the "file system clean" messages and GDM won't come up.
After some time, it shows a "oops, something has gone wrong"-message and I can log in, but my settings are gone (mouse moves slowly, battery applet shows no battery, etc.).
After a few minutes, gnome-shell will crash.
sudo systemctl status gdm.service:
gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled)
Active: active (running) since Fr 2013-08-02 19:11:27 CEST; 4min 43s ago
Main PID: 404 (gdm)
CGroup: name=systemd:/system/gdm.service
├─ 404 /usr/bin/gdm
├─ 915 /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Displays/_0
├─ 962 /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-setsPX/database -seat seat0 -nolisten tcp vt1
└─3050 gdm-session-worker [pam/gdm-password]
Aug 02 19:11:27 tp systemd[1]: Started GNOME Display Manager.
Aug 02 19:11:28 tp gdm[404]: Failed to give slave programs access to the display. Trying to proceed.
Aug 02 19:13:24 tp gdm-password][3050]: pam_unix(gdm-password:session): session opened for user neunerseb by (unknown)(uid=0)
Aug 02 19:13:24 tp gdm[404]: Failed to remove slave program access to the display. Trying to proceed.
last lines (those with "gdm[404]" get repeated when it crashes".
However (!) when I disable gdm.service and put "exec gnome-session" into my xinitrc and call "startx" it works just fine.
Any ideas?
Last edited by neunerseb (2013-08-03 08:46:03)
Offline
I have nearly the same problem. But my gnome crashes instantly after "startx". Came with an update i think.
Offline
I just tried "systemctl start gdm.service" from tty twice. First time was good, the second time I had the same old error again.
I also tried running gdm as root with the same result.
Running gnome-session works fine, so it's either a gdm or systemd thing...
edit: just found this in the log
gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; disabled)
Active: inactive (dead)
Aug 03 00:49:52 tp gdm[3062]: Freeing conversation 'gdm-launch-environment' with active job
Aug 03 00:49:52 tp gdm[3062]: GLib-GObject: g_object_ref: assertion `object->ref_count > 0' failed
Aug 03 00:49:52 tp gdm[3062]: GLib-GObject: g_object_unref: assertion `object->ref_count > 0' failed
Aug 03 00:49:52 tp systemd[1]: Stopped GNOME Display Manager.
Aug 03 00:50:34 tp systemd[1]: Starting GNOME Display Manager...
Aug 03 00:50:34 tp systemd[1]: Started GNOME Display Manager.
Aug 03 00:50:35 tp gdm[3005]: Failed to give slave programs access to the display. Trying to proceed.
Aug 03 00:52:03 tp systemd[1]: Stopping GNOME Display Manager...
Aug 03 00:52:03 tp gdm[3005]: GLib-GObject: g_object_ref: assertion `object->ref_count > 0' failed
Aug 03 00:52:03 tp systemd[1]: Stopped GNOME Display Manager.
Last edited by neunerseb (2013-08-02 23:09:04)
Offline
Looks like I fixed it by removing old stuff, namely:
- dkms-apci_call-git (AUR)
- hal (AUR)
- hal-info
- open-vm-tools-dkms
Not sure, which of those packages caused the bug though...
Offline