AWN Icons Dissapear Under Auto-Resize

[Jack Deslippe]

I use fedora 7 and am new to AWN. I use the latest svn of AWN, but sometimes when I rotate my cube under compiz or cause there to be an auto-resize of AWN, all the icons disappear, and I am just left with a black bar at the bottom of my screen. As soon as I force a resize, by opening another window for example, the icons come back and all is good. The bug is still a bit annoying, though. Does anyone else have this problem? Can I do anything to fix it on my machine?

[Miika-Petteri Matikainen (mpmatikainen)]

The resizing code is rewritten in the latest bzr revision (r27). What revision of Awn are you using?

[kevinbeard (kevinbeard)]

Could also be the bug where awn wasn't picking up changes of viewports. That should also be in the latest bzr version.

[Jack Deslippe (jdeslip)]

I am using an rpm from svn. I think the rpm was compiled from an August 2: 0.1.1-42.20070802svn How can I tell was revision this is?

There errror does not occur everytime. Some viewport switches cause perfect auto resizes and sometimes the autoresize turns into the blank bar.

[Jack Deslippe (jdeslip)]

I am using revision 29 where this bug occurs.

[Jack Deslippe (jdeslip)]

Sorry to continue spamming this bug report, but I have discovered more about this bug. It only occurs when autohide is on. There appears to be a problem doing autohide and autoresize at the same time. I can now reproduce the bug at will. Here is what I do:

Open a bunch of windows on viewport 1. Let awn minimize, switch an empt viewport 2 and bring the mouse down to the bottom of the screen. AWN tries to both un-autohide and shink (becauset this viewport has no open windows) at the same time and ends up just causing all the icons to disappear. Opening a new window brings them back.

[Andrew Starr-Bochicchio (andrewsomething)]

I attempted to reproduce following the above steps, and after trying it repetitively I could only make this happen once. But I could make it happen none the less.

[Jack Deslippe (jdeslip)]

Today it is doesn't seem to crash every single time for me either. It seems to now happen more often if I switch from the viewport with fewer open windows to the one with more. By the way, I should mention that I have AWN set to display windows from only the current viewport (if this was not the case my description above would not make sense).

Aside - [Another bug? to notice is that when autohide is on and you bring the mouse cursor down to activate AWN, the current bouncing icon is bouncing about 3 times too fast most times. Once you move the cursor to another AWN launcher, the bouncing returns to a normal speed.

In general, it just seems like auto-hide needs a bit of work; having settings to control the speed/time of autohide would be nice as well.]

[Michal Hruby (mhr3)]

This patch fixes the issue with faster bouncing.. Unfortunately I haven't looked on the other issue.

[Jack Deslippe (jdeslip)]

Anyone figured anything out about this - it is my most major problem with AWN.

[Neil J. Patel (njpatel)]

I've been making some progress on this, but it is not perfect yet (the icons still go AWOL sometimes). Just thought i'd give an update :-)

[Jack Deslippe (jdeslip)]

Progress is good to hear!! I look forward to a version where this bug is gone ;)

[Neil J. Patel (njpatel)]

This will be fixed when awn resizes as a whole, rather than just the taskmanager.

[korvins (katarata)]

This bug is there since 2007... and it is happening every 5 minutes to me (I have autohide on).

Assuming 3 million people use awn, 1 million use it with autohide on and they hit this bug around 10 times every day, it means that in 2 years we hit the bug around 6000 million times... maybe the time to fix it has come, hasn't it?

[moonbeam (rcryderman)]

korvins,

You are correct that this bug has been in awn for far too long. Basically the original code base ( <0.4) has an architecture where autohide was/is a hack. IMO it is probably not possible to fix in <=0.3.x... and it seems that all the devs agree as no one has really tried in recent memory - fixing one thing would probably break another. I think autohide probably should have been removed once it was realized the extent of the issues but that probably would have caused even more screaming.

Anyway, 0.4 should resolve all the autohide issues. And if some issues slip through then the new architecture should allow them to be fixed without breaking something else. I know several people have been using autohide in the rewrite branch and I have not heard of any issues.

So, yes your point that it's been a long time is true. On the other hand rewrite is shaping up nicely and we expect everyone will find it wll worth the wait:-)