Ubuntu
nautilus package

nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #422393 reported by Alex Mauer on 2009-09-01

244

This bug affects 55 people

Affects		Status	Importance	Assigned to	Milestone
	nautilus (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

Binary package hint: nautilus

No further information available

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Sep 1 00:18:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.91-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
LANGUAGE=en_US.UTF-8
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
SegvAnalysis:
Segfault happened at: 0x807a21f <g_themed_icon_append_name@plt+58139>: mov 0x4(%eax),%edi
PC (0x0807a21f) ok
source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
g_cclosure_marshal_VOID__VOID ()
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Tags: ubuntu-unr
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.31-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin src video

Tags:

Related branches

lp:ubuntu/lucid/nautilus

Revision history for this message

Alex Mauer (hawke) wrote on 2009-09-01:

Dependencies.txt Edit (4.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (50.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Registers.txt Edit (479 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.8 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (217 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-01: Stacktrace.txt (retraced)

Stacktrace.txt (retraced) Edit (12.9 KiB, text/plain)

StacktraceTop:nautilus_file_management_properties_dialog_show (
IA__g_cclosure_marshal_VOID__VOID (closure=0xa32b0f0,
IA__g_closure_invoke (closure=0xa32b0f0, return_value=0x0,
signal_emit_unlocked_R (node=<value optimized out>,
IA__g_signal_emit_valist (instance=0xa248e00,

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-01: ThreadStacktrace.txt (retraced)

ThreadStacktrace.txt (retraced) Edit (14.4 KiB, text/plain)

Changed in nautilus (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Sebastien Bacher (seb128) on 2009-09-02

visibility:

private → public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2009-09-02:

This bug was fixed in the package nautilus - 1:2.27.91-0ubuntu3

---------------
nautilus (1:2.27.91-0ubuntu3) karmic; urgency=low

  * debian/patches/92_git_change_fix_preferences_crash.patch:
    - git change to fix preference dialog crashing
      (lp: #422282, #422393, #422781)

-- Sebastien Bacher <email address hidden> Wed, 02 Sep 2009 17:19:21 +0200

Changed in nautilus (Ubuntu):
status:	New → Fix Released

Revision history for this message

Blümchen Blau (bluemchen-blau) wrote on 2009-10-01:

How come, that I am experiencing this bug today? (My system is daily updated!)

Deleted files from an USB-Thumbdrive.

Revision history for this message

Sebastien Bacher (seb128) wrote on 2009-10-01:

you might have a different issue and should open a new bug

Revision history for this message

Andrea (adenatale) wrote on 2009-10-03:

I was deleting files from 4Gb SD card, and after about 300 files it crashed. Happened two times, i'm reporting the second event but the first one was the same

Revision history for this message

emmeda (emmeda) wrote on 2009-10-24:

This bug crashed my nautilus today, when I deleted one file and went up in the directory tree before the just deleted file disappeared.

Revision history for this message

Balázs Attila (battila9) wrote on 2009-10-27:

The same. I try to delet files, and Nautilus crashed.

Nicolas Müller (nicolas-mue-deactivatedaccount-deactivatedaccount) on 2009-10-30

Changed in nautilus (Ubuntu):
status:	Fix Released → Fix Committed
status:	Fix Committed → Fix Released

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2009-11-20:

#10

Despite I read a fix was released last month, Nautilus has just crashed, and I landed here after submitting the required information to the developers through Apport.

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2009-11-23:

#11

I had another crash, and submitted a new report with Apport. Is anyone reading? This bug is not fixed.

Revision history for this message

souplin (klage) wrote on 2009-11-27:

#12

can confirm - the fix didn't work - nautlius crashes. Maybe one should reopen this or submit the bug as a new one. Don't know how the policy works here...

Changed in nautilus (Ubuntu):
status:	Fix Released → Confirmed

Revision history for this message

Sebastien Bacher (seb128) wrote on 2009-11-30:

#13

use apport to open a new bug rather, it might be a different or new issue...

Changed in nautilus (Ubuntu):
status:	Confirmed → Fix Released

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2009-11-30:

#14

> use apport to open a new bug rather

Apport brought me here twice because it identified the problem with this bug, and labelled my bug reports as "nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()"

> it might be a different or new issue...

If you don't know and Apport can't tell, why and how should I?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2009-11-30:

#15

that's not because the first function matches that the crash is the same, open a new bug and wait for retracing...

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2009-11-30:

#16

> that's not because the first function matches that the crash is the same

I got that the first time. Then again, if Apport brings average users here, they are not aware of the issue at hand, they usually only have a crash and a program to report it that pops up a window with a pre-compiled field. Usually, users tend to trust its ability to identify what caused the crash. If they don't, we may as well doubt every single instance, and report each crash as a separate bug in the event it might be a new issue, regardless of duplicates.

> open a new bug and wait for retracing...

I'll make sure I do so, as soon as this happens again. These days Ubuntu doesn't fail to crash every other day...

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2010-02-01:

#17

> I'll make sure I do so, as soon as this happens again.

It happened again, I did so: Bug #515495

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2010-02-02:

#18

And again: Bug #516219

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2010-02-05:

#19

... and again: Bug #517740

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntunautilus package

nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
nautilus package