Bug 324580

Summary: Kwin crash on login after mesa update
Product: [Plasma] kwin Reporter: wintonian <bugzilla>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash Keywords: drkonqi
Priority: NOR    
Version First Reported In: 4.10.5   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description wintonian 2013-09-06 12:00:52 UTC 
Application: kwin (4.10.5)
KDE Platform Version: 4.10.5
Qt Version: 4.8.5
Operating System: Linux 3.10.10-200.fc19.x86_64 x86_64
Distribution: "Fedora release 19 (Schrödinger’s Cat)"

-- Information about the crash:
- What I was doing when the application crashed:

Restarted after mesa (and others) update.

I now have severe screen tareing and catalyst crashes on trying to start it.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  xcb_glx_query_server_string_string_length (R=R@entry=0x0) at glx.c:2448
#7  0x0000003baa63ae35 in __glXQueryServerString (dpy=dpy@entry=0x1524590, opcode=<optimized out>, screen=screen@entry=0, name=name@entry=2) at glx_query.c:55
#8  0x0000003baa61c606 in AllocAndFetchScreenConfigs (priv=0x16a5160, dpy=0x1524590) at glxext.c:764
#9  __glXInitialize (dpy=0x1524590) at glxext.c:879
#10 0x0000003baa618871 in glXQueryVersion (dpy=<optimized out>, major=0x7fff47ff5a08, minor=0x7fff47ff5a0c) at glxcmds.c:487
#11 0x0000003bab40f24d in KWin::initGLX () at /usr/src/debug/kde-workspace-4.10.5/kwin/libkwineffects/kwinglutils.cpp:75
#12 0x0000003baa2cb736 in KWin::GlxBackend::init (this=0x15f18a0) at /usr/src/debug/kde-workspace-4.10.5/kwin/glxbackend.cpp:82
#13 0x0000003baa2c5691 in KWin::SceneOpenGL::createScene () at /usr/src/debug/kde-workspace-4.10.5/kwin/scene_opengl.cpp:233
#14 0x0000003baa2af995 in KWin::Compositor::slotCompositingOptionsInitialized (this=0x16546b0) at /usr/src/debug/kde-workspace-4.10.5/kwin/composite.cpp:206
#15 0x0000003baa23a355 in KWin::Compositor::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at /usr/src/debug/kde-workspace-4.10.5/x86_64-redhat-linux-gnu/kwin/moc_composite.cpp:112
#16 0x0000003e8418df78 in QMetaObject::activate (sender=0x1671d80, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#17 0x0000003e8406bb58 in QFutureWatcherBase::event (this=<optimized out>, event=0x7f64140008c0) at concurrent/qfuturewatcher.cpp:344
#18 0x0000003e86dc84dc in QApplicationPrivate::notify_helper (this=this@entry=0x14f8a80, receiver=receiver@entry=0x1671d80, e=e@entry=0x7f64140008c0) at kernel/qapplication.cpp:4562
#19 0x0000003e86dceaa0 in QApplication::notify (this=this@entry=0x7fff47ff64c0, receiver=receiver@entry=0x1671d80, e=e@entry=0x7f64140008c0) at kernel/qapplication.cpp:4348
#20 0x0000003e880415ba in KApplication::notify (this=0x7fff47ff64c0, receiver=0x1671d80, event=0x7f64140008c0) at /usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311
#21 0x0000003e8417a26d in QCoreApplication::notifyInternal (this=0x7fff47ff64c0, receiver=receiver@entry=0x1671d80, event=event@entry=0x7f64140008c0) at kernel/qcoreapplication.cpp:949
#22 0x0000003e8417d1df in sendEvent (event=0x7f64140008c0, receiver=0x1671d80) at kernel/qcoreapplication.h:231
#23 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x14a7170) at kernel/qcoreapplication.cpp:1573
#24 0x0000003e8417d683 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1466
#25 0x0000003e86e6573c in sendPostedEvents () at ../../src/corelib/kernel/qcoreapplication.h:236
#26 QEventDispatcherX11::processEvents (this=0x14a8ad0, flags=...) at kernel/qeventdispatcher_x11.cpp:75
#27 0x0000003e84178ecf in QEventLoop::processEvents (this=this@entry=0x7fff47ff6330, flags=...) at kernel/qeventloop.cpp:149
#28 0x0000003e841791c5 in QEventLoop::exec (this=this@entry=0x7fff47ff6330, flags=...) at kernel/qeventloop.cpp:204
#29 0x0000003e8417e45b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#30 0x0000003e86dc6c9c in QApplication::exec () at kernel/qapplication.cpp:3823
#31 0x0000003baa26744f in kdemain (argc=3, argv=0x7fff47ff6608) at /usr/src/debug/kde-workspace-4.10.5/kwin/main.cpp:537
#32 0x0000003e78c21b75 in __libc_start_main (main=0x400960 <main(int, char**)>, argc=3, ubp_av=0x7fff47ff6608, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff47ff65f8) at libc-start.c:258
#33 0x0000000000400991 in _start ()

This bug may be a duplicate of or related to bug 213182.

Possible duplicates by query: bug 323298, bug 306361.

Reported using DrKonqi
Comment 1 Thomas Lübking 2013-09-06 12:16:18 UTC 
Your OpenGL installation broke - even "glxinfo" should fail on this.

Eventually (actually: most likely) you've a colliding installation between mesa and fglrx.
Eventually you're using the "wrong" fglrx version (older GPUs moved into fglrx-legacy)

Check /var/log/Xorg.0.log on which driver is loaded, compare that to the resolved GL library and contact your distribution on how to resolve that (package choice) correctly.

running "aticonfig --initial" *might* resove this unless you should now be useing fglrx-legacy

*** This bug has been marked as a duplicate of bug 213182 ***
Comment 2 wintonian 2013-09-06 16:54:17 UTC 
Yeh, thanks, resolved (after a some faffing around with yum) by getting rid of fglrx and scrubbing clean by loosing akmod etc. Followed by reinstalling mesa and catalyst from ATI.

It happened just at the wrong time whilst trying to do something rather urgent so I got into a tis and swore at Fedora. :-)