nautilus crashed with SIGSEGV in g_type_check_instance()

Bug #753241 reported by Adriano Santos da Silva on 2011-04-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)

Bug Description

Binary package hint: nautilus

1) Ubuntu 11.04
2) unknown
3) nothing
4) Nautilus just crash after i closed qBittorrent

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Thu Apr 7 03:45:36 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: nautilus
 Segfault happened at: 0x3473f3 <g_type_check_instance+35>: mov (%eax),%edx
 PC (0x003473f3) ok
 source "(%eax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
 g_type_check_instance () from /usr/lib/i386-linux-gnu/
 g_signal_connect_data () from /usr/lib/i386-linux-gnu/
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: Upgraded to natty on 2011-04-02 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

 g_type_check_instance (type_instance=0x8edf158) at /build/buildd/glib2.0-2.28.5/./gobject/gtype.c:4068
 g_signal_connect_data (instance=0x8edf158, detailed_signal=0x81ac469 "destroy", c_handler=0x812f040 <pending_icon_to_reveal_destroy_callback>, data=0x8823018, destroy_data=0, connect_flags=0) at /build/buildd/glib2.0-2.28.5/./gobject/gsignal.c:2243
 set_pending_icon_to_reveal (container=0x8823018, icon=0x9123000) at nautilus-icon-container.c:622
 end_renaming_mode (container=0x8823018, commit=1) at nautilus-icon-container.c:8481
 icon_toggle_selected (container=0x8823018, icon=0x9123000) at nautilus-icon-container.c:472

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers