Summary: | Kwin crash after changing screen resolution | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Jeff Burns <admiraljkb> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | Keywords: | investigated, triaged |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jeff Burns
2010-09-17 00:22:02 UTC
crashes in nvidias blob, glDeleteTextures(), causing or caused by a mem corruption - 260 is still the beta driver? - is this reproducible? (if you do exact the same, the exact smae happens again?) -> to workaround the issue, suspend compositing (SHIFT+ALT+F12) before changing screen/resolution (plain resolution changes via xrandr should be ok, afaics) toggle again to resume compositing 260.19.04 is a beta driver. Sorry, I can't reproduce at will... I switch screens and resolution 2-3 (or more) times a day, and have been running that driver for a week or two. Thanks for the workaround. At this point I won't use it so as to catch more data. 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! 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! |