Bug 533325 – crash in Clock: Setting weather location

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 533325 - crash in Clock: Setting weather location


Summary:	crash in Clock: Setting weather location


Status:	RESOLVED DUPLICATE of bug 519493

Product:	gnome-panel
Classification:	Other
Component:	clock
Version:	2.22.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-05-15 18:11 UTC by marc
Modified:	2008-05-15 21:18 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description marc 2008-05-15 18:11:30 UTC

Version: 2.22.0

What were you doing when the application crashed?
Setting weather location


Distribution: Unknown
Gnome Release: 2.22.0 2008-03-11 (Foresight Linux)
BugBuddy Version: 2.22.0

System: Linux 2.6.23.16-0.0.1.smp.gcc4.1.x86.i686 #1 SMP Tue Feb 12 00:14:27 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Foresight
Icon Theme: Tango

Memory status: size: 95178752 vsize: 95178752 resident: 19427328 share: 13533184 rss: 19427328 rss_rlim: 4294967295
CPU usage: start_time: 1210874281 rtime: 308 utime: 289 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/clock-applet'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb681b900 (LWP 3258)]
0xb7f95410 in __kernel_vsyscall ()

+ Trace 197812

Thread 1 (Thread 0xb681b900 (LWP 3258))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#8 <signal handler called>
#9 clock_map_place_locations
at clock-map.c line 432
#10 highlight
at clock-map.c line 673
#11 ??
from /usr/lib/libglib-2.0.so.0
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
from /usr/lib/libglib-2.0.so.0
#17 ??
from /usr/lib/libglib-2.0.so.0
#18 ??
from /lib/libpthread.so.0
#19 ??
#20 ??
from /usr/lib/libglib-2.0.so.0
#21 ??
#22 ??
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#0 __kernel_vsyscall



----------- .xsession-errors (46 sec old) ---------------------
5/15/2008 7:09:49 PM [Info]: Updated first results for 'w'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'x'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'y'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'a'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'b'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'c'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'd'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'e'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'f'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'g'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'h'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'i'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'j'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'k'.
5/15/2008 7:09:49 PM [Info]: Updated first results for 'l'.
--------------------------------------------------

Comment 1 Philip Withnall 2008-05-15 21:18:58 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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