Bug 917825

Summary: [abrt] xscreensaver-base-5.21-2.fc17: kill_job: Process /usr/bin/xscreensaver was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Jeremy Christian <jchristi>
Component: xscreensaverAssignee: Mamoru TASAKA <mtasaka>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: jchristi, mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:83a86f4f869d7b14261eb99ca89b4685461b720c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-13 03:17:04 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: build_ids
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: smolt_data
none
File: var_log_messages
none
code dump none

Description Jeremy Christian 2013-03-04 20:49:08 UTC 
Description of problem:
I replaced gnome-screensaver with xscreensaver. Now when I lock the screen with xscreensaver and close my laptop lid, it crashes xscreensaver. This is a serious security issue!

Version-Release number of selected component:
xscreensaver-base-5.21-2.fc17

Additional info:
backtrace_rating: 4
cmdline:        xscreensaver -nosplash
crash_function: kill_job
executable:     /usr/bin/xscreensaver
kernel:         3.7.9-101.fc17.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 kill_job at ../../driver/subprocs.c:442
 #5 kill_screenhack at ../../driver/subprocs.c:1040
 #6 resize_screensaver_window at ../../driver/windows.c:1469
 #7 passwd_event_loop at ../../driver/lock.c:1921
 #8 gui_auth_conv at ../../driver/lock.c:2124
 #9 pam_conversation at ../../driver/passwd-pam.c:474
 #10 pam_vprompt at pam_vprompt.c:83
 #11 pam_prompt at pam_vprompt.c:111
 #12 _unix_read_password at support.c:819
 #13 pam_sm_authenticate at pam_unix_auth.c:157
Comment 1 Jeremy Christian 2013-03-04 20:49:11 UTC 
Created attachment 705152 [details]
File: backtrace
Comment 2 Jeremy Christian 2013-03-04 20:49:13 UTC 
Created attachment 705153 [details]
File: build_ids
Comment 3 Jeremy Christian 2013-03-04 20:49:14 UTC 
Created attachment 705154 [details]
File: cgroup
Comment 4 Jeremy Christian 2013-03-04 20:49:16 UTC 
Created attachment 705155 [details]
File: core_backtrace
Comment 5 Jeremy Christian 2013-03-04 20:49:17 UTC 
Created attachment 705156 [details]
File: dso_list
Comment 6 Jeremy Christian 2013-03-04 20:49:19 UTC 
Created attachment 705157 [details]
File: environ
Comment 7 Jeremy Christian 2013-03-04 20:49:20 UTC 
Created attachment 705158 [details]
File: limits
Comment 8 Jeremy Christian 2013-03-04 20:49:22 UTC 
Created attachment 705159 [details]
File: maps
Comment 9 Jeremy Christian 2013-03-04 20:49:27 UTC 
Created attachment 705160 [details]
File: open_fds
Comment 10 Jeremy Christian 2013-03-04 20:49:28 UTC 
Created attachment 705161 [details]
File: proc_pid_status
Comment 11 Jeremy Christian 2013-03-04 20:49:30 UTC 
Created attachment 705162 [details]
File: smolt_data
Comment 12 Jeremy Christian 2013-03-04 20:49:31 UTC 
Created attachment 705163 [details]
File: var_log_messages
Comment 13 Mamoru TASAKA 2013-03-05 00:41:54 UTC 
Can you upload core file somewhere? From backtrace currently I see something impossible happened..??
Comment 14 Mamoru TASAKA 2013-03-05 00:46:14 UTC 
Or is this issue reproducible?
Comment 15 Jeremy Christian 2013-03-05 17:06:18 UTC 
Mamoru, where would I find the core file?
Comment 16 Mamoru TASAKA 2013-03-06 00:17:31 UTC 
Try checking
/var/spool/abrt/
or
~/.cache/abrt/spool/
Comment 17 Jeremy Christian 2013-03-12 18:16:16 UTC 
Created attachment 709117 [details]
code  dump
Comment 18 Jeremy Christian 2013-03-12 18:20:00 UTC 
Mamoru, I am no longer able to recreate this bug. It may have been a bug that can only be reproduced after initial install. Possibly something leftover from gnome-screensaver.
Comment 19 Mamoru TASAKA 2013-03-13 03:17:04 UTC 
Thank you for coredump. I checked the core with gdb, however still I cannot figure out why this issue happened (looks impossible...)

Now I once close this bug as WORKSFORME. If issues similar to this or something else, please let me know it. Thank you for reporting anyway.