nautilus crashed with SIGABRT in __kernel_vsyscall()

Bug #839941 reported by Michael R. Crusoe
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Possible out of memory issue? During a file copy from a GVFS SSH mount into a directory sync'd w/ ubuntoone on my netbook

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu13
ProcVersionSignature: Ubuntu 2.6.38-11.49-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
Architecture: i386
Date: Fri Sep 2 15:16:02 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to natty on 2011-04-28 (127 days ago)
UserGroups: adm admin audio cdrom davfs2 dialout dip fax fcron floppy fuse logcheck lpadmin netdev plugdev sambashare tape video

Revision history for this message
Michael R. Crusoe (misterc) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=0x0, file=0x81c304a "nautilus-directory-async.c", line=2419, func=0x81c389f "directory_count_stop", message=<optimized out>) at /build/buildd/glib2.0-2.28.6/./glib/gtestutils.c:1358
 g_assertion_message_expr (domain=0x0, file=0x81c304a "nautilus-directory-async.c", line=2419, func=0x81c389f "directory_count_stop", expr=0x81c31f4 "file->details->directory == directory") at /build/buildd/glib2.0-2.28.6/./glib/gtestutils.c:1369
 directory_count_stop (directory=0xafbb5c0) at nautilus-directory-async.c:2419
 start_or_stop_io (directory=0xafbb5c0) at nautilus-directory-async.c:4549
 nautilus_directory_async_state_changed (directory=0xafbb5c0) at nautilus-directory-async.c:4631

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
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, the trace matches bug https://bugzilla.gnome.org/show_bug.cgi?id=648395. Linking that report.

Changed in nautilus (Ubuntu):
status: New → Triaged
visibility: private → public
Changed in nautilus:
importance: Unknown → Critical
status: Unknown → New
Changed in nautilus:
status: New → Incomplete
Changed in nautilus:
status: Incomplete → Expired
Changed in nautilus (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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