Application: kwin (4.11.18) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 4.0.4-202.fc21.x86_64 x86_64 Distribution: "Fedora release 21 (Twenty One)" -- Information about the crash: - What I was doing when the application crashed: Logged into KDE (Plasma) This was after reinstalling nvidia drivers (346.72-2) -- Backtrace: Application: KWin (kwin), signal: Aborted Using host libthread_db library "/usr/lib64/libthread_db.so.1". 81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #6 0x00007f31ed25a8d7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x00007f31ed25c53a in __GI_abort () at abort.c:89 #8 0x00007f31ed25347d in __assert_fail_base (fmt=0x7f31ed3accb8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f31f3d1af50 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f31f3d1adab "xcb_io.c", line=line@entry=274, function=function@entry=0x7f31f3d1b256 "poll_for_event") at assert.c:92 #9 0x00007f31ed253532 in __GI___assert_fail (assertion=0x7f31f3d1af50 "!xcb_xlib_threads_sequence_lost", file=0x7f31f3d1adab "xcb_io.c", line=274, function=0x7f31f3d1b256 "poll_for_event") at assert.c:101 #10 0x00007f31f3ca7ad9 in () at /usr/lib64/libX11.so.6 #11 0x00007f31f3ca7b8b in poll_for_response () at /usr/lib64/libX11.so.6 #12 0x00007f31f3ca7e9d in _XEventsQueued () at /usr/lib64/libX11.so.6 #13 0x00007f31f3caac35 in _XGetRequest () at /usr/lib64/libX11.so.6 #14 0x00007f31ee035f02 in SendMakeCurrentRequest () at /usr/lib64/libGL.so.1 #15 0x00007f31ee035ff9 in indirect_bind_context () at /usr/lib64/libGL.so.1 #16 0x00007f31ee0335e7 in glXMakeCurrentReadSGI () at /usr/lib64/libGL.so.1 #17 0x00007f31f56ab942 in KWin::GlxBackend::initRenderingContext() () at /usr/lib64/libkdeinit4_kwin.so #18 0x00007f31f56abe49 in KWin::GlxBackend::init() () at /usr/lib64/libkdeinit4_kwin.so #19 0x00007f31f56a641c in KWin::SceneOpenGL::createScene() () at /usr/lib64/libkdeinit4_kwin.so #20 0x00007f31f56889d8 in KWin::Compositor::slotCompositingOptionsInitialized() () at /usr/lib64/libkdeinit4_kwin.so #21 0x00007f31f5608305 in KWin::Compositor::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.47] () at /usr/lib64/libkdeinit4_kwin.so #22 0x00007f31ef5abd9c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #23 0x00007f31ef47d462 in QFutureWatcherBase::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #24 0x00007f31ee6ceefc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #25 0x00007f31ee6d5958 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #26 0x00007f31f02bae0a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #27 0x00007f31ef59722d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #28 0x00007f31ef59a4f1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #29 0x00007f31ee7728ec in QEventDispatcherX11::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtGui.so.4 #30 0x00007f31ef595d81 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #31 0x00007f31ef5960e5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #32 0x00007f31ef59b7c9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #33 0x00007f31f563b048 in kdemain () at /usr/lib64/libkdeinit4_kwin.so #34 0x00007f31ed245fe0 in __libc_start_main (main=0x4009d0 <main>, argc=3, argv=0x7ffc1f653c68, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc1f653c58) at libc-start.c:289 #35 0x00000000004009fe in _start () Possible duplicates by query: bug 347734, bug 346854, bug 344371, bug 341645, bug 337359. Reported using DrKonqi
looks a bit like bug #327310, but smells more like a broken driver installation (nvidia ./. MESA) => What's the ouput of "glxinfo"?
I think this is related to a bad symlink after updating nvidia. I changed /usr/lib64/libGL.so.1 to reference /usr/lib64/nvidia/libGL.so.1 instead (before it was referencing /usr/lib64/libGL.so.1.2.0). I had previously run glxgears and saw this: libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast And my other opengl applications had the same problem. Now they work fine
Yupp, broken driver installation - if you installed nvidia through your distro (ie. their package is broken) please report to them.
Created attachment 94005 [details] New crash information added by DrKonqi kwin (4.11.16) on KDE Platform 4.14.5 using Qt 4.8.6 - What I was doing when the application crashed:Grafik GT210 auflösung verändert - Unusual behavior I noticed: - Custom settings of the application: Mit dem älteren Treiber von Mageia 4.1 ist das System einwandfrei gelaufen -- Backtrace (Reduced): #9 0x00007ff7ced64559 in poll_for_event () from /lib64/libX11.so.6 #10 0x00007ff7ced645ee in poll_for_response () from /lib64/libX11.so.6 #11 0x00007ff7ced648cd in _XEventsQueued () from /lib64/libX11.so.6 #12 0x00007ff7ced56880 in XEventsQueued () from /lib64/libX11.so.6 #13 0x00007ff7cace6e4a in QEventDispatcherX11::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtGui.so.4
Das Problem ist iA. eine falsch aufgelöste Treiberbibliothek - jedes GL Programm (glxgears, glxinfo) wird crashen. ls -l /usr/lib/libGL.*so* nvidias Bibliotheken enden zB. "so.352.21" - alles andere sind zu nvidia inkompatible MESA Bibliotheken. Alternativ bin ich nicht sicher, ob die GT210 schon in den legacy support gefallen ist (also mit den allerbrandneuesten Treibern nicht mehr funktioniert - das README gibt dazu Auskunft) PS: Wenn Du so auch nur sowas ähnliches wie Englisch sprichst, ist das die bevorzugte Sprache (erreicht wesentliche mehr Leute)