kwin_opengl_test crashed with SIGSEGV in XF86DRIQueryVersion()

Bug #647610 reported by aanno
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: kdebase-workspace

Log-in on KDE after rebooting 10.10-beta (maverick)

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: kdebase-workspace-bin 4:4.5.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sat Sep 25 17:48:08 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/kde4/libexec/kwin_opengl_test
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcCmdline: /usr/lib/kde4/libexec/kwin_opengl_test
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
SegvAnalysis:
 Segfault happened at: 0x7f31b3ba838e <XF86DRIQueryVersion+174>: mov 0x4(%rax),%eax
 PC (0x7f31b3ba838e) ok
 source "0x4(%rax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdebase-workspace
StacktraceTop:
 XF86DRIQueryVersion () from /usr/lib/fglrx/libGL.so.1
 XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 ?? () from /usr/lib/fglrx/libGL.so.1
 ?? () from /usr/lib/fglrx/libGL.so.1
 glXQueryVersion () from /usr/lib/fglrx/libGL.so.1
Title: kwin_opengl_test crashed with SIGSEGV in XF86DRIQueryVersion()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (process:2039): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
aanno (thomas-pasch) wrote :
aanno (thomas-pasch)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XF86DRIQueryVersion ()
 XF86DRIQueryExtension ()
 ?? () from /usr/lib/fglrx/libGL.so.1
 ?? () from /usr/lib/fglrx/libGL.so.1
 glXQueryVersion () from /usr/lib/fglrx/libGL.so.1

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in kdebase-workspace (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
affects: kdebase-workspace (Ubuntu) → fglrx-installer (Ubuntu)
Bryce Harrington (bryce)
tags: added: kubuntu
Revision history for this message
bugbot (bugbot) wrote :

Hey aanno,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

Changed in fglrx-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
Grgoffe (grgoffe) wrote :
Download full text (3.8 KiB)

Howdy,

I'm not running Ubuntu yet but you might be interested in this info anyway. This is Fedora Core 14, fully up to date. I did an "Ask.com" search and got a hit on this code. I have filed a bug at bugzilla.redhat.com.

I get corefiles frequently from this code: /usr/libexec/kde4/kwin_opengl_test. Did it come from ATI? Should I file a bug with them for this?

I keep getting core files with the following gdb info. They seem to appear in relation to logging out from KDE 4.5.5 but may be happening at other times as well. Periodically I get a strange event on the display. It's like the monitor got a shock. It seems to show the contents of a buffer that QUICKLY re-asserts itself before you can read it. Maybe a core file results from this? I'll start watching... Just got an event... checking... Argh! No perceivable timestamps... I'll include my "current" Xorg.0.log file...

Anything I can do to help with this bug?

George...

gdb core.3943
GNU gdb (GDB) Fedora (7.2-45.fc14)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...

warning: core file may not match specified executable file.
Reading symbols from /usr/libexec/kde4/kwin_opengl_test...Reading symbols from /usr/lib/debug/usr/libexec/kde4/kwin_opengl_test.debug...done.
done.
[New Thread 3943]
Missing separate debuginfo for
Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/25/7d0d6467b9f4374470e0384a3e602be99b058e
Reading symbols from /usr/lib/libXau.so.6.0.0...Reading symbols from /usr/lib/debug/usr/lib/libXau.so.6.0.0.debug...done.
done.
Loaded symbols for /usr/lib/libXau.so.6.0.0
Reading symbols from /usr/lib/libXdmcp.so.6.0.0...Reading symbols from /usr/lib/debug/usr/lib/libXdmcp.so.6.0.0.debug...done.
done.
Loaded symbols for /usr/lib/libXdmcp.so.6.0.0
Reading symbols from /usr/lib/libGL.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libGL.so.1
Reading symbols from /lib/libm-2.13.so...Reading symbols from /usr/lib/debug/lib/libm-2.13.so.debug...done.
done.
Loaded symbols for /lib/libm-2.13.so
Reading symbols from /lib/libc-2.13.so...Reading symbols from /usr/lib/debug/lib/libc-2.13.so.debug...done.
done.
Loaded symbols for /lib/libc-2.13.so
Reading symbols from /lib/libdl-2.13.so...Reading symbols from /usr/lib/debug/lib/libdl-2.13.so.debug...done.
done.
Loaded symbols for /lib/libdl-2.13.so
Reading symbols from /lib/libpthread-2.13.so...Reading symbols from /usr/lib/debug/lib/libpthread-2.13.so.debug...done.
[Thread debugging using libthread_db enabled]
done.
Loaded symbols for /lib/libpthread-2.13.so
Reading symbols from /usr/lib/libatiuki.so.1...done.
Loaded symbols for /usr/lib/libatiuki.so.1
Reading symbols from /lib/ld-2.13.so...Reading symbols from /usr/lib/debug/lib/ld-2.13.so.debug...done.
done.
Loaded symbols for /lib/ld-2.13.s...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for fglrx-installer (Ubuntu) because there has been no activity for 60 days.]

Changed in fglrx-installer (Ubuntu):
status: Incomplete → Expired
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.