Bug 573381 - [abrt] crash in totem-2.28.5-1.fc12: Process /usr/bin/totem was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in totem-2.28.5-1.fc12: Process /usr/bin/totem was killed by sig...
Keywords:
Status: CLOSED DUPLICATE of bug 590323
Alias: None
Product: Fedora
Classification: Fedora
Component: totem
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d16a48cf83731d455ab7cca2f8b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-14 14:32 UTC by Pavel Mezhuyev
Modified: 2010-05-25 09:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:05:54 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (76.40 KB, text/plain)
2010-03-14 14:32 UTC, Pavel Mezhuyev 		no flags Details
View All

Description Pavel Mezhuyev 2010-03-14 14:32:08 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: totem '/home/lordbeaver/\xd0\x9c\xd1\x83\xd0\xb7\xd1\x8b\xd0\xba\xd0\xb0/\xd0\x9c\xd0\xb5\xd0\xbb\xd1\x8c\xd0\xbd\xd0\xb8\xd1\x86\xd0\xb0/\xd0\x97\xd0\xbe\xd0\xb2 \xd0\xba\xd1\x80\xd0\xbe\xd0\xb2\xd0\xb8/01 - \xd0\x9d\xd0\xb5\xd0\xb2\xd0\xb5\xd1\x81\xd1\x82\xd0\xb0 \xd0\x9f\xd0\xbe\xd0\xbb\xd0\xbe\xd0\xb7\xd0\xb0.flac'
component: totem
executable: /usr/bin/totem
kernel: 2.6.32.9-70.fc12.x86_64
package: totem-2.28.5-1.fc12
rating: 4
reason: Process /usr/bin/totem was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 Pavel Mezhuyev 2010-03-14 14:32:11 UTC 
Created attachment 399989 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:05:54 UTC 

*** This bug has been marked as a duplicate of bug 590323 ***
Comment 3 Karel Klíč 2010-05-25 09:05:54 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 #590323.

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