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 573632 - crash in Weather Report: adding it to the panel
crash in Weather Report: adding it to the panel
Status: RESOLVED DUPLICATE of bug 523583
Product: gnome-applets
Classification: Other
Component: gweather
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-01 14:18 UTC by juhani.karlsson
Modified: 2009-03-02 00:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description juhani.karlsson 2009-03-01 14:18:16 UTC 
What were you doing when the application crashed?
adding it to the panel


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

System: Linux 2.6.26.043-lrdlnx #1 SMP PREEMPT Mon Feb 2 02:22:53 EET 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: Tango

Memory status: size: 31924224 vsize: 31924224 resident: 11227136 share: 9076736 rss: 11227136 rss_rlim: 4294967295
CPU usage: start_time: 1235917040 rtime: 15 utime: 12 stime: 3 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 0xb6f346b0 (LWP 31896)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 213023

Thread 1 (Thread 0xb6f346b0 (LWP 31896))

  • #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 (23 sec old) ---------------------
Ikkunointiohjelman varoitus:Virheellinen WM_TRANSIENT_FOR ikkuna 0x4400008 kohteelle 0x4400221 (Kaffeine P).
Ikkunointiohjelman varoitus:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400008 (Prisma_ Yd)
Ikkunointiohjelman varoitus:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
kbuildsycoca running...
DCOP Cleaning up dead connections.
Ikkunointiohjelman varoitus:Virheellinen WM_TRANSIENT_FOR ikkuna 0x4400008 kohteelle 0x44000e8 (Kaffeine P).
Ikkunointiohjelman varoitus:Virheellinen WM_TRANSIENT_FOR ikkuna 0x4400008 kohteelle 0x44001f9 (Kaffeine P).
Ikkunointiohjelman varoitus:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400008 (Prisma_ Yd)
Ikkunointiohjelman varoitus:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Ikkunointiohjelman varoitus:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400008 (Prisma_ Yd)
Ikkunointiohjelman varoitus:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(gnome-panel:29787): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80ecb58
(gnome-panel:29787): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80ecb58
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-03-02 00:16:11 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.


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