awn only exists on the workspace it was launched on (xfce)

Bug #152822 reported by Matt
4
Affects Status Importance Assigned to Milestone
Xfwm4
In Progress
Unknown
xfwm4 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

When avant-window-navigator is launched it only appears on the workspace it was launched on. If you change workspaces, it disappears, but when you return to the original workspace, it is still there.

Reproducible: Always

Steps to Reproduce:
1.Run XFWM4
2.Run AWN
3.Change Workspace

Actual Results:
AWN is not present on new workspace

Expected Results:
AWN is on all of the workspaces.

Debian Linux Lenny (Testing)
libwnck 2.18.3
xfwm4-SVN
avant-window-navigator-bzr
(also tried on avant-window-navigator desktop-agnostic branch compiled with xfce4 support)

Related branches

Revision history for this message
Matt (mlweber91) wrote :

Accidentally attached to wrong bug.

Sorry. http://bugzilla.xfce.org/show_bug.cgi?id=3609

Changed in xfwm4:
assignee: nobody → mlweber91
assignee: mlweber91 → nobody
status: New → Unknown
Revision history for this message
Matt (mlweber91) wrote :

Problem definately isolated to xfwm4.

0. make sure awn isn't running
1. killall xfwm4
2. metacity
3. xcompmgr
4. avant-window-navigator

And it works.

Changed in xfwm4:
status: Unknown → Confirmed
Revision history for this message
Matt (mlweber91) wrote : Problem

(Quoted from Oliver Fourdan, xfce devel)

"An xprop on AWN window gives:

WM_STATE(WM_STATE):
                window state: Normal
                icon window: 0x0
_NET_WM_STATE(ATOM) = _NET_WM_STATE_DEMANDS_ATTENTION
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CHANGE_DESKTOP
_NET_WM_DESKTOP(CARDINAL) = 0
WM_HINTS(WM_HINTS):
                Client accepts input or input focus: True
                Initial state is Normal State.
                window id # of group leader: 0x2e00001
XdndAware(ATOM) = BITMAP
_MOTIF_DRAG_RECEIVER_INFO(_MOTIF_DRAG_RECEIVER_INFO) = 0x6c, 0x0, 0x5, 0x0,
0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x10, 0x0, 0x0, 0x0
WM_TRANSIENT_FOR(WINDOW): window id # 0x2e0000b
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 48234537
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK
WM_CLIENT_LEADER(WINDOW): window id # 0x2e00001
_NET_WM_PID(CARDINAL) = 6537
WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_CLIENT_MACHINE(STRING) = "m1710"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
                program specified minimum size: 388 by 96
                program specified maximum size: 388 by 96
                window gravity: NorthWest
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING,
_NET_WM_SYNC_REQUEST
WM_CLASS(STRING) = "avant-window-navigator", "Avant-window-navigator"
WM_ICON_NAME(STRING) = "avant-window-navigator"
_NET_WM_ICON_NAME(UTF8_STRING) = 0x61, 0x76, 0x61, 0x6e, 0x74, 0x2d, 0x77,
0x69, 0x6e, 0x64, 0x6f, 0x77, 0x2d, 0x6e, 0x61, 0x76, 0x69, 0x67, 0x61, 0x74,
0x6f, 0x72
WM_NAME(STRING) = "avant-window-navigator"
_NET_WM_NAME(UTF8_STRING) = 0x61, 0x76, 0x61, 0x6e, 0x74, 0x2d, 0x77, 0x69,
0x6e, 0x64, 0x6f, 0x77, 0x2d, 0x6e, 0x61, 0x76, 0x69, 0x67, 0x61, 0x74, 0x6f,
0x72

You can see that _NET_WM_STATE doesn't include and NET_WM_DESKTOP is 0, so
there is nothing in AWN window that instructs the window manager to set it
sticky.

FYI, the same problem shows in KDE (kwin) too. I believe AWN is not using the
standards (EWMH) ways of setting its window sticky but rather relies on
specific implementation that set dock windows sticky by default (which is not
specified by the standard) - I do not see why docks should be necessarily
sticky...

FTI, both metacity and compiz do treat docks as sticky, but neither kwin nor
xfwm4 do.

So this is a bug with AWN, not xfwm4."

To sum it up, he said that AWN does not do anything to tell the window manager that it should be on all desktops; all it does is set itself as a dock. The attached patch instructs xfwm to display all docks on all workspaces. He has not yet decided if it should be merged into the svn tree, but would not have to if AWN were standards complient.

Revision history for this message
Matt (mlweber91) wrote :

Problem fixed with a patch. Patch has not been committed to xfwm, as the problem should be fixed in awn.

Changed in awn:
status: New → In Progress
Revision history for this message
Matt (mlweber91) wrote :

Patch merged into svn

Changed in awn:
status: In Progress → Fix Committed
Revision history for this message
Mark Lee (malept) wrote :

I pretty much agree with Olivier on this one - this is AWN's fault. I'll see if I can cook up a patch for AWN, and it'll go in my desktop-agnostic branch (even though window manager stuff isn't in one of my areas of knowledge).

Changed in xfwm4:
status: Confirmed → In Progress
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

0.2.1 released

Changed in awn:
status: Fix Committed → Fix Released
Revision history for this message
Mark Lee (malept) wrote :

This one isn't fixed, per se. I gave writing a patch a go, and froze my X session. Someone with more X coding experience than myself needs to make AwnWindows have the following properties:

_NET_WM_DESKTOP = 0xFFFFFFFF (all desktops)

_NET_WM_STATE += _NET_WM_STATE_STICKY

Revision history for this message
Neil J. Patel (njpatel) wrote :

or,

gtk_window_stick ()

should work.

Revision history for this message
Mark Lee (malept) wrote :

Fix not released. I have reports (on the forum) that this also affects KWin, KDE's window manager.

Changed in awn:
status: Fix Released → Confirmed
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Adding an Ubuntu bug task and marking it as fix committed.

Lionel: do we already have this patch in our package ?

Changed in xfwm4:
importance: Undecided → Low
status: New → Fix Committed
Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Yes, this patch is already included in xfwm 4.4.2.

Changed in xfwm4:
status: Fix Committed → Fix Released
Revision history for this message
Michal Hruby (mhr3) wrote :

Not AWN's problem.

Changed in awn:
status: Confirmed → Invalid
Michal Hruby (mhr3)
no longer affects: awn
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.