Bug 427563 – crash in Dia: I was moving objects abo...

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 427563 - crash in Dia: I was moving objects abo...


Summary:	crash in Dia: I was moving objects abo...


Status:	RESOLVED DUPLICATE of bug 334771

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-04-08 12:23 UTC by sampsonrdn
Modified:	2007-04-08 12:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description sampsonrdn 2007-04-08 12:23:50 UTC

Version: @VERSION@

What were you doing when the application crashed?
I was moving objects about the page


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 323682304 vsize: 323682304 resident: 34533376 share: 16953344 rss: 51486720 rss_rlim: 445470720
CPU usage: start_time: 1176034500 rtime: 1298 utime: 1195 stime: 103 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/dia'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47496305130368 (LWP 6359)]
(no debugging symbols found)
0x00002b329622ac25 in waitpid () from /lib64/libpthread.so.0

+ Trace 126025

Thread 1 (Thread 47496305130368 (LWP 6359))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 diagram_ungroup_selected
#4 objects_ungroup_callback
#5 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#6 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#8 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#9 gtk_widget_activate
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#10 gtk_menu_shell_activate_item
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#11 gtk_menu_shell_append
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#12 gtk_marshal_BOOLEAN__VOID
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#13 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#14 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#16 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#17 gtk_widget_get_default_style
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#18 gtk_propagate_event
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#19 gtk_main_do_event
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#20 gdk_add_client_message_filter
from /opt/gnome/lib64/libgdk-x11-2.0.so.0
#21 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#22 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#23 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#24 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#25 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Hans Breuer 2007-04-08 12:40:02 UTC

from the crash I guess you are using dia 0.95. 0.95.1 was released almost a year ago to specifically fix this bug. Please ask your distributor to distribute a more recent version. Recently 0.96 was released which has that fix as well.
If my guess is wrong please dont hesitate to unduplicate and provide the exact version you are using, e.g. the output of:
  dia --version --verbose


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