Nautilus

nautilus crashed with SIGSEGV in trash_or_delete_done_cb()

Bug #948233 reported by Chris Hubbell on 2012-03-06

20

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Nautilus	New	Critical	gnome-bugs #671961
	nautilus (Ubuntu)	Invalid	Low	Unassigned

Bug Description

I was working on files on an ftp server when crash occurred

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.90-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94-0ubuntu2
Architecture: i386
Date: Tue Mar 6 12:49:10 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
org.gnome.nautilus.window-state geometry '800x550+564+188'
org.gnome.nautilus.window-state maximized true
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: nautilus -n
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x80b13ff: movl $0x0,0xd8(%eax)
PC (0x080b13ff) ok
source "$0x0" ok
destination "0xd8(%eax)" (0xaaaaab82) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
?? ()
?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Chris Hubbell (christopher-hubbell) wrote on 2012-03-06:

#1

Dependencies.txt Edit (5.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (537 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (56.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (800 bytes, text/plain; charset="utf-8")
Registers.txt Edit (495 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (981 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (3.6 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (14.3 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (308 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-06:

#2

StacktraceTop:
trash_or_delete_done_cb (debuting_uris=0xa83ef88, user_cancel=1, view=0xa4ea5a0) at nautilus-view.c:4086
delete_job_done (user_data=0xaaa04e0) at nautilus-file-operations.c:1986
mainloop_proxy_func (data=0xa867790) at /build/buildd/glib2.0-2.31.20/./gio/gioscheduler.c:286
g_idle_dispatch (source=0xab2b1e0, callback=0xb6b72c70 <mainloop_proxy_func>, user_data=0xa867790) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:4629
g_main_dispatch (context=0x9f733a8) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:2510

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-06: Stacktrace.txt

#3

Stacktrace.txt Edit (2.3 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-06: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (8.8 KiB, text/plain)

Changed in nautilus (Ubuntu):
importance:	Undecided → Medium
summary:	- nautilus crashed with SIGSEGV in g_main_context_dispatch() + nautilus crashed with SIGSEGV in trash_or_delete_done_cb()
tags:	removed: need-i386-retrace

Sebastien Bacher (seb128) on 2012-03-08

visibility:	private → public
Changed in nautilus (Ubuntu):
importance:	Medium → Low

Revision history for this message

Sebastien Bacher (seb128) wrote on 2012-03-12:

#5

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in nautilus (Ubuntu):
status:	New → Triaged
status:	Triaged → Confirmed

Revision history for this message

Vadim Rutkovsky (roignac) wrote on 2012-03-13:

#6

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=671961

Changed in nautilus (Ubuntu):
status:	Confirmed → Triaged

Bug Watch Updater (bug-watch-updater) on 2012-03-13

Changed in nautilus:
importance:	Unknown → Critical
status:	Unknown → New

Revision history for this message

Sebastien Bacher (seb128) wrote on 2018-03-17:

#7

there has been no such issue reported in years, assuming it doesn't exist in the current version of the code and closing

Changed in nautilus (Ubuntu):
status:	Triaged → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #1123628

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

gnome-bugs #671961
[UNCONFIRMED] Edit

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