Bug 620798 - [abrt] crash in rhythmbox-0.12.8-4.fc13: raise: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in rhythmbox-0.12.8-4.fc13: raise: Process /usr/bin/rhythmbox wa...
Keywords:
Status: CLOSED DUPLICATE of bug 597675
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5252b152a46fc92e4094f00cc44...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-03 14:09 UTC by Dan Weber
Modified: 2010-11-09 14:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 14:30:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (25.79 KB, text/plain)
2010-08-03 14:09 UTC, Dan Weber
no flags Details

Description Dan Weber 2010-08-03 14:09:44 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: rhythmbox
comment: This worked perfectly in all tested versions until now. Previously, I was using fedora 12, so I don't know whether or not this is a brand new problem for 13, but it ceratinly is a regression. I used my Creative Zen mp3 player for this test. Gnomad2 still works, so I doubt the problem is in libmtp. Assertions should never fail anyway.
component: rhythmbox
crash_function: raise
executable: /usr/bin/rhythmbox
global_uuid: 5252b152a46fc92e4094f00cc4408b66471dd542
kernel: 2.6.33.6-147.fc13.i686.PAE
package: rhythmbox-0.12.8-4.fc13
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Open Rhythmbox with the mtp plugin enabled
2. Plug in an mtp device

Comment 1 Dan Weber 2010-08-03 14:09:46 UTC
Created attachment 436281 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 14:30:34 UTC

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

Comment 3 Karel Klíč 2010-11-09 14:30:34 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 #597675.

Sorry for the inconvenience.


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