GNOME Bugzilla – Bug 425748
crash in Drivel Journal Editor: writing a blog post to n...
Last modified: 2007-04-15 19:59:51 UTC
What were you doing when the application crashed? writing a blog post to new Blogger with several other applications open, particularly kdirstat and the gnome disk usage tool. The crash went down just after I opened the graphic map in the gnome disk tool. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 47714304 vsize: 0 resident: 47714304 share: 0 rss: 14376960 rss_rlim: 0 CPU usage: start_time: 1175580194 rtime: 0 utime: 583 stime: 0 cutime:521 cstime: 0 timeout: 62 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/drivel' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1230633296 (LWP 6613)] [New Thread -1232069728 (LWP 6616)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 124529
Thread 1 (Thread -1230633296 (LWP 6613))
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 355701 ***