nautilus crashed with SIGSEGV in exit()

[Angel Guzman Maeso]

Binary package hint: nautilus

Just a crash.

ProblemType: Crash
Architecture: i386
Date: Fri Jul 24 22:53:08 2009
Disassembly: 0x1b169f0:
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.4-0ubuntu2
ProcCmdline: nautilus --sm-client-id 10d173c22f5b45bdd1124767146018488000000036130047 --sm-client-state-file /home/User Name/.config/session-state/nautilus-1248453862.desktop
ProcEnviron:
 PATH=(custom, user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.21-generic
SegvAnalysis:
 Segfault happened at: 0x1b169f0:
 PC (0x01b169f0) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0x01b169f0 in ?? ()
 #1 0x04034679 in exit () from /lib/tls/i686/cmov/libc.so.6
 #2 0x0401a7cd in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #3 0x0806be31 in _start () at ../sysdeps/i386/elf/start.S:119
 No locales.
StacktraceTop:
 ?? ()
 exit () from /lib/tls/i686/cmov/libc.so.6
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 _start () at ../sysdeps/i386/elf/start.S:119
Title: nautilus crashed with SIGSEGV in exit()
Uname: Linux 2.6.31-4-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy kvm lpadmin netdev plugdev powerdev pulse-rt sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:?? ()
__libc_start_main (main=0x8080c40 <main>, argc=5,
_start () at ../sysdeps/i386/elf/start.S:119

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Also, please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will greatly aid us in tracking down your problem and resolving this bug.

[Angel Guzman Maeso (shakaran)]

The bug happens sometimes, but I dont know how to reproduce it.

[Scott Howard (showard314)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually 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.

[Angel Guzman Maeso (shakaran)]

I dont know how to do a nice backtrace:
 gdb nautilus 2>&1 | tee ~/gdb-nautilus.txt
GNU gdb (GDB) 6.8.50.20090628-cvs-debian
Copyright (C) 2009 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 "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run --sm-client-id 10d173c22f5b45bdd1124767146018488000000036130047 --sm-client-state-file /home/shakaran/.config/session-state/nautilus-1248453862.desktop
Starting program: /usr/bin/nautilus --sm-client-id 10d173c22f5b45bdd1124767146018488000000036130047 --sm-client-state-file /home/shakaran/.config/session-state/nautilus-1248453862.desktop
[Thread debugging using libthread_db enabled]

(nautilus:27466): EggSMClient-WARNING **: Could not load SM state file '/home/shakaran/.config/session-state/nautilus-1248453862.desktop': No such file or directory
[Nuevo Thread 0xb7e3cb90 (LWP 27470)]
[Thread 0xb7e3cb90 (LWP 27470) exited]

Program exited normally.
(gdb) backtrace full
No stack.

Could you indicate the exact commands?

[kylea (kylea)]

Also got this crash on AMD64 - Karmic Alpha -3

[Nemes Ioan Sorin (nemes-sorin)]

right after Desktop is loaded this crash occur.

Nothing too visible for the user. I have radeon driver for an Radeon HD2600 PCIe.

Sometime when I open folders from my desktop, last 3 lines of icons on the bottom side of the screen got a duplicate shadow which disappear when I drag a rectangle with mouse around the problematic area.

My kernel is 2.6.31-5

[Scott Howard (showard314)]

Thank you all for noticing this, but we need more information to debug this.
The easiest thing to do is:
1) create a file named: "~/nautilus-debug-log.conf"
2) edit it and add:
[debug log]
max lines = 1000
enable domains = async
3) when nautlus crashes, attach the file "~/nautilus-debug-log.txt" to this bug report.

If that doesn't work, we would need a complete backtrace to properly debug this (one without ?? in it).
The instructions are here:
http://wiki.ubuntu.com/DebuggingProgramCrash

specifically follow:
https://wiki.ubuntu.com/DebuggingProgramCrash#Hardy%20Heron%208.04,%20Intrepid%20Ibex%208.10,%20and%20Jaunty%20Jackalope%209.04

then:
https://wiki.ubuntu.com/Backtrace , but follow the instructions of a program already running

[Pedro Villavicencio (pedro)]

This looks like bug https://bugzilla.gnome.org/show_bug.cgi?id=584745 ; linking the report.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Angel Guzman Maeso (shakaran)]

I cant make a valgrind log because this crash only happens sometimes:

$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log nautilus --sm-client-id 10d173c22f5b45bdd1124767146018488000000036130047 --sm-client-state-file /home/shakaran/.config/session-state/nautilus-1248453862.desktop
(nautilus:23511): EggSMClient-WARNING **: Could not load SM state file '/home/shakaran/.config/session-state/nautilus-1248453862.desktop': No such file or directory

The trick for nautilus-debug-log.txt dont work.

PS: I have translated the Valgrind wiki page into Spanish, for potential users who need it.
https://wiki.ubuntu.com/Valgrind_es

[cool_cero (alexredondosk8)]

no arranca el nautilus cuando el S.O inicia.

[msieloff (m-sieloff-web)]

nautilus crashed every time after desktop is loaded.

[osta (pascal-brachais)]

no comment

[Gustavo (gstv.inc)]

nautilus crashed every time after desktop is loaded. for me to......again again again....!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[Mohammed Sayed (msayed2004)]

Not sure if it is related to the graphics driver but when I use the Intel driver (for my i810) I get this crash repeatedly, using vesa just alleviate the situation.

[clint (kafnir-deactivatedaccount)]

I am not sure if its nautilus that crash because I just reboot the system and the crash bug program display the error message.

[Uoc Nguyen (tiger2wander)]

I have same problem with clint

[VcDeveloper (developer-gardenofedenblessing)]

I just upgraded from 9.04 to 9.10 via Update Manager and it consistantly crashes after reboot or after booting. I will try to send a report according to the info above.

[Martin Wildam (mwildam)]

For me it happened just one time after rebooting where I think it tried to remember open windows. - Try to disable remember of open windows in System->Preferences->Startp Applications->Options

Maybe that helps

[Philipp Gampe (pgampe)]

From Gnome Bug Tracker:

remove nautilus-actions might solve it

https://bugzilla.gnome.org/show_bug.cgi?id=584745#c7

[VcDeveloper (developer-gardenofedenblessing)]

Uhmmm, I just updated my Vbox installed ZorinOS Ubuntu and sofar no crashes!

[VcDeveloper (developer-gardenofedenblessing)]

Well, My Vbox version is now having the crashes. I'm not sure if it was because I had my Language changed and updated to English(USA) and/or after I did the update, I did a complete shutdown and boot.

[Martin Wildam (mwildam)]

My VBox runs well - But I have chosen language English but location Denmark (although I am not there - I have shosen ist because I wanted iso date format everywhere.

I cannot really let go nNautilus-actions - I have a few things in there I use all the time.

[Ted (ted-kell)]

Just upgraded to Ubuntu 9.10

[rotsee (leo-wallentin)]

A few seconds after logging in this happens everytime I start my laptop after upgrading to Ubuntu 9.10

[Martin Wildam (mwildam)]

In my case this happened/happens only when starting up with my mobile internet Huawei E160G HSPDA Modem connected and WLAN disabled (my machine is a real one - Dell Latitude E5500 - no Virtual machine).

[Unspeakable Horror (carlos-uh)]

I got this too after restarting from upgrading to Ubuntu 9.10

[kylea (kylea)]

Since doing a complete re-Install (not upgrade) have not had a repeat of this error.

2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux
------------------
Description: Ubuntu 9.10
Release: 9.10

[clayart (clayart-gr)]

Hello,
I am not sure but it seems it has to do with ubuntuone. Nautilus crashed after loading the desktop and connection to ubuntuone.

[Martin Wildam (mwildam)]

I didn't have the Ubuntu one startet - neither wasn't subscribed and happened to me also.

[Glauco (glauco-hass)]

I confirm this bug in Karmic and the error at login has gone after disabling Ubuntuone from startup session programs.

[Ivana Trčak (the-real-mimoza-deactivatedaccount)]

I re-installed ubuntu 9.10. And now have no prolems with it.

[Martin Wildam (mwildam)]

Since disabling autostart of UbuntuOne and (at the same time registering at UbuntuOne) I don't face that problem again - so one or both actions helped in my case. - By default after the Upgrade the UbuntuOne is automatically started - even if you don't have an account yet and even I did not see an UbuntuOne icon in the tray.

[dobey (dobey)]

I'm marking this as invalid for the ubuntuone-client package. The origianl retraced backtrace shows a stack of 3 frames, with #0 being some unknown that _libc_start_main() is calling, which means it's probably g_main_loop_run() or something, and not anything in an extension (and ubuntuone doesn't run another main loop in the extension). The reports that somehow disabling the start-up of the ubuntuone-client-applet at log-in causing the crash to no longer occur I believe are without merit. There is no connection at all between the applet and the nautilus extension. They are both independent clients of the ubuntuone-syncdaemon dbus interface (and there are no references to DBus anywhere in this bug).

This is most likely a memory corruption error in upstream nautilus, but I am not seeing the crash, and it may well have been inadvetently fixed in 2.28.x already.

[omyk (omyk)]

Hi,
The crash happened only once, just after first restart after upgrade. I
think we can close this case.
Thank you!
Tomasz

-----Original Message-----
From: Rodney Dawes <email address hidden>
To: <email address hidden>
Subject: [Bug 404351] Re: nautilus crashed with SIGSEGV in exit()
Date: Wed, 25 Nov 2009 14:36:53 -0000

I'm marking this as invalid for the ubuntuone-client package. The
origianl retraced backtrace shows a stack of 3 frames, with #0 being
some unknown that _libc_start_main() is calling, which means it's
probably g_main_loop_run() or something, and not anything in an
extension (and ubuntuone doesn't run another main loop in the
extension). The reports that somehow disabling the start-up of the
ubuntuone-client-applet at log-in causing the crash to no longer occur I
believe are without merit. There is no connection at all between the
applet and the nautilus extension. They are both independent clients of
the ubuntuone-syncdaemon dbus interface (and there are no references to
DBus anywhere in this bug).

This is most likely a memory corruption error in upstream nautilus, but
I am not seeing the crash, and it may well have been inadvetently fixed
in 2.28.x already.

** Changed in: ubuntuone-client (Ubuntu)
       Status: New => Invalid

[Pedro Villavicencio (pedro)]

The last duplicate of this bug is from 2009-12-01 and there's no duplicates using the Lucid version of Nautilus, is any of you able to reproduce it with Lucid or with Latest packages on Karmic?. We haven't received any duplicates since Dec, so this is probably fixed already. Thanks in advance!.

[morstofolini luigi (gigmo)]

Pedro Villavicencio ha scritto:
> The last duplicate of this bug is from 2009-12-01 and there's no
> duplicates using the Lucid version of Nautilus, is any of you able to
> reproduce it with Lucid or with Latest packages on Karmic?. We haven't
> received any duplicates since Dec, so this is probably fixed already.
> Thanks in advance!.
>
>
Io da allora sono passato alla versione Karmic amd64 e questo bug non mi
si è più presentato.

[C de-Avillez (hggdh2)]

<butchered translation>
I have gone to Karmic amd64, and cannot see this bug anymore.
</butchered translation>

This is not exactly what was written, but this is the gist.

[hugeanes (hugeanes)]

Hello,
I haven't tried Lucid, and with Karmic it seems that the crash doesn't
appear anymore but I don't know when.
hope it is solved!
Regards.

Le jeudi 28 janvier 2010 à 18:23 +0000, Pedro Villavicencio a écrit :
> The last duplicate of this bug is from 2009-12-01 and there's no
> duplicates using the Lucid version of Nautilus, is any of you able to
> reproduce it with Lucid or with Latest packages on Karmic?. We haven't
> received any duplicates since Dec, so this is probably fixed already.
> Thanks in advance!.
>

[Martin Wildam (mwildam)]

Maybe it's not reported with Lucid because error reporting does not work - at least for me I have crashes each start (didn't look at the details) - automatic reporting does not work - already filed a bug for that.

[richalux (richalux)]

No more crashes on my amd64 machine since mid December, running with all updates on karmic. Thanks!

a piedrazos sigo cuidando la milpa...

--- On Thu, 1/28/10, Pedro Villavicencio <email address hidden> wrote:

From: Pedro Villavicencio <email address hidden>
Subject: [Bug 404351] Re: nautilus crashed with SIGSEGV in exit()
To: <email address hidden>
Date: Thursday, January 28, 2010, 12:23 PM

The last duplicate of this bug is from 2009-12-01  and there's no
duplicates using the Lucid version of Nautilus, is any of you able to
reproduce it with Lucid or with Latest packages on Karmic?. We haven't
received any duplicates since Dec, so this is probably fixed already.
Thanks in advance!.

--
nautilus crashed with SIGSEGV in exit()
https://bugs.launchpad.net/bugs/404351
You received this bug notification because you are a direct subscriber
of a duplicate bug.

[midas_337 (midas-337)]

Hi,

Happened only once, I have applied all updates continously and haven't seen the bug anymore.

Regards,
  Mats

> Date: Thu, 28 Jan 2010 18:23:01 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 404351] Re: nautilus crashed with SIGSEGV in exit()
>
> The last duplicate of this bug is from 2009-12-01 and there's no
> duplicates using the Lucid version of Nautilus, is any of you able to
> reproduce it with Lucid or with Latest packages on Karmic?. We haven't
> received any duplicates since Dec, so this is probably fixed already.
> Thanks in advance!.
>
> --
> nautilus crashed with SIGSEGV in exit()
> https://bugs.launchpad.net/bugs/404351
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Nautilus: Unknown
> Status in “nautilus” package in Ubuntu: Incomplete
> Status in “ubuntuone-client” package in Ubuntu: Invalid
>
> Bug description:
> Binary package hint: nautilus
>
> Just a crash.
>
> ProblemType: Crash
> Architecture: i386
> Date: Fri Jul 24 22:53:08 2009
> Disassembly: 0x1b169f0:
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/nautilus
> Package: nautilus 1:2.27.4-0ubuntu2
> ProcCmdline: nautilus --sm-client-id 10d173c22f5b45bdd1124767146018488000000036130047 --sm-client-state-file /home/User Name/.config/session-state/nautilus-1248453862.desktop
> ProcEnviron:
> PATH=(custom, user)
> LANG=es_ES.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-4.21-generic
> SegvAnalysis:
> Segfault happened at: 0x1b169f0:
> PC (0x01b169f0) not located in a known VMA region (needed executable region)!
> SegvReason: executing unknown VMA
> Signal: 11
> SourcePackage: nautilus
> Stacktrace:
> #0 0x01b169f0 in ?? ()
> #1 0x04034679 in exit () from /lib/tls/i686/cmov/libc.so.6
> #2 0x0401a7cd in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> #3 0x0806be31 in _start () at ../sysdeps/i386/elf/start.S:119
> No locales.
> StacktraceTop:
> ?? ()
> exit () from /lib/tls/i686/cmov/libc.so.6
> __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> _start () at ../sysdeps/i386/elf/start.S:119
> Title: nautilus crashed with SIGSEGV in exit()
> Uname: Linux 2.6.31-4-generic i686
> UserGroups: adm admin audio cdrom dialout dip floppy kvm lpadmin netdev plugdev powerdev pulse-rt sambashare scanner video
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/nautilus/+bug/404351/+subscribe

_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969

[_sRg_ (sor-sergey)]

I've just forgotten to close nautilus window and logged off user from GNOME session. Then logged in again and saw this bug report.

[Pedro Villavicencio (pedro)]

Ok thanks all, let's close this bug report for now, but Please if you noticed it again open a bug with apport and let the auto retracer to decide if it's a duplicate or a person in our team, Thanks everybody who confirmed that this is no longer an issue.