Bug 621074 - [abrt] crash in totem-mozplugin-2.30.2-1.fc13: Process /usr/libexec/totem-plugin-viewer was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in totem-mozplugin-2.30.2-1.fc13: Process /usr/libexec/totem-plu...
Keywords:
Status: CLOSED DUPLICATE of bug 622233
Alias: None
Product: Fedora
Classification: Fedora
Component: totem
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:df9a1ba655fe87d4a682e32e00b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-04 07:53 UTC by Bug Reporter
Modified: 2010-11-09 15:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 15:13:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (82.73 KB, text/plain)
2010-08-04 07:53 UTC, Bug Reporter
no flags Details

Description Bug Reporter 2010-08-04 07:53:23 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/totem-plugin-viewer --plugin-type gmp --user-agent Windows-Media-Player/10.00.00.4019 --referrer http://www.ketaketa.com/portfolio/work/kevin-janice-world/ --mimetype video/x-msvideo --no-autostart
component: totem
executable: /usr/libexec/totem-plugin-viewer
global_uuid: df9a1ba655fe87d4a682e32e00b5502e5b71db45
kernel: 2.6.33.6-147.2.4.fc13.i686.PAE
package: totem-mozplugin-2.30.2-1.fc13
rating: 4
reason: Process /usr/libexec/totem-plugin-viewer was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 Bug Reporter 2010-08-04 07:53:29 UTC
Created attachment 436461 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:13:26 UTC

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

Comment 3 Karel Klíč 2010-11-09 15:13:26 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 #622233.

Sorry for the inconvenience.


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