Notification baloon tooltip appears in wrong place

[Martin Olsson]

I just booted Gutsy Tribe 5 and noticed that the baloon tooltip appeared in the wrong place. It appears to start from a random location instead of starting at the little corresponding icon (next to the battery etc).

[Martin Olsson (mnemo)]

Look at this screenshot and the problem should be very clear.

[Martin Olsson (mnemo)]

I've seen similar bug reports before for other applications. In those bug reports people were suggesting that the "hint coordinates" for the baloon might me wrong? Should like GNOME menu provide coords for this baloon though? Maybe it's a gnome bug maybe it's a restricted-drivers-manager bug? I'm not sure...

[Martin Olsson (mnemo)]

Just so there is no confusion; I expected this baloon to be starting or "coming from" the little green circuit icon that appears next to the little battery icon on the top-leftish area of the screen.

[LEVIS Cyril (atlas95)]

Yes, same problem with a lot of apps, for example at boot start, sometime popup come but the icon systray isn't appears yet, and the ballon is not at the good place...

[Alan Young (alanfyoung)]

Same problem with me, the balloon appears at exactly the same location as in mnemo's screenshot.

[Nanley Chery (nanoman)]

1st time i booted the live cd, same thing happend. 2nd time, it was in the right place.
This also happens when network manager says i'm connected to a network.

[Nanley Chery (nanoman)]

I've set the restricted-manager and update-notifier packages to invalid because the notification-daemon handles notifications? If i'm wrong, please change it and tell me why.

[Pascal De Vuyst (pascal-devuyst)]

The restricted-manager and update-notifier tasks were added because this comment was made in one of the duplicates:
I initially thought this was a bug in the notification library, but apparently it is caused by constructing the notification message before the icon is placed in the bar.
So it could be a problem with the mentioned applications, a developer with more knowledge about notifications should be able to tell.

[Alex Mayorga (alex-mayorga)]

This still happens randomly on Hardy, especially with the "Restricted Drivers Manager".

[Jeenu V (jeenuv)]

I'm seeing the same problem with Ibex release as well.

I've the task and main-menu bar moved to the bottom and I removed the top desktop-menu. I.e. it's exactly like MS Windows. But I still see the balloons appearing at the top-left of desktop, pointing upwards, as if my menu is there.

[xteejx (xteejx)]

This isn't a problem in Jaunty, but then it wouldn't be as the notification system is completely different now using the OSD. Can you provide steps to reproduce this please?
Also, is this really a bug in:
restricted-manager, i.e. does the notification error ONLY happen when there are restricted drivers, and
update-notifier, i.e. does this happen ONLY when there are updates?
If it is both it is unlikely that both of these packages are the problem, but the notification-daemon itself.
Please confirm. Thank you.

[Habib (habibseifzadeh)]

The problem still remains in Karmic beta.

The balloons are shown only at the top right corner of the screen regardless of the location of notification area applet in the panel...

[A. Walton (awalton)]

That's because Notify-OSD does not support setting the locations on the screen: it's only supported by Notification-Daemon. The original bug is very likely update-notifier's problem with not setting the attach hint correctly (as many other apps still do this, the test case for it passes). Could be a bug in python-libnotify...

[Peter (fpeter)]

looks in karmic (Linux darktop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux) has the same problem
there is a screenshot of a message from thunderbird, the same happens on "network connected" or "disconnected" message too

[xteejx (xteejx)]

I think it's safe to say that this should be set "Won't Fix". The 2 main reasons being that this was reported against, and continues in old/unsupported versions of Ubuntu, and that newer versions of Ubuntu are extremely unlikely to come across this based on updated notification areas, daemons, etc. especially with Unity coming in Natty.
If you feel this is wrong, or it still affects you, please reopen this bug report by changing the status back to New, or perhaps for quicker review of the bug, just file a new one with ubuntu-bug. Thank you.