Bug 492645 – crash in Dia Diagram Editor: Importing a Microsoft Vi...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 492645 - crash in Dia Diagram Editor: Importing a Microsoft Vi...


Summary:	crash in Dia Diagram Editor: Importing a Microsoft Vi...


Status:	RESOLVED DUPLICATE of bug 490546

Product:	dia
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Dia maintainers
QA Contact:	Dia maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-02 10:20 UTC by s1ick
Modified:	2007-11-02 19:28 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description s1ick 2007-11-02 10:20:18 UTC

Version: @0.96.1@

What were you doing when the application crashed?
Importing a Microsoft Visio file into Dia Diagram editor.  The file being imported is a .vsd file as opposed to a .vsx file and may be the problem


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 73658368 vsize: 73658368 resident: 49029120 share: 22011904 rss: 49029120 rss_rlim: 4294967295
CPU usage: start_time: 1193998688 rtime: 432 utime: 373 stime: 59 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 -1208604960 (LWP 2926)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 174569

Thread 1 (Thread -1208604960 (LWP 2926))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 __assert_fail
from /lib/libc.so.6
#8 ??
#9 g_object_unref
from /lib/libgobject-2.0.so.0
#10 diagram_load
#11 ??
#12 g_cclosure_marshal_VOID
from /lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /lib/libgobject-2.0.so.0
#14 ??
from /lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#16 g_signal_emit
from /lib/libgobject-2.0.so.0
#17 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /lib/libgobject-2.0.so.0
#21 ??
from /lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#23 g_signal_emit
from /lib/libgobject-2.0.so.0
#24 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib/libgtk-x11-2.0.so.0
#26 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#27 ??
from /lib/libgobject-2.0.so.0
#28 g_closure_invoke
from /lib/libgobject-2.0.so.0
#29 ??
from /lib/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#31 g_signal_emit
from /lib/libgobject-2.0.so.0
#32 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
from /lib/libgobject-2.0.so.0
#36 g_closure_invoke
from /lib/libgobject-2.0.so.0
#37 ??
from /lib/libgobject-2.0.so.0
#38 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#39 g_signal_emit
from /lib/libgobject-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/libgdk-x11-2.0.so.0
#44 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#45 ??
from /lib/libglib-2.0.so.0
#46 g_main_loop_run
from /lib/libglib-2.0.so.0
#47 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#48 main
#0 __kernel_vsyscall

Comment 1 Lars Clausen 2007-11-02 17:00:17 UTC

Yes, VSD files are not supported yet.  However, crashing the program is not the correct response.  It doesn't seem to be something inherent to VSD files, as I can attempt to open it with no more bad effects than an error dialog.  So if you can attach the VSD file, we can take a closer look.

Comment 2 Hans Breuer 2007-11-02 19:28:22 UTC

the crash is (was) easily reproduced with any not supported file format. See:

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



*** This bug has been marked as a duplicate of 490546 ***