Bug 620048 - [abrt] crash in totem-2.30.2-1.fc13: pre_resample: Process /usr/bin/totem-video-indexer was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in totem-2.30.2-1.fc13: pre_resample: Process /usr/bin/totem-vid...
Status: CLOSED DUPLICATE of bug 641435
Alias: None
Product: Fedora
Classification: Fedora
Component: totem   
(Show other bugs)
Version: 13
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:9c52510e74dbfc08a3b2def1591...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-31 16:21 UTC by David M.
Modified: 2010-11-08 19:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-08 19:49:37 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (22.94 KB, text/plain)
2010-07-31 16:21 UTC, David M.
no flags Details

Description David M. 2010-07-31 16:21:07 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: totem-video-indexer /home/dmcinnis63/midi/Star_Trek_Voyager.mid
comment: ???
component: totem
crash_function: pre_resample
executable: /usr/bin/totem-video-indexer
global_uuid: 9c52510e74dbfc08a3b2def15910b130a52f0b52
package: totem-2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/totem-video-indexer was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1.  Opened midi.

Comment 1 David M. 2010-07-31 16:21:08 UTC
Created attachment 435764 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 19:49:37 UTC

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

Comment 3 Karel Klíč 2010-11-08 19:49:37 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 #641435.

Sorry for the inconvenience.

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