GNOME Bugzilla – Bug 70309
gnome-panel-2 (2x) and .gnome-desktop buttons visible in Tasklist
Last modified: 2016-02-07 03:36:34 UTC
Action: 1.) First start-up of Gnome 2 alpha 2: No panel started 2.) start panel Result: Bottom panel has a tasklist embedded. On it are the 2 panels and the nautilus desktop visibel as normal applications Expected: Desktop infrastructure apps not in tasklist as in Gnome 1.4 When: always
This has gone away with a new build with garnome 0.6.0
If it went away you should close it :)
I'm awfully sorry. This is ok to be closed for gnome-core, but should be opened for sawfish, as it's an issue with sawfish-gnome2-0.0.1 (I have no idea how to do this, sorry). It works OK with metacity. It's not filed for sawfish either
Created attachment 6597 [details] Pic of my panel with Workspace List and Tasklist
Urgh, forgot a comment. Sorry again, panel-maint, to spam you. Please move bug to sawfish In the attachment you see what sawfish is doing to my bottom panel: On the left you see 8 Workspaces on the Workspace List: #1 has a maximized Evolution 1.0.2. The Evo Icon is shown "Fullscreen" in miniwindow #2 is empty -> Nautilus icon (corresponds to Nautilus bein shown as an app on Tasklist) #3 Galeon 1.0.2 -> Icon #4 Empty #5 Gimp 1.2.2. If you look closely you can see Gimp windows being shown as it was in Gnome 1.4 #6/7 empty #8 gftp 2.0.8 Then comes the Tasklist, with 2 x "gnome-panel-2" & 1x nautilus (".gnome-desktop") shown as normal apps
This is really a bug in Metacity because it sets SKIP_TASKBAR on dock/desktop windows, but SKIP_TASKBAR is supposed to be set only by apps. Then it's also a bug in libwnck for requiring SKIP_TASKBAR when it could rely on the semantic type. So, a metacity/libwnck bug.
Interesting. So... Havoc, if I grok you right, the bug in metacity is covering up a bug in panel. Which means this should be two bugs, one against panel (for non-metacity and 'fixed' metacity users in the future) and one here against metacity?
One bug for metacity, and one for libwnck (not the panel itself)
I can't reproduce this anymore with libwnck-0.6 sawfish-20020215-snap metacity-2.3.55 Has it been fixed?
AFAIK fixed for libwnck/metacity. Someone needs to check Sawfish.
From your and luis' comments I thought it was a bug in libwnck covered up by a bug in metacity. It was visible in sawfish since sawfish /lacked/ the metacity bug to cover it up. So, if both wnck and meta are fixed, it should have gone away completely? In any case, I don't see it in sawfish
Let's close then.