Bug 540180 - [abrt] crash detected in subtitleeditor-0.30.0-5.fc12
Summary: [abrt] crash detected in subtitleeditor-0.30.0-5.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 538382
Alias: None
Product: Fedora
Classification: Fedora
Component: subtitleeditor
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Martin Sourada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:850e01bca8de8316def49cd612d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-22 17:21 UTC by pankaj pandey
Modified: 2009-11-22 18:12 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-22 18:12:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (64.36 KB, text/plain)
2009-11-22 17:21 UTC, pankaj pandey
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.