Bug 670382

Summary: [abrt] xscreensaver-base-1:5.12-9.fc14: g_main_context_init_pipe: Process /usr/bin/xscreensaver was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Sean Hunter <sean>
Component: fprintdAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: bnocera, mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:46e7e47be6ae1b07f0ca0359e330dd925e66ef4f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-18 05:35:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Sean Hunter 2011-01-18 05:21:51 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: xscreensaver -nosplash
component: xscreensaver
crash_function: g_main_context_init_pipe
executable: /usr/bin/xscreensaver
kernel: 2.6.35.10-72.fc14.x86_64
package: xscreensaver-base-1:5.12-9.fc14
rating: 4
reason: Process /usr/bin/xscreensaver was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1295258050
uid: 500

How to reproduce
-----
1. Computer was idle
2. So the screensaver kicked in
3. It then crashed
Comment 1 Sean Hunter 2011-01-18 05:21:53 UTC 
Created attachment 473970 [details]
File: backtrace
Comment 2 Mamoru TASAKA 2011-01-18 05:35:31 UTC 

*** This bug has been marked as a duplicate of bug 665852 ***
Comment 3 Mamoru TASAKA 2011-01-20 07:18:32 UTC 
To be clear, "when" did you see this crash?

i.e. 
Did you see this crash immediately after screen got blank and
a hack (animation) lauched? Or after that you moved mouse or something
else?