You are not logged in.
75% of the time it boots fine and GDM loads, but I've noticed for some reason, at random gdm will simply not load, it will just sit there at the tty with nothing happening. I can switch to another tty and restart the service or reboot and then it will load. Does anyone else have this problem, anyway to get it to load consistantly?
Last edited by bwat47 (2013-07-08 14:37:24)
Offline
Yes I have this problem, if you leave it for long enough it will go to gnomes 'oooopps' screen and then restart itself in my cases.
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
Same problem here, since the update to 3.8 I'm facing this problem.
I'd rather try touching the moon
than take on a whore's thinking.
Al Swearengen
Offline
I have the same issue. If you have an intel graphic card, you can try to enable SNA -> https://wiki.archlinux.org/index.php/In … ion_method.
It works most of the time.
« En essayant continuellement, on finit par réussir.
Donc plus ça rate, plus ça a de chance de marcher. »
Devise Shadock
Offline
I have the same issue. If you have an intel graphic card, you can try to enable SNA -> https://wiki.archlinux.org/index.php/In … ion_method.
It works most of the time.
I've already been using SNA for a few days, but am still seeing the issue with the same frequency:
[brandon@arch-lemu4 ~]$ cat /var/log/Xorg.0.log | grep backend
[ 3.204] (II) intel(0): SNA initialized with Ivybridge (gen7, gt2) backend
Last edited by bwat47 (2013-07-04 16:55:56)
Offline
Apparently its related to this upstream intel driver bug: https://bugs.freedesktop.org/show_bug.cgi?id=56416
disabling rc6 is supposed to be a working workaround but I haven't tried it yet (and I'd rather not rely on that workaround since this is a laptop and I want the power-savings of rc6). Apparently there's been a fix committed in mesa master, I'm going to try mesa-git fromt he aur and see if that fixes it.
Last edited by bwat47 (2013-07-04 20:23:07)
Offline
Installed mesa-git (9.2) from aur, gave it 3 reboots and so far so good, but since it happened infrequently I'll obviously have to give it a while to be able to really tell if its fixed or not.
Last edited by bwat47 (2013-07-05 01:37:29)
Offline
That's good news. I will try it too !
Last edited by Cthulhu82 (2013-07-05 05:34:02)
« En essayant continuellement, on finit par réussir.
Donc plus ça rate, plus ça a de chance de marcher. »
Devise Shadock
Offline
Damnit, mesa-git didn't fix it either
In addition to GDM not loading I've also noticed gnome-shell sometime does the same thing, GDM will load and I will go to login and it will just sit there. Really getting on my nerves ![]()
Guess I'll try disabling RC6, or using UXA (I had been using SNA every since I installed arch, so I haven't even tried UXA yet).
Offline
Same here, doesn't fix it and performances were awful.
« En essayant continuellement, on finit par réussir.
Donc plus ça rate, plus ça a de chance de marcher. »
Devise Shadock
Offline
In addition to GDM not loading I've also noticed gnome-shell sometime does the same thing, GDM will load and I will go to login and it will just sit there.
I have witnessed the same behavior. Sometime it's happening during the GDM start sequence, and sometimes it's when i try to login into a gnome-shell session.
I am using a Nvidia GPU by the way.
There what gives journalctl:
l 06 13:17:20 msytux666 systemd[1]: Starting GNOME Display Manager...
Jul 06 13:17:20 msytux666 systemd-logind[177]: Removed session 1.
Jul 06 13:17:20 msytux666 systemd[1]: Started GNOME Display Manager.
Jul 06 13:17:20 msytux666 dbus-daemon[176]: dbus[176]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=858 comm="/usr/bin/gdm ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=862 comm="/us
Jul 06 13:17:20 msytux666 dbus[176]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=858 comm="/usr/bin/gdm ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=862 comm="/usr/lib/gdm/gdm-simp
Jul 06 13:17:20 msytux666 dbus-daemon[176]: dbus[176]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Jul 06 13:17:20 msytux666 dbus[176]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Jul 06 13:17:20 msytux666 systemd[1]: Starting Accounts Service...
Jul 06 13:17:20 msytux666 dbus-daemon[176]: dbus[176]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Jul 06 13:17:20 msytux666 dbus[176]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Jul 06 13:17:20 msytux666 systemd[1]: Starting Authorization Manager...
Jul 06 13:17:20 msytux666 polkitd[871]: Started polkitd version 0.111
Jul 06 13:17:20 msytux666 polkitd[871]: Loading rules from directory /etc/polkit-1/rules.d
Jul 06 13:17:20 msytux666 polkitd[871]: Loading rules from directory /usr/share/polkit-1/rules.d
Jul 06 13:17:20 msytux666 polkitd[871]: Finished loading, compiling and executing 2 rules
Jul 06 13:17:20 msytux666 dbus-daemon[176]: dbus[176]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jul 06 13:17:20 msytux666 dbus[176]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jul 06 13:17:20 msytux666 systemd[1]: Started Authorization Manager.
Jul 06 13:17:20 msytux666 polkitd[871]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Jul 06 13:17:20 msytux666 accounts-daemon[867]: started daemon version 0.6.32
Jul 06 13:17:20 msytux666 dbus-daemon[176]: dbus[176]: [system] Successfully activated service 'org.freedesktop.Accounts'
Jul 06 13:17:20 msytux666 dbus[176]: [system] Successfully activated service 'org.freedesktop.Accounts'
Jul 06 13:17:20 msytux666 systemd[1]: Started Accounts Service.
Jul 06 13:17:21 msytux666 kernel: NVRM: Your system is not currently configured to drive a VGA console
Jul 06 13:17:21 msytux666 kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
Jul 06 13:17:21 msytux666 kernel: NVRM: requires the use of a text-mode VGA console. Use of other console
Jul 06 13:17:21 msytux666 kernel: NVRM: drivers including, but not limited to, vesafb, may result in
Jul 06 13:17:21 msytux666 kernel: NVRM: corruption and stability problems, and is not supported.
Jul 06 13:17:22 msytux666 gdm[858]: Failed to give slave programs access to the display. Trying to proceed.
Jul 06 13:17:22 msytux666 systemd-logind[177]: New session c1 of user gdm.
Jul 06 13:17:22 msytux666 systemd-logind[177]: Linked /tmp/.X11-unix/X0 to /run/user/120/X11-display.
Jul 06 13:17:22 msytux666 /usr/bin/dbus-launch[894]: gnome-session[894]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
Jul 06 13:17:22 msytux666 gnome-session[894]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
Jul 06 13:17:22 msytux666 systemd-coredump[918]: Invalid number of arguments passed from kernel.
Jul 06 13:17:22 msytux666 /usr/bin/dbus-launch[894]: gnome-session[894]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal 11
Jul 06 13:17:22 msytux666 gnome-session[894]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal 11
Jul 06 13:17:22 msytux666 kernel: dconf worker[917]: segfault at 70e0 ip 00007f0acf0f432d sp 00007f0ac4c18790 error 4 in libc-2.17.so[7f0acf0bd000+1a3000]
Jul 06 13:18:15 msytux666 systemd[1]: Starting Getty on tty2...
Jul 06 13:18:15 msytux666 systemd[1]: Started Getty on tty2.
Jul 06 13:18:22 msytux666 login[919]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Jul 06 13:18:22 msytux666 systemd-logind[177]: New session 2 of user root.
Jul 06 13:18:22 msytux666 login[919]: ROOT LOGIN ON tty2
Jul 06 13:18:53 msytux666 /usr/bin/dbus-launch[894]: gnome-session[894]: WARNING: Application 'gnome-settings-daemon.desktop' failed to register before timeout
Jul 06 13:18:53 msytux666 gnome-session[894]: WARNING: Application 'gnome-settings-daemon.desktop' failed to register before timeout
Jul 06 13:18:53 msytux666 gnome-session[894]: Unrecoverable failure in required component gnome-settings-daemon.desktop
Jul 06 13:18:53 msytux666 gnome-session[894]: Entering running state
Jul 06 13:18:53 msytux666 /usr/bin/dbus-launch[894]: (gnome-shell:938): Gvc-WARNING **: Failed to connect context: OK
Jul 06 13:18:53 msytux666 polkitd[871]: Registered Authentication Agent for unix-session:c1 (system bus name :1.13 [gnome-shell --mode=gdm], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C)
Jul 06 13:18:53 msytux666 /usr/bin/dbus-launch[894]: JS LOG: GNOME Shell started at Sat Jul 06 2013 13:18:53 GMT+0200 (CEST)
Jul 06 13:18:54 msytux666 /usr/bin/dbus-launch[894]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Jul 06 13:18:54 msytux666 /usr/bin/dbus-launch[894]: Window manager warning: Got a request to focus 0xa00003 () with a timestamp of 0. This shouldn't happen!
Jul 06 13:18:55 msytux666 /usr/bin/dbus-launch[894]: (gnome-shell:938): Cogl-ERROR **: Failed to create an OpenGL framebuffer object
Jul 06 13:18:55 msytux666 kernel: traps: gnome-shell[938] trap int3 ip:7fd0cf7e1d4d sp:7fffa94a9560 error:0
Jul 06 13:18:55 msytux666 polkitd[871]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.13, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C) (disconnected from bus)
Jul 06 13:18:56 msytux666 /usr/bin/dbus-launch[894]: (gnome-shell:951): Gvc-WARNING **: Failed to connect context: OK
Jul 06 13:18:56 msytux666 polkitd[871]: Registered Authentication Agent for unix-session:c1 (system bus name :1.15 [gnome-shell --mode=gdm], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C)
Jul 06 13:18:56 msytux666 /usr/bin/dbus-launch[894]: JS LOG: GNOME Shell started at Sat Jul 06 2013 13:18:56 GMT+0200 (CEST)
Jul 06 13:18:56 msytux666 /usr/bin/dbus-launch[894]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Jul 06 13:18:56 msytux666 /usr/bin/dbus-launch[894]: Window manager warning: Got a request to focus 0xa00003 () with a timestamp of 0. This shouldn't happen!
Jul 06 13:18:57 msytux666 /usr/bin/dbus-launch[894]: (gnome-shell:951): Cogl-ERROR **: Failed to create an OpenGL framebuffer object
Jul 06 13:18:57 msytux666 kernel: traps: gnome-shell[951] trap int3 ip:7f22ca6e0d4d sp:7fff06558c10 error:0
Jul 06 13:18:57 msytux666 polkitd[871]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.15, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C) (disconnected from bus)
Jul 06 13:18:57 msytux666 /usr/bin/dbus-launch[894]: gnome-session[894]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Jul 06 13:18:57 msytux666 gnome-session[894]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Jul 06 13:18:57 msytux666 gnome-session[894]: Unrecoverable failure in required component gnome-shell.desktop
Jul 06 13:18:57 msytux666 /usr/bin/dbus-launch[894]: gnome-session[894]: dconf-WARNING: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code17: Cannot open dconf database: invalid gvdb header
Jul 06 13:18:57 msytux666 gnome-session[894]: dconf-WARNING: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code17: Cannot open dconf database: invalid gvdb header
Jul 06 13:22:33 msytux666 systemd[1]: Stopping GNOME Display Manager...This error looks pretty suspicious to me:
Jul 06 13:17:22 msytux666 kernel: dconf worker[917]: segfault at 70e0 ip 00007f0acf0f432d sp 00007f0ac4c18790 error 4 in libc-2.17.so[7f0acf0bd000+1a3000]Offline
I have two different computers with Arch, desktop and netbook, and they are both having this random gdm hangs issue. I suspect this new feature of zooming-in of the desktop image (this is the one that uses GL?) to be responsible. It would be nice if I could disable that, ugly and unnecessary, effect.
Offline
I suspect this new feature of zooming-in of the desktop image (this is the one that uses GL?) to be responsible. It would be nice if I could disable that, ugly and unnecessary, effect.
I don't think the zoom-in feature is responsible (or at least fully responsible) since the crash sometimes occur during the GDM start-up where no zoom-in is involved. The zoom-in effect takes place when you actually enter a gnome-shell session.
Offline
I think SNA may have actually **been the problem** for me. Using UXA its been booting every single time, and I've rebooted quite a few times over the past day to test. Gnome-shell hasn't froze on login either.
Last edited by bwat47 (2013-07-08 14:39:03)
Offline
I have this issue with one nouveau and one ati pc. I think everyone actually has this issue.
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
This should be fixed in latest updates! looks like it was a gnome-settings-daemon issue. I did indeed notice something in my journalctl logs the other day when this happened saying gnome-settings-daemon failed to start, so it does sound like this was the issue, and this is probably why UXA/SNA etc... didn't have any effect:
https://projects.archlinux.org/svntogit … a023385ed2
https://bugs.archlinux.org/task/36009
Last edited by bwat47 (2013-07-08 14:38:28)
Offline