Bug 540180

Summary: [abrt] crash detected in subtitleeditor-0.30.0-5.fc12
Product: [Fedora] Fedora Reporter: pankaj pandey <pankaj86>
Component: subtitleeditorAssignee: Martin Sourada <martin.sourada>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: martin.sourada
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:850e01bca8de8316def49cd612d5d6b6ef37b535
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-22 18:12:19 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

Description pankaj pandey 2009-11-22 17:21:27 UTC 
abrt detected a crash.

How to reproduce
-----
1. start subtitleeditor
2. load any video using the menu
3. See the crash

The following output came on the terminal

$ subtitleeditor
application run: 0.2

Gdk-ERROR **: The program 'subtitleeditor' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 5059 error_code 14 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Aborted (core dumped)

Attached file: backtrace
cmdline: subtitleeditor
component: subtitleeditor
executable: /usr/bin/subtitleeditor
kernel: 2.6.31.5-127.fc12.x86_64
package: subtitleeditor-0.30.0-5.fc12
rating: 4
reason: Process was terminated by signal 6
Comment 1 pankaj pandey 2009-11-22 17:21:35 UTC 
Created attachment 372936 [details]
File: backtrace
Comment 2 Martin Sourada 2009-11-22 18:12:19 UTC 
I wish abrt was a tad wiser in this case... already a second duplicate of Bug 538382 :( At least here, seeing the terminal output makes me to believe that the X error you see is indeed the cause of these crashes (which I've already suspected from examining gdb backtraces)...

*** This bug has been marked as a duplicate of bug 538382 ***