Regarding my examples 1 & 3 in the bug description, I have to make a correction based on further observation:
It seems that this is not a bug, but only an irritating behaviour: Sometimes if I open an app which was maximized when I last closed it, and the app did not remember the "maximized" state but the position and size of the window, the new window will be slightly misplaced. Therefore, it could "leak" a few pixels into the next or previous workspace, which may or may not clearly visible. Since the window then is partially on this other workspace, too, its icon is displayed "correctly" in the window list.
So, this is NOT a bug (and my description was wrong, because it can be seen on DEmaximized windows which just happen to be nearly as large as if they were maximized).
However, the 2nd example, which is also what Andreas reported, is independent from the other ones. During the last few days, this effect did not reappear, however.
Regarding my examples 1 & 3 in the bug description, I have to make a correction based on further observation:
It seems that this is not a bug, but only an irritating behaviour: Sometimes if I open an app which was maximized when I last closed it, and the app did not remember the "maximized" state but the position and size of the window, the new window will be slightly misplaced. Therefore, it could "leak" a few pixels into the next or previous workspace, which may or may not clearly visible. Since the window then is partially on this other workspace, too, its icon is displayed "correctly" in the window list.
So, this is NOT a bug (and my description was wrong, because it can be seen on DEmaximized windows which just happen to be nearly as large as if they were maximized).
However, the 2nd example, which is also what Andreas reported, is independent from the other ones. During the last few days, this effect did not reappear, however.