Summary: | Error message when viewing windows settings | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Piotr Belniak <belniak> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | Keywords: | drkonqi, triaged |
Priority: | NOR | ||
Version: | 5.3.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=346742 https://bugs.kde.org/show_bug.cgi?id=346748 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Step 1 |
Description
Piotr Belniak
2015-06-03 10:03:18 UTC
Does is also crash if you uninstall nvidia binary drivers? Did you *only* open the compositor settings ("kcmshell5 kwincompositing") or did you choose "More Actions/Window manager settings" from the titlebar rightclick menu? In case this is reproducible, is it also reproducible with *only* the compositor kcm (run "kcmshell5 kwincompositing")? Created attachment 93053 [details]
Step 1
Sorry - I wanted to add screenshots :) btw to be 100% precise - it is 100% reproducible on 2 independent PC's - step 1 - choose More Actions/Window manager settings (Rendering engine is OpenGL 3.1) - step 2 - change Rendering engine to OpenGL 2.0 ( do not apply change) - step 3 - go back to previous value (3.1) - step 4 - click Cancel button - error message will appear. I am using Nvidia driver. Will do that test on another PC with intel graphics card later. This has probably nothing to do with the driver or even the compositing kcm. Please close the dialog and (from konsole or krunner) run kcmshell5 kwincompositing this will open only the compositing config dialog. Try to cause the crash there and report back. When invoking the settings dialog by this command: kcmshell5 kwincompositing issue is not appearing. This is most likely related to bug #346748 then. And apparently the approach to avoid it failed =( Unfortunately the backtrace is missing debug symbols. This makes it impossible to proper investigate. If you are still able to reproduce please install debug symbols and attach a new backtrace. Sorry that we forgot to ask you about this really important step in a timely manner. 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! |