GNOME Bugzilla – Bug 457828
crash in Dia Diagram Editor: starting up dia
Last modified: 2008-04-05 09:28:40 UTC
Version: @0.96.1@ What were you doing when the application crashed? starting up dia 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.20-1.2952.fc6 #1 SMP Wed May 16 18:59:18 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: 29466624 vsize: 29466624 resident: 13156352 share: 9539584 rss: 13156352 rss_rlim: 4294967295 CPU usage: start_time: 1184726444 rtime: 11 utime: 9 stime: 2 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 -1208621344 (LWP 4148)] (no debugging symbols found) 0x001d8402 in __kernel_vsyscall ()
+ Trace 148737
Thread 1 (Thread -1208621344 (LWP 4148))
----------- .xsession-errors (206 sec old) --------------------- File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 165, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 261, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 598, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files Initializing nautilus-open-terminal extension ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e00058 (Buddy List) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** (gnome-panel:3244): WARNING **: Failed to establish a connection with GDM: No such file or directory ** Message: <info> You are now connected to the wireless network 'dbuck'. --------------------------------------------------
It would appear that this is a problem in the Python module. Which version of Python do you have installed? Hans, can you read anything from the stacktrace?
Looks like Python is crashing while importing expat. If you run Python standalone and type import xml.parsers.expat My guess is that there is something broken with the Python installation and the above will crash as well. Not much the PyDia can do about that.
running a standalone python and trying the 'import xml.parsers.expat' worked with no errors. Here's something that I didn't see in the crashlog - running dia also spits this to stdout: dia: Objects/stringobject.c:107: PyString_FromString: Assertion `str != ((void *)0)' failed. Let me know what else I can do to help.
2007-09-08 Hans Breuer <hans@breuer.org> * plug-ins/python/doxrev.py : moved the import of xml.parsers.expat to Parse() so it is not called during start-up. Fixes the start-up crash without understanding what is really causing it, bug #457828
*** Bug 486643 has been marked as a duplicate of this bug. ***
*** Bug 490053 has been marked as a duplicate of this bug. ***
*** Bug 490040 has been marked as a duplicate of this bug. ***
*** Bug 490039 has been marked as a duplicate of this bug. ***
*** Bug 490054 has been marked as a duplicate of this bug. ***
*** Bug 490145 has been marked as a duplicate of this bug. ***
*** Bug 490146 has been marked as a duplicate of this bug. ***
*** Bug 490165 has been marked as a duplicate of this bug. ***
Just reported https://bugzilla.redhat.com/show_bug.cgi?id=352431 it myself. If you don't want to wait for the Fedora people just remove /usr/share/dia/python/doxrev.py . It is is triggering the bug, but just an unimportant plug-in you'll probably never need ;)
*** Bug 490172 has been marked as a duplicate of this bug. ***
If anyone who reported this is still listening, could you help your distributor by answering the questions below """ In the mean time, could you ask some of the reports if: 1) This is 100% reproducable 2) If this still happens after applying all available Fedora 7 updates? Maybe this just happens with a mixture of some but not all Fedora 7 updates? """ [ https://bugzilla.redhat.com/show_bug.cgi?id=352431 ]
*** Bug 494054 has been marked as a duplicate of this bug. ***
*** Bug 494055 has been marked as a duplicate of this bug. ***
*** Bug 494204 has been marked as a duplicate of this bug. ***
*** Bug 494216 has been marked as a duplicate of this bug. ***
*** Bug 499924 has been marked as a duplicate of this bug. ***
*** Bug 499925 has been marked as a duplicate of this bug. ***
*** Bug 501186 has been marked as a duplicate of this bug. ***
*** Bug 510224 has been marked as a duplicate of this bug. ***
*** Bug 498849 has been marked as a duplicate of this bug. ***
*** Bug 515778 has been marked as a duplicate of this bug. ***