Bug 528964 – crash in File Browser:

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 528964 - crash in File Browser:


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 524453

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-04-19 22:36 UTC by nexus
Modified:	2008-04-20 09:43 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description nexus 2008-04-19 22:36:58 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 32538624 vsize: 32538624 resident: 12197888 share: 9687040 rss: 12197888 rss_rlim: 4294967295
CPU usage: start_time: 1208644610 rtime: 16 utime: 12 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c0a720 (LWP 7678)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 195651

Thread 1 (Thread 0xb6c0a720 (LWP 7678))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 PyModule_GetDict
from /usr/lib/libpython2.4.so.1.0
#7 nautilus_python_init_python
from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
#8 nautilus_module_initialize
from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
from /usr/lib/libgobject-2.0.so.0
#14 ??
#15 ??
#16 ??
#17 g_type_module_use
from /usr/lib/libgobject-2.0.so.0
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
Initializing nautilus-image-converter extension
(nautilus:7678): Liboobs-WARNING **: Failed to connect to socket /var/run/dbus/system_bus_socket: No existe el fichero o el directorio
seahorse nautilus module initialized
Initializing nautilus-share extension
Initializing nautilus-open-terminal extension
Initializing gnome-mount extension
** (nautilus:7678): WARNING **: Cannot connect to system bus: org.freedesktop.DBus.Error.FileNotFound : Failed to connect to socket /var/run/dbus/system_bus_socket: No existe el fichero o el directori
** (nautilus:7678): WARNING **: Could not initialize hal context
Shutting down gnome-mount extension
(nautilus:7678): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.4.so: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio
--------------------------------------------------

Comment 1 Gianluca Borello 2008-04-20 09:43:17 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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