Bug 512351 – crash in Home Folder: Update Nautilus

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 512351 - crash in Home Folder: Update Nautilus


Summary:	crash in Home Folder: Update Nautilus


Status:	RESOLVED DUPLICATE of bug 166672

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-27 11:38 UTC by marek.zaborowski
Modified:	2008-01-29 23:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description marek.zaborowski 2008-01-27 11:38:55 UTC

What were you doing when the application crashed?
Update Nautilus 


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-1-686 #1 SMP Sat Dec 8 14:19:30 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: ClearlooksOSX

Memory status: size: 27820032 vsize: 27820032 resident: 10924032 share: 8654848 rss: 10924032 rss_rlim: 4294967295
CPU usage: start_time: 1201433880 rtime: 2 utime: 2 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b296c0 (LWP 8344)]
0xb75eb2fe in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 186946

Thread 1 (Thread 0xb6b296c0 (LWP 8344))

#0 __waitpid_nocancel
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 PyModule_GetDict
from /usr/lib/libpython2.4.so.1.0
#6 nautilus_python_init_python
from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
#7 nautilus_module_initialize
from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
#8 nautilus_module_load
at nautilus-module.c line 99
#9 g_type_module_use
from /usr/lib/libgobject-2.0.so.0
#10 nautilus_module_init
at nautilus-module.c line 176
#11 nautilus_application_startup
at nautilus-application.c line 410
#12 main
at nautilus-main.c line 541
#13 __libc_start_main
from /lib/libc.so.6
#14 _start
#0 __waitpid_nocancel
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
Initializing nautilus-open-terminal extension
(nautilus:8312): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.4.so: Kann die Shared-Object-Datei nicht \xf6ffnen: Datei oder Verzeichnis nicht gefunden
Initializing nautilus-open-terminal extension
(nautilus:8322): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.4.so: Kann die Shared-Object-Datei nicht \xf6ffnen: Datei oder Verzeichnis nicht gefunden
The application 'bug-buddy' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
Initializing nautilus-open-terminal extension
(nautilus:8333): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.4.so: Kann die Shared-Object-Datei nicht \xf6ffnen: Datei oder Verzeichnis nicht gefunden
Initializing nautilus-open-terminal extension
(nautilus:8344): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.4.so: Kann die Shared-Object-Datei nicht \xf6ffnen: Datei oder Verzeichnis nicht gefunden
--------------------------------------------------

Comment 1 André Klapper 2008-01-29 23:42:41 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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