Summary: | kwin crashed after attempting to set display to mirror vertically | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | sparhawk <kdebugs> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | endless1239 |
Priority: | NOR | ||
Version: | 4.9.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
sparhawk
2012-11-02 11:03:21 UTC
crashes in the driver, not much we can do about that, sorry. To circumvent the problem press once Alt+Shift+F12 prior to changing the monitor settings. Afterwards you can use the same shortcut again to re-enable compositing. No worries. FWIW, that workaround didn't work for me. It did prevent the crash, but the setting just reverts to "No Rotation" again. bug/defect in driver, bug in libxrandr, bug in the randr kcm or you missed the confirmation dialog. run "xrandr -o inverted" and see what happens Ah yes, that works fine. Thank you. ok, interesting. please use "xrandr -q" to determine the exact string of your display (will be sth. around "LVDS1") and use it in "xrand --output LVDS1 --rotate inverted" If that works as well, there might be a bug in the krandr kcm, please file it against that component then (please do not just relable this one, would be too confusing) That does work as well. Should I just replicate the crash then immediately change the component to xrandr? (In reply to comment #6) > That does work as well. Should I just replicate the crash then immediately > change the component to xrandr? No. Do not relabel this bug, but file a new one against krandr, explining in the description what GUI way you attempt to use an fail while flipping with xrandr works. Also maybe try 90° rotations for the report. Sorry, I was unclear. I meant refile the bug by replicating the crash, then change the component on the new bug. No, the backtrace of kwin is completely irrelevant to the krandr developers. That's for the moment a problem in the GPU driver (but of course maybe induced by the krandr action if you can perform the xrandr inversion with activated compositing) Thanks. New bug filed against krandr here: https://bugs.kde.org/show_bug.cgi?id=309789 *** Bug 310612 has been marked as a duplicate of this bug. *** |