vlc crashed with SIGSEGV in AGER_Term()

[Alex Mauer]

Binary package hint: vlc

This happened upon closing VLC after playing a DVD

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: vlc-nox 1.0.6-1ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Tue May 18 21:26:40 2010
ExecutablePath: /usr/bin/vlc
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: vlc
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7fc6370d1b0b: mov %rax,(%rdx)
 PC (0x7fc6370d1b0b) ok
 source "%rax" ok
 destination "(%rdx)" (0x7fc6374440e8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
 ?? () from /usr/lib/fglrx/libGL.so.1
 AGER_Term () from /usr/lib/fglrx/libGL.so.1
 ?? () from /usr/lib/fglrx/dri/fglrx_dri.so
 ?? () from /usr/lib/fglrx/dri/fglrx_dri.so
 ?? () from /usr/lib/fglrx/dri/fglrx_dri.so
Title: vlc crashed with SIGSEGV in AGER_Term()
UserGroups: Domain Admins Domain Users adm admin cdrom lpadmin sambashare video

[Apport retracing service (apport)]

StacktraceTop:
 ?? () from /usr/lib/fglrx/libGL.so.1
 AGER_Term () from /usr/lib/fglrx/libGL.so.1
 ?? () from /usr/lib/fglrx/dri/fglrx_dri.so
 ?? () from /usr/lib/fglrx/dri/fglrx_dri.so
 ?? () from /usr/lib/fglrx/dri/fglrx_dri.so

[Rémi Denis-Courmont (rdenis)]

This bug cannot be investigated as the retracing failed. That said, it looks like a problem in FGLRX

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for posting this bug.

Does this happen in Maverick?

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. My apologies as I should not have marked this Invalid. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.