Hello all,
I have been running Tumbleweed Gnome for a couple of years with very few issues, but this one has me stumped. I can boot in to the login screen just fine, select the user and enter the password. After a short blink, it returns to the enter password screen with no message. ctl>alt>F1 gets me to a terminal and I can log in with full admin rights and everything works fine (in CLI mode). Every once in a while I can successfully log in on GUI and everything works fine, but once I log out I typically can’t log back in regardless of how many times I repeat the same process and hope for a different outcome (insanity?). All of the installed DEs / window managers react the same way.
Any ideas out there? I am sure the issue is logged somewhere on the machine, but I have no idea what log to check or how to interpret any message I may have there. I am stuck in “Ubuntu Land” and really want to get back to my SUSE Gnome! Please help!
I think that means that your Gnome session has crashed.
As to why it crashed – that might be harder to find out. But look in files with names starting “.xsession-error” and see if there is anything that might be relevant.
You should, at least, be able to login to the Icewm desktop, but that might overwrite those “.session-error*” files. So instead, use CTRL-ALT-F1 and login at a terminal to check those files. Use “more” or “less” to scroll through them. But first check the file date, and ignore any of them dated before the most recent Gnome session crash.
After checking that, login to Icewm (it’s a bit more congenial), and see if there are other indicators in files in “/var/log” or in the output of “dmesg”.
Well, sheesh…
I realize this is not helpful but I have scoured through my logs as much as I can and haven’t found anything that looks suspicious.
- Looking for today’s date, I have gone through:
- .local/share/xorg/Xorg.1.log
- ~/.xsession-errors-:1
- Anything in /var/log that had today’s date in it
- dmesg
Nothing had any entry that looked like an error in the tail --lines=30, although I don’t really know what I am looking at.
Normally I can’t log in to anything - including Icewm. Oddly enough, I was able to log in to everything (including SUSE) and am replying from SUSE but I am sure once I log out I will not be able to get back in again. As a work around I may create a new user just to see if I am able to log into that user if my normal user is locked out. Doesn’t seem likely and a poor solution but desperate times…
To be clear, there is no obvious Gnome “crash” as far as I can tell. It simply acts as if I have not entered a password and wants to keep starting over at the “enter password” screen.
Gnome is picky with wanting OpenGL so can possibly be a video driver problem but it usually will throw a something went wrong error
Hopefully not my problem. I have a System76 Kudu running all Intel.
I’m wondering if there is a way to force a reinstall of the Gnome login files that may be broken. Is there an easy way to do that?
Did you try another user? Desktop config files are in your home
Also be sure you are not out of space on root. BTRFS with snapper can eat a lot of disk space especially on TW since the files churn a lot more then a more static distor.
I did add a user in Yast as well as making a few basic permission changes to myself by removing myself from the virtualbox user group hoping that might create some magic. Neither one helped. When I can’t log into my user (Gnome, Icewm, and all), I also can’t log in to the newly created user.
Interestingly enough I have found that if I restart the machine, try to log in, restart again, try to log in again, restart etc, I can usually log in with a couple of tries. Then, as long as I don’t reboot I seem to be able to log out and in again as much as I want including Icewm, etc.
Also checked my root drive. 15GB used on a 30GB partition.
Hi I had similar symptoms. May I suggest you go in as CLI root. Use Yast partition to see if your “/home” is mounted. If it is, exit Yast and open /etc/fstab using nano or Vi and remove the line which mounts “/home”, save then reboot. Retry to login from GUI. Hope this helps Tale: after Feb’s Tumbleweed snapshot my system failed, so I made my principle drive UEFI and did a fresh install of March snapshot.all worked; as my principle drive is SSD I thought to try “Gnome-disk-util”, I opened the program and noted “/home” didn’t show as mounted so exited prog and opened Yast-partioner and mounted “/home” got an error -3002 but forced the changes. rebooted and got symptoms you described, logged in as root but couldn’t seem to undo changes through Yast so edited “/etc/fstab” and all is well. only newbie so can’t reason why this is; new kernel or UEFI ?
Is it BTRFS? If so how did you look at the space not all tools give true disk space when snapper is involved. If EXT4 then all is god on space
Took a look at my fstab and /home is not mounted. Drive is formatted EXT4 and I used gparted to check the partition size and usage. https://www.dropbox.com/s/n4njvsm7z9xaix8/Screenshot.jpg?dl=0
