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 546311 - crash in Weather Report: Hello, I was doing noth...
crash in Weather Report: Hello, I was doing noth...
Status: RESOLVED DUPLICATE of bug 535865
Product: gnome-applets
Classification: Other
Component: gweather
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 547150 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-08-04 20:16 UTC by zepep
Modified: 2008-10-08 15:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
Backtrace with debugging symbols (9.19 KB, text/plain)
2008-08-11 16:14 UTC, Tomi Riitahaara 		Details

Description zepep 2008-08-04 20:16:46 UTC 
What were you doing when the application crashed?
Hello,

I was doing nothing but trying to launch the applet. It just crashed down by itself. The problems started after some update of my OS, I don't know which specific package of gnome weather was concerned.
I also tried to reinstall it, no more success.

Thank you for your work to this applet, it is useful.

Regards,
Benoit


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

System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 44257280 vsize: 44257280 resident: 13447168 share: 9572352 rss: 13447168 rss_rlim: 4294967295
CPU usage: start_time: 1217879081 rtime: 15 utime: 11 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 0xb6e54910 (LWP 3466)]
(no debugging symbols found)
0xb7fa7424 in __kernel_vsyscall ()

+ Trace 204585

Thread 1 (Thread 0xb6e54910 (LWP 3466))

  • #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 ??
  • #20 ??
  • #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 






Comment 1


Jens Granseuer





          2008-08-10 14:25:44 UTC
        



*** Bug 547150 has been marked as a duplicate of this bug. ***






Comment 2


Jens Granseuer





          2008-08-10 14:26:11 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 3


Tomi Riitahaara





          2008-08-11 16:14:10 UTC
        



Created attachment 116362 [details]
Backtrace with debugging symbols






Comment 4


Tomi Riitahaara





          2008-08-16 07:21:07 UTC
        



Comment on attachment 116362 [details]
Backtrace with debugging symbols

I tried to make a stack trace with debugging symbols? Hope this helps!

- Tomi






Comment 5


Callum McKenzie





          2008-09-02 01:02:30 UTC
        



The stack trace definitely helps. I've had two guesses about whats causing it: one is that glib is stuffing up somehow (it appears to be passed a legitimate string). The other is that it only appears to be passed a legitimate string, and that bug 535865 is the cause.

Still looking into this problem.







Comment 6


Dan Winship





          2008-10-08 15:40:59 UTC
        



fixed with libgweather 2.24.1

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