Bug 540420 - [abrt] crash detected in xine-ui-0.99.5-16.fc12
Summary: [abrt] crash detected in xine-ui-0.99.5-16.fc12
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xine-ui
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Susi Lehtola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5e569a98142b6cbcd55fbd84fbf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-23 11:23 UTC by Cavan Mejias
Modified: 2010-02-10 07:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-10 07:33:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (10.12 KB, text/plain)
2009-11-23 11:23 UTC, Cavan Mejias
no flags Details

Description Cavan Mejias 2009-11-23 11:23:38 UTC
abrt detected a crash.

Attached file: backtrace
cmdline: /usr/bin/xine
component: xine-ui
executable: /usr/bin/xine
kernel: 2.6.31.5-127.fc12.x86_64
package: xine-ui-0.99.5-16.fc12
rating: 2
reason: Process was terminated by signal 6

Comment 1 Cavan Mejias 2009-11-23 11:23:41 UTC
Created attachment 373074 [details]
File: backtrace

Comment 2 Susi Lehtola 2009-11-23 11:43:33 UTC
Please attach the output of
$ rpm -q xine-ui xine-lib

Comment 3 Susi Lehtola 2009-11-29 19:04:09 UTC
ping?

Comment 4 Cavan Mejias 2009-12-06 22:07:19 UTC
              Hello,
                My apologies to the bug assignee for the tardy response. I hope the output below is usefull. 

[keren_sky@fedora ~]$ rpm -q xine-ui xine-lib
xine-ui-0.99.5-16.fc12.x86_64
xine-lib-1.1.16.3-4.fc12.x86_64


                    Bye,

Comment 5 Susi Lehtola 2009-12-06 23:01:04 UTC
What did you do that caused the crash?

**

Please run
# debuginfo-install xine-ui
and run xine-ui in gdb with

$ gdb xine
(gdb) r

If the program crashes, the reason should be listed in the gdb output.

Comment 6 Susi Lehtola 2010-02-10 07:33:34 UTC
Can't reproduce, closing due to submitter inactivity.


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