GNOME Bugzilla – Bug 508670
crash in Dia Diagram Editor: copying & pasting a clas...
Last modified: 2008-04-08 21:37:01 UTC
Version: @0.96.1@ What were you doing when the application crashed? copying & pasting a class in a medium-sized class diagram (i pressed ctrl-C then ctrl-V fairly quickly, not sure which key event triggered the crash) Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 1252868096 vsize: 1252868096 resident: 354902016 share: 13262848 rss: 354902016 rss_rlim: 4294967295 CPU usage: start_time: 1199856932 rtime: 66957 utime: 64097 stime: 2860 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 -1208506656 (LWP 31339)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184887
Thread 1 (Thread -1208506656 (LWP 31339))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libgdk-x11-2.0.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgdk_pixbuf-2.0.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libselinux.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libsepol.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
there was an issue with copy and paste connected object (your crash shows object_unconnect). I think this is fixed by the fix for bug #497070 *** This bug has been marked as a duplicate of 497070 ***