Bug 673245 - [abrt] rhythmbox-0.13.2-1.fc14: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] rhythmbox-0.13.2-1.fc14: Process /usr/bin/rhythmbox was killed by sign...
Keywords:
Status: CLOSED DUPLICATE of bug 701746
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:80d04ebbd3410d1715fff3fc46f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-27 20:05 UTC by kibokin
Modified: 2012-03-21 16:50 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-21 16:50:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (64.49 KB, text/plain)
2011-01-27 20:05 UTC, kibokin
no flags Details

Description kibokin 2011-01-27 20:05:08 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: rhythmbox
component: rhythmbox
crash_function: rb_sync_settings_sync_category
executable: /usr/bin/rhythmbox
kernel: 2.6.35.10-74.fc14.x86_64
package: rhythmbox-0.13.2-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296158009
uid: 500

How to reproduce
-----
1. I run Rhythmbox with the MTP Plugin enabled and connect my MP3 Player via the USB Port
2. Rhythmbox recognizes the MP3 Player and displays it
3. Inside Rhythmbox, when I right-click my MP3 Player and choose properties, Rhythmbox crashes every time.

Comment 1 kibokin 2011-01-27 20:05:11 UTC
Created attachment 475674 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 16:50:11 UTC
Backtrace analysis found this bug to be similar to bug #701746, closing as duplicate.

Bugs which were found to be similar to this bug: bug #655198, bug #662252, bug #679724, bug #701746

This comment is automatically generated.

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


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