GNOME Bugzilla – Bug 377250
(BlueFish) Finish of application when the document is save (ctrl+s)
Last modified: 2006-11-20 13:04:22 UTC
Please describe the problem: The program lets respond when I save of manual form or with accelerating (ctrl+s). Steps to reproduce: 1. Pressing the Ctrl+s accelerator to save. Actual results: the application finalizes of unexpected way Expected results: That satifactoria saved the document of form, without finalize the application Does this happen every time? Whenever it is tried to save. Other information: Distribution: Debian 4.0 Package: bluefish Version: GNOME2.14.3 unspecified Gnome-Distributor: Debian Bluefish Version 1.0.6 Debugging Information: Backtrace was generated from '/usr/bin/bluefish' (no debugging symbols found) Using host libthread_db library "/lib/tls/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 -1493969216 (LWP 17175)] [New Thread -1498240080 (LWP 17182)] (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) 0xa73db231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 87873
Thread 1 (Thread -1493969216 (LWP 17175))
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. Thanks in advance!
This bug is fixed in the 1.0.7 release. *** This bug has been marked as a duplicate of 360401 ***