Bug 617839 - [abrt] crash in totem-2.30.2-1.fc13: magazine_chain_pop_head: Process /usr/bin/totem was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in totem-2.30.2-1.fc13: magazine_chain_pop_head: Process /usr/bi...
Keywords:
Status: CLOSED DUPLICATE of bug 603977
Alias: None
Product: Fedora
Classification: Fedora
Component: totem
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6e4d2e9b5f715592892396b5f88...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-24 10:26 UTC by Serg Merkelov
Modified: 2010-11-09 13:23 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:23:49 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (98.47 KB, text/plain)
2010-07-24 10:26 UTC, Serg Merkelov 		no flags Details
View All

Description Serg Merkelov 2010-07-24 10:26:13 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: totem '/home/storage2/Music/\xd0\x9f\xd0\xb8\xd0\xba\xd0\xbd\xd0\xb8\xd0\xba/2010 - \xd0\xa2\xd0\xb5\xd0\xb0\xd1\x82\xd1\x80 \xd0\x90\xd0\xb1\xd1\x81\xd1\x83\xd1\x80\xd0\xb4\xd0\xb0.m3u'
component: totem
crash_function: magazine_chain_pop_head
executable: /usr/bin/totem
global_uuid: 6e4d2e9b5f715592892396b5f889e1715310e899
kernel: 2.6.33.6-147.fc13.x86_64
package: totem-2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/totem was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.change volume
2.
3.
Comment 1 Serg Merkelov 2010-07-24 10:26:20 UTC 
Created attachment 434127 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:23:49 UTC 

*** This bug has been marked as a duplicate of bug 603977 ***
Comment 3 Karel Klíč 2010-11-09 13:23:49 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 #603977.

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