nautilus crashed with SIGSEGV in sort_column_changed_callback()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Nautilus segfaults after performing a search.
Steps to reproduce:
1) Launch Nautilus from Gnome Shell
2) Click the search button and enter something to search for
3) It will take some time to do the searcing. When it appears to display the result, Nautilus crashes.
Reproducible: Always
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.5-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-15-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Tue Feb 14 15:35:19 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: nautilus
ProcEnviron:
LANGUAGE=en_HK:en
PATH=(custom, no user)
LANG=en_HK.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2011-08-26 (172 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
visibility: | private → public |
Thanks for your bug report. This has a coredump attached, which can contain sensitive information, so I'm going to mark this as private until the retracer gets what it needs and removed the attachment.