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 619069 - GNOME clock applet displays its calendar/locations popup window too high when used in the bottom panel
GNOME clock applet displays its calendar/locations popup window too high when...
Status: RESOLVED DUPLICATE of bug 622254
Product: gnome-panel
Classification: Other
Component: clock
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-19 10:29 UTC by Davy Defaud
Modified: 2010-10-04 22:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
clock popup window too high (289.93 KB, image/png)
2010-05-19 10:29 UTC, Davy Defaud
Details

Description Davy Defaud 2010-05-19 10:29:23 UTC
Created attachment 161421 [details]
clock popup window too high

When the GNOME clock applet is used in the bottom panel. The popup window displaying calendar/locations when you click on the applet, has a wrong vertical position that is too high. This vertical offset seems to be equal to the window's height.
See the attached screenshot...
Comment 1 Dylan Grose 2010-05-31 17:47:50 UTC
I can confirm this on Fedora 13 with GNOME 2.30.0. The clock applet window is actually truncated on top if the "Locations" pane is expanded, so I can't see most of it (since the submitter's screen resolution appears to be larger than mine, this makes sense since the offset from the bottom does appear to always be equal to the current height of the popup window).
Comment 2 Glen 2010-06-03 10:42:36 UTC
I also have this issue after upgrading FC12-64  to FC13-64
Comment 3 Gábor Czombos 2010-09-21 10:45:52 UTC
Ubuntu 10.10, also affected.
Comment 4 Oliver 2010-10-04 22:06:04 UTC
Running Ubuntu 10.10 as well. The bug is only present *while running Compiz*.
Comment 5 Vincent Untz 2010-10-04 22:58:19 UTC
See bug 622254.

*** This bug has been marked as a duplicate of bug 622254 ***