Bug 551451 – crash in Computer: % 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 551451 - crash in Computer: % nautilus


Summary:	crash in Computer: % nautilus


Status:	RESOLVED DUPLICATE of bug 526868

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-09-09 02:49 UTC by nicolas.s-dev
Modified:	2008-09-09 12:10 UTC

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

Description nicolas.s-dev 2008-09-09 02:49:08 UTC

Version: 2.22.5.1

What were you doing when the application crashed?
% nautilus


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.22.3 2008-09-02 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-gentoo-r8-v3 #3 SMP Sat Sep 6 14:39:32 CEST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Gion

Memory status: size: 413974528 vsize: 413974528 resident: 30060544 share: 15589376 rss: 30060544 rss_rlim: 18446744073709551615
CPU usage: start_time: 1220928475 rtime: 42 utime: 38 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b426794b990 (LWP 28890)]
[New Thread 0x41001950 (LWP 28895)]
[New Thread 0x40800950 (LWP 28894)]
0x00002b4260349878 in __lll_mutex_lock_wait () from /lib/libpthread.so.0

+ Trace 206521

Thread 2 (Thread 0x41001950 (LWP 28895))

#0 waitpid
from /lib/libpthread.so.0
#1 IA__g_spawn_sync
at gspawn.c line 374
#2 IA__g_spawn_command_line_sync
at gspawn.c line 682
#3 ??
from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 IA__g_unix_mount_guess_should_display
at gunixmounts.c line 1877
#6 _g_unix_mount_new
at gunixmount.c line 111
#7 _g_mount_get_for_mount_path
at gunionvolumemonitor.c line 576
#8 g_local_file_find_enclosing_mount
at glocalfile.c line 1061
#9 find_enclosing_mount_async_thread
at gfile.c line 4432
#10 run_in_thread
at gsimpleasyncresult.c line 613
#11 io_job_thread
at gioscheduler.c line 178
#12 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#13 g_thread_create_proxy
at gthread.c line 635
#14 start_thread
from /lib/libpthread.so.0
#15 clone
from /lib/libc.so.6
#16 ??



----------- .xsession-errors (58 sec old) ---------------------
seahorse nautilus module initialized
(nautilus:28822): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized
(nautilus:28838): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized
(nautilus:28856): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized
(nautilus:28871): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-09-09 12:10:51 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 526868 ***