Bug 604839 - [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 626041
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:9cedef78a2817dda5a92f9e54c0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-16 20:09 UTC by Sebastián Ramírez
Modified: 2010-11-09 16:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:32:28 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (24.19 KB, text/plain)
2010-06-16 20:09 UTC, Sebastián Ramírez 		no flags Details
View All

Description Sebastián Ramírez 2010-06-16 20:09:52 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: rhythmbox '/home/sebastian/.gvfs/gphoto2 montado en usb%3A003,003'
comment: La aplicación falla cuanto conecto un teléfono Samsung SGH-F250 en modo mtp, para reproducir canciones. El mismo fallo se ha producido con versiones anteriores de Rhythmbox. El teléfono funciona correctamente pues he probado de sincronizarlo con el Windows media player 11 y marcha a la perfección.
component: rhythmbox
crash_function: raise
executable: /usr/bin/rhythmbox
global_uuid: 9cedef78a2817dda5a92f9e54c021b00890594af
kernel: 2.6.33.5-112.fc13.i686
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)
Comment 1 Sebastián Ramírez 2010-06-16 20:09:57 UTC 
Created attachment 424574 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:32:28 UTC 

*** This bug has been marked as a duplicate of bug 626041 ***
Comment 3 Karel Klíč 2010-11-09 16:32:28 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 #626041.

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