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
Created attachment 705152 [details] File: backtrace
Created attachment 705153 [details] File: build_ids
Created attachment 705154 [details] File: cgroup
Created attachment 705155 [details] File: core_backtrace
Created attachment 705156 [details] File: dso_list
Created attachment 705157 [details] File: environ
Created attachment 705158 [details] File: limits
Created attachment 705159 [details] File: maps
Created attachment 705160 [details] File: open_fds
Created attachment 705161 [details] File: proc_pid_status
Created attachment 705162 [details] File: smolt_data
Created attachment 705163 [details] File: var_log_messages
Can you upload core file somewhere? From backtrace currently I see something impossible happened..??
Or is this issue reproducible?
Mamoru, where would I find the core file?
Try checking /var/spool/abrt/ or ~/.cache/abrt/spool/
Created attachment 709117 [details] code dump
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.
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.