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 538178 - crash in Weather Report: Rien. L'applet Bulletin ...
crash in Weather Report: Rien. L'applet Bulletin ...
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: 2008-06-13 18:16 UTC by Pierre Crescenzo
Modified: 2008-06-15 12:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Pierre Crescenzo 2008-06-13 18:16:01 UTC 
What were you doing when the application crashed?
Rien. L'applet Bulletin météo plante depuis quelques minutes (pas auparavant), apparemment à chaque fois qu'elle tente de mettre à jour le bulletin.


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: toolbox2
Icon Theme: Noia

Memory status: size: 36339712 vsize: 36339712 resident: 14839808 share: 11358208 rss: 14839808 rss_rlim: 4294967295
CPU usage: start_time: 1213380867 rtime: 18 utime: 16 stime: 2 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)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f91720 (LWP 24482)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 200337

Thread 1 (Thread 0xb6f91720 (LWP 24482))

  • #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 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (34 sec old) ---------------------
Video: no video
Starting playback...
A:   0.0 (00.0) of 0.3 (00.2) ??,?%                                             A:   0.0 (00.0) of 0.3 (00.2) ??,?%                                             A:   0.0 (00.0) of 0.3 (00.2) ??,?%   
Exiting... (End of file)
xscreensaver: 20:11:59: 0: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 20:11:59: 0: for window 0x2c00003 (gdeskcal / Gdeskcal)
xscreensaver: 20:11:59: 0: unrecognised ClientMessage "_NET_WM_DESKTOP" received
xscreensaver: 20:11:59: 0: for window 0x2c00003 (gdeskcal / Gdeskcal)
xscreensaver: 20:13:39: 0: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 20:13:39: 0: for window 0x2c00003 (gdeskcal / Gdeskcal)
xscreensaver: 20:13:39: 0: unrecognised ClientMessage "_NET_WM_DESKTOP" received
xscreensaver: 20:13:39: 0: for window 0x2c00003 (gdeskcal / Gdeskcal)
xscreensaver: 20:14:05: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 20:14:05: 0: for window 0x1218f3b (gnome-panel / Gnome-panel)
--------------------------------------------------
Comment 1 André Klapper 2008-06-15 12:03:45 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 ***