[Bug 1104642] New: sddm hangs/waits forever after PW entered, after upgrade to OpenSuse-2018-862
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642 Bug ID: 1104642 Summary: sddm hangs/waits forever after PW entered, after upgrade to OpenSuse-2018-862 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: michaelof@rocketmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Today I received an update for sddm - OpenSuse-2018-862. After install, and reboot, no login into plasma possible, anymore. System boots, sddm starts, passwort is entered, login button clicked/return pressed: Hangs/waits forever. System itself runs fine, virtual consoles are available. started yast and fell back to sddm 0.17.0-lp150.8.1 from repo OSS, login fine again. Reproducible always on my box. Does NOT happen on my wife's laptop. Please advice if you need any specific logs etc. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c1
--- Comment #1 from Michael from Offenbach Germany
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c2
Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c3
--- Comment #3 from Michael from Offenbach Germany
Please provide the system journal during login.
Thank you very much for helping with this issue! - Installed current sddm. - Rebooted. - Before Plasma login, on a virtual console, I've performed as root a "journalctl -cf > journalctl.txt" - Switched to sddm login screen - entered pw and tried to login, failed. - waited a while, pressed ctrl-C to stop running journalctl cmd - again waited a while, compared last lines of captured file and current journal: identical, no new changes. login still hangs. --> journalctl.txt attached.
Does it work if you set
[XDisplay] UserAuthFile=Xauthority.temp
in /etc/sddm.conf and rcxdm restart?
Unfortunately no. Remark 1: I've made the attached journal log with the parameter above already added to /etc/sddm.conf. Please advice, if you want a log without your parameter. Remark 2: I've forgot to erase your parameter when fallen back to sddm from base repo. Having forgotten this, I've recognized that WITH this paramater, the login with the base sddm (0.17.0-lp150.8.1) is also not possible (anymore), same symptom. Erased from /etc/sddm.conf, now able to login again.
Do you have any custom edited sddm configuration?
Promised , no :-) Content of /etc/sddm.conf: [Theme] [XDisplay] Only Plasma (maybe) speciality I have is file ~/.config/plasma-workspace/env/ssh-add.sh, containing just "ssh-add", to have my ssh keys unlocked for all consecutive bash Konsole/bash windows after Plasma login. But tried also without this file before opening this bug, same error, no login. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c4
Michael from Offenbach Germany
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c5
Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c6
--- Comment #6 from Michael from Offenbach Germany
Please try without pam_kwallet.
Not familiar with PAM, so as I found too much appearances of "pam_kwallet" in /etc/pam.d/*, I've decided just to sudo mv /lib64/security/pam_kwallet5.so /lib64/security/pam_kwallet5.so.SAV and rebooted. --> Does NOT change anything, reverted. Please advice if "Please try without pam_kwallet" means something different
If that doesn't work, what's the output of:
xauth -n -f /home/michael/Xauthority.temp list
hostname.localdomain/unix:0 MIT-MAGIC-COOKIE-1 dcbf037322e85b5edc06f4b276964146 (from a virtual console, after plasma login hangs)
sudo xauth -n -f /run/sddm/* list
hostname.localdomain/unix:0 MIT-MAGIC-COOKIE-1 f986cce2ebbea566e14715a06a4fea0c (from a virtual console, after plasma login hangs)
uname -n
hostname.localdomain (from a virtual console, after plasma login hangs)
hostname
hostname.localdomain (from a virtual console, after plasma login hangs)
Do other session types (icewm, plasma wayland) work?
with sddm 0.17.0-lp150.8.1 *ALL* working: plasma, icewm, twm with current sddm: - hanging plasma - hanging twm (same than plasma) - icewm: after correct login: showing empty black screen plus mouse pointer for some secs, then switching back to sddm login screen again, no msgs -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c7
--- Comment #7 from Fabian Vogt
(In reply to Fabian Vogt from comment #5)
Please try without pam_kwallet.
Not familiar with PAM, so as I found too much appearances of "pam_kwallet" in /etc/pam.d/*, I've decided just to
sudo mv /lib64/security/pam_kwallet5.so /lib64/security/pam_kwallet5.so.SAV
and rebooted.
--> Does NOT change anything, reverted.
Please advice if "Please try without pam_kwallet" means something different
zypper rm pam_kwallet. What you did is dangerous, you broke PAM.
If that doesn't work, what's the output of:
xauth -n -f /home/michael/Xauthority.temp list
hostname.localdomain/unix:0 MIT-MAGIC-COOKIE-1 dcbf037322e85b5edc06f4b276964146
(from a virtual console, after plasma login hangs)
sudo xauth -n -f /run/sddm/* list
hostname.localdomain/unix:0 MIT-MAGIC-COOKIE-1 f986cce2ebbea566e14715a06a4fea0c
The output should be the same - is the UserAuthFile line still in /etc/sddm.conf?
(from a virtual console, after plasma login hangs)
uname -n
hostname.localdomain
(from a virtual console, after plasma login hangs)
hostname
hostname.localdomain
(from a virtual console, after plasma login hangs)
Do other session types (icewm, plasma wayland) work?
with sddm 0.17.0-lp150.8.1 *ALL* working: plasma, icewm, twm
with current sddm: - hanging plasma
Wayland?
- hanging twm (same than plasma) - icewm: after correct login: showing empty black screen plus mouse pointer for some secs, then switching back to sddm login screen again, no msgs
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c8
Michael from Offenbach Germany
zypper rm pam_kwallet. What you did is dangerous, you broke PAM.
That's why I've immediately reverted my change :-) Tried with zypper rm also, no change, hangs.
If that doesn't work, what's the output of:
xauth -n -f /home/michael/Xauthority.temp list hostname.localdomain/unix:0 MIT-MAGIC-COOKIE-1 dcbf037322e85b5edc06f4b276964146
sudo xauth -n -f /run/sddm/* list hostname.localdomain/unix:0 MIT-MAGIC-COOKIE-1 f986cce2ebbea566e14715a06a4fea0c
The output should be the same - is the UserAuthFile line still in /etc/sddm.conf?
Promised, NO. Checked also with the working0.17.0-lp150.8.1, output lines are also different. --> And, maybe relevant, "sudo xauth -n -f /home/michael/Xauthority.temp list" does NOT change it's output, for days, many reboots and even several sddm (re-)installs now. Always the same string "dcbf037322e85b5edc06f4b276964146"
Wayland?
It seems that I've several Wayland pkgs installed, can provide list if wanted. But there's no "Wayland" option offered in sddm, only icewm, twm, and plasma. No idea how to change/add. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c9
Fabian Vogt
(In reply to Fabian Vogt from comment #7)
zypper rm pam_kwallet. What you did is dangerous, you broke PAM.
That's why I've immediately reverted my change :-) Tried with zypper rm also, no change, hangs.
If that doesn't work, what's the output of:
xauth -n -f /home/michael/Xauthority.temp list hostname.localdomain/unix:0 MIT-MAGIC-COOKIE-1 dcbf037322e85b5edc06f4b276964146
sudo xauth -n -f /run/sddm/* list hostname.localdomain/unix:0 MIT-MAGIC-COOKIE-1 f986cce2ebbea566e14715a06a4fea0c
The output should be the same - is the UserAuthFile line still in /etc/sddm.conf?
Promised, NO.
Please add it back and run the commands again - they assume the line was active.
Checked also with the working0.17.0-lp150.8.1, output lines are also different.
--> And, maybe relevant, "sudo xauth -n -f /home/michael/Xauthority.temp list" does NOT change it's output, for days, many reboots and even several sddm (re-)installs now. Always the same string "dcbf037322e85b5edc06f4b276964146"
Wayland?
It seems that I've several Wayland pkgs installed, can provide list if wanted. But there's no "Wayland" option offered in sddm, only icewm, twm, and plasma. No idea how to change/add.
"Plasma (Wayland)" is installed by default. If you don't have it, you either locked it or have an invalid package selection. It's part of "plasma5-session-wayland". -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c10
--- Comment #10 from Michael from Offenbach Germany
Please add it back and run the commands again - they assume the line was active.
Added the line "UserAuthFile=Xauthority.temp" to section [Display] in /etc/sddm.conf again. Result: sudo sudo xauth -n -f /run/sddm/* list hostname/unix:0 MIT-MAGIC-COOKIE-1 035594cc2ff0ee82aaa4d016b3ef5a60 sudo xauth -n -f /home/michael/Xauthority.temp hostname.localdomain/unix:0 MIT-MAGIC-COOKIE-1 035594cc2ff0ee82aaa4d016b3ef5a60 So NOW they'vc identicalvalues, but the /run/sddm/* entry does NOT have a FQDN. No idea why, does this have an impact? Remark: As said, with the UserAuthFile=Xauthority.temp line I'm NOT able to login anymore, hangs, even with the previously working old sddm pkg. Have to revert after testing for this issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c11
Michael from Offenbach Germany
Wayland?
It seems that I've several Wayland pkgs installed, can provide list if wanted. But there's no "Wayland" option offered in sddm, only icewm, twm, and plasma. No idea how to change/add.
"Plasma (Wayland)" is installed by default. If you don't have it, you either locked it or have an invalid package selection. It's part of "plasma5-session-wayland".
Didn't have plasma5-session-wayland pkg installed, maybe because my box started with 13.1 and was zypper dup-ed via 13.2, 42.1, .... all the way to now 15.0, no wayland that time, afaik :-) --> installed, ~5 pkgs added automatically as deps. Result: Wayland login for my user (michael) WORKS FINE. Screen/desktop is ugly, but probably a calibration issue, with wayland only pars of the screen are used, same resolution, but not "fit" to display size. Additional finding, maybe helpful: I've two users "available" on sddm login screen: "michael" and my wife. My wife's user was created by me years ago, 13.1 afaik, not really used since then, she has her own Leap 15 laptop. BUT with my wife's user I CAN login, even with the latest sddm. So only my own user "michael" hangs. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c12
--- Comment #12 from Michael from Offenbach Germany
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c13
--- Comment #13 from Michael from Offenbach Germany
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642
http://bugzilla.opensuse.org/show_bug.cgi?id=1104642#c14
Fabian Vogt
*** [SOLVED] ***
As I found out that only my user "michael" was affected, and not my wife's (unused) user, I've diff-ed file by file all "usual suspects".
Found the following line at the end of ~/.bashrc:
export XAUTHORITY=~/.local/share/sddm/.Xauthority
The released sddm update fixes your original issue by switching back to ~/.Xauthority, but broke your hack by doing that. Thanks for reporting back! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com