Bug 1098353

Summary: [abrt] xscreensaver-base: _IO_new_fclose(): xscreensaver killed by SIGABRT
Product: [Fedora] Fedora Reporter: Jonathan Ervine <jervine>
Component: glibcAssignee: Carlos O'Donell <codonell>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: cheese, codonell, fweimer, jakub, jervine, law, mtasaka, pfrankli, spoyarek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a5408cb18835b0ee177a80fd72352317923a8a60
Whiteboard: abrt_hash:451649ec38a624e883c20c88447b11fd35e9924a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-03 04:45:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
Output from command 'valgrind xscreensaver' none

Description Jonathan Ervine 2014-05-15 23:24:57 UTC 
Description of problem:
Running XFCE4 with XScreensaver with the /etc/pam.d/xscreensaver set to use the pam_yubico.so module. The YubiKey authentication is set to sufficient, and the screensaver unlock prompts for the YubiKey input. Once this is input the screensaver unlocks but xscreensaver immediately crashes and does not start again.

Version-Release number of selected component:
xscreensaver-base-5.26-5.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        xscreensaver -no-splash
crash_function: _IO_new_fclose
executable:     /usr/bin/xscreensaver
kernel:         3.14.2-200.fc20.x86_64
runlevel:       3 5
type:           CCpp
uid:            1591200001

Truncated backtrace:
Thread no. 1 (8 frames)
 #5 _IO_new_fclose at iofclose.c:85
 #6 internal_endent at nss_files/files-XXX.c:160
 #7 _nss_files_gethostbyname4_r at nss_files/files-hosts.c:479
 #8 gaih_inet at ../sysdeps/posix/getaddrinfo.c:850
 #9 getaddrinfo at ../sysdeps/posix/getaddrinfo.c:2405
 #10 Curl_getaddrinfo_ex at curl_addrinfo.c:128
 #11 getaddrinfo_thread at asyn-thread.c:273
 #12 curl_thread_create_thunk at curl_threads.c:59
Comment 1 Jonathan Ervine 2014-05-15 23:25:02 UTC 
Created attachment 896096 [details]
File: backtrace
Comment 2 Jonathan Ervine 2014-05-15 23:25:04 UTC 
Created attachment 896097 [details]
File: cgroup
Comment 3 Jonathan Ervine 2014-05-15 23:25:07 UTC 
Created attachment 896098 [details]
File: core_backtrace
Comment 4 Jonathan Ervine 2014-05-15 23:25:10 UTC 
Created attachment 896099 [details]
File: dso_list
Comment 5 Jonathan Ervine 2014-05-15 23:25:12 UTC 
Created attachment 896100 [details]
File: environ
Comment 6 Jonathan Ervine 2014-05-15 23:25:14 UTC 
Created attachment 896101 [details]
File: limits
Comment 7 Jonathan Ervine 2014-05-15 23:25:16 UTC 
Created attachment 896102 [details]
File: maps
Comment 8 Jonathan Ervine 2014-05-15 23:25:18 UTC 
Created attachment 896103 [details]
File: open_fds
Comment 9 Jonathan Ervine 2014-05-15 23:25:20 UTC 
Created attachment 896104 [details]
File: proc_pid_status
Comment 10 Jonathan Ervine 2014-05-15 23:25:22 UTC 
Created attachment 896105 [details]
File: var_log_messages
Comment 11 Mamoru TASAKA 2014-05-16 01:04:31 UTC 
Looks like this is very alike bug 1085215 (note that this bug is marked as private). 

Once assigning to glibc. Would you try valgrind so that glibc maintainer can debug this in detail?
Comment 12 Jonathan Ervine 2014-05-18 05:37:35 UTC 
Created attachment 896741 [details]
Output from command 'valgrind xscreensaver'

Running the command 'valgrind xscreensaver' and then reproducing the bug by locking the display, and activating the screensaver. The unlock dialog box prompts for the YubiKey input, which once accepted unlocks the display, but also crashes the xscreensaver program (as before). If additional valgrind options are required, please let me know.
Comment 13 Jonathan Ervine 2014-06-17 04:08:49 UTC 
I have read through the details of bug 1085215 and installed the updated glibc RPMs from rawhide as suggested in that bug report. This has made no difference to the symptoms. When the yubikey is pressed to unlock the xscreensaver the input is accepted and the screen is unlocked, but xscreensaver then segfaults, so further attempts to lock the screen fail, unless xscreensaver is manually reloaded.

This has been reproduced on a separate Fedora 20 x86_64 system, fully updated running xscreensaver version 5.29.

The only noticeable difference is that xscreensaver will not run under valgrind. If the output from trying to run xscreensaver under valgrind is required, please let me know.
Comment 14 Fedora End Of Life 2015-05-29 11:51:31 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 15 Carlos O'Donell 2015-06-03 04:45:46 UTC 
We've never gotten enough information to determine what is wrong with xscreensaver-base. The backtrace in question is impossible really, it would mean locking was completely broken. Given that we can't reproduce it I don't know what we're going to do about this. I'll keep watching if it shows up again.