nautilus crashed with SIGSEGV in do_unmount()

Bug #936321 reported by graz on 2012-02-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)

Bug Description

Crash in Ubuntu 12.04 Precise Pangolin 64 bit (alpha 2)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 19 17:02:06 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: org.gnome.nautilus.window-state geometry '800x607+466+167'
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: nautilus -n
 Segfault happened at: 0x4a5921: mov 0x10(%rdi),%rdi
 PC (0x004a5921) ok
 source "0x10(%rdi)" (0x00000011) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to precise on 2012-02-16 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

graz (graz966) wrote :

 do_unmount (data=0x1) at nautilus-file-operations.c:2071
 empty_trash_job_done (user_data=0x18c3260) at nautilus-file-operations.c:6323
 mainloop_proxy_func (data=0x7fbc78006d60) at /build/buildd/glib2.0-2.31.16/./gio/gioscheduler.c:286
 g_main_dispatch (context=0xbd0eb0) at /build/buildd/glib2.0-2.31.16/./glib/gmain.c:2510
 g_main_context_dispatch (context=0xbd0eb0) at /build/buildd/glib2.0-2.31.16/./glib/gmain.c:3047

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
summary: - nautilus crashed with SIGSEGV in g_main_context_dispatch()
+ nautilus crashed with SIGSEGV in do_unmount()
tags: removed: need-amd64-retrace
visibility: private → public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers