Bug 649270 - [abrt] rhythmbox-0.13.1-1.fc14: rb_shell_guess_source_for_uri: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] rhythmbox-0.13.1-1.fc14: rb_shell_guess_source_for_uri: Process /usr/b...
Keywords:
Status: CLOSED DUPLICATE of bug 673001
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:55bf96fdb982cefa8967e4078af...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-03 12:24 UTC by Dmitrij Rebrov
Modified: 2012-03-21 17:54 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-21 17:54:27 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (27.30 KB, text/plain)
2010-11-03 12:24 UTC, Dmitrij Rebrov 		no flags Details
View All

Description Dmitrij Rebrov 2010-11-03 12:24:56 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: rhythmbox /home/aliaric/.opera/temporary_downloads/high.m3u
component: rhythmbox
crash_function: rb_shell_guess_source_for_uri
executable: /usr/bin/rhythmbox
kernel: 2.6.35.6-48.fc14.i686
package: rhythmbox-0.13.1-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288785697
uid: 500

How to reproduce
-----
1. I tried to open .m3u file with rhythmbox from opera 10.63
2. ...and then rhythmbox crashed
3.
Comment 1 Dmitrij Rebrov 2010-11-03 12:24:59 UTC 
Created attachment 457417 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 17:54:27 UTC 
Backtrace analysis found this bug to be similar to bug #673001, closing as duplicate.

Bugs which were found to be similar to this bug: bug #652466, bug #657955, bug #658454, bug #667068, bug #668883, bug #673001, bug #702397, bug #702604

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 673001 ***
Note You need to log in before you can comment on or make changes to this bug.