GNOME Bugzilla – Bug 150787
gconf-editor - Crash when selecting /apps/panel/default_setup/applets/clock
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gconf-editor Severity: major Version: GNOME2.7.1 unspecified Gnome-Distributor: Gnome.org Synopsis: gconf-editor - Crash when selecting /apps/panel/default_setup/applets/clock Bugzilla-Product: gconf-editor Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.7.1) Description: Description of the crash: gconf-editor (gconf-editor-2.7.0-1.1.fc2.nr) crashes when selecting "/apps/panel/default_setup/applets/clock" Steps to reproduce the crash: 1. Open gconf-editor 2. Navigate to /apps/panel/default_setup/applets 3. Select "clock" Expected Results: Normal behavior would be to show the configuration options for the clock panel applet. How often does this happen? 100% reproducible Additional Information: I'm using: gnome-applets-2.6.1-2.1.fc2.nr gconf-editor-2.7.0-1.1.fc2.nr on Fedora Core 2 (x86) Debugging Information: Backtrace was generated from '/usr/bin/gconf-editor' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1073862272 (LWP 19828)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in ?? ()
+ Trace 49545
Thread 1 (Thread 1073862272 (LWP 19828))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-22 14:14 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gconf-editor". Setting to default milestone for this product, '---' 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.
This was fixed on 2.7.1