Bug ID | 1234405 |
---|---|
Summary | devel:microos/libeconf: Bug libeconf 0.7.5 causes systemd/sddm/pam/libc crash and prevents login |
Classification | openSUSE |
Product | openSUSE.org |
Version | unspecified |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | 3rd party software |
Assignee | rbrown@suse.com |
Reporter | pallaswept@proton.me |
QA Contact | screening-team-bugs@suse.de |
Target Milestone | --- |
Found By | --- |
Blocker | --- |
Created attachment 879108 [details]
output of `journalctl -b -2 |rg dumped -A 40`
After today's dup, I rebooted to a desktop with a mouse cursor and otherwise
unresponsive. Switching to a TTY showed an error "Unable to start user manager
for user 1000". I was unable to login with any account including root.
Using the recovery console, I was able to retrieve logs, find this culprit,
rollback, and am currently working after locking out the libeconf updates with
`sudo zypper al libeconf0 libeconf0-32bit libeconf-devel`
Not sure if this is just me, hopefully it is. I did have some custom pam
config, which I naturally removed to test, and there was no change, but I did
notice that `rpm -qf /etc/pam.d/*` returns several "file foo is not owned by
any package", and none of those files are mine. I'm not sure if this is
intentional or if it is related.
Relevant section of the journal is attached. Please let me know if I can help
in any way.