Bug 604998 - [abrt] crash in tracker-0.8.4-1.fc13: __memcpy_ssse3: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in tracker-0.8.4-1.fc13: __memcpy_ssse3: Process /usr/libexec/tr...
Keywords:
Status: CLOSED DUPLICATE of bug 603771
Alias: None
Product: Fedora
Classification: Fedora
Component: gstreamer-plugins-bad-free
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Benjamin Otte
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:641e2f0836cec60e6623f014407...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-17 09:15 UTC by Alfredo Pons Menargues
Modified: 2010-06-17 12:35 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-17 12:35:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (66.96 KB, text/plain)
2010-06-17 09:15 UTC, Alfredo Pons Menargues 		no flags Details
The file (73.73 KB, image/x-portable-pixmap)
2010-06-17 09:18 UTC, Alfredo Pons Menargues 		no flags Details
View All

Description Alfredo Pons Menargues 2010-06-17 09:15:23 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/tracker-extract
component: tracker
crash_function: __memcpy_ssse3
executable: /usr/libexec/tracker-extract
global_uuid: 641e2f0836cec60e6623f014407a8c8c416d4149
kernel: 2.6.33.5-112.fc13.i686
package: tracker-0.8.4-1.fc13
rating: 4
reason: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Alfredo Pons Menargues 2010-06-17 09:15:30 UTC 
Created attachment 424727 [details]
File: backtrace
Comment 2 Alfredo Pons Menargues 2010-06-17 09:18:05 UTC 
Created attachment 424728 [details]
The file

I  attach the file
Comment 3 Deji Akingunola 2010-06-17 12:28:53 UTC 
@gstreamer maintainer,

Here is another variation of Bug 603771.
Comment 4 Benjamin Otte 2010-06-17 12:35:38 UTC 

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