! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Taskbar still shows a previously shaded task as "=Application Name" AFTER uns...


Description Armin Jarmusch 2009-05-08 15:45:41 CEST
The taskbar usually shows shaded applications as "=blabla", just like it shows minimized apps like "[blabla]".

After unshading apps the title in the taskbar still remains with the = in it.
Comment 1 Mathias Brodala 2009-06-20 12:04:40 CEST
Seems like taskbar only updates the shade indicator on minimize of windows. Test case:

1) Shade window → taskbar does not change
2) Minimize shaded window → taskbar indicates shading
3) Restore window → taskbar still indicates shading
4) Unshade window → taskbar still indicates shading
5) Minimize window → taskbar removes shading indicator

I remember this working just fine with Xfce pre-4.6.
Comment 2 Olivier Fourdan editbugs 2009-06-21 12:26:26 CEST
Yes but not but yes... but no.

I can reproduc ethe problem, indeed, but this is not a window manager problem.

The window manager properly sets the NET_WM_STATE atom:

1) identify the window ID with xwininfo
2) Check the property NET_WM_STATE when the status change:

2.a: The window is mapped, the perperty is empy:

  $ xprop -id 0x3600045 | grep NET_WM_STATE

2.b: Shade the window, redo:

  $ xprop -id 0x3600045 | grep NET_WM_STATE

2.c: Hide the shaded window, redo:

  $ xprop -id 0x3600045 | grep NET_WM_STATE

2.d: Restore the window (still shaded):

  $ xprop -id 0x3600045 | grep NET_WM_STATE

2.e: Unshade the window:

  $ xprop -id 0x3600045 | grep NET_WM_STATE

So from a window manager point of view, all is well and done right. So this is not a problem with the window manager. Prossibly an issue with libwnck?

Another hint, I did not change anything of this between 4.4 and 4.6 (but we replaced our own taskbar implementation wit hteh one from libwnck)
Comment 3 Armin Jarmusch 2011-06-18 14:18:50 CEST
i'm not able to reproduce this since 4.8, so i'm going to close this bug.
Comment 4 Mathias Brodala 2011-06-18 15:45:07 CEST
(In reply to comment #3)
> i'm not able to reproduce this since 4.8, so i'm going to close this bug.

Yes, I can confirm that the issue was fixed, thanks.

Bug #5341

Reported by:
Armin Jarmusch
Reported on: 2009-05-08
Last modified on: 2011-06-18


Olivier Fourdan
CC List:
1 user



Additional information