nautilus crashed with SIGSEGV in g_timer_stop()

[useResa]

Got informed that there was an issue with Nautilus after a reboot.
Hopefully the attached information is helpful to determine the cause.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic i686
Architecture: i386
Date: Fri Jul 1 15:49:19 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x96e87e <g_timer_stop+30>: andb $0xfe,0x10(%esi)
 PC (0x0096e87e) ok
 source "$0xfe" ok
 destination "0x10(%esi)" (0xaaaaaaba) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_timer_stop () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgdk-3.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_timer_stop()
UpgradeStatus: Upgraded to oneiric on 2011-04-29 (64 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_timer_stop (timer=0xaaaaaaaa) at /build/buildd/glib2.0-2.29.8/./glib/gtimer.c:148
 gtk_timeline_run_frame (timeline=0x9eedc10) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtktimeline.c:356
 gdk_threads_dispatch (data=0x9cf9860) at /build/buildd/gtk+3.0-3.1.6/./gdk/gdk.c:754
 g_timeout_dispatch (source=0x9e7f3a0, callback=0xb02bf0 <gdk_threads_dispatch>, user_data=0x9cf9860) at /build/buildd/glib2.0-2.29.8/./glib/gmain.c:3955
 g_main_dispatch (context=0x993e7a0) at /build/buildd/glib2.0-2.29.8/./glib/gmain.c:2477

[Pedro Villavicencio (pedro)]

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

[Joschi Poschi (joschiposchi)]

Nautilus didn't start correctly (empty window) so I closed it.

[useResa (rdrijsen)]

I am not sure what to make of comment #6. Does this mean that this bug is closed?

Fact is indeed that Nautilus did not start correctly and that I have an entirely empty window.
However, until today I encounter this every time I use Nautilus for the first time after a reboot.

Can someone please clarify the status?

[Pedro Villavicencio (pedro)]

The status of the bug is Triaged it says that clearly at the top of it, please look there and not the comments random users add to it. Thanks.

[Evan Huus (eapache)]

The status is what it says at the top: Triaged. This means that the bug is open, and has enough information for a developer to code a fix.

You can find more information on bug statuses at <https://help.launchpad.net/Bugs/Statuses>

I believe Johannes was referring to the empty window, not the bug :)

[useResa (rdrijsen)]

Thanks for clarifying the situation. I had indeed seen that the bug status was saying "Triaged" but was confused by the remark of Johannes. Thus I thought it was better to confirm.

[Laura Czajkowski (czajkowski)]

Getting this error today after I upgraded from Natty to Oneiric. On start up after a few mins of doing nothing it pops up with the crash report. Doing nothing in particular to set it off and only have a terminal and a browser open

[ironwit (ironwit)]

downloading torrent on 2 MB/s, open nautilus and crash. notebook asus a3f

[Moussouni Mehdi (mmoussouni47)]

At some moments (like open a new tab or a window of nautilus), it crashes at the next reboot there isn't a new crash (the most time).

[igi (igor-cali)]

Got this error after USB media insertion: Nautilus automatically opened (setting on media insertion), but only an empty grey window (captioned Nautilus) with no GUI control inside. After a while the window disappeared and the crash report popped up.

[ahmetcgl (ahmetcgl)]

it just happened dont know why maybe because I was trying to do a lot of things at one time

[Scott Stensland (scottstensland)]

I also just got this same crash
just prior to crash my freshly launched nautilus window went DARK
as apps do when the machine is busy and app is not responsive
I feel nautilus is TOO sensitive to such resource constrained (cpu or I/O) delays
and pops up with such a crash window prematurely - it needs to chill a bit more
before throwing up its hands and claiming a crash happened

[sebastian-s (sebastian-s)]

Open nautilus via dialogue that comes up when plugging my SD card in

[jerrylamos (jerrylamos)]

Oneiric Ocelot 13 Sept Daily Build, running Live on real hardware
Opened terminal, did
df then
Selected Install and got this bug.

This is from first time boot non-persistent, not a reboot as in the header to this problem.

Jerry

[Leon (leonbo)]

I was running a python script which indexes my (huge) Maildir. Then I opened nautilus and it crashed.

[Luke Scharf (lukescharf)]

I was managing files on a remote SFTP server "mounted" via gvfs.

[Michael Harkess (michaelharkess)]

Right clicked on dekstop and clicked desktop settings

[matrinko (konstiak)]

It crashed when I launched nautilus from file roller (archiver) as "Show files" button.

[Colin Law (colin-law)]

Bug #903845 may be related to this, or may be a duplicate. I have submitted it as a new bug as it occurs fairly consistently for me and in syslog/dmesg I see
nautilus[31311]: segfault at aaaaaaba ip 00be929e sp bfb75fa0 error 6 in libglib-2.0.so.0.3102.0[b7f000+f3000]
which is not something I have seen mentioned here and I wanted to make sure the stack trace and so on were captured and I was not sure how to do that other than reporting a new bug.

[skipper (attila-egri-nagy)]

Same in Precise, I connected an external harddrive, nautilus could only show a blank windowframe, then crashed.

[George Christofis (geochr)]

Nautilus i not running on 12.04 alpha 1 with kernel 3.2.0-8-generic.

[psamuel (persaudsamuel)]

alguna solucion?

[Launchpad Janitor (janitor)]

This bug was fixed in the package gtk+3.0 - 3.3.10-0ubuntu2

---------------
gtk+3.0 (3.3.10-0ubuntu2) precise; urgency=low

  * debian/patches/git_gtkrecentmanager_updated.patch:
    - git patches to ensure that saved files are recorded in the recently
      used files, which will make them i.e available in the files lens
      (lp: #920961)
  * debian/patches/git_gtktimer_unref_protection.patch:
    - git patch, fixes a possible invalid unread in gtktimer,
      should fix a common nautilus segfault (lp: #804891)
 -- Sebastien Bacher <email address hidden> Thu, 26 Jan 2012 17:40:10 +0100