After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 445562 - crash in Open Folder: starting system
crash in Open Folder: starting system
Status: RESOLVED DUPLICATE of bug 442829
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-08 17:51 UTC by r-mccarthy
Modified: 2007-06-09 00:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description r-mccarthy 2007-06-08 17:51:02 UTC 
Version: 2.18.1

What were you doing when the application crashed?
starting system


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 43028480 vsize: 43028480 resident: 10362880 share: 8355840 rss: 10362880 rss_rlim: 4294967295
CPU usage: start_time: 1181325016 rtime: 10 utime: 8 stime: 2 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 -1208916256 (LWP 3788)]
(no debugging symbols found)
0x0074b402 in __kernel_vsyscall ()

+ Trace 139413

Thread 1 (Thread -1208916256 (LWP 3788))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PyModule_GetDict
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #5 nautilus_python_init_python
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #6 nautilus_module_initialize
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #7 ??
  • #8 g_type_module_use
    from /lib/libgobject-2.0.so.0
  • #9 nautilus_module_init
  • #10 nautilus_application_startup
  • #11 main
  • #0 __kernel_vsyscall 

----------- .xsession-errors (8 sec old) ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/arl19.anesthesia.nmh.org:/tmp/.ICE-unix/3662
** (gnome-session:3662): WARNING **: Host name lookup failure on localhost.
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
You can not run beagle as root.  Beagle is designed to run from your own
user account.  If you want to create multiuser or system-wide indexes, use
the beagle-build-index tool.
You can override this setting using the beagle-config or beagle-settings tools.
(nautilus:3788): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.4.so: cannot open shared object file: No such file or directory
Could not find platform independent libraries <prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
'import site' failed; use -v for traceback
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-09 00:39:47 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 442829 ***