GNOME Bugzilla – Bug 301805
Gweather crashing
Last modified: 2010-01-24 01:06:16 UTC
Distribution: Debian 3.1 Package: gnome-applets Severity: normal Version: GNOME2.10.0 0 Gnome-Distributor: Ubuntu Synopsis: Gweather crashing Bugzilla-Product: gnome-applets Bugzilla-Component: gweather Bugzilla-Version: 0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Unknown/unexpected crash of the applet Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? 1st time Additional Information: Terminated while left running for 6+ hours. Debugging Information: Backtrace was generated from '/usr/libexec/gweather-applet-2' Using host libthread_db library "/lib/tls/i686/cmov/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) [Thread debugging using libthread_db enabled] [New Thread -1221689216 (LWP 10213)] [New Thread -1225528400 (LWP 10266)] [New Thread -1224754256 (LWP 10216)] [New Thread -1224029264 (LWP 10215)] [New Thread -1223763024 (LWP 10214)] (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) (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) 0xffffe410 in ?? ()
+ Trace 58644
Thread 4 (Thread -1224029264 (LWP 10215))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-24 16:21 ------- Unknown version 0 in product gnome-applets. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-applets". 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 juanjr@vt.edu. 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.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
*** Bug 302088 has been marked as a duplicate of this bug. ***
*** Bug 304173 has been marked as a duplicate of this bug. ***
*** Bug 316987 has been marked as a duplicate of this bug. ***
*** Bug 317206 has been marked as a duplicate of this bug. ***
All of these stacktraces seem pretty awful and so it is actually hard to tell, but I think they are all #170628. *** This bug has been marked as a duplicate of 170628 ***