GNOME Bugzilla – Bug 520140
crash in Dia Diagram Editor: Trying to open dxf file...
Last modified: 2008-04-05 09:50:49 UTC
Version: @0.96.1@ What were you doing when the application crashed? Trying to open dxf file. Nothing displayed properly and it crashed when I closed the program. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 128393216 vsize: 128393216 resident: 52752384 share: 15392768 rss: 52752384 rss_rlim: 4294967295 CPU usage: start_time: 1194616035 rtime: 771 utime: 704 stime: 67 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 -1209100576 (LWP 3432)] (no debugging symbols found) 0x0034e402 in __kernel_vsyscall ()
+ Trace 191172
Thread 1 (Thread -1209100576 (LWP 3432))
----------- .xsession-errors --------------------- Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". --------------------------------------------------
looks like this is fixed by bug #490546 *** This bug has been marked as a duplicate of 490546 ***