GNOME Bugzilla – Bug 567017
crash in Weather Report: writting in vim
Last modified: 2009-01-08 14:55:47 UTC
What were you doing when the application crashed? writting in vim Distribution: Debian 5.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686-bigmem #1 SMP Mon Dec 15 18:58:47 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: 50417664 vsize: 50417664 resident: 20316160 share: 11657216 rss: 20316160 rss_rlim: 4294967295 CPU usage: start_time: 1231403984 rtime: 138 utime: 130 stime: 8 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 0xb6ef19e0 (LWP 8376)] (no debugging symbols found) 0xb7fb8424 in __kernel_vsyscall ()
+ Trace 211382
Thread 1 (Thread 0xb6ef19e0 (LWP 8376))
----------- .xsession-errors (78 sec old) --------------------- OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) OggS-SEEK: at 6848 want 1032 got 0 (diff-requested -5816) --------------------------------------------------
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 529773 ***