After the last update of OpenSuse Tumbleweed 20190417 and the last update of Gnome Shell 3.30.2,
When I try to login, it make loginloop. Then I need to restart xdm.services and then everything works as usual.
How can I fix this issue.
P.S.
I have tried with Xorg and WayLand.
After an unsuccessful login and you have to re-login, you should be able to view your current bootlog with the following command, you should be able to locate your failure sometime just before you have to restart gdm and re-login.
journalctl -b
If you’re unable to figure out what is happening, you can upload your bootlog to a pastebin and then post the link here.
If you need to create a file containing your bootlog, the following can do that
journalctl -b > somefilename.txt
TSU
journalctl -b > somefilename.txt
My file is 35 MB, but I can’t upload it here.
How can I upload here?
Wherever and whenever you want to post something that’s not allowed,
You can post to a pastebin.
The big general purpsoe pastebin
http://pastebin.com
Like most other distros, opensuse also has its own pastebin
https://paste.opensuse.org/
You can paste the contents (preferred because the file can be read online), or the file uploaded which will downloading before it can be read.
When you create your pastebin, the URL will change and you can then post that to this Forum for others to visit.
TSU
I see a lot of snapshots related errors.
Have you checked your disk for free space?
Perhaps you’ve run out of space and need to manually remove some snapshot data.
Also,
I see you have Virtualbox installed.
Interesting now that I think about it especially with 15.1 now installing /home as BTRFS by default, is your Virtualbox disk storage on BTRFS or something else (likely XFS)?
TSU
I am talking about xdm.services on real bear machine. My VirtualBox doesn’t have any disk storage.
The issue is that when I restart my real machine, and when I want to login, it become looplogin.
Than I need to restat xdm.services, and than everything is ok.
Kind Regards,
Ivo Nenchev
Before you login 2nd time, switch to an terminal with STRG+ALT+F2, login as root and execute:
systemctl status xdm.service > /home/USERNAME/xdm.txt
Expand USERNAME with your existing Username and you will get xdm.txt in your Users /home.
Please post the contend here.
Before my 2nd time to login, I switched to the terminal with STRG+ALT+F6, login as root and execute:
systemctl status xdm.service > /home/ivonenchev/xdm.txt
The output file includes follow rows :
● display-manager.service - X Display Manager
Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-04-22 00:26:17 EEST; 2min 36s ago
Process: 2829 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
Main PID: 2867 (gdm)
Tasks: 3 (limit: 4915)
Memory: 8.1M
CGroup: /system.slice/display-manager.service
└─2867 /usr/sbin/gdm
Apr 22 00:26:17 linux-456c display-manager[2829]: Starting service gdm…done
Apr 22 00:26:17 linux-456c systemd[1]: Started X Display Manager.
Apr 22 00:26:19 linux-456c gdm-launch-environment][2877]: accountsservice: Could not get current seat: Няма налични данни
Apr 22 00:26:22 linux-456c gdm[2867]: GdmDisplay: display lasted 3,772115 seconds
Apr 22 00:26:22 linux-456c gdm[2867]: Child process -2891 was already dead.
Apr 22 00:26:22 linux-456c gdm[2867]: Child process 2877 was already dead.
Apr 22 00:26:22 linux-456c gdm[2867]: Unable to kill session worker process
Apr 22 00:26:22 linux-456c gdm-launch-environment][2913]: accountsservice: Could not get current seat: Няма налични данни
Apr 22 00:27:58 linux-456c gdm-password][3333]: accountsservice: Could not get current seat: Няма налични данни
Apr 22 00:28:06 linux-456c gdm[2867]: GdmDisplay: display lasted 2,146621 seconds
That forum thread suggests the problem was resolved by a code patch. Considering how long ago that was, I hope that can’t still reoccur.
But, it <might> be useful to downgrade the accountservice package as described as part of your troubleshooting.
Here is another hit when searching on your error,
The Users found taht the User was invoking a login script that was invoking either the wrong shell or was invoking the needed shell by way of another shell
https://bbs.archlinux.org/viewtopic.php?id=243514
TSU