nautilus crashed with SIGSEGV in g_str_hash()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nautilus
Reproducible but not on different systems
TESTCASE:
1. Click on the application place (Top left corner)
2. Select 'Find Internet Apps'. It opens Nautilus
3. Click on the window close button
Result:
Nautilus crashes and generate this report.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu5
ProcVersionSign
Uname: Linux 2.6.38-3-generic i686
Architecture: i386
CrashCounter: 1
Date: Fri Feb 11 12:33:07 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
ProcCmdline: nautilus
ProcEnviron:
LANGUAGE=
LANG=en_US.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x4cd64c <g_str_hash+12>: movzbl (%ecx),%edx
PC (0x004cd64c) ok
source "(%ecx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_str_hash () from /lib/libglib-
?? ()
g_hash_
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in g_str_hash()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(nautilus:1229): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nautilus:1229): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nautilus:1457): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nautilus:1457): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nautilus:1839): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
usr_lib_nautilus: nautilus 1:2.32.
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 #718098, 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.