nautilus crashed with SIGSEGV in g_object_unref()

Bug #403628 reported by h1l4nd0r
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

more logs

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Jul 23 20:50:09 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.4-0ubuntu2
ProcCmdline: nautilus --sm-client-id 1049356e31e64b0a23123730530227191200000041050026 --sm-client-state-file /home/username/.config/session-state/nautilus-1248323588.desktop
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0x7ffd329cc679: mov 0x8(%rbp),%rdi
 PC (0x7ffd329cc679) ok
 source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_object_unref()
Uname: Linux 2.6.31-3-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

visibility: private → public
tags: removed: need-amd64-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.