Ubuntu
nautilus package

nautilus crashed with SIGSEGV in nautilus_icon_canvas_item_get_drag_surface()

Bug #923237 reported by Jhosman Lizarazo on 2012-01-29

This bug report is a duplicate of: Bug #958139: nautilus crashed with SIGSEGV in nautilus_icon_canvas_item_get_drag_surface(). Edit Remove

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nautilus (Ubuntu)	Expired	Low	Unassigned

Bug Description

Ubuntu 12.04 Alpha
I have installed ESET Antivitus for Linux

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.2.1-2ubuntu12
ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1
Uname: Linux 3.2.0-11-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sun Jan 29 01:14:27 2012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
LocalLibraries: /opt/eset/esets/lib/libesets_pac.so
ProcCmdline: nautilus
SegvAnalysis:
Segfault happened at: 0x8158795: mov (%esi),%edx
PC (0x08158795) ok
source "(%esi)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
?? ()
g_cclosure_marshal_VOID__OBJECT () 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__OBJECT()
UpgradeStatus: Upgraded to precise on 2012-01-27 (1 days ago)
UserGroups:

Tags:

Revision history for this message

Jhosman Lizarazo (jhosman) wrote on 2012-01-29:

#1

Dependencies.txt Edit (4.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (576 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (141 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (53.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (751 bytes, text/plain; charset="utf-8")
Registers.txt Edit (461 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.7 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (6.5 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (304 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-01-29:

#2

StacktraceTop:
nautilus_icon_canvas_item_get_drag_surface (item=0x1) at nautilus-icon-canvas-item.c:448
drag_begin_callback (widget=0x8c5e080, context=0x8e3dea0, data=0x0) at nautilus-icon-dnd.c:1304
g_cclosure_marshal_VOID__OBJECT (closure=0x8cbd760, return_value=0x0, n_param_values=2, param_values=0x8c46e78, invocation_hint=0xbfd28840, marshal_data=0x0) at /build/buildd/glib2.0-2.31.12/./gobject/gmarshal.c:644
g_closure_invoke (closure=0x8cbd760, return_value=0x0, n_param_values=2, param_values=0x8c46e78, invocation_hint=0xbfd28840) at /build/buildd/glib2.0-2.31.12/./gobject/gclosure.c:774
signal_emit_unlocked_R (node=0x89f7090, detail=0, instance=0x8c5e080, emission_return=0x0, instance_and_params=0x8c46e78) at /build/buildd/glib2.0-2.31.12/./gobject/gsignal.c:3302

Revision history for this message

Apport retracing service (apport) wrote on 2012-01-29: Stacktrace.txt

#3

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

Revision history for this message

Apport retracing service (apport) wrote on 2012-01-29: ThreadStacktrace.txt

#4

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

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

Revision history for this message

Sebastien Bacher (seb128) wrote on 2012-02-01:

#5

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

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

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-04-02:

#6

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #958139 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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