Bug 563387 – crash in Weather Report: Nothing

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


Summary:	crash in Weather Report: Nothing


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-12-05 21:25 UTC by Bruno Durand
Modified:	2008-12-05 23:59 UTC

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

Description Bruno Durand 2008-12-05 21:25:01 UTC

What were you doing when the application crashed?
Nothing


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24 #2 Sat Nov 1 13:00:44 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 51662848 vsize: 51662848 resident: 13467648 share: 7245824 rss: 13467648 rss_rlim: 4294967295
CPU usage: start_time: 1228510329 rtime: 429 utime: 404 stime: 25 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 0xb6d8c6b0 (LWP 5443)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 210520

Thread 1 (Thread 0xb6d8c6b0 (LWP 5443))

#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 ??
from /usr/lib/libX11.so.6
#21 ??
#22 ??
#23 ??
#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



----------- .xsession-errors (3592 sec old) ---------------------
Warning:          No symbols defined for <I7A> (keycode 250)
Warning:          No symbols defined for <I7B> (keycode 251)
Warning:          No symbols defined for <I7C> (keycode 252)
Warning:          No symbols defined for <I7D> (keycode 253)
Warning:          No symbols defined for <I7E> (keycode 254)
Warning:          No symbols defined for <I7F> (keycode 255)
** (nm-applet:3644): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.52" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:3644): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.52" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:3644): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.52" is not allowed to own the service "org.freedesktop.Networ
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Sergio Infante Montero 2008-12-05 23:59:22 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 523583 ***