Description of problem: xscreensaver crashes immediately when wake-ing from lock, doesn't prompt user for passphrase. Version-Release number of selected component (if applicable): xscreensaver-5.34-1.fc23.x86_64 How reproducible: Always since update last weekend. Steps to Reproduce: 1. On 13 March 2016, update system with dnf --enablerepo=updates-testing upgrade 2. reboot Actual results: xscreensaver crashes always Expected results: shouldn't crash Additional info:
Could you try debugging yourself? * First of all, would you attach the result of $ ps auwwx when you login? (Please don't paste the result directly on this bug! Please save the result on a text and add it to this bug as an attachment) * Is it possible to execute $ dnf history undo <ID> ? * Would you try below? - install xscreensaver-debuginfo - Once exit xscreensaver with $ xscreensaver-command -e - On terminal - set core side to unlimited by $ ulimit -c unlimited - launch $ xscreensaver on the terminal - If xscreensaver crash and leaves a core, try gdb by $ gdb xscreensaver core.foo and gdb> thread apply all bt full
* And for sure would you attach the result of $ rpm -qa --last ?
Actually, I'm sure this is pam_yubico related. May not be xscreensaver problem. I found this in the logs: User Logs: -- Logs begin at Sat 2015-01-10 10:25:45 PST, end at Tue 2016-03-15 13:28:05 PDT. -- Mar 15 13:28:04 <hostname> xscreensaver[1439]: PAM unable to dlopen(/usr/lib64/security/pam_yubico.so): /usr/lib64/security/pam_yubico.so: undefined symbol: ykclient_set_proxy Mar 15 13:28:04 <hostname> xscreensaver[1439]: PAM adding faulty module: /usr/lib64/security/pam_yubico.so Mar 15 13:28:04 <hostname> audit[1439]: ANOM_ABEND auid=13013 uid=13013 gid=13013 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1439 comm="xscreensaver" exe="/usr/bin/xscreensaver" sig=11 (In reply to Mamoru TASAKA from comment #1) > Could you try debugging yourself? Sure, no problem. ...Correction: No, I cannot; dnf cannot find pkg xscreensaver-debuginfo Is that why ABRT server replied "...cannot find debuginfo. Is this package in official repositories?" > * First of all, would you attach the result of > $ ps auwwx > when you login? (Please don't paste the result directly on this bug! > Please save the result on a text and add it to this bug as an attachment) Sure, next time I reboot. > * Is it possible to execute $ dnf history undo <ID> ? I don't know; never done that before. I can try that next reboot, also. > * Would you try below? > - install xscreensaver-debuginfo > - Once exit xscreensaver with $ xscreensaver-command -e > - On terminal > - set core side to unlimited by $ ulimit -c unlimited > - launch $ xscreensaver on the terminal > - If xscreensaver crash and leaves a core, try gdb by > $ gdb xscreensaver core.foo > and gdb> thread apply all bt full core is in abrt directory. I'd be happy to debug if I could find debuginfo.
Downgrading pam_yubico fixed it. My apologies.
Thank you for information. Well, it is not "not a bug", actually and actually pam_yubico needs fixing. Other person already seems to have opened a bug against pam_yubico (but for F-24), so I will notify pam_yubico maintainer that this issue happens now for F-23. Again thank you. *** This bug has been marked as a duplicate of bug 1312659 ***