nautilus crashed with SIGSEGV in PyThreadState_New()

Bug #427946 reported by Nizar Kerkeni
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus-python (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

crash after updating from jaunty to karmic alpha 5

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 11 16:29:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.92-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SegvAnalysis:
 Segfault happened at: 0x7fbe472ce71f <PyThreadState_New+239>: mov 0x8(%rbp),%rax
 PC (0x7fbe472ce71f) ok
 source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 PyThreadState_New ()
 PyGILState_Ensure ()
 ?? ()
 g_datalist_clear () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in PyThreadState_New()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Nizar Kerkeni (nizarus) wrote :
affects: nautilus (Ubuntu) → nautilus-python (Ubuntu)
Revision history for this message
dino99 (9d9) wrote :

This version has died long ago; no more supported

Changed in nautilus-python (Ubuntu):
status: New → Invalid
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.