AllTray does not work with OpenBox

I see the same behavior with firefox: when first launching "alltray firefox -no-remote -P default" I see firefox's icon in the tray. Once I click it, firefox's window is displayed and a button is added to the Window List on my panel. This button then remains regardless of the state of its window: shown, minimized, closed to tray.

This behavior defeats the purpose of alltray, which in my case was to unclutter my window list.

What window manager are you using, compiz, metacity, or something else altogether?

I use openbox as window manager

Hi.

I'm getting exactly the same problem here. it works when I start a gnome session, but if I start a gnome/openbox session it no longer works...
I tried with any program but get the same result... the windows remain in the "task bar" so it's just minimized...
That'd be nice to have a fix for this

There is a testing release of AllTray available (0.7.2dev) that is working towards the next stable, 0.8.0, available. It does not have all of the features of the current AllTray, and so I don't recommend it for general use just yet, but could someone test it against the GNOME/Openbox combination to determine if it makes progress towards solving this bug? Thanks!

Download information: https://edge.launchpad.net/alltray/trunk/0.7.1dev

One additional note: GNOME Terminal uses a setup wherein when you start a new GNOME Terminal, and you already have other ones running, the new process just asks the old one to open a new window and exits. So, prior to testing for this bug's resolution in the development version of AllTray, be sure to not have any GNOME terminal windows open. A workaround will make it into the new AllTray later to try to change this behavior, though that fix depends on another issue in that release that needs a resolution.

A decent way to test it is to start an xterm and start "alltray gnome-terminal" from within xterm.

Just tested AllTray 0.7.3dev with OpenBox 3.4.7.2, which indeed does not work. It would appear that there is an issue with the interaction between the two pieces of software, which is documented in a rather old bug in OpenBox's tracker; I will add that bug to the watch list for this, and have asked for the OpenBox developer's assistance in trying to track this one down.

As this would seem to be dependent on a fix from upstream with perhaps some collaboration, I'm going to mark this bug as “incomplete” for the time being, at least until such time as I have a better idea of the disposition of this bug. If I can't raise a response in a reasonable period of time, though, it'll be up to the OpenBox users to follow the issue there and I'll eventually close this bug. Hopefully, that doesn't happen.

Okay, so I'm a douche. I have fixed this in AllTray's trunk, and will look at a fix for the old-maintenance branch soon; someone may be able to advocate for this being pushed to Jaunty via an SRU.