Minimize and Restore in tasklist frequently, made the icon "switched" to the rightmost

[Sutanto Kurniawan]

Further information:
Minimizing and restoring application in the tasklist for about 4-7 times, make the icon dissapeared and switched to the rightmost of the tasklist.
Interestingly, (I think) AWN "remembers" the state, so if I continue to work, and minimize and restore in later time (randomly), the task that have been minimized and restored for about 4-7 times, gracefully switched to the rightmost of the tasklist.
This doesn't happen for icon that "sit" in the launcher.

Steps to reproduce:
Minimize and restoring same task (icon) for about 4-7 times.

Version information:
- bzr "trunk" rev. 123 (this also happen the first time I check out with bzr, but I can't remember the date or the rev, sorry).
- Ubuntu Feisty 7.04 32bit (Kernel 2.6.20, patched with CFS).
- Gnome 2.18.1
- Compiz Fusion 0.5.3 (also happened in beryl).
- NVidia 8400GS with 100.14.19 driver

[Sutanto Kurniawan (tanto)]

Upgrading to:
- Gutsy Beta 32bit (Kernel 2.6.20, patched with CFS).
- Gnome 2.20.0
- Compiz Fusion 0.6.1
- on same hardware

the problem still exist.

[Sutanto Kurniawan (tanto)]

Ooops, typo, I meant:
Kernel 2.6.22

[Andrew Starr-Bochicchio (andrewsomething)]

I can reproduce this consistently with an up-to-date AWN built from source on Gutsy.

No terminal output when the issue occurs.

[Neil J. Patel (njpatel)]

Hmm, I can't repriduce this with gnome-terminal, firefox or evolution. Does this still occur for you guys?

[moonbeam (rcryderman)]

Still easily reproducible here last time I started the awn taskmanager/launcher (which was in the last week).

[Sutanto Kurniawan (tanto)]

Neil, I just checked out the latest bazaar version (revno: 174).
This still occur for me.

[SkiesOfAzel (valiant-wing)]

Version 194 fixed this for me.

[Sutanto Kurniawan (tanto)]

Still happened in 195.

[Sutanto Kurniawan (tanto)]

Hi...

It's seems fixed on version 0.3.1
I'm no longer pull the bazaar version (so I don't know the exact revisio no.), I'm using the awn-testing from ppa.launchpad.net repository instead, the last update fix this.
I'll try this version for a week, and will mark this as Fix Committed (I can do that right?) if the bug not shown in a week, just to make sure... :)

Thanks.

[moonbeam (rcryderman)]

Sutanto,

No fix has been committed to awn for this bug. It actually is related to interactions between awn and libwnck. If it does end up being resolved on your system please post the version of libwnck in use. But don't change the bug status.

thanks,

[Sutanto Kurniawan (tanto)]

moonbeam,

Yes, I think I made a conclusion too fast. The bug still exist, but in "different form".
The icon no longer switched to the right most, but the application does, so now the "switched" applications sit to the rightmost of the dock "sitting" on another applications icon. The icons position stays the same, but it not represent the current real applications position.
I hope you can understand what I meant, my English is terrible...

As for the libwnck version, it's the 2.22.1, it's still the original version shipped with Hardy.

Thanks.

[Massimo Tisi (massimotisi)]

I confirm the same strange behavior described by moonbeam

[oisin (ninja-gofer)]

I can confirm this on Gentoo. Tested both 2.6 and latest bazaar versions, no difference between the two.

Dependency versions;
kernel 2.6.25
libwnck 2.22.3 (tested 2.24.1)
compiz-fusion 0.7.8
xorg-x11 7.2
xorg-server 1.3
nvidia-drivers 180.06

[Jeremy Gove (jeremy-gove)]

This happens to me, too in Gentoo. Sometimes it happens after restoring the program just once or twice; it often happens before four to seven attempts.

[moonbeam (rcryderman)]

Changing the status. This bug should be resolved in the 0.4 rewrite branch. If it is not already fixed it _will_ be before the release.

[Michal Hruby (mhr3)]

Hopefully fix for this will get into 0.3.2.

[haytjes (h4writer)]

There is an temp. fix added in trunk. The real cause isn't found yet (Is it a Wnck or an AWN bug?). But for now this temp. fix is added to be tested before release of 0.3.2. Just in cause the real cause isn't found.
If there is any regression or something with this fix, this temp. fix will get removed.
(I added it now, to have a time to test it, before the release)

[Michal Hruby (mhr3)]

Seems like the workaround done by haytjes didn't cause any regressions, therefore setting as Fix commited.

[Faeq (faeq)]

where is the fix?i cant find it
and please tell me how to patch it

[Sutanto Kurniawan (tanto)]

Just stop by to say that the fix have fixed the problem.
I'm using AWN from the ppa.launchpad.net/awn-testing for hardy , and don't experience this problem after 2-3 weeks of usage.
Great jobs devs, thank you.