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 138467 - Clock Applet crashes
Clock Applet crashes
Status: RESOLVED DUPLICATE of bug 136721
Product: gnome-panel
Classification: Other
Component: clock
1.5.x
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-30 03:42 UTC by damirc
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description damirc 2004-03-30 03:42:15 UTC 
Distribution: Fedora Core release 1.91 (FC2)
Package: gnome-panel
Severity: normal
Version: GNOME2.5.91 0
Gnome-Distributor: Red Hat, Inc
Synopsis: Clock Applet crashes
Bugzilla-Product: gnome-panel
Bugzilla-Component: clock applet
Bugzilla-Version: 0
BugBuddy-GnomeVersion: 2.0 (2.5.92)
Description:
Description of the crash:
The applet crashes completely and needs to be restarted.	

Steps to reproduce the crash:
1. Right click on the clock applet in the panel
2. Click on preferences
3. Crash

Expected Results:
Preference window opens?

How often does this happen?
Always.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-29 22:42 -------


Unknown version 0 in product gnome-panel. Setting version to "1.5.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-panel".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was damirc@gmx.net.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Mark McLoughlin 2004-03-30 06:10:42 UTC 

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