Bug 468702 – crash in Open Folder: opening the home folder

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 468702 - crash in Open Folder: opening the home folder


Summary:	crash in Open Folder: opening the home folder


Status:	RESOLVED DUPLICATE of bug 442829

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Duplicates:	468982 (view as bug list)
Depends on:
Blocks:

Reported:	2007-08-21 00:48 UTC by hferretluv
Modified:	2007-08-22 19:08 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description hferretluv 2007-08-21 00:48:05 UTC

Version: 2.18.1

What were you doing when the application crashed?
opening the home folder


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: Fedora

Memory status: size: 42799104 vsize: 42799104 resident: 10604544 share: 8552448 rss: 10604544 rss_rlim: 4294967295
CPU usage: start_time: 1187657316 rtime: 17 utime: 14 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 -1209248032 (LWP 3465)]
(no debugging symbols found)
0x007b7402 in __kernel_vsyscall ()

+ Trace 156708

Thread 1 (Thread -1209248032 (LWP 3465))

#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 ---------------------
ERROR: metadata Audio:TrackPeakGain not found
ERROR: metadata Audio:TrackPeakGain not found
ERROR: metadata Audio:TrackPeakGain not found
ERROR: metadata Audio:TrackPeakGain not found
ERROR: metadata Audio:TrackPeakGain not found
ERROR: metadata Audio:TrackPeakGain not found
ERROR: metadata Audio:TrackPeakGain not found
Initializing nautilus-open-terminal extension
Initializing nautilus-image-converter extension
Initializing nautilus-search-tool extension
(nautilus:3465): 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 palfrey 2007-08-22 13:33:05 UTC

*** Bug 468982 has been marked as a duplicate of this bug. ***

Comment 2 Susana 2007-08-22 19:08:45 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 ***