Bug 281965

Summary: Empty spaces on the taskbar
Product: [Unmaintained] plasma4 Reporter: Leonardo La Malfa <leonardo.la.malfa>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: Letto2, shadow.walker, v01d3r
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Chakra   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: snapshot

Description Leonardo La Malfa 2011-09-13 19:36:52 UTC
Created attachment 63628 [details]
snapshot

Version:           unspecified (using KDE 4.7.1) 
OS:                Linux

Ever since I upgraded to kde 4.7 I get random empty spaces in the taskbar, as shown in the screenshot. I hoped 4.7.1 fixed this, but I keep getting them. If I try grabbing a minimised window I can move it over the empty area, which in turns moves over as well, but I can't grab the empty area. It doesn't occur in every virtual desktop, and is not the result of a closed window, in fact the empty areas appear randomly right after start up. I'd be glad to help with more info, if needed. Thanks.

Reproducible: Always

Steps to Reproduce:
.


Expected Results:  
.
Comment 1 Letto2 2011-09-18 12:38:00 UTC
I have finally managed to find a way to consistently reproduce this annoying bug.(hopefully)

Have the task manager set to show only windows from current desktop and set the  option to switch desktop by moving the windows to the border.

Then open a window on a desktop and while holding it move it to a different desktop and back again. Then close it. The desktop that it visited will have a empty space in the task manager. 

This also seems to screw with the number of rows that the task manager shows as after doing this the task manager on the second desktop will start to show 3 rows even though I set it to always show 2 rows.
Comment 2 Andrew Trabo 2011-09-21 17:26:34 UTC
Here is discussion on this bug: https://bugs.kde.org/show_bug.cgi?id=278891
Comment 3 Christoph Feck 2011-10-04 13:34:08 UTC

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