Bug 331056

Summary: kwin crashed at startup
Product: [Plasma] kwin Reporter: John <johndemicco>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: ali.sherif10
Priority: NOR Keywords: drkonqi, triaged
Version: 4.11.5   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: New crash information added by DrKonqi

Description John 2014-02-12 15:32:56 UTC
Application: kwin (4.11.5)
KDE Platform Version: 4.11.5
Qt Version: 4.8.5
Operating System: Linux 3.13.0-6-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Just rebooted. only change before reboot was installation of hlip

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f6a4bd45a7e in glXGetFBConfigs () from /usr/X11R6/lib64/libGL.so.1
#7  0x00007f6a4bd466fa in ?? () from /usr/X11R6/lib64/libGL.so.1
#8  0x00007f6a4bd46959 in glXChooseFBConfigSGIX () from /usr/X11R6/lib64/libGL.so.1
#9  0x00007f6a511ee705 in KWin::GlxBackend::initDrawableConfigs (this=this@entry=0x158eb80) at /usr/src/debug/kde-workspace-4.11.5/kwin/glxbackend.cpp:314
#10 0x00007f6a511ef441 in KWin::GlxBackend::init (this=0x158eb80) at /usr/src/debug/kde-workspace-4.11.5/kwin/glxbackend.cpp:86
#11 0x00007f6a511ea34c in KWin::SceneOpenGL::createScene () at /usr/src/debug/kde-workspace-4.11.5/kwin/scene_opengl.cpp:223
#12 0x00007f6a511ceb95 in KWin::Compositor::slotCompositingOptionsInitialized (this=0x150c510) at /usr/src/debug/kde-workspace-4.11.5/kwin/composite.cpp:202
#13 0x00007f6a51156975 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.11.5/build/kwin/moc_composite.cpp:193
#14 0x00007f6a4b26ed68 in QMetaObject::activate (sender=0x15e78e0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3556
#15 0x00007f6a4b14c458 in QFutureWatcherBase::event (this=<optimized out>, event=0x7f6a24001340) at concurrent/qfuturewatcher.cpp:344
#16 0x00007f6a4a3da8ac in QApplicationPrivate::notify_helper (this=this@entry=0x130ebc0, receiver=receiver@entry=0x15e78e0, e=e@entry=0x7f6a24001340) at kernel/qapplication.cpp:4562
#17 0x00007f6a4a3e0e70 in QApplication::notify (this=this@entry=0x7fff77494ac0, receiver=receiver@entry=0x15e78e0, e=e@entry=0x7f6a24001340) at kernel/qapplication.cpp:4348
#18 0x00007f6a4fa8e18a in KApplication::notify (this=0x7fff77494ac0, receiver=0x15e78e0, event=0x7f6a24001340) at /usr/src/debug/kdelibs-4.11.5/kdeui/kernel/kapplication.cpp:311
#19 0x00007f6a4b25b0ad in QCoreApplication::notifyInternal (this=0x7fff77494ac0, receiver=receiver@entry=0x15e78e0, event=event@entry=0x7f6a24001340) at kernel/qcoreapplication.cpp:949
#20 0x00007f6a4b25e0ff in sendEvent (event=0x7f6a24001340, receiver=0x15e78e0) at kernel/qcoreapplication.h:231
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x129a1f0) at kernel/qcoreapplication.cpp:1573
#22 0x00007f6a4b25e5a3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1466
#23 0x00007f6a4a4780ac in sendPostedEvents () at ../../src/corelib/kernel/qcoreapplication.h:236
#24 QEventDispatcherX11::processEvents (this=0x129fa70, flags=...) at kernel/qeventdispatcher_x11.cpp:75
#25 0x00007f6a4b259d0f in QEventLoop::processEvents (this=this@entry=0x7fff77494930, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007f6a4b25a005 in QEventLoop::exec (this=this@entry=0x7fff77494930, flags=...) at kernel/qeventloop.cpp:204
#27 0x00007f6a4b25f13b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#28 0x00007f6a4a3d906c in QApplication::exec () at kernel/qapplication.cpp:3823
#29 0x00007f6a51187266 in kdemain (argc=3, argv=0x7fff77494c08) at /usr/src/debug/kde-workspace-4.11.5/kwin/main.cpp:597
#30 0x00007f6a50d7abe5 in __libc_start_main () from /lib64/libc.so.6
#31 0x0000000000400761 in _start () at ../sysdeps/x86_64/start.S:122

Possible duplicates by query: bug 329698, bug 329443, bug 327028, bug 325545, bug 324896.

Reported using DrKonqi
Comment 1 Thomas Lübking 2014-02-12 16:54:06 UTC
Not the typical "broken fglrx" bug (looks like, but does not resolve libGL from some fglrx subdir)

a) is this reproducible
b) in case of (a), please attach the output of "glxinfo"
Comment 2 Christoph Feck 2014-07-16 15:04:21 UTC
If you can provide the information requested in comment #1, please add it.
Comment 3 ali.sherif10 2014-12-14 00:27:46 UTC
Created attachment 89962 [details]
New crash information added by DrKonqi

kwin (4.11.14) on KDE Platform 4.14.3 using Qt 4.8.6

- What I was doing before the application crashed:
I installed the latest version of fglrx 64-bit for OpenSUSE 13.2 then restarted. During installation grub couldn't install a module.

After logging in, I saw the crash and AMD Control Center gave, "There was a problem initializing Catalyst Control Center Linux edition.  It could be caused by the following.

No AMD graphics driver is installed, or the AMD driver is not functioning properly.
Please install the AMD driver appropriate for you AMD hardware, or configure using aticonfig."

Vendor: HP.
Graphics: Switchable graphics (AMD + Intel).

-- Backtrace (Reduced):
#6  0x00007f23a70cc1de in glXGetFBConfigs () from /usr/X11R6/lib64/libGL.so.1
[...]
#8  0x00007f23a70cd0b9 in glXChooseFBConfigSGIX () from /usr/X11R6/lib64/libGL.so.1
#9  0x00007f23ac581745 in KWin::GlxBackend::initDrawableConfigs (this=this@entry=0x1e12030) at /usr/src/debug/kde-workspace-4.11.14/kwin/glxbackend.cpp:315
#10 0x00007f23ac581fe1 in KWin::GlxBackend::init (this=0x1e12030) at /usr/src/debug/kde-workspace-4.11.14/kwin/glxbackend.cpp:86
#11 0x00007f23ac57ceec in KWin::SceneOpenGL::createScene () at /usr/src/debug/kde-workspace-4.11.14/kwin/scene_opengl.cpp:222
Comment 4 Martin Flöser 2015-01-09 08:26:34 UTC
still waiting for information requested in comment #1.
Comment 5 Thomas Lübking 2015-01-09 12:26:47 UTC
at least comment #3 (talks about amd control center -> fglrx, but uses mesa gl and the acc complains about missing driver) suggests some weirdness in the opengl installation, related to fglrx and sounds like the fglrx driver is used, but resolves the mesa gl lib, pot. occurs due to the additional intel chip.

if both crashes are the same, this is downstream (driver/libgl messup) but one needs some system info (lspci, XOrg.0.log) to say for sure - as no gl client will work, the users might also have abandoned linux.
Comment 6 Andrew Crouthamel 2018-09-25 03:43:26 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-10-27 04:14:04 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!