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 551454 - crash in Computer: Bug report came just aft...
crash in Computer: Bug report came just aft...
Status: RESOLVED DUPLICATE of bug 526868
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-09 02:55 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:55:38 UTC 
Version: 2.22.5.1

What were you doing when the application crashed?
Bug report came just after 551453. No more action done.



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: 347422720 vsize: 347422720 resident: 29839360 share: 15482880 rss: 29839360 rss_rlim: 18446744073709551615
CPU usage: start_time: 1220928892 rtime: 41 utime: 35 stime: 6 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 0x2b6aa5848990 (LWP 28998)]
[New Thread 0x41001950 (LWP 29003)]
[New Thread 0x40800950 (LWP 29001)]
0x00002b6a9e246878 in __lll_mutex_lock_wait () from /lib/libpthread.so.0

+ Trace 206524

Thread 3 (Thread 0x40800950 (LWP 29001))

  • #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 ---------------------
(nautilus:28871): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized
(nautilus:28944): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed
Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou répertoire de ce type
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized
(nautilus:28973): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed
Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou répertoire de ce type
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized
(nautilus:28998): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-09-09 12:10:21 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 ***