nautilus crashed with SIGSEGV in g_file_query_info()

Bug #804330 reported by useResa on 2011-07-01
This bug affects 27 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)

Bug Description

This bug report is a follow up on bug #803728 since I experienced the same issue.
The information gathered is required as suggested by Pedro Villavicencio in comment #2.

I am running oneiric and started apport by using the command: sudo service apport start force_start=1
Next I issued the command: gksu nautilus
The crash report generated is the one that is submitted here.

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:34:08 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
ProcCmdline: nautilus
 PATH=(custom, no user)
 Segfault happened at: 0x40d76fa: cmp (%edx),%al
 PC (0x040d76fa) ok
 source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
 ?? () from /lib/i386-linux-gnu/
 ?? () from /usr/lib/i386-linux-gnu/
 ?? () from /usr/lib/i386-linux-gnu/
 g_file_query_info () from /usr/lib/i386-linux-gnu/
 ?? () from /usr/lib/i386-linux-gnu/
Title: nautilus crashed with SIGSEGV in g_file_query_info()
UpgradeStatus: Upgraded to oneiric on 2011-04-29 (62 days ago)

useResa (rdrijsen) wrote :

 __strcmp_ia32 () at ../sysdeps/i386/i686/multiarch/../strcmp.S:40
 _g_local_file_info_get (basename=0x8c97d00 "/", path=0x8c377f0 "/", attribute_matcher=0x8c97038, flags=G_FILE_QUERY_INFO_NONE, parent_info=0xb6e2f000, error=0xb6e2f0bc) at /build/buildd/glib2.0-2.29.8/./gio/glocalfileinfo.c:1609
 g_local_file_query_info (file=0x8b320c0, attributes=0x8c96f88 "standard::*,access::*,mountable::*,time::*,unix::*,owner::*,selinux::*,thumbnail::*,id::filesystem,trash::orig-path,trash::deletion-date,metadata::*", flags=G_FILE_QUERY_INFO_NONE, cancellable=0x8c74e40, error=0xb6e2f0bc) at /build/buildd/glib2.0-2.29.8/./gio/glocalfile.c:1188
 g_file_query_info (file=0x8b320c0, attributes=0x8c96f88 "standard::*,access::*,mountable::*,time::*,unix::*,owner::*,selinux::*,thumbnail::*,id::filesystem,trash::orig-path,trash::deletion-date,metadata::*", flags=G_FILE_QUERY_INFO_NONE, cancellable=0x8c74e40, error=0xb6e2f0bc) at /build/buildd/glib2.0-2.29.8/./gio/gfile.c:1106
 query_info_async_thread (res=0x8c83900, object=0x8b320c0, cancellable=0x8c74e40) at /build/buildd/glib2.0-2.29.8/./gio/gfile.c:4830

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
useResa (rdrijsen) on 2011-07-04
visibility: private → public
Pedro Villavicencio (pedro) wrote :

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:

Changed in nautilus (Ubuntu):
status: New → Triaged
Changed in nautilus:
importance: Unknown → Medium
status: Unknown → New

Got the same thing when running from the terminal with gksudo trying to reproduce another bug

Changed in nautilus:
importance: Medium → Critical
Doug McMahon (mc3man) wrote :

Fixed here with 07/25 iso install and current nautilus (1:3.1.4-0ubuntu1), - root file browser works fine from available means ( terminal, Alt+F2, nautilus-action

Doug McMahon (mc3man) wrote :

I have removed the bug I filed that was duped to here and duped to a new one , bug #819109
On FRESH installs I'm still unable to run a root nautilus, and get the same crash
However if I remove deja-dup then a root nautilus opens with no issue, this has been confirmed here on both a fresh install today and several recent live sessions w/ the dailt iso
May want to be considered in resolution here.

Changed in nautilus:
status: New → Invalid
dino99 (9d9) wrote :

This version has expired

Changed in nautilus (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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