You are not logged in.
Hi, forums! After switching to systemd GDM is failing to start at boot. It seems that X server is working properly (and I still can run startx without any problems), but gdm only shows black screen with mouse pointer. Doing 'systemctl restart gdm' doesn't help at all. Installing gdm from scratch doesn't help either.
And, yes, system is totally up to date.
Honestly, I don't know how to debug gdm properly, so maybe you can point me? Logs at /var/log/gdm/:0-slave.log is full of this:
gdm-simple-slave[1409]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
gdm-simple-slave[1409]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
gdm-simple-slave[1409]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
gdm-simple-slave[1409]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Any help appreciated.
Offline
did you remember to enable graphic target? you need to do that after switching to systemd. I use slim and slim exited and dropped me into tty1 the first time I ran systemd
Offline
did you remember to enable graphic target? you need to do that after switching to systemd. I use slim and slim exited and dropped me into tty1 the first time I ran systemd
Like this?
systemctl enable graphical.target
ls -l /etc/systemd/system/default.target
/etc/systemd/system/default.target -> /usr/lib/systemd/system/graphical.target
No, this didn't help. BTW, slim is working just fine.
Last edited by Alsvartr (2012-11-25 21:21:58)
Offline
After upgrading to gdm 3.6.2-1, I got same problem: box hangs at boot while trying to start gdm.
/var/log/gdm/:0-slave.log is filled with:
gdm-simple-slave[408]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
gdm-simple-slave[408]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
gdm-simple-slave[408]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
gdm-simple-slave[408]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
gdm-simple-slave[408]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
gdm-simple-slave[408]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
gdm-simple-slave[408]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Didn't have this problem with the older gdm version which also got started by systemd.
Edit:typo
Last edited by Birkov (2012-11-26 13:14:43)
Offline
There is a problem with accountsservice versions higher than 0.6.25 and GDM. Try downgrading to 0.6.25.
Also see:
https://bbs.archlinux.org/viewtopic.php?id=144371
https://bbs.archlinux.org/viewtopic.php?id=153356
Offline
@Omer666
Thank you very much for reply and info. Using gdm-old from AUR for now.
Offline
@Omer666
I was having the same issue as the OP. Downgrading accountsservice to 0.6.25 fixed the issue for me. gdm now loads and I can login to my awesome-gnome session!
Machine: Lenovo ThinkCenter M92 (M3209) - Inte i7-3770 CPU
Offline