Even though I set in my $HOME/.config/xfce4/xfwm4/xfwm4rc line: cycle_minimum=true I always have panel in the list of applications when I do alt-tab. Also panel is always included in the task list and visible in the graphical pager. In 4.0.6 this worked properly and I did not see the panel.
xfwm4 --version This is xfwm4 version 4.1.90 for Xfce 4.1.90 built with GTK+-2.2.1, linked with GTK+-2.2.1.
This usually comes from a race condition at startup between the panel and the window manager. 1) Do you start xfce with the standard xfce4-session? 2) Else, do you have a customized statup script (namely xinitrc)? 3) If so, do you run xfwm4 wit hthe -daemon option prior to run the panel?
1) I am not using xfce4-session 2) yes I do have a slightly customized xinitrc. it is based on 4.0.6 and not modified while upgrading to 4.1.90. 3) Yes xfce4 --daemon starts before the panel. Note that I have restarted panel and xfwm and those do not help. Main things in my xinitrc: ................................................ xsetroot -solid black -cursor_name watch xrdb -nocpp -merge - << EOF Xft.dpi: 96 Xft.hinting: 1 Xft.hintstyle: hintmedium EOF test -f $HOME/.Xmodmap && xmodmap $HOME/.Xmodmap test $UID -gt 0 && test -z $VNCSESSION && xscreensaver -no-splash & xfce-mcs-manager xfwm4 --daemon if test -d "$HOME/Desktop/Autostart"; then for i in `ls -1 -L ${HOME}/Desktop/Autostart/ 2>/dev/null`; do if test -x $HOME/Desktop/Autostart/$i; then $HOME/Desktop/Autostart/$i & fi done fi xfdesktop& xfce4-panel .................................... so I have only removed some lines from it. Can you reproduce the problem or does it work in your system ?
just tested and verified that cycle_hidden works. This tells that I am using the correct parameter file and that xfwm4 successfully reads it
I debugged this a little and actually it seems that it is the panel that is doing something wrong. xprop shows: _NET_WM_STATE(ATOM) = _NET_WM_STATE_STICKY, _NET_WM_STATE_ABOVE But I believe it should show (which is what I get if I start 4.0.6 panel): _NET_WM_STATE(ATOM) = _NET_WM_STATE_STICKY, _NET_WM_STATE_SKIP_PAGER, _NET_WM_STATE_SKIP_TASKBAR, _NET_WM_STATE_ABOVE Not sure, but I think xfwm can't know that panel should be skipped if panel does not set those hints ?
that's correct, but on the other hand, the panel use std GTK methods for setting these. It's a NET_STATE, which means that the app doesn't set it directly but asks the WM to set/usnset or even toggle the state. That's why I said that it usually happens when a race condition occurs at startup... Unless gtk+-2.2.1 has a bug there. Did you try to upgrade to the latest 2.2.x version (2.2.4 IIRC)?
it can't be race since I tried it without panel and manually started it. But I agree that it is worth upgrading my gtk sine I simply can't see anything wrong in the code. These statements just do not seem to have any effect: gtk_window_set_skip_taskbar_hint (window, TRUE); gtk_window_set_skip_pager_hint (window, TRUE); from panel.c:949-950 Will let you know what effect the upgrade had.
This version works perfectly: This is xfwm4 version 4.1.90 for Xfce 4.1.90 built with GTK+-2.2.1, linked with GTK+-2.4.11. So it very much looks like Gtk 2.2.1 at least has a problem. Impossible to know if it works with later releases of 2.2 (the upgrade is not trivial so I did not want to do it twice) I am happy. Feel free to close this BUG.
Gtk 2.2.1 problem. Not worth reporting to GTK+ since works in new version.