Bug 489573 – crash in Dia Diagram Editor: I trying to open a file ...

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 489573 - crash in Dia Diagram Editor: I trying to open a file ...


Summary:	crash in Dia Diagram Editor: I trying to open a file ...


Status:	RESOLVED DUPLICATE of bug 443651

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-10-23 21:13 UTC by rolim_moura
Modified:	2007-10-27 11:47 UTC

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

Description rolim_moura 2007-10-23 21:13:00 UTC

Version: @0.96.1@

What were you doing when the application crashed?
I trying to open a file that was created by Vision 2003


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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 76947456 vsize: 76947456 resident: 49672192 share: 21901312 rss: 49672192 rss_rlim: 4294967295
CPU usage: start_time: 1193177279 rtime: 291 utime: 248 stime: 43 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 -1208596768 (LWP 5585)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 172353

Thread 1 (Thread -1208596768 (LWP 5585))

#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 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
from /lib/libglib-2.0.so.0
#28 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#29 ??
from /lib/libglib-2.0.so.0
#30 g_main_loop_run
from /lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
#0 __kernel_vsyscall

Comment 1 Lars Clausen 2007-10-25 19:51:38 UTC

If you can provide the diagram that caused this, we can get our local expert to take a closer look.

Comment 2 Hans Breuer 2007-10-27 11:47:18 UTC

http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi?id=490546

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