nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #858986 reported by Jeroen T. Vermeulen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash in oneiric beta. This may have happened when I tried to copy a file from an external NTFS disk on USB to a VFAT USB stick, but I'm getting rather a lot of this stuff so it could have been another crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.92-0ubuntu3
Uname: Linux 3.0.0-11-generic-pae i686
Architecture: i386
CheckboxSubmission: e56271c144a9c8f9f675c77e2e4edb56
CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b
CrashCounter: 1
Date: Sun Sep 25 13:13:21 2011
ExecutablePath: /usr/bin/nautilus
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: nautilus -n
ProcEnviron:
 LC_TIME=en_DK.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80cbfd7: mov 0x60(%edx),%eax
 PC (0x080cbfd7) ok
 source "0x60(%edx)" (0x00000060) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev pulse pulse-access sambashare video

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #857749, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.