Bug 535391 – crash in Weather Report: Change the setting of th...

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 535391 - crash in Weather Report: Change the setting of th...


Summary:	crash in Weather Report: Change the setting of th...


Status:	RESOLVED DUPLICATE of bug 523583

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-05-29 03:53 UTC by y-hayase
Modified:	2008-06-15 12:03 UTC

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

Description y-hayase 2008-05-29 03:53:30 UTC

What were you doing when the application crashed?
Change the setting of the location.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686-bigmem #1 SMP Sat Apr 19 01:23:53 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 81539072 vsize: 81539072 resident: 24199168 share: 14561280 rss: 24199168 rss_rlim: 4294967295
CPU usage: start_time: 1212033043 rtime: 140 utime: 130 stime: 10 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 0xb6fa0720 (LWP 26573)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 198929

Thread 1 (Thread 0xb6fa0720 (LWP 26573))

#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 <signal handler called>
#6 g_markup_escape_text
from /usr/lib/libglib-2.0.so.0
#7 ??
from /usr/lib/libgtk-x11-2.0.so.0
#8 ??
#9 ??
#10 ??
#11 g_value_transform
from /usr/lib/libgobject-2.0.so.0
#12 g_object_set_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_object_set
from /usr/lib/libgobject-2.0.so.0
#14 gtk_widget_set_tooltip_text
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
from /usr/lib/libglib-2.0.so.0
#20 ??
#21 ??
#22 ??
#23 ??
from /usr/lib/libgthread-2.0.so.0
#24 ??
#25 __pthread_mutex_unlock_usercnt
from /lib/i686/cmov/libpthread.so.0
#26 requests_done_check
from /usr/lib/libgweather.so.1
#27 close_cb
from /usr/lib/libgweather.so.1
#28 ??
from /usr/lib/libgnomevfs-2.so.0
#29 ??
#30 ??
#0 __kernel_vsyscall

Comment 1 Diego Escalante Urrelo (not reading bugmail) 2008-05-31 06:51:29 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 2 André Klapper 2008-06-15 12:03:34 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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