totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gstreamer1.0 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
lsb_release -rd;apt-cache policy totem
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
totem:
Installed: 3.10.1-1ubuntu3
Candidate: 3.10.1-1ubuntu3
Version table:
*** 3.10.1-1ubuntu3 0
500 http://
100 /var/lib/
I opened nautilus and this seems to happen anytime there are videos in the folder
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libgstreamer1.0-0 1.2.3-1
ProcVersionSign
Uname: Linux 3.13.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sun Mar 9 22:36:31 2014
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2014-03-09 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140309)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f32af6df297 <g_slice_
PC (0x7f32af6df297) ok
source "(%rbx)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%rax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gstreamer1.0
StacktraceTop:
g_slice_alloc () from /lib/x86_
g_slice_alloc0 () from /lib/x86_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: totem-video-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1289125, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.