Bug 565601 – crash in Weather Report:

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 565601 - crash in Weather Report:


Summary:	crash in Weather Report:


Status:	RESOLVED DUPLICATE of bug 529773

Product:	gnome-applets
Classification:	Other
Component:	gweather
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-12-25 07:18 UTC by Feza CAKIR
Modified:	2009-01-08 14:56 UTC

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

Description Feza CAKIR 2008-12-25 07:18:42 UTC

What were you doing when the application crashed?



Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Mon Dec 15 18:15:07 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: LiNsta-0.3

Memory status: size: 33312768 vsize: 33312768 resident: 11624448 share: 9138176 rss: 11624448 rss_rlim: 4294967295
CPU usage: start_time: 1230189298 rtime: 16 utime: 12 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/gweather-applet-2'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e346b0 (LWP 10768)]
(no debugging symbols found)
0xb7f74424 in __kernel_vsyscall ()

+ Trace 211059

Thread 1 (Thread 0xb6e346b0 (LWP 10768))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/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 <signal handler called>
#7 g_markup_escape_text
from /usr/lib/libglib-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
#10 ??
#11 ??
#12 g_value_transform
from /usr/lib/libgobject-2.0.so.0
#13 g_object_set_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_object_set
from /usr/lib/libgobject-2.0.so.0
#15 gtk_widget_set_tooltip_text
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#0 __kernel_vsyscall



----------- .xsession-errors (33300 sec old) ---------------------
 to Thu Dec 25 00:00:01 2008
alarm-queue.c:544 (load_alarms) 
alarm-queue.c:563 (load_alarms) - Disconnecting old queries 
alarm-queue.c:573 (load_alarms) - Setting Call backs 
alarm-queue.c:247 (add_client_alarms_cb) - Adding (nil)
alarm-queue.c:607 (load_alarms_for_today) - From Thu Dec 25 00:00:01 2008
 to Thu Dec 25 00:00:01 2008
alarm-queue.c:544 (loevolution-alarm-notify-Message: alarm.c:246: Requested removal of nonexistent alarm!
evolution-alarm-notify-Message: Setting timeout for 86400 1230242400 1230156000
evolution-alarm-notify-Message:  Fri Dec 26 00:00:00 2008
evolution-alarm-notify-Message:  Thu Dec 25 00:00:00 2008
--------------------------------------------------

Comment 1 palfrey 2009-01-08 14:56:28 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 529773 ***