nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()

[bob1z]

Binary package hint: nautilus

Hi

my Ubuntu is 10:10 a3
nautilus:
Installed: 1:2.31.90-0ubuntu1

Nautilus when i was removing a usb stick .

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.31.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-17.23-generic 2.6.35.2
Uname: Linux 2.6.35-17-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Aug 25 16:53:54 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x808aaa2: mov (%esi),%eax
 PC (0x0808aaa2) ok
 source "(%esi)" (0x00000008) 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__BOXED ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Ivan Brasil Fuzzer (ivanbrasil)]

same error, but ejecting a cdrom

[bob1z (josephcaseley-deactivatedaccount)]

 nautilus makes an invalid memory reference(SIGSEGV) which makes is crash .

[bob1z (josephcaseley-deactivatedaccount)]

edit ! nautilus makes an invalid memory reference(SIGSEGV) which makes it crash

[bob1z (josephcaseley-deactivatedaccount)]

There are lots of t=SIGSEGV's

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bugs?field.searchtext=SIGSEGV&orderby=-importance&search=Search&field.status:list=NEW&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[bob1z (josephcaseley-deactivatedaccount)]

how do make a backtrace ?

[bob1z (josephcaseley-deactivatedaccount)]

hi

i found https://wiki.ubuntu.com/Backtrace when i run gdb <nautilus > 2>&1 | tee gdb-<nautilus >.txt i get the output :
bash: syntax error near unexpected token `2'

any thoughts ??

[Sebastien Bacher (seb128)]

you should write "nautilus" instead of "<nautilus >" there

[bob1z (josephcaseley-deactivatedaccount)]

when i run backtrace full i get :

"Reading symbols from /usr/bin/nautilus...(no debugging symbols found)...done.
(gdb) backtrace full
No stack."

any thoughts ??

[Sebastien Bacher (seb128)]

try typing "continue" as described on the wikipage?

[bob1z (josephcaseley-deactivatedaccount)]

hi

this the output "continue
The program is not being run.
"

any thoughts ???

[Jens (jens.timmerman)]

install nautilus-dbg first

[bob1z (josephcaseley-deactivatedaccount)]

Hi ,

Am still getting no stack

any Thoughts ???

[Vladislav Rovda (filincrew)]

In my case I got this crash after returning from suspend mod

[PatrickSCarrroll (patrickscarroll-hotmail)]

I was formatting an SD card with "Disk Utility". I unmounted the SD card, tried to format it, the format failed, then nautilus popped up showing some other directory (other than the SD card, I believe) then crashed. I was prompted to submit a bug report, and it brought me here.

[Jens (jens.timmerman)]

PatrickSCarroll this bug was marked as incomplete because there is no backtrace, Are you able to make a backtrace? (read previous comments)

bob1z: you have to recreate the crash before you can make the backtrace again.
follow the steps in https://wiki.ubuntu.com/Backtrace carefully.

[Ристе Ристевски (risteristevski)]

I cannot recreate this bug, it happened to me only once. I assume its fixed with the latest update somehow.
If someone else can recreate this bug, please do a backtrace.

[bob1z (josephcaseley-deactivatedaccount)]

Hi ,

I think this is the issue :
/home/user/nautilus": not in executable format: File format not recognised

any thoughts ??

[Jens (jens.timmerman)]

You shouldn't be running /home/user/nautilus bug /usr/bin/nautilus

bob1z, do you keep getting this crash? I haven been unable to reproduce it after the first 2 times it happened.

[bob1z (josephcaseley-deactivatedaccount)]

"You shouldn't be running /home/user/nautilus bug /usr/bin/nautilus"

how do fix this then ?

[PatrickSCarrroll (patrickscarroll-hotmail)]

why doesn't the bug reporting software do the backtrace for us? I've never done one before, and when I tried it's been several reboots since then. Seems like a waste of time to even report bugs.

[bob1z (josephcaseley-deactivatedaccount)]

hi ,

I've fix "/home/user/nautilus": not in executable format: File format not recognised" by running :

sudo gdb /usr/bin/nautilus 2>&1 | tee gdb- nautilus .txt
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/nautilus...Reading symbols from /usr/lib/debug/usr/bin/nautilus...done.
done.

but :

I still get "backtrace full
No stack."

any thoughts ??

[MaksimKa (netvin)]

I catch this bug when ejected flash drive without unmounting it.

[Dmitry Shachnev (mitya57)]

> I catch this bug when ejected flash drive without unmounting it.
The same

[Lorenz (lorenzloidl)]

I got too this when ejecting a flash drive - actually I did press on "eject" before and it told me it was ready to be removed.

[Marat Dyatko (marat-dyatko)]

> I catch this bug when ejected flash drive without unmounting it.
Same

[Ryan Kitty (gothickitty93)]

I also got this bug when ejecting a drive, except it was a USB hard drive

[dokuro (dario-soto)]

for me it was an ipod. i removed it by the nautilus arrows to eject drives on the side panel.

[Vsevolod Velichko (torkvemada)]

Hello, have the same bug (ejected two partitions of the USB HDD). I retraced my own stacktrace by apport-retrace and I hope it'll help you.

[Ryan Kitty (gothickitty93)]

This is exactly the same thing that caused the bug for me.

On Sep 29, 2010, at 3:34 PM, Vsevolod Velichko <email address hidden> wrote:

> Hello, have the same bug (ejected two partitions of the USB HDD). I
> retraced my own stacktrace by apport-retrace and I hope it'll help you.

[Jacopo Moronato (jmoronat)]

Just happened when trying to unmount a partition.

[Omer Akram (om26er)]

seems like Gleidson assigned himself mistakenly

[Oliver Joos (oliver-joos)]

I am testing Ubuntu 10.10 rc1. This crash happens whenever I "Safely Remove Drive" my USB-HDD containing 2 partitions. Ubuntu 10.04 kept complaining to be "Unable to stop" this drive (Bug #466575). I consider this crash to be worse than the unnecessary dialog in 10.04!

[chrigu (ch-ba)]

Crash on live-USB (release testing) if I unmount a Partition from the build in HDD. #maverickrelease