nautilus crashed with SIGSEGV in g_file_query_info()

Bug #819109 reported by Doug McMahon
94
This bug affects 13 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
Undecided
Unassigned
deja-dup (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

This crash occurs when trying to run a root nautilus and has been reported. The issue here and on other installs of mine is caused by the deja-dup package being installed
As soon as it is removed I can open a root nautilus browser from terminal or run dialog.

Please note that on this fresh install if deja-dup is re-installed I can no longer open a root nautilus. (same crash occurs
However on an older install I can re-install deja-dup, though I'd need to ck. to see if I disabled it from autostart

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
CrashCounter: 1
Date: Sun Jul 31 23:27:58 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110731)
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x3e52e08: movzbl (%eax),%ecx
 PC (0x03e52e08) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 g_file_query_info () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_file_query_info()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Doug McMahon (mc3man) wrote :
visibility: private → public
Changed in deja-dup (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #777611, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-i386-retrace
Revision history for this message
Michael Terry (mterry) wrote :

This was apparently due to deja-dup's nautilus plugin using some glib functions during nautilus initialization. By delaying deja-dup's own initialization until nautilus is done, we avoid the crash. I fixed it upstream, will shortly push a patch in Ubuntu.

Changed in deja-dup:
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package deja-dup - 19.4-0ubuntu2

---------------
deja-dup (19.4-0ubuntu2) oneiric; urgency=low

  * debian/patches/delay_nautilus_init.patch:
    - Patch from upstream to fix nautilus crash when running as root.
      LP: #819109
 -- Michael Terry <email address hidden> Mon, 01 Aug 2011 11:41:04 -0400

Changed in deja-dup (Ubuntu):
status: Confirmed → Fix Released
Michael Terry (mterry)
Changed in deja-dup:
milestone: none → 19.5
Michael Terry (mterry)
Changed in deja-dup:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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