Bug 418166 – crash in Dia Diagram Editor: Trying to paste the clip...

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 418166 - crash in Dia Diagram Editor: Trying to paste the clip...


Summary:	crash in Dia Diagram Editor: Trying to paste the clip...


Status:	RESOLVED DUPLICATE of bug 414708

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-03-14 10:28 UTC by luuk
Modified:	2007-03-15 21:41 UTC

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

Description luuk 2007-03-14 10:28:14 UTC

Version: @VERSION@

What were you doing when the application crashed?
Trying to paste the clipboard.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.6.4.fc6 #1 SMP Sat Feb 24 14:39:04 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 102670336 vsize: 0 resident: 102670336 share: 0 rss: 38227968 rss_rlim: 0
CPU usage: start_time: 1173279364 rtime: 0 utime: 13149 stime: 0 cutime:12199 cstime: 0 timeout: 950 it_real_value: 0 frequency: 1

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 -1208699184 (LWP 20361)]
(no debugging symbols found)
0x006b0402 in __kernel_vsyscall ()

+ Trace 118510

Thread 1 (Thread -1208699184 (LWP 20361))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ddisplay_add_update_pixels
#5 diagram_add_update_pixels
#6 handle_add_update
#7 object_add_updates
#8 textedit_remove_focus_all
#9 diagram_remove_all_selected
#10 edit_paste_callback
#11 gtk_item_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
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_widget_can_activate_accel
from /usr/lib/libgtk-x11-2.0.so.0
#18 g_closure_invoke
from /lib/libgobject-2.0.so.0
#19 g_signal_chain_from_overridden
from /lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#21 g_signal_emit
from /lib/libgobject-2.0.so.0
#22 gtk_accel_group_activate
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_accel_groups_activate
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_window_activate_key
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_window_activate_key
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#27 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#28 g_closure_invoke
from /lib/libgobject-2.0.so.0
#29 g_signal_chain_from_overridden
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_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#35 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#36 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#37 g_main_context_check
from /lib/libglib-2.0.so.0
#38 g_main_loop_run
from /lib/libglib-2.0.so.0
#39 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#40 main
#0 __kernel_vsyscall



----------- .xsession-errors (576 sec old) ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x425aa0a (Picture)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x425aa0a (Picture)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x425aa0a (Picture)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x425aa0a (Picture)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x425aa0a (Picture)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x426208c (Picture)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x426208c (Picture)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 Lars Clausen 2007-03-15 21:41:25 UTC

Thanks for the reporting this crash.  The bug in question has been fixed in 0.96-pre7.

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