Bug 495074 – crash in Dia Diagram Editor: Tried to open bzLifecycl...

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 495074 - crash in Dia Diagram Editor: Tried to open bzLifecycl...


Summary:	crash in Dia Diagram Editor: Tried to open bzLifecycl...


Status:	RESOLVED DUPLICATE of bug 490546

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

Importance:	High critical
Target Milestone:	---
Assigned To:	Hans Breuer
QA Contact:	Hans Breuer

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-08 18:55 UTC by johng
Modified:	2007-11-09 09:31 UTC

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

Description johng 2007-11-08 18:55:53 UTC

Version: @0.96.1@

What were you doing when the application crashed?
Tried to open bzLifecycle.xml from Bugzilla 3.0


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 116273152 vsize: 116273152 resident: 63885312 share: 35995648 rss: 63885312 rss_rlim: 4294967295
CPU usage: start_time: 1194547927 rtime: 196 utime: 181 stime: 15 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 -1208969504 (LWP 5879)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 176402

Thread 1 (Thread -1208969504 (LWP 5879))

#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



----------- .xsession-errors (10 sec old) ---------------------
    classes.extend (Parse (f.read()))
  File "/usr/share/dia/python/doxrev.py", line 391, in Parse
    p.Parse(sData)
  File "/usr/share/dia/python/doxrev.py", line 344, in start_element
    o = eval (s + "()")
<type 'exceptions.SyntaxError'>SyntaxError('invalid syntax', ('<string>', 1, 4, 'Dia:diagram()'))Traceback (most recent call last):
  File "/usr/share/dia/python/doxrev.py", line 482, in import_file
    classes = GetClasses ([sFile])
  File "/usr/share/dia/python/doxrev.py", line 400, in GetClasses
    classes.extend (Parse (f.read()))
  File "/usr/share/dia/python/doxrev.py", line 391, in Parse
    p.Parse(sData)
  File "/usr/share/dia/python/doxrev.py", line 344, in start_element
    o = eval (s + "()")
dia: diagram.c:107: diagram_finalize: Assertion `dia->displays==((void *)0)' failed.
--------------------------------------------------

Comment 1 Lars Clausen 2007-11-08 19:33:56 UTC

Downloading http://www.bugzilla.org/docs/3.0/images/bzLifecycle.xml and opening it with todays SVN or 0.96.1 does not reproduce this bug.  Compiling in Python gives me an error message pop-up, but no crash, in both versions.  Using Python 2.5.1 for it.  Note that if I rename the file to bzLifecycle.dia, it opens even when Python is compiled in.

Comment 2 johng 2007-11-08 19:47:54 UTC

Based on the note in comment 1, I renamed the file to have a .dia extension, and it opened successfully. Thanks!

Comment 3 Hans Breuer 2007-11-09 09:31:18 UTC

The crash looks like the one being fixed in SVN recently:

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

you can find it by the "simpe dup finder" link on the top of this page.

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