vlc crashed with SIGSEGV when trying to play m4v file

Bug #959058 reported by sean.h.muir@gmail.com
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vlc (Ubuntu)
New
Undecided
Unassigned

Bug Description

was trying to play a m4v file and vlc didnt even open

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: vlc-nox 2.0.0-4
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 19 07:29:14 2012
ExecutablePath: /usr/bin/vlc
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /usr/bin/vlc /home/User Name/.cache/gvfs/disk_b1\ on\ 192.168.1.253/Media/Movies/Batman\ Begins/Batman\ Begins.m4v
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fee83bf8561: movdqu (%rdi),%xmm1
 PC (0x7fee83bf8561) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/vlc/plugins/demux/libmp4_plugin.so
 ?? () from /usr/lib/vlc/plugins/demux/libmp4_plugin.so
 ?? () from /usr/lib/vlc/plugins/demux/libmp4_plugin.so
 ?? () from /usr/lib/vlc/plugins/demux/libmp4_plugin.so
Title: vlc crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-03-13 (5 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
sean.h.muir@gmail.com (sean-h-muir) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #936488, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.