GNOME Bugzilla – Bug 166672
Crash in PyModule_GetDict
Last modified: 2008-02-01 01:12:33 UTC
Distribution: Debian 3.1 Package: nautilus Severity: blocker Version: GNOME2.9.91 cvs (head) Gnome-Distributor: Ubuntu Synopsis: nautilus has quit unexpectedly Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: cvs (head) BugBuddy-GnomeVersion: 2.0 (2.9.1) Description: Description of the crash: Nautilus does'nt load, just appers the error dialoge, Steps to reproduce the crash: 1. Unknow. 2. 3. Expected Results: How often does this happen? First time in 3 weeks using ubuntu hoary, Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225042432 (LWP 8843)] [New Thread -1226781776 (LWP 8844)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 55453
Thread 2 (Thread -1226781776 (LWP 8844))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-08 09:30 ------- Unknown version cvs (head) in product nautilus. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Appears to be a unique stack trace. Reassigning to nautilus-python.
I removed the "python-nautilus" package and it the bug is gone. Some nautilus =scripts iwritten in python too, btw...
*** Bug 167778 has been marked as a duplicate of this bug. ***
It seems to be because the availablity of a module is missing. Seems like the module handle, sent in to PyModuel_GetDict is NULL. Could be either pygtk, gobject, gtk or nautilus. Checks should probably be added so it doesn't crash if it tries to load a module it can't find.
*** Bug 168824 has been marked as a duplicate of this bug. ***
*** Bug 169878 has been marked as a duplicate of this bug. ***
https://launchpad.net/products/gedit/+bug/28860 has another report of this.
Daniel, that's not the same issue, one is about nautilus-python and the other about gedit
Ok, nevermind my comment then.
The crash was probably due to missing gnomevfs module. Shouldn't crash anymore, but only give a g_warning in console, in CVS. 0.4.3 still had the problem, though.
*** Bug 333575 has been marked as a duplicate of this bug. ***
*** Bug 381201 has been marked as a duplicate of this bug. ***
*** Bug 442829 has been marked as a duplicate of this bug. ***
*** Bug 512351 has been marked as a duplicate of this bug. ***
*** Bug 513541 has been marked as a duplicate of this bug. ***