totem-video-thumbnailer crashed with SIGSEGV in oil_init()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
totem (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I was viewing a couple folders of video files in pcmanfm on a Lubuntu 11.10 i386 system. One folder was of .mkv files; the other was of .avi files. Nothing seemed to go wrong--pcmanfm did not itself crash, and all the files were properly thumbnailed. I was not using Totem itself to open any of the files, but I was playing some with VLC.
Apport informed me that totem had crashed, and when I saw the crash was in the binary totem-video-
This crash resembles these other two bugs:
https:/
https:/
But I cannot yet tell if it is really the same as either. It's also a little similar to these bugs:
https:/
https:/
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: totem 3.4.3-0ubuntu5
ProcVersionSign
Uname: Linux 3.2.0-39-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
Date: Sun Mar 31 21:57:34 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2012-08-21 (222 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MarkForUpload: True
ProcCmdline: /usr/bin/
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x1d98ce28: mov 0x10(%eax),%edx
PC (0x1d98ce28) ok
source "0x10(%eax)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%edx" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/
oil_init () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: totem-video-
UpgradeStatus: Upgraded to quantal on 2013-03-21 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #403110, 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.