nautilus crashed with signal 7

Bug #580958 reported by Rickard Gustavsson
36
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
gvfs (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: nautilus

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.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: openafs nvidia
Architecture: i386
CrashCounter: 1
Date: Sat May 15 15:15:29 2010
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=sv_SE:sv:en_GB:en
 PATH=(custom, no user)
 LANG=sv_SE.utf8
 SHELL=/bin/bash
Signal: 7
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
Title: nautilus crashed with signal 7
UserGroups: admin audio plugdev pulse

Revision history for this message
Rickard Gustavsson (gustavsson-rickard) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 meta_tree_needs_rereading (tree=0x9abd878) at metatree.c:624
 meta_tree_refresh (tree=0x9abd878) at metatree.c:680
 meta_tree_lookup_by_name (name=0xbfd7c0 "home", for_write=0)
 meta_lookup_cache_lookup_path (cache=0x9dd1948,
 g_daemon_vfs_local_file_add_info (vfs=0x9adb8c0,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=626134

Changed in nautilus (Ubuntu):
status: New → Triaged
Changed in nautilus:
status: Unknown → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

is your home on a NFS or another network mount?

Revision history for this message
Rickard Gustavsson (gustavsson-rickard) wrote : Re: [Bug 580958] Re: nautilus crashed with signal 7

Yes, it is located on an AFS share.

Changed in nautilus:
importance: Unknown → Critical
Changed in nautilus:
status: New → Expired
Vlad Orlov (monsta)
affects: nautilus (Ubuntu) → gvfs (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.