Bug 180994 - desktop effects are not working after xrandr events
Summary: desktop effects are not working after xrandr events
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: investigated, triaged
: 188208 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-16 18:04 UTC by thomas coopman
Modified: 2018-10-21 04:26 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thomas coopman 2009-01-16 18:04:45 UTC
Version:           4.1.96 (using Devel)
OS:                Linux
Installed from:    Compiled sources

When I rotate my desktop with xrandr, after rotating desktop effects are not working anymore (Although they are checked in the settings dialog)
To get them working again, I have to uncheck and check them again.

This is with a nvidia Geforce 6800M GT, driver: 180.22 on a 64bit system with opensuse 11.1
Qt: 4.4.4
KDE: 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 77.1"
KWin: 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 76.2"
Comment 1 thomas coopman 2009-01-17 09:19:36 UTC
After some more testing I found out that this doesn't get triggered by all rotations, only by left and right, rotation:inverted keeps the desktop effects on.
Comment 2 Will Stephenson 2009-02-27 13:01:04 UTC
Generalising, it appears kwin doesn't handle other xrandr events which it needs to when compositing is enabled.

If I change the screen mode from my laptop (intel 945gm)'s native 1024x768 to 1024x600, to emulate a netbook, kwin's painting is badly corrupted - things are painted in the wrong place on the screen or not painted at all.

Steps to reproduce:

$ gtf 1024 600 50 (for a modeline)
$ xrandr --newmode "1024x600" 39.55 1024 1048 1152 1280 600 601 604 618 -HSync +Vsync
$ xrandr --addmode LVDS 1024x600 ("LVDS" here is hardware specific...)
$ xrandr --output LVDS --mode 1024x600

and painting is corrupted

Be ready with

$ xrandr --output LVDS --mode 1024x768 

in your clipboard to get the display usable again, you may not be able to see what you are typing....
Comment 3 Aike J Sommer 2009-03-10 09:06:49 UTC
SVN commit 937637 by asommer:

Resize the overlay-window to allow compositing to continue working after xrandr-events.
CCBUG:180994

 M  +1 -0      composite.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=937637
Comment 4 Aike J Sommer 2009-03-10 09:09:05 UTC
SVN commit 937639 by asommer:

Backport 937637.
Resize the overlay-window to allow compositing to continue working after xrandr-events.
CCBUG:180994

 M  +1 -0      composite.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=937639
Comment 5 Aike J Sommer 2009-03-27 08:42:46 UTC
*** Bug 188208 has been marked as a duplicate of this bug. ***
Comment 6 Aaron J. Seigo 2009-06-10 02:48:41 UTC
Aike: do your commits fix this bug completely, or only partially?
Comment 7 Latev 2009-07-29 03:52:40 UTC
I can confirm that switching modes with xrandr/krandrtray brakes the effects on my system too

tl@I7:~/Documents$ uname -a
Linux I7 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC 2009 x86_64 GNU/Linux

to reproduce - just switch to any mode using xrandr -s 1024x768 for example
the effects are gone after that

tl@I7:~/Documents$ kwin --version
Qt: 4.5.0
KDE: 4.2.2 (KDE 4.2.2)
KWin: 4.2.2 (KDE 4.2.2)
Comment 8 FiNeX 2010-10-10 21:49:16 UTC
Hi! Is this bug still valid with KDE 4.5?
Comment 9 Andrew Crouthamel 2018-09-20 21:58:10 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 10 Andrew Crouthamel 2018-10-21 04:26:51 UTC
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!