Bug 230629 - Desaturate desktop disabled but still desaturates
Summary: Desaturate desktop disabled but still desaturates
Status: RESOLVED WORKSFORME
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: general (show other bugs)
Version: 4.5 and older
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords: triaged
: 238291 269110 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-13 23:02 UTC by Russell
Modified: 2018-10-27 02:18 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Russell 2010-03-13 23:02:48 UTC
Version:            (using KDE 4.3.5)
OS:                Linux
Installed from:    openSUSE RPMs

I goto Personal Settings -> Desktop:

- I have "Enable Desktop Effects" enabled/checked.
- I click the "All Effects" tab.
- I go to the option, "Logout - Desaturate the desktop when display the
Logout Dialog" and disabled/uncheck it.

If I click the Leave button to logout, the desktop DOES NOT Desaturate. Good, but... I cancel the logout. I click Leave again, and logout for real this time. I login and click the Leave button. The desktop DOES Desaturate this time. Bad!!! I double-check the option, and it is still disabled/unchecked. 

Desaturate desktop is causing another problem.

If a user is logged-in through VNC, the Desaturate desktop is causing great pains because it is soooo slow. The VNC user does not have "Enable desktop effects" enabled/checked, but their desktop still Desaturates when they select the Leave button to logout.
Comment 1 Martin Flöser 2010-03-13 23:12:01 UTC
yes this is actually expected. If desktop effects are disabled the Desaturation is done by the logout dialog in a worse way. I do not know if it can be disabled...
Comment 2 Russell 2010-03-18 22:09:39 UTC
I might have caused some confusion above by describing 2 situations where desaturation occurs on logout, local and remote.  It sounds like this may
be two different issues.  

On the local machine, it does it once correctly. 

When I disable the option Logout, and logout, the screen does not desaturate. This is what I expected to see.

But when I login, and logout again, the screen desaturates.  The checkbox is still unset, which is inconsistent. The option appears to only be applied during the session when it was set.

I believe the option Logout should be saved, restored, and applied across sessions to accurately reflect the state of the Logout checkbox.

HTH
Comment 3 Martin Flöser 2010-03-18 22:25:54 UTC
The situation is a little bit more complicated. The logout effect is just a visual effect to replace the "normal" effect. When compositing is disabled the normal effect is used, which is in fact worse than the composited effect.

I have not found any options to disable the "normal" effect. So I rassign to the appropriate component
Comment 4 Martin Flöser 2010-05-20 21:29:54 UTC
*** Bug 238291 has been marked as a duplicate of this bug. ***
Comment 5 veritas13579 2011-03-22 08:31:03 UTC
Alright, so there is a normal effect which takes a screen shot and slowly desaturates it completely to black and white while painting the result to the screen successively.  I can witness this by pressing Left Shift + Alt + F12, to suspend compositing, and then opening the logout dialog.

Now with compositing reactivated, this effect shouldn't be visible, and if the Logout effect under Desktop Effects is activated, it won't be.  The bug is that if compositing is suspended and then reenabled, this "normal" logout effect will become active whenever the Desktop Effect, Logout, is not activated.

Originally this had confused me greatly, but it has now become quite clear to me what is happening.

Furthermore, I'd just like to point out that I prefer the complete black and white desaturation of the "normal" effect and would like that to be the effect of the Desktop Effect, Logout, however there are no settings for this effect.
Comment 6 veritas13579 2011-03-22 08:42:19 UTC
Just had to be sure, and tested it several times.

CONFIRMED

REPRODUCIBLE

Debian 6.0
Kwin 4.4.5

Make sure the compositing effect "Logout" is not active.
Suspend compositing and then re-enable it (Left Shift + Alt + F12  -- twice)
The "normal" logout effect is now active while compositing is active, which it shouldn't be.
Comment 7 veritas13579 2011-03-22 08:52:43 UTC
Jeez, I hate to be blowing this thing up like this, but here is how to restore the correct functionality:

kquitapp kwin && sleep 10s && rm -f $(kde4-config --localprefix)/share/config/kwin* && kwin --replace &

After the preceding commands have executed and kwin is running again, Desktop Effects can be enabled, the Logout effect can be deactivated, and once the logout dialog is opened there will be no effect applied.

If at any point compositing is suspended and then re-enabled the problem will return.  I can't find what setting might be affecting this.
Comment 8 Thomas Lübking 2011-03-22 14:11:41 UTC
*** Bug 269110 has been marked as a duplicate of this bug. ***
Comment 9 Thomas Lübking 2011-03-22 14:40:34 UTC
a) i think this is a plasma issue rather than a ksmserver one? (no logout effect w/o plasma & compositing here, ksmserver is running)
b) it doesn't look like there's supposed to be a way to disable the logout effect (the logout effect would rather be like the scale one, takes over control if acivated)
c) the bug would than actually be that you can interim have no logout desaturation at all

d) possible solution would be to add such central config option and (if checked) use kwin effects if possible and the SW fallback otherwise.

tbs: attaching plasma ;-)
Comment 10 Myriam Schweingruber 2012-09-08 12:31:25 UTC
Is this still valid with KDE 4.9.x?
Comment 11 Andrew Crouthamel 2018-09-23 02:41:50 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 12 Andrew Crouthamel 2018-10-27 02:18:50 UTC
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!