vlc crashed with SIGSEGV in vaInitialize()

[Texas Jack]

Binary package hint: vlc

Description: Ubuntu Natty (development branch)
Release: 11.04

vlc:
  Installed: 1.1.9-1ubuntu1
  Candidate: 1.1.9-1ubuntu1
  Version table:
 *** 1.1.9-1ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages
        100 /var/lib/dpkg/status

Expected to see a .mp4 video, but when I opened the file VLC just 'freeze'. At the first click or movement inside the app's window they just crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: vlc-nox 1.1.9-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sun Apr 17 11:49:29 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/vlc
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcCmdline: vlc
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f89625df5d1: movdqu (%rdi),%xmm1
 PC (0x7f89625df5d1) 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
 vaInitialize () from /usr/lib/libva.so.1
 ?? () from /usr/lib/vlc/plugins/codec/libavcodec_plugin.so
 ?? () from /usr/lib/vlc/plugins/codec/libavcodec_plugin.so
 ?? () from /usr/lib/libavcodec.so.52
Title: vlc crashed with SIGSEGV in vaInitialize()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #754802, 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.