nautilus crashed with SIGSEGV in IA__g_str_hash()

Bug #401426 reported by banza
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

crash after emtying trash

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Jul 19 18:55:31 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.4-0ubuntu1
ProcCmdline: nautilus --sm-client-id 102c8c265638fb0bfd124557294073022900000037520022 --sm-client-state-file /home/username/.config/session-state/nautilus-1245583224.desktop
ProcEnviron:
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0x5bcee7 <IA__g_str_hash+7>: movsbl (%edx),%eax
 PC (0x005bcee7) ok
 source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 IA__g_str_hash (v=0x0) at /build/buildd/glib2.0-2.21.3/glib/gstring.c:95
 g_hash_table_lookup_node (hash_table=0x8cfd260, key=0x0)
 IA__g_hash_table_lookup (hash_table=0x8cfd260, key=0x0)
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in IA__g_str_hash()
Uname: Linux 2.6.31-3-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video

Revision history for this message
banza (banza) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

crash at the ubuntuone-client, reassigning, thanks.

visibility: private → public
affects: nautilus (Ubuntu) → ubuntuone-client (Ubuntu)
tags: added: 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.