GNOME Bugzilla – Bug 167401
Dia crashes when diagram window closed
Last modified: 2006-02-26 16:17:20 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: dia Severity: minor Version: GNOME2.8.0 0.94 Gnome-Distributor: Red Hat, Inc Synopsis: Dia crashes when diagram window closed Bugzilla-Product: dia Bugzilla-Component: general Bugzilla-Version: 0.94 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: I closed a diagram window using the upper right cross on a saved diagram, the program crashed altogether Steps to reproduce the crash: 1. See above 2. 3. Expected Results: Diagram window should close normally, leaving the application still running How often does this happen? First time I have used the application. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/dia' (no debugging symbols found)...Using host libthread_db library "/lib64/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)...[Thread debugging using libthread_db enabled] [New Thread 46912496370464 (LWP 6335)] (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)...(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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x0000003f0b30bff4 in waitpid () from /lib64/tls/libpthread.so.0
+ Trace 55708
Thread 1 (Thread 46912496370464 (LWP 6335))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-14 17:26 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "dia". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was euanmaxwell@gmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Looks similar to the stack trace in bug 152682...
or bug 163574. *** This bug has been marked as a duplicate of 163574 ***
Oops, dup setting shouldn't have been committed. Looks very much like bug 152682 indeed, but this one is not invalid. Reopening, but not marking dup of 152682
Maybe a 64bit issue or a general fedora build problem like bug #154637. Could you please provide what Dia dumps to console. This *may* be more useful than the stack trace. Thanks, Hans
*** Bug 305793 has been marked as a duplicate of this bug. ***
A bunch of diagram-close related bugs was fixed and 0.95 is almost out. Please give it a try.