Application: kwin (4.10.1) KDE Platform Version: 4.10.1 Qt Version: 4.8.4 Operating System: Linux 3.5.0-22-generic x86_64 Distribution: Ubuntu Raring Ringtail (development branch) -- Information about the crash: - What I was doing when the application crashed: I restarted the system and dr konqi appeared on shutdown but I could not interact with it and did not have time to identify the application before the system shutdown. On restarting dr konqi was sitting on the desktop waiting to file this report. I had reccently upgraded Kubuntu to 13.04 and have been trying to get the fglrx driver to work. -- Backtrace: Application: KWin (kwin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbe487eb7c0 (LWP 2793))] Thread 2 (Thread 0x7fbe27de9700 (LWP 2799)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fbe44a09e77 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x00007fbe44a09ea9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x00007fbe3bd8ff8e in start_thread (arg=0x7fbe27de9700) at pthread_create.c:311 #4 0x00007fbe4811ae1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7fbe487eb7c0 (LWP 2793)): [KCrash Handler] #6 0x00007fbe4404c74e in glXGetFBConfigs () from /usr/lib/fglrx/libGL.so.1 #7 0x00007fbe484b5c68 in KWin::GlxBackend::initDrawableConfigs (this=this@entry=0x983090) at ../../kwin/glxbackend.cpp:323 #8 0x00007fbe484b62aa in KWin::GlxBackend::init (this=0x983090) at ../../kwin/glxbackend.cpp:88 #9 0x00007fbe484afe87 in KWin::SceneOpenGL::createScene () at ../../kwin/scene_opengl.cpp:224 #10 0x00007fbe4849aba5 in KWin::Compositor::slotCompositingOptionsInitialized (this=0xaba3d0) at ../../kwin/composite.cpp:206 #11 0x00007fbe435910df in QMetaObject::activate (sender=0xa8a250, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539 #12 0x00007fbe43470577 in QFutureWatcherBase::event (this=<optimized out>, event=0x7fbe200008c0) at concurrent/qfuturewatcher.cpp:344 #13 0x00007fbe429228ec in QApplicationPrivate::notify_helper (this=this@entry=0x907820, receiver=receiver@entry=0xa8a250, e=e@entry=0x7fbe200008c0) at kernel/qapplication.cpp:4567 #14 0x00007fbe4292525b in QApplication::notify (this=0x7fffd0fc67f0, receiver=0xa8a250, e=0x7fbe200008c0) at kernel/qapplication.cpp:4428 #15 0x00007fbe47c05af6 in KApplication::notify (this=0x7fffd0fc67f0, receiver=0xa8a250, event=0x7fbe200008c0) at ../../kdeui/kernel/kapplication.cpp:311 #16 0x00007fbe4357c62e in QCoreApplication::notifyInternal (this=0x7fffd0fc67f0, receiver=receiver@entry=0xa8a250, event=event@entry=0x7fbe200008c0) at kernel/qcoreapplication.cpp:946 #17 0x00007fbe43580161 in sendEvent (event=0x7fbe200008c0, receiver=0xa8a250) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #18 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x89f1f0) at kernel/qcoreapplication.cpp:1570 #19 0x00007fbe429c89fc in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #20 QEventDispatcherX11::processEvents (this=0x8a0ad0, flags=...) at kernel/qeventdispatcher_x11.cpp:75 #21 0x00007fbe4357b37f in QEventLoop::processEvents (this=this@entry=0x7fffd0fc6500, flags=...) at kernel/qeventloop.cpp:149 #22 0x00007fbe4357b608 in QEventLoop::exec (this=0x7fffd0fc6500, flags=...) at kernel/qeventloop.cpp:204 #23 0x00007fbe43580ce6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #24 0x00007fbe48450c6a in kdemain (argc=3, argv=0x7fffd0fc6938) at ../../kwin/main.cpp:537 #25 0x00007fbe48042ea5 in __libc_start_main (main=0x4006d0 <main(int, char**)>, argc=3, ubp_av=0x7fffd0fc6938, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffd0fc6928) at libc-start.c:260 #26 0x0000000000400701 in _start () This bug may be a duplicate of or related to bug 314602. Possible duplicates by query: bug 314602. Reported using DrKonqi
Attach you /var/log/Xorg.0.log but it's likely the same issue (mixed installation between fglrx & mesa) *** This bug has been marked as a duplicate of bug 314602 ***
Created attachment 78120 [details] Xorg.0.log As requested.
.......... [ 73.414] (==) Matched fglrx as autoconfigured driver 0 [ 73.414] (==) Matched ati as autoconfigured driver 1 [ 73.414] (==) Matched fglrx as autoconfigured driver 2 [ 73.414] (==) Matched ati as autoconfigured driver 3 [ 73.414] (==) Matched vesa as autoconfigured driver 4 [ 73.414] (==) Matched modesetting as autoconfigured driver 5 [ 73.415] (==) Matched fbdev as autoconfigured driver 6 [ 73.415] (==) Assigned the driver to the xf86ConfigLayout [ 73.415] (II) LoadModule: "fglrx" [ 73.489] (WW) Warning, couldn't open module fglrx [ 73.489] (II) UnloadModule: "fglrx" [ 73.489] (II) Unloading fglrx [ 73.489] (EE) Failed to load module "fglrx" (module does not exist, 0) .......... [ 73.783] (II) RADEON(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 73.783] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 [ 73.783] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 73.783] (==) RADEON(0): Default visual is TrueColor .......... and from the crash: #6 0x00007fbe4404c74e in glXGetFBConfigs () from /usr/lib/fglrx/libGL.so.1 => you're using the radeon Xorg driver (xf86-video-ati) but still the GL library from fglrx. Is dupe, either ensure to install the fglrx X11 driver or get rid of its OpenGL leftovers. And please tell Canonical to fix up their packages You're the second reporter *here* to run into this and the packages should contain a conflict or some script post un/installation to fix path exports.