Bug 530940 – 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 530940 - crash in File Browser:


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 522534

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-05-01 20:31 UTC by amgelinux
Modified:	2008-05-02 23:26 UTC

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

Description amgelinux 2008-05-01 20:31:29 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-powerpc #1 Fri Apr 18 19:53:00 CEST 2008 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gartoon

Memory status: size: 75710464 vsize: 75710464 resident: 26923008 share: 20168704 rss: 26923008 rss_rlim: 4294967295
CPU usage: start_time: 1209673752 rtime: 1007 utime: 956 stime: 51 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 0x4804a100 (LWP 10207)]
(no debugging symbols found)
0x0f158290 in waitpid () from /lib/libpthread.so.0

+ Trace 196623

Thread 1 (Thread 0x4804a100 (LWP 10207))

#0 waitpid
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 ??
#5 <signal handler called>
#6 ??
#7 ??
#8 ??
from /usr/lib/libglib-2.0.so.0
#9 ??
#10 ??
#11 ??
#12 ??
from /usr/lib/libgnomevfs-2.so.0
#13 ??
from /usr/lib/libglib-2.0.so.0
#14 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#15 ??
from /usr/lib/libglib-2.0.so.0
#16 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#17 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
#19 ??
from /lib/libc.so.6
#20 __libc_start_main
from /lib/libc.so.6
#21 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (7 sec old) ---------------------
** (nautilus:10207): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
** (nautilus:10207): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
** (nautilus:10207): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
** (nautilus:10207): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
** (nautilus:10207): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
** (nautilus:10207): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
** (nautilus:10207): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
** (nautilus:10207): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-05-02 23:26:56 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 522534 ***