I've been having two problems, one of which is quite definitely caused by the openGL library of fglrx:
1) when I try to load warzone 2100 I get a segmentation fault and according to the developers the game dump file contains the line:
#5 0x00670ef6 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
which indicates something broken with fglrx.The game was running smoothly up to about a week ago.
2)When I try to configure my desktop using system settings the system settings application crashes with the crash report showing this line:
#6 0x035b7ef6 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
which seems to have no meaningful difference from the warzone line problem. The whole bug report is :
Code:
Application: System Settings (systemsettings), signal: Segmentation fault
[Current thread is 1 (Thread 0xb78b2710 (LWP 15072))]
Thread 2 (Thread 0xb4a61b70 (LWP 15073)):
#0 0x00ab4422 in __kernel_vsyscall ()
#1 0x005e0b86 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0x025204eb in g_poll () from /lib/libglib-2.0.so.0
#3 0x025130ac in ?? () from /lib/libglib-2.0.so.0
#4 0x025134b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5 0x00d0f60f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#6 0x00ce2059 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#7 0x00ce24aa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#8 0x00bde5a8 in QThread::exec() () from /usr/lib/libQtCore.so.4
#9 0x00cc1c1b in ?? () from /usr/lib/libQtCore.so.4
#10 0x00be132e in ?? () from /usr/lib/libQtCore.so.4
#11 0x006a196e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#12 0x005eea4e in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 1 (Thread 0xb78b2710 (LWP 15072)):
[KCrash Handler]
#6 0x035b7ef6 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
#7 0x051aaff4 in ?? () from /usr/lib/libX11.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
if it helps.
Does anyone know how I solve this problem?