Bug 699095

Summary: [abrt] totem-1:2.32.0-1.fc14: Process /usr/bin/totem-video-thumbnailer was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Dario Meloni <mellon85>
Component: totemAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bnocera, jeff.raber
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:40fd74e3d2f57d8d87a0a89d189700412359676b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-30 23:38:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Dario Meloni 2011-04-23 03:40:22 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 40720 bytes
cmdline: /usr/bin/totem-video-thumbnailer -s 128 file:///home/dario/Desktop/Data/Community%20-%202x21%20-%20Paradigms%20of%20Human%20Memory.mkv /tmp/.gnome_desktop_thumbnail.IP5MUV
comment: It may be caused by inconsistency in the header of the file wrt missing data. but it shouldn't crash.
component: totem
Attached file: coredump, 84725760 bytes
crash_function: gst_matroska_demux_search_cluster
executable: /usr/bin/totem-video-thumbnailer
kernel: 2.6.35.12-88.fc14.x86_64
package: totem-1:2.32.0-1.fc14
rating: 4
reason: Process /usr/bin/totem-video-thumbnailer was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1303529681
uid: 500

How to reproduce
-----
1. interrupt a copy operation of a video file when a small amount of data has been copied
2. open the nautilus folder where was been saved
Comment 1 Dario Meloni 2011-04-23 03:40:25 UTC 
Created attachment 494363 [details]
File: backtrace
Comment 2 Jeff Raber 2011-04-30 23:38:19 UTC 
Marking as a duplicate of 664606 as the stack-trace indicates that this is the same bug.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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