Description of Problem: Attempts to drag a window in "Workspace Switcher" display to another workspace sometimes succeed and sometimes not. It is always ok to drag a window to an "active" workspace and you have a pretty good chance of success if this is done to a some "remote" workspace. If you will do that to one of "neighbours" of an active workspace then you are playing a game of chance with a pretty good probability that a dragged window will "jump" back to its original position but it will likely get "lost" and has to be "re-dragged" again to an active workspace before showing up. If this happen then the window will be also lost on a window list on a panel. This "jump-and-loose" may be easier to observer with sawfish. Windows are not lost on a "Windows" sawfish menu (middle mouse button). Opening a window in another workspace and later switching back to a messed up one seems to restore sanity on a panel. Attached is a screenshot with three terminal windows and only one entry on a windows list.
Created attachment 64664 [details] A screenshot with a messed up panel
Is the workspace bug related to the window-list-losing-stuff bug? Or are there two bugs here? Related-looking: http://bugzilla.gnome.org/show_bug.cgi?id=86608 http://bugzilla.gnome.org/show_bug.cgi?id=83542 http://bugzilla.gnome.org/show_bug.cgi?id=74321 There was one other on gnome.org that I can't find right now.
"Lost from a list" part indeed looks remarkably similar to what you quoted so these may be indeed two bugs. OTOH so far I observed this vanishing only when a window jumped back on its own after beeing dragged. Note that this re-dragging in an active workspace may be needed before a window will show up again so both things may actually be related.
I can't duplicate this at all. Is this sawfish only, or can you reproduce it with metacity?
I do not know. I did not see that recently, so maybe (null) does not have this problem, but I will try to see if I can actively reproduce that.
Based on upstream bug status and lack of recent reports let's assume this one fixed, unless we get more reports from people using rawhide.