You are not logged in.
A while ago (six months to a year), I updated my system and somehow introduced an irritating new problem: While formerly I could log in, log out, suspend, and resume in just a few seconds at most, now the screen goes blank (my monitor actually enters a power-saving mode), and it takes about thirty seconds before things proceed normally. I've lived with this problem for a while, intermittently trying to fix it and hoping in vain that an update would save me the trouble, but I've become really fed up with it and have come here seeking advice.
I'm running Gnome Shell on an up-to-date Arch Linux installation with a GTX 770 graphics card. I'm using the proprietary Nvidia drivers.
The problem, so far as I've found, seems to have something to do with GDM and X. Using "journalctl --user", I find that after the pause, there are two errors:
Aug 07 22:51:30 arch-desktop /usr/lib/gdm/gdm-x-session[1406]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
Aug 07 22:51:30 arch-desktop /usr/lib/gdm/gdm-x-session[1406]: _XSERVTransMakeAllCOTSServerListeners: server already runningThen it just goes on to load normally. In my "/var/log/Xorg.0.log", the only errors pertain to loading modules that don't exist, such as "nouveau", which I don't have installed. I've tried looking elsewhere for relevant errors but haven't been able to find anything.
Any suggestions? Am I missing something really obvious?
Last edited by ausgat (2015-08-11 19:11:45)
Offline
Have you tried disabling the wayland backend for GDM? It's wayland by default in GDM 3.16 (which came out a little less than 6 months ago), and wayland doesn't work with the nvidia proprietary drivers. So the devs have tried to set it up to fail over gracefully to X, but a) the failover isn't always graceful, and b) that takes time even if working as expected.
Last edited by mwillems (2015-08-08 12:24:22)
Offline
Is that done by uncommenting the "#WaylandEnable=false" line in "/etc/gdm/custom.conf"? If so, I've already done that, but it seems to make no difference.
Offline
I had similar issues for while. When trying to solve unrelated issues of segfaults on exit() from gtk3 programs and vlc not working, I incidentally solved my slow as hell suspend and resumes. I had simply bungled micro code updates. No idea if micro codes is your issue, but I thought it worth a mention.
Recognizing the arbitrary nature of human drive leaves the philosopher no more emancipated than the most thoughtless.
Offline
I researched microcode updates a bit and found this guide: https://wiki.archlinux.org/index.php/Microcode. Sadly, after updating it, my problem persists totally unaltered.
Offline
A google search led me here. Similar issue, pause, and same warning in my xorg log (the gdm copy of xorg log is however clean). I get a pause on logging it. From the times in the logs, the user's Xorg instance is not starting yet. I wait ~30 seconds and then have to press escape (as if dismissing an invisible warning) and then suddenly my Xorg starts and desktop loads.
Not the end of the world since it allows logging in eventually (updated to gnome 3.17.91 and issue is there as well).
Also using nvidia.
Hopefully this won't regress into not being able to log in at all in future gnome versions...
By the way, rootless xorg doesn't log to /var/log/.
gdm's xorg logs to /var/lib/gdm/.local/share/xorg/
and user's xorg session logs to ~/.local/share/xorg/
Last edited by hussam (2015-09-09 22:13:49)
Offline