GNOME Bugzilla – Bug 626134
nautilus crashed with signal 7
Last modified: 2015-02-20 10:10:31 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/580958 "Nautilus crashes if it has not been used for some time (I don't now the exact time but maybe 15 minutes). If it is already started it crashes and if I start it it crashes. But it works if I start it a second time, but crashes again when it has been idle for 15 minutes." ".
+ Trace 223125
Thread 2 (process 2788)
Thread 1 (process 4686)
-> gvfs Looks like a crash in the gvfs metadata engine. Is your home on NFS or on another network mount?
Similar problem here: various processes from Gnome 2.30.1 (from JHBuild) crash when they were not used for a while (observed with Gedit, Nautilus, and Evince so far). Random inspection of the core file usually shows "Bus error" in some metatree-related function. Latest backtrace (anonymized; "/workdir/" is in fact a longer path): Core was generated by `evince /workdir/TestReport.pdf'. Program terminated with signal 7, Bus error.
+ Trace 227532
The opened PDF file is on NFS, and home directory is on NFS as well.
On Solaris 11u1 I'm seeing a very similar nautilus core dump with this stack trace: > ::status debugging core file of nautilus (32-bit) from alton file: /usr/bin/nautilus initial argv: nautilus --no-desktop threading model: native threads status: process terminated by SIGBUS (Bus Error), addr=f5a40008 > ::stack libgvfsdbus.so`meta_tree_needs_rereading+0x28(84b7788, 1, fd43eaf8, fd540922) libgvfsdbus.so`meta_tree_refresh+0x2e(84b7788, fd547dc8, 5, fd540526) libgvfsdbus.so`meta_tree_lookup_by_name+0x135(fd547dc8, 0, fd43eb48, fd5441f1) libgvfsdbus.so`meta_lookup_cache_lookup_path+0x248(868e308, 8616f20, 99c0002, 0, 0, fd43ec2c) libgvfsdbus.so`g_daemon_vfs_local_file_add_info+0x77(82c2580, 8616f20, 99c0002, 0, 85d5748, 8602e18) libgio-2.0.so.0.2800.6`_g_local_file_info_get+0xa62(8616ef0, 8616f20, 85d5748, 0, fd43ee20) libgio-2.0.so.0.2800.6`g_local_file_query_info+0x79(86a8920, 86a8878, 0, 86a79c0, fd43eedc, 82d9cd8) libgio-2.0.so.0.2800.6`g_file_query_info+0xb8(86a8920, 86a8878, 0, 86a79c0, fd43eedc, 1) libgio-2.0.so.0.2800.6`query_info_async_thread+0x3e(85bd448, 86a8920, 86a79c0, fdf4f132) libgio-2.0.so.0.2800.6`run_in_thread+0x45(861baa8, 86a79c0, 864c830, fdf41a3e) libgio-2.0.so.0.2800.6`io_job_thread+0x35(861baa8) libglib-2.0.so.0.2800.6`g_thread_pool_thread_proxy+0x58(83160e8, 861bb30, 208, fde1b6b2) libglib-2.0.so.0.2800.6`g_thread_create_proxy+0x12e(861bb30, fe762000, fd43efe8, fe6c43e9) libc_hwcap2.so.1`_thrp_setup+0x9d(fd950a40) libc_hwcap2.so.1`_lwp_start(fd950a40, 0, 0, 0, 0, 0) My home directory is an NFS share. Note, this is happening semi-regularly and is def. annoying.
It has been pushed several fixes also for the case when home directory is on nfs since this bug was reported. Closing as obsolete, because there aren't any abrt bug reports reporting crashes with such backtrace. Please reopen if you still facing those crashes.