Bug 606158 - [abrt] crash in gnome-dvb-daemon-0.1.19-2.fc13: raise: Process /usr/bin/gnome-dvb-daemon was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnome-dvb-daemon-0.1.19-2.fc13: raise: Process /usr/bin/gnome...
Status: CLOSED DUPLICATE of bug 601001
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-dvb-daemon   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:13a4dba12dd8b728ec76699a670...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-20 22:49 UTC by Lars Schotte
Modified: 2010-11-09 15:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 15:51:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (12.40 KB, text/plain)
2010-06-20 22:49 UTC, Lars Schotte
no flags Details

Description Lars Schotte 2010-06-20 22:49:14 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gnome-dvb-daemon
comment: played w/ gnome-dvb-control
component: gnome-dvb-daemon
crash_function: raise
executable: /usr/bin/gnome-dvb-daemon
global_uuid: 13a4dba12dd8b728ec76699a6702c79500bfb2fa
package: gnome-dvb-daemon-0.1.19-2.fc13
rating: 4
reason: Process /usr/bin/gnome-dvb-daemon was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1.played w/ gnome-dvb-control

Comment 1 Lars Schotte 2010-06-20 22:49:16 UTC
Created attachment 425501 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:51:13 UTC

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

Comment 3 Karel Klíč 2010-11-09 15:51:13 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #601001.

Sorry for the inconvenience.

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