GNOME Bugzilla – Bug 423292
When I click "save as" the application crashes and gives a crash report.
Last modified: 2007-03-27 11:02:01 UTC
Steps to reproduce: 1. Make a document, some text or whatever, 2. Click save as. 3. Stack trace: Memory status: size: 83456000 vsize: 0 resident: 83456000 share: 0 rss: 18345984 rss_rlim: 0 CPU usage: start_time: 1174560699 rtime: 0 utime: 524 stime: 0 cutime:507 cstime: 0 timeout: 17 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/bluefish' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226561872 (LWP 8368)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 122573
Thread 1 (Thread -1226561872 (LWP 8368))
Other information: The problem isn't showing up anymore after a reboot so i'm not able to reproduce the error. Though I think this is quite important because I kept losing all my work.
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 fixed in release 1.0.7 of bluefish. Please update to this version or apply the patch http://librarian.launchpad.net/4728944/ubuntu-bug-64016.patch to your bluefish source and re-compile. *** This bug has been marked as a duplicate of 360401 ***