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 697301 - 'Open Clocks' shows even when gnome-clocks isn't installed
'Open Clocks' shows even when gnome-clocks isn't installed
Status: RESOLVED DUPLICATE of bug 697725
Product: gnome-shell
Classification: Core
Component: calendar
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-04-05 00:19 UTC by Jeremy Bicha
Modified: 2013-05-16 21:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeremy Bicha 2013-04-05 00:19:14 UTC 
Ubuntu GNOME 13.04 with GNOME Shell 3.8.0.1

According to https://git.gnome.org/browse/gnome-shell/commit/?id=5e5798 the 'Open Clocks' menu item in the clock menu in the top bar is only supposed to show if gnome-clocks is installed. However it always shops up.

(Personally, I'm hesitant to install gnome-clocks by default in Ubuntu GNOME until bug 689082 is fixed.)
Comment 1 darkxst 2013-04-05 05:47:26 UTC 
The Clocks menu item, does get hidden after the 'installed-changed' signal fires.

Perhaps AppSystem is just not ready when dateMenu first loads?
Comment 2 Pacho Ramos 2013-04-27 14:41:49 UTC 
We see the same problem on Gentoo: button is shown even when gnome-clocks is not installed
Comment 3 Colin Walters 2013-04-27 15:13:08 UTC 
For what it's worth I just decided to make gnome-clocks mandatory.
Comment 4 Pacho Ramos 2013-05-09 19:54:22 UTC 
Do you have any idea about why is currently failing to drop the entry when it's not available? Workarounding it making the dependency a hard requirement looks overkill to me :/
Comment 5 Jeremy Bicha 2013-05-16 21:50:47 UTC 
I'm no longer able to duplicate this bug with gnome-shell 3.8.2 and gnome-clocks not installed. I'm going to mark this a duplicate of bug 697725 which I think fixed this issue.

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