Bug 308074 - Orphan/ghost buttons, windows, and panels when switching desktop
Summary: Orphan/ghost buttons, windows, and panels when switching desktop
Status: RESOLVED DUPLICATE of bug 259640
Alias: None
Product: kwin
Classification: Plasma
Component: effects-various (show other bugs)
Version: 4.9.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-08 13:31 UTC by Rahul Goma Phulore
Modified: 2012-12-29 09:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of a bug (349.82 KB, image/png)
2012-10-14 20:03 UTC, Kyrylo Bohdanenko
Details
qdbus org.kde.kwin /KWin supportInformation run 2 times (10.52 KB, text/plain)
2012-12-10 08:10 UTC, Ian Newton
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rahul Goma Phulore 2012-10-08 13:31:33 UTC
Sometimes when I am switching virtual desktops, regardless of the method used for switching, some orphan/ghost buttons or windows or panels pop up momentarily, and then go away when switching is completed.

Some screenshots: http://www.mediafire.com/?s2xpmqyz8d23b.

Once such ghost thingies start to appear, you have to restart kwin to make them go away.

Reproducible: Sometimes

Steps to Reproduce:
Don't know.
Actual Results:  
Orphan/ghost thingies.

Expected Results:  
No orphan/ghost thingies.
Comment 1 Martin Flöser 2012-10-08 15:29:57 UTC
Is this really 4.9.2? Because openSUSE does not yet ship 4.9 in the official repositories.

In case it is 4.9 please provide the output of 

qdbus org.kde.kwin /KWin supportInformation

when the problem is present.
Comment 2 Rahul Goma Phulore 2012-10-08 15:31:44 UTC
Okay, thank you. I will.
Comment 3 Rahul Goma Phulore 2012-10-08 15:32:48 UTC
Yes, it is 4.9.2. I have rolling release enabled on my system (via Tumbleweed).
Comment 4 Kyrylo Bohdanenko 2012-10-14 20:03:06 UTC
Created attachment 74546 [details]
Screenshot of a bug

Affects me too. Kubuntu 12.10, kde 4.9.2.
Comment 5 Kyrylo Bohdanenko 2012-10-14 20:07:48 UTC
Probably related: https://bugs.kde.org/show_bug.cgi?id=259640
Comment 6 Thomas Lübking 2012-10-14 20:27:20 UTC
please see comment #1 - that information is much more important than screenshots
Comment 7 Ian Newton 2012-12-09 22:14:02 UTC
I have the same issues with KDE 4.9 though I have Sabayon 10 as distribution (Gentoo derived). The orphaned closer buttons and even dialogue windows (Pidgin buddy list) seem to occur if certain screen-edge actions are enabled and used using the default settings.

I have isolated this to "Present Windows on all desktops" where if in the control panel of Desktop Effects for "Present Windows" the option "Provide buttons to close windows" is enabled. Closing any window in this display leaves the closer button behind which can not then be removed except by logging out and back in.

Switching "Provide buttons to close windows" off prevents the closer buttons being displayed and so being orphaned. A proper fix would be preferable.
Comment 8 Thomas Lübking 2012-12-10 00:06:31 UTC
We know what introduces those buttons, just now what keeps them around.
Therefore please see comment #1 and if possible provide the output of

   qdbus org.kde.kwin /KWin supportInformation

when the problem is present.
Comment 9 Ian Newton 2012-12-10 08:10:11 UTC
Created attachment 75764 [details]
qdbus org.kde.kwin /KWin supportInformation run 2 times

KDE output as requested (qdbus org.kde.kwin /KWin supportInformation). 1st run is with button display disabled. The second with button display enabled and 1 window selected leaving an orphan button. Orphan button appears on cube-rotate switching of desktop.
Comment 10 Ian Newton 2012-12-10 10:12:37 UTC
KDE trace from KDE 4.9.3 on Sabayon 10 with kernel 3.5
Comment 11 Thomas Lübking 2012-12-10 11:04:30 UTC
Can you try disabling the translucency effect?
Comment 12 Ian Newton 2012-12-10 11:19:00 UTC
Makes no difference. The Orphans still appear.
Comment 13 Martin Flöser 2012-12-29 09:18:48 UTC

*** This bug has been marked as a duplicate of bug 259640 ***