nautilus crashed with SIGSEGV

Bug #1034810 reported by Bence Lukács
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

I just try to erase the search field after a search, and then the nautilus crashed.
Ubuntu 12.10 Quantal, Nautilus 1:3.5.5-0ubuntu1

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-7.7-generic 3.5.0
Uname: Linux 3.5.0-7-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
Date: Thu Aug 9 11:35:52 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+1640+84'"
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120627)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80d9faa: movzbl 0x28(%edx),%edx
 PC (0x080d9faa) ok
 source "0x28(%edx)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus:
 brasero 3.4.1-0ubuntu2
 evince 3.5.5-0ubuntu1
 file-roller 3.5.4-0ubuntu1
 nautilus-share 0.7.3-1ubuntu2
 totem 3.4.3-0ubuntu1

Revision history for this message
Bence Lukács (lukacs-bence1) 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 this software better. This particular crash has already been reported and is a duplicate of bug #1034548, 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.