GNOME Bugzilla – Bug 443651
crash in Dia Diagram Editor: openin` visio (.vsd) =)
Last modified: 2007-10-27 11:48:06 UTC
Version: @0.96@ What were you doing when the application crashed? openin` visio (.vsd) =) Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 67149824 vsize: 67149824 resident: 42008576 share: 14962688 rss: 42008576 rss_rlim: 4294967295 CPU usage: start_time: 1180894885 rtime: 588 utime: 512 stime: 76 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/dia' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209129248 (LWP 3514)] (no debugging symbols found) 0x008ab402 in __kernel_vsyscall ()
+ Trace 137885
Thread 1 (Thread -1209129248 (LWP 3514))
I'm unable to reproduce your problem, because my Dia does not offer to open *.vsd files, only *.vdx files. Could you provide a sample file that causes the problem?
Dia does not understand .vsd files at all, so it makes a last-ditch attempt at opening them as .dia files, which fails. It shouldn't crash, though. It would be nice to get the file that causes the problem, as random samples I've drawn from the net are nicely rejected.
In fact dia did crash on every failed load into the default diagram. It was not specific to the import file format. 2007-10-27 Hans Breuer <hans@breuer.org> * app/diagram.c(diagram_load) : don't kill the default diagram on import failure. Fixes bug #490546
*** Bug 448203 has been marked as a duplicate of this bug. ***
*** Bug 470782 has been marked as a duplicate of this bug. ***
*** Bug 489573 has been marked as a duplicate of this bug. ***
*** Bug 490546 has been marked as a duplicate of this bug. ***