After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 603985 - GtkStatusIcon tooltips appear in the wrong position after closing context menu
GtkStatusIcon tooltips appear in the wrong position after closing context menu
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other Linux
: Normal minor
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-12-07 15:09 UTC by Michael Doube
Modified: 2010-01-14 14:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Doube 2009-12-07 15:09:31 UTC
If I right click on a notification area icon (nm-applet, audio applet, battery applet) to see its context menu, then left click on the icon to close the menu, the tooltip turns up in the wrong place, on the top left hand corner of the screen. This only appears to affect notification area applets and not ordinary launchers.

ProblemType: Bug
Architecture: amd64
CheckboxSubmission: d6587df64f5abea33dcf94c42360ad73
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
Date: Sun Dec 6 12:14:58 2009
DistroRelease: Ubuntu 9.10
Package: gnome-panel 1:2.28.0-0ubuntu6
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: gnome-panel
Uname: Linux 2.6.31-15-generic x86_64
Comment 1 Michael Doube 2009-12-07 15:12:44 UTC
Also being tracked downstream at:
https://bugs.launchpad.net/gnome-panel/+bug/493128
Comment 2 Vincent Untz 2010-01-14 00:54:27 UTC
Screenshot at http://launchpadlibrarian.net/36497226/Screenshot-1.png

This is not handled by the notification area, but GtkStatusIcon, I guess.
Comment 3 Michael Doube 2010-01-14 14:39:03 UTC
After Vincent's interest in this bug I tried to replicate it and can't do so anymore so it looks as though something has fixed it.  Will reopen the bug if it reappears.