nautilus crashed with SIGSEGV in g_file_query_info()

Bug #804764 reported by Blümchen Blau
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

New system and new bug? The crash was not caused by user-active operation in nautilus.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0-2.3-generic-pae 3.0.0-rc4
Uname: Linux 3.0-2-generic-pae i686
Architecture: i386
CrashCounter: 1
Date: Sat Jul 2 13:09:47 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110531.1)
ProcCmdline: nautilus
ProcCwd: /home/ralf
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=de_AT:de
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6b0f6fa: cmp (%edx),%al
 PC (0xb6b0f6fa) 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
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
Blümchen Blau (bluemchen-blau) wrote :
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 #804330, 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.

visibility: private → public
tags: removed: need-i386-retrace
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.