GNOME Bugzilla – Bug 451061
crash in Open Folder: booting/logging in
Last modified: 2007-10-19 22:32:01 UTC
Version: 2.18.1 What were you doing when the application crashed? booting/logging in Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Crux Memory status: size: 38981632 vsize: 38981632 resident: 8347648 share: 6242304 rss: 8347648 rss_rlim: 4294967295 CPU usage: start_time: 1182806786 rtime: 8 utime: 5 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 -1208850720 (LWP 2741)] (no debugging symbols found) 0x009dc402 in __kernel_vsyscall ()
+ Trace 143695
Thread 1 (Thread -1208850720 (LWP 2741))
----------- .xsession-errors --------------------- `default' server already active SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2608 Traceback (most recent call last): File "/usr/bin/puplet", line 25, in <module> import pygtk ImportError: No module named pygtk Traceback (most recent call last): File "/usr/share/system-config-printer/applet.py", line 20, in <module> import cups ImportError: No module named cups (nautilus:2741): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.5.so: cannot open shared object file: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory --------------------------------------------------
*** Bug 451069 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
I 'fixed' it by removing the packages: nautilus-actions nautilus-python and now no longer get the crash, bug buddy dialog and I can now see the icons on my desktop once again and get the (right click) context menu on the desktop. I did NOT reinstall them to find out which one was the culprit. Should I attempt that?
Looks like it was a crash in nautilus-python. If you can install debug symbols for that and get us a better stacktrace, that would be useful. Thanks!
I looked on the site for a debug version of nautilus-python and did not find it. I do have another clue which may be helpful though in nautilus-debug-log.txt there was some feedback: ===== BEGIN MILESTONES ===== 0x87fe098 2007/06/26 13:46:09.9094 (GLog): g_module_open libpython failed: libpython2.5.so: cannot open shared object file: No such file or directory 0x87fe098 2007/06/26 13:46:09.9342 (USER): debug log dumped due to signal 11 ===== END MILESTONES ===== ===== BEGIN RING BUFFER ===== 0x87fe098 2007/06/26 13:46:09.9094 (GLog): g_module_open libpython failed: libpython2.5.so: cannot open shared object file: No such file or directory 0x87fe098 2007/06/26 13:46:09.9342 (USER): debug log dumped due to signal 11 ===== END RING BUFFER ===== Does this help?
I went looking for the module it couldn't find and this was the result: locate libpython2.5.so /usr/lib/libpython2.5.so.1.0
Yup, that error message is probably an indicator of the problem. However, judging from the current source for nautilus-python, I can't see immediately how to fix this crash, and hence why we need the debugging symbols for nautilus-python to get more information about the problem.
same as bug 442829, installing debug packages (as described by tom) and posting a better stacktrace at bug 442829 would be highly appreciated. *** This bug has been marked as a duplicate of 442829 ***