AWN launches on startup but is "invisible"

Thanks for filing a bug.

Per the bug reporting guidelines (located next to the bug reporting form), we need the following information, in order to properly diagnose the problem:

* Distribution name and version
* Method of installing Awn (if via repository, which repository? If from source, via tarball or bzr? any other distribution-specific configuration with regards to these packages?)
* Awn version (if from bzr, which branch and which revision?)
* Window manager used when running Awn
* Video card and driver name/version (for example, nvidia GeForce2 GTS/Pro, nvidia binary drivers version 7182)
* If it's a crash/segfault, a backtrace.

Here's all the info I could find (I've only been using Ubuntu for a few months) - the one thing I couldn't find was the video driver info....

Distribution name and version: Ubuntu 10.04

Method of installing Awn: Ubuntu Software Center

Awn version: 0.4.0-0ubuntu1

Window manager used when running Awn: Compiz

Video card and driver name/version: Intel Corporation Mobile 945GME Express Integrated Graphics Controller rev 03

Same here:

Distribution name and version: Ubuntu 10.04

Method of installing Awn: Ubuntu Software Center

Awn version: 0.4.0-0ubuntu1

Window manager used when running Awn: Compiz

Video: Intel Mobile 915GM (Haven't loaded any proprietary drivers so whatever the default is... not sure how to look it up)

Also this bug is intermittent sometimes when I start up it loads fine but about half the time it's invisible.

Edit the autostart entry to have this exec line: "avant-window-navigator --startup --startup-delay=10" (System -> Preferences -> Startup Applications in GNOME)

Here's another thing I've noticed - this bug seems to crop up when my system was not shut down properly (e.g. my laptop runs out of power) and is then restarted. If I do a proper shutdown/restart it's more likely to be just fine.

Could this be related to bug 499382 - invisible after suspend?

No, #499382 is not related to this.

This happened to me once, but I have an ATI graphics card and using the open drivers. Maybe because it starts before Compiz?

Happens to me about 70% of the time, exactly as described, the rest of the time it works as expected. (That is, it is visible) Nothing I can do any differently makes it boot up visible or invisible, it is just a random occurrence.
Ubuntu 10.04
Gnome 2.30.0
Kernel 2.6.32-22-generic
Intel(R) Celeron(R) M processor 1.40GHz
GPU Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)

I finally got mine to work - it used to 100% of the time *not* come up properly, now by simply changing my startup item entry to include --startup-delay=20 (not 10, as mentioned previously - your mileage may vary) it works perfectly 100% of the time.

if you have interesting check my duplicated bugs for see my logs about this problem

https://bugs.launchpad.net/ubuntu/+source/avant-window-navigator/+bug/599693

Ubuntu Lucid 10.04
ASUS eee PC 1001p (Atom N450 @ 1.67GHz, 2GB RAM, 160GB hdd, Intel GMA3150 graphics)

I had to give a startup delay of 75 seconds before I could see anything.

Okay, I had this issue, and with startup-delay added, it worked fine. But GNOME-DO refuses to start (its there in the startup). Now on removing the startup-delay, GNOME-DO starts. Any idea? I have tried with delay of 5,10,15 secs.

Same problem invisible at startup:

Distribution name and version: Linux Mint 9 Isadora, Linux 2.6.32.21.22-generic (i686)
Desktop Environment: GNOME 2.30.2

Method of installing Awn: synaptic 0.63.1ubuntu7
Awn version: 0.4.0-0ubuntu1 (lucid)

Window manager used when running Awn: OpenGL window and compositing manager: compiz 1:0.8.4-0ubuntu15 (lucid)
Desktop Settings: Use Gnome compositing

Video card and driver name/version:
ATI embedded RADEON 9100 IGP (integrated 9200-based 2D/3D GPU), X.Org X server -- AMD/ATI Radeon display driver 1:6.13.0-1ubuntu5

I kinda had a similar problem so I'd like to sharing a solution. Awn used to work nicely for me but after I upgraded to Ubuntu 10.10 it now started with a 5-10 seconds delay. It was not visible nor running in the background, neither was anything keeping the system busy (I keep my startup soft list very small), I just had to wait some 10 secs before it started. Adding the "--startup-delay=XX" did not help but only made it start even later. What solved the problem for me was removing the "--startup" option that was in the startup string. Now Awn starts immediately, regardless if the "--startup-delay=XX" option is there or not (probably it is not considered at all without the "--startup"). Apparently something weird is happening if the "--startup" is used.
I know that is not fully relevant to this bug, and I'm sorry for o/t, but my search for answers brought me here and comments in this thread helped me out, so I decided to write here too, in case someone else has a similar problem.