GNOME Bugzilla – Bug 328895
Attempts to open the Navigation window cause dia to crash
Last modified: 2006-01-27 23:10:17 UTC
Distribution: Debian testing/unstable Package: dia Severity: Normal Version: GNOME2.12.2 0.94 Gnome-Distributor: Debian Synopsis: Attempts to open the Navigation window cause dia to crash Bugzilla-Product: dia Bugzilla-Component: general Bugzilla-Version: 0.94 Description: Description of Problem: The diagram window has a button in the lower right that reads "Pops up the Navigation window." Clicking on this button results in dia-gnome crashing with an error dialog 'The Application "dia-gnome" has quit unexpectedly.' Steps to reproduce the problem: 1. Launch dia-gnome. 2. Click on the "Pops up Navigation window." button. Actual Results: Dia-gnome crashes Expected Results: The Navigation window opens. How often does this happen? Every time the button is clicked Additional Information: Launching dia-gnome from a terminal window provides no additional information. No errors show in the console. Launching dia (non-gnome version) results in a crash with no error dialog, but the terminal window reads "Segmentation fault". Running 'strace dia' shows that the application was attempting to open a file named "sys" prior to the segfault. stat64("sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/lib/python2.3/site-packages/gtk-2.0/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/share/dia/python/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/lib/python23.zip/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/lib/python2.3/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/lib/python2.3/plat-linux2/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/lib/python2.3/lib-tk/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/lib/python2.3/lib-dynload/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/local/lib/python2.3/site-packages/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/lib/python2.3/site-packages/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/lib/python2.3/site-packages/Numeric/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) stat64("/usr/lib/python2.3/site-packages/cairo/sys", 0xbfac0838) = -1 ENOENT (No such file or directory) write(2, "sys:1: GtkWarning: gdk_cursor_un"..., 78sys:1: GtkWarning: gdk_cursor_unref: assertion `cursor->ref_count > 0' failed ) = 78 --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ ------- Bug created by bug-buddy at 2006-01-27 21:01 ------- Bugreport had an attachment. This cannot be imported to Bugzilla. Contact bugmaster@gnome.org if you are willing to write a patch for this.
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 marked as a duplicate of 151696 ***
I don't think this is the same issue. Only a single click is required to cause this segfault and the gdk error messages are different. In any case, the Debian maintainers for dia are fairly active, so I'll wait and see if they incorporate the fix in the next update. Thank you, Pete White
IIRC the issue was a race between window construction and destruction. This could give different messages depending on the speed of your machine. And the speed of your click. Leaving duplicate. Feel free to reopen if the issue persists with the upcoming release.