Summary: | kwin crashed at startup | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | John <johndemicco> |
Component: | general | Assignee: | 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
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" If you can provide the information requested in comment #1, please add it. 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
still waiting for information requested in comment #1. 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. 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! 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! |