kwin_opengl_test crashed with SIGSEGV in XF86DRIQueryExtension()

[Braiam Peguero]

Binary package hint: kdebase-workspace

I installed kde yesterday. When I want to login, the screen show at start, after that I have no panels, no key binds and a useless desktop. I can't even change to the tty's. When I reboot and start with gnome this report has generated.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: kde-window-manager 4:4.6.2a-0ubuntu5.1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CheckboxSubmission: 453209310f36aec088f7597a7838878c
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Fri Jun 3 10:58:06 2011
ExecutablePath: /usr/lib/kde4/libexec/kwin_opengl_test
ProcCmdline: /usr/lib/kde4/libexec/kwin_opengl_test
ProcEnviron:
 LANGUAGE=es:do
 PATH=(custom, user)
 LANG=es_DO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb72824 <XF86DRIQueryExtension+142>: movzbl 0x4(%esi),%edx
 PC (0x00b72824) ok
 source "0x4(%esi)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace:
 #0 0x00b72824 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 No symbol table info available.
 #1 0x005f9ae6 in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 No symbol table info available.
StacktraceTop:
 XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: kwin_opengl_test crashed with SIGSEGV in XF86DRIQueryExtension()
UpgradeStatus: Upgraded to natty on 2011-06-01 (1 days ago)
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 #757321, 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.