[SOLVED] GDM / GNOME crashes on login screen after standby

Brand new Arch installation on a Lenovo IdeaPad Flex 10. Most of the stuff works out of the box (except touchscreen https://bbs.archlinux.org/viewtopic.php?pid=1478128).
Using plain vanilla GNOME + GDM things seem ok, but once every few times upon returning from standby the login screen crashes and just freezes on the password screen. Nothing can be done (except for jumping to another vt) and a reboot is required.
If I SSH into the machine during this period, nothing suspicious shows up on journalctl.
Any ideas what's going on?
Last edited by yuvadm (2014-12-01 11:08:40)

Since I'm also getting some random freezes even when not in the login screen, I'm now suspecting a graphics driver problem.
Now testing UXA mode, per the Intel Graphics wiki page, hoping it will solve the freezes.
EDIT: UXA mode seems to have fixed the problem.
Last edited by yuvadm (2014-12-01 11:08:27)

Similar Messages

Gnome often turn back to gdm login screen after I hit the keybord

I am not sure whether there are anybody get same problem as me. Gnome often suddently turn back to GDM login screen after I hit keybord( any keys). The rate I get this problem is 2 times within about 6 hours . This is really bad problem ,while I was writting php codes ,the gnome suddently turn back to GDM caused I lost all codes I wrote!
is there any solution?

http://bbs.archlinux.org/viewtopic.php?id=82308
I have same problem, but sometimes it works perfectly until I reboot my PC O.o

[SOLVED] GDM/Gnome won't start after update

Today after I run pacman -Suy, GDM/Gnome won't start anymore after reboot. The error message I get after GDM starts is:
Oh no! Something has gone wrong.
A problem has occurred and the system can't recover. Please contact a system administrator
Does anyone have any idea what happened and how can I recover the system?
Here is the complete log for the update:
http://bpaste.net/show/209520/
Here is the journalctl -u gdm log:
http://sprunge.us/LEOU
Here is tail -2000 /var/log/messages.log:
http://sprunge.us/ObWY
And here is the /var/log/Xorg.0.log:
http://bpaste.net/show/209549/
I can't imagine any other log file that might help figure out what happened, let me know if there's anything else.
Any help is appreciated. Thanks.
Edit: I stopped gdm, created a ~/.xinitrc and could successfully start Gnome with startx. The problem remains with GDM.
Edit: The last update solved my problem: http://sprunge.us/RKWA
Last edited by falmp (2014-04-22 20:38:20)

I'm not sure my issue is really the same one, but am hoping for some guidance here if possible. Trying to start GDM gives me the same error message/screen. After tdm fails I can switch to a console,
sudo systemctl stop gdm.service
then
sudo systemctl start lightdm.service
and lightdm starts fine. However, trying to log in to gnome-session gives me the very same error as I had with GDM. I can log into XFCE just fine. Attempting to start gnome-ession via startx also gives me the error screen. Does anyone know how I can diagnose the problem? Thanks,
Matt

Stuck at login screen after update froze

Hi everyone, I have a Macbook that is a couple years old and have Leopard on it. Last night, I was prompted to install several updates and then restart my Macbook. I did so and then the updates began to install, but then appeared to stall. I hit the power off button and then turned my Macbook back on again. This brought me to the login screen, but I don't have my Macbook set to require me to login each time I use it. I entered my password and then it went to the blue screen like it was about to bring me to the desktop. But that didn't happen. It brought me back to the login screen, which is where I am still stuck as of this writing. Is there anything I can do? Thanks for your help.

No guarantee this will solve your problem, but you can give it a try:
You will need to type some Unix commands. If you are not comfortable with this, I don't know of anything other than a re-install. But if you are careful, you should be OK. I recommend you print this out in a largish mono-spaced font so you don't miss any spaces (or add extra ones). Note that case is important.
Be careful. Some of these commands are dangerous, since you are going to be root.
Start up in Single-User mode by holding down the command (Apple) key and the 's' key while you press the power switch. You can let go the keys when you see white text on a black background. When this has finished you will see a prompt ending in '#', although there may be other messages. Type
/sbin/fsck -fy
followed by a return, at the prompt and wait a few seconds for 8-10 lines of output. If the last line says repairs were carried out, repeat this command until you get a message 'The volume <yourdiskname> appears to be OK'. Then continue with
/sbin/mount -uw /
cd /Library/Preferences
rm com.apple.loginwindow.plist
rm com.apple.windowserver.plist
cd /Library/Caches
rm -r *
cd /System/Library
rm Extensions.kextcache
cd /System/Library/Caches
rm -r *
reboot
This should now take you to a proper login screen after the normal boot sequence. You should then Repair Permissions by using Disk Utility (in your /Applications/Utilities folder).
If you get error messages saying files do not exist, just ignore them and type reboot.
If the above is unsuccessful then you may be able to reinstall OS X using an Archive and Install which does not erase the hard drive:
How to Perform an Archive and Install
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger) and/or TechTool Pro (4.5.2 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

Stuck at login screen after Lion install

I downloaded and installed Lion on my late 2008 mbp with the latest updated snow leopard and after the install, I'm stuck on a screen with icons of my users. If I click nothing happens. I tried repairing disk permissions as well as re-installing Lion but nothing has helped. Any ideas?

You might see if this works:
Clearing Caches to Fix Login Problem
You will need to type some Unix commands. If you are not comfortable with this, I don't know of anything other than a re-install. But if you are careful, you should be OK. I recommend you print this out in a largish mono-spaced font so you don't miss any spaces (or add extra ones). Note that case is important.
Be careful. Some of these commands are dangerous, since you are going to be root.
Start up in Single-user Mode. When this has finished you will see a prompt ending in '#', although there may be other messages. Enter the following commands after the prompt:
/sbin/fsck -fy
Press RETURN. Wait a few seconds for 8-10 lines of output. If the last line says repairs were carried out, repeat this command until you get a message 'The volume <yourdiskname> appears to be OK'. Then continue with:
/sbin/mount -uw /
cd /Library/Preferences
rm com.apple.loginwindow.plist
rm com.apple.windowserver.plist
cd /Library/Caches
rm -r *
cd /System/Library
cd /System/Library/Caches
rm -r *
reboot
Press RETURN after each command.
This should now take you to a proper login screen after the normal boot sequence. You should then Repair Permissions by using Disk Utility (in your /Applications/Utilities folder).

IMAC crashing in login screen

Hey there.
My iMAC crashes quite often in the login scree. last time it happened , I got the log file from the console. This is the activity from the moment I turned on my iMAc and it crashed on login screen. i then rebooted and got the log file as soon as I was in the system.
here it is:
27/06/2009 21:17:27 com.apple.launchctl.System[2] fsck_hfs: Volume is journaled. No checking performed.
27/06/2009 21:17:27 com.apple.launchctl.System[2] fsck_hfs: Use the -f option to force checking.
27/06/2009 21:17:28 com.apple.launchctl.System[2] BootCacheControl: could not open /var/db/BootCache.playlist: No such file or directory
27/06/2009 21:17:28 com.apple.launchctl.System[2] BootCacheControl: could not unlink playlist /var/db/BootCache.playlist: Unknown error: -1
27/06/2009 21:17:29 com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
27/06/2009 21:17:29 com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
27/06/2009 21:17:29 com.apple.launchd[1] (com.apple.usbmuxd) Unknown key for boolean: EnableTransactions
27/06/2009 21:17:29 com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
27/06/2009 21:17:29 com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
27/06/2009 21:17:29 com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
27/06/2009 21:17:36 com.apple.launchd[1] (com.openssh.sshd) Unknown key: SHAuthorizationRight
27/06/2009 21:17:41 com.apple.launchd[1] (com.paceap.pacesupport52) posix_spawnp("/System/Library/Extensions/PACESupportFamily.kext/Contents/Resour ces/paceload", ...): No such file or directory
27/06/2009 21:17:41 com.apple.launchd[1] (com.paceap.pacesupport52) Exited with exit code: 1
27/06/2009 21:17:44 com.vmware.launchd.vmware53 VMware Fusion 51348: Starting VMware Fusion:
27/06/2009 21:17:45 com.vmware.launchd.vmware53 kextload serialization lock busy; sleeping (89 retries left)
27/06/2009 21:17:46 org.ntp.ntpd26 Error : nodename nor servname provided, or not known
27/06/2009 21:17:46 com.vmware.launchd.vmware53 kextload serialization lock busy; sleeping (88 retries left)
27/06/2009 21:17:48 com.vmware.launchd.vmware53 kextload: /Library/Application Support/VMware Fusion/kexts/vmmon.kext loaded successfully
27/06/2009 21:17:49 com.vmware.launchd.vmware53 kextload: /Library/Application Support/VMware Fusion/kexts/vmci.kext loaded successfully
27/06/2009 21:17:52 com.vmware.launchd.vmware53 kextload: /Library/Application Support/VMware Fusion/kexts/vmioplug.kext loaded successfully
27/06/2009 21:17:52 com.vmware.launchd.vmware53 kextload: /Library/Application Support/VMware Fusion/kexts/vmnet.kext loaded successfully
27/06/2009 21:17:53 com.vmware.launchd.vmware53 Internet Software Consortium DHCP Server 2.0
27/06/2009 21:17:53 com.vmware.launchd.vmware53 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
27/06/2009 21:17:53 com.vmware.launchd.vmware53 All rights reserved.
27/06/2009 21:17:53 com.vmware.launchd.vmware53 Please contribute if you find this software useful.
27/06/2009 21:17:53 com.vmware.launchd.vmware53 For info, please visit http://www.isc.org/dhcp-contrib.html
27/06/2009 21:17:53 com.vmware.launchd.vmware53 Can't open lease database /var/db/vmware/vmnet-dhcpd-vmnet8.leases: No such file or directory -- check for failed database rewrite attempt!
27/06/2009 21:17:53 com.vmware.launchd.vmware53 Please read the dhcpd.leases manual page if you.
27/06/2009 21:17:53 com.vmware.launchd.vmware53 don't know what to do about this.
27/06/2009 21:17:53 com.vmware.launchd.vmware53 exiting.
27/06/2009 21:17:53 com.apple.launchd[1] (com.vmware.launchd.vmware53) Exited with exit code: 1
27/06/2009 21:18:00 com.apple.SystemStarter31 PACESupport - Couldn't find the paceload script
27/06/2009 21:18:01 com.apple.SystemStarter31 Starting Qmaster services
27/06/2009 21:23:08 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow97) Exited: Terminated
27/06/2009 21:23:08 com.apple.launchd112 (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
27/06/2009 21:23:08 com.apple.launchd112 (org.x.startx) Unknown key for boolean: EnableTransactions
27/06/2009 21:23:09 com.apple.FolderActions.enabled115 launchctl: Error unloading: com.apple.FolderActions.folders
27/06/2009 21:23:11 Dock125 _DESCRegisterDockExtraClient failed 268435459
27/06/2009 21:23:17 Dock125 QL ERROR Generator database update takes too long... we will use what we currently have
27/06/2009 21:23:25 0x0-0x10010.info.virtuedesktops.VirtueDesktops137 dyld: Library not loaded: @executable_path/../Frameworks/TAUserInterfaceElements.framework/Versions/A/TAU serInterfaceElements
27/06/2009 21:23:25 0x0-0x10010.info.virtuedesktops.VirtueDesktops137 Referenced from: /Applications/VirtueDesktops.app/Contents/MacOS/VirtueDesktops
27/06/2009 21:23:25 0x0-0x10010.info.virtuedesktops.VirtueDesktops137 Reason: unsafe use of @executable_path in /Applications/VirtueDesktops.app/Contents/MacOS/VirtueDesktops with setuid binary
27/06/2009 21:23:27 com.apple.launchd112 (0x0-0x10010.info.virtuedesktops.VirtueDesktops137) Exited abnormally: Trace/BPT trap
27/06/2009 21:23:36 0x0-0x12012.com.apple.systemevents139 com.apple.FolderActions.enabled: Already loaded
27/06/2009 21:26:49 0x0-0x18018.com.apple.Safari168 Debugger() was called!
27/06/2009 21:29:40 com.apple.launchd112 (0x0-0x1c01c.com.apple.Console177) Exited: Terminated
Thanx!

HI,
If you can access these files, delete them and see if it helps.
com.apple.loginitems.plist
com.apple.loginitems.plist
/Users/YourName/Library/Preferences. Drag those files from the Preferences folder to the Trash, empty the Trash and restart your Mac.
*"27/06/2009 21:17:44 com.vmware.launchd.vmware53 VMware Fusion 51348: Starting VMware Fusion:"*
Are you running a Windows partition?
Are you using VirtueDesktops? If so, you may want to delete the app and see if that makes a difference.
Carolyn

Thinkpad X300 with windows xp sp2 gets blue screen after standby.

We have a Thinkpad X300 (with windows xp sp2) gets blue screen after standby. I mean after you close the lid then open it. Anyone has see this kind of behave before?
Thanks,

I have found the solution to this problem - hope you are still watching the thread.
Express install in parallels seems to be the culprit. Do a custom install instead and set your own virtual hard disk size. I set mine to 12 Gb (12000 Mb)and made it a fixed size instead of "growing" or whatever the heck parallels calls it. I also chose shared network instead of "bridged" (I read that someone else had identified this as part of the problem).
After making those changes it worked like a charm.

GDM, gnome-session exits to login screen after a few seconds

Recently, I've done a fresh installation of Arch Linux on my girlfriends laptop. She's using gnome and would like to log in graphically using GDM.
However, when I try to login via gdm, I get kicked out of gnome after a couple of (say about 30) seconds back to the login screen. It doesn't seem to matter if I do something. Even with no input/programms/whatsoever, the session ends after a short time.
The problem appears to be related to gdm, not gnome, though, because if I do not start GDM but launch my gnome-session via 'startx' from a terminal everything works perfectly fine.
I've read something about KMS issues somewhere and tried adding "nomodeset" to my kernel command line. The kickout was gone but gnome started in failback mode and issueing "gnome-shell --replace" started the gnome-shell but messed up parts of the screen.
Since I'm using fluxbox with no graphical login on my own machine, I really don't know where to start looking. Any clues/suggestions what to look at for fixing the problem?

i had the same issue but with xfce , a full system update fixed it . try doing that without starting 'X' . Also have you checked logs for any errors.

Gnome crashes on login

Hi,
my laptop is running on Arch with kernel 3.11.2-1 and I use the current gnome version as desktop environment.
To look closer to an image position of a website i'm currently creating I used the desktop-zoom function provided by gnome. After like 5 seconds gnome crashed and displayed the message: "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. All extensions have been disabled as a precaution." and a logout-button. So i logged out, rebootet my laptop and hoped it would help, but sadly it didn't. So each time I try to log in now I get this message.
So I looked throw dmesg and found this:
systemd-joufnald[121]: Failed to write entry(26 items, 228856444 bytes) despite vaccuming, ignoring: Argument list too long
traps: gnome-shell[1661]: trap int3 ip:7f4fccd6fd3d sp;7fff6ca4ab00 error:0
systemd-journald[121]: Vaccumin done, freed 0 bytes
systemd-journald[121]: Failed to write entry(26 items, 254325372 bytes) despite vaccuming, ignoring: Argument list too long
traps: gnome-shell[1661]: trap int3 ip:7ffaa0780d3d sp:7fff613a1af0 error: 0
I searched the web a bit but couldn't find anything helpfull so far.
Anyone has an idea how to fix this?
Greetings
Dero

Update.
The crashes are to be expected now. I'm circumventing the whole thing by logging into my other Gnome session without a window manager, logging out and then logging back into my regular Gnome with Metacity.
I've noticed the tty1 sessions(not sure what's it's called) is strange. Apparently my session runs on tty8 but when I try logging in, it'll crash me and tty7 gives me a blank screen with a blinking underscore. The other tty1s work regularly. Not sure if this has anything to do with it.
Is there a way to just reset the Gnome settings?

Gray Background of Login Screen After Returning from Screen Saver

I'm setting require password after sleep or screen saver begins
When awaking from sleep
login screen background is blur wallpaper ( correct ),
but when return from screen saver
login screen background is gray ( incorrect )
how to fix it?
Answer Similar Question
http://www.cnet.com/news/os-x-desktop-backgrounds-gray-after-waking-from-sleep/
I try to solve it,
but it dose not any effect.
Now I will updating OS X to v10.10.3
but I think the problem is still there.
MacBook Pro , OS X Yosemite v10.10.2

right, i'd just like to add that this issue was solved by installing "proper" ati drivers, or lowering sync and refresh rates in /etc/X11/xorg.conf, one of those

Get login screen after I logged in

When i Login i get the standard background screen and after that a blue one, it stays a few minutes this way and after that i get the login screen again.
I tried to safeboot but I get redirected to the login screen again.
Anyone got a solution for this, =S
zeemeeuw

This has been mentioned in some of the other threads about this issue, but an Archive and Install from your Leopard Installer DVD will solve this problem.
I had the same problem and was unable to login to my main working account. All the admin and the other accounts were all okay.
I did an archive and install, plus installed the updates (huge combo updater) and all is well again. Yeah it is a pain, but this is the first system reinstall since I originally installed Leopard.
Just make sure to run the Disk Utility Repair Disk before you do this.
Message was edited by: Zac.

Thrown back to login screen after logging in.

This is with Mac OS X 10.3.7
I've been having some strange problems lately, but today when if I log in (any user account) within about 15 seconds, the screen goes blue, then bumps me back to the login screen (list of users).
So, basically I get kicked out after 15 seconds or so (sometimes more sometimes less). Why is it doing that?
I suspected some disk problem, so I booted from the install disk and tried Disk Utility. But, I get the "lost connection from disk management tool" problem. (And, I didn't see the discussion of this until after this started happening, so I can't try the solution that was posted because I can't stay logged in long enough to manage files.)
I ran Repair Disk Permissions earlier today, as part of trying to solve a printer driver problem and didn't have the "lost connection" issue. I don't know if all these problems are related or not.
Any ideas?

OK, here's where I finally landed. Thanks for all the help.
I did an Erase with zeros and the install still failed. The failure was different every time, but I apologize for not listing what it was.
I finally went back to firewire mode, connected to my daughter's iMac (which is how I saved off the data before I started formatting and installing). I used her iMac to install the OS over firewire. After a few nervous moments (it looked like my daughter's iMac wouldn't reboot), it seems to have all worked.
So (other than my router acting funny), I think I'm on track. I need to get the router working and copy over files (or hook up via firewire again), but I think I'm on my way.
Thanks to everyone who helped. Learning the firewire trick was the key. I related that to someone at work and they were very impressed. (I almost have him talked into a Mac.)
Thanks,
Michael

MBA hangs on login screen after mountain lion upgrade

I have a mid 2011 macbook air. Ever since I did the upgrade to mountain lion last week, I have had about 10 instances where it hangs on the login screen. I bring it up from sleep, I see the login but when I enter my password and hit enter, it just hangs with the login box grayed. I can hit the cancel button and it gives me the ability to interact with the login box again, but will not log in. on all but one of these instances I have had to restart the machine. I have timed it to 5 minutes twice before restarting the machine to get back in. This never happened with lion. Anyone else have this issue?

I have issues also.
With a samba share on Linux, ML can see it correctly, but on my Windows Home Server 2011, if i do smb://"server address" i receive and error saying that the share dows not exist on server. Before on Lion i had a list of my shares. On finder the Server apears with a "/" which i can not open.
If i do smb://"server address/share" is works correctly, but i would like to have tha before behaviour. Besides this the only issue that i found after upgrading is the WHS 2011 Lauchpad could not sign in (before in Lion was working).
Any ideas on how to solve this?

How can I return to login screen after screensaver??

I am trying to set up my Parents new Mac like their old Windows XP machine. When the Windows PC sat idle it went to screensaver and if the mouse was moved it returned to the login screen with their user icons.
On the Mac the option under Security "Require password after screensaver" will bring up a password prompt for the user who is currently logged in with a "Switch User" button.
Hitting that "Switch User" button will bring me to the login screen with the list of users and their icons. Does anyone know of a way where it will bypass prompting for a password and goto the login screen without hitting the "Switch Users" button?

it's possible but what's wrong with hitting "switch user"? that's really the easiest. anything else will require extra work. see this link
http://discussions.apple.com/thread.jspa?messageID=10785767&#10785767

Spinning beach ball at login screen after upgrading to 10.4.8

Ok, I so used software update to install the 10.4.8 update (I know, big mistake, should have used combo update, etc.), and upon restart can't get past the login screen. After several seconds, the spinning beach ball appears and that's it. Been like that for hours.
Booted into single user mode and ran fsck, says that the volume is fine. diskutil stalls out in single user mode (can't place my hands on the install CD, otherwise I'd use diskutil fron that).
So, ideas?

I had this happen on my wife's iBook G4.. Here's what I did..
Remove the battery.. Unplug the power. Let it sit for a few seconds. (30 to be safe)..
Then plug it all back in
Turn it on and press APPLE-OPTION-P-R immediately after pressing the power button and hold it in for a LONG time.. even after you hear the chime.. keep holding it in for FOUR CHIMES and FOUR initialiations of the CD/DVD drive.
Then let go and let it boot.. you will then see the Apple Grey screen and it should boot normally.. Once it boots, repair permissions immediately.
At least that's what worked on her iBook, exact same problem.
Hope this helps.
Greg

[SOLVED] GDM / GNOME crashes on login screen after standby

Similar Messages

Maybe you are looking for