nautilus crashed with SIGSEGV in PyThreadState_New()

Bug #734840 reported by madw0lf
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ground Control
Won't Fix
Critical
Unassigned
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: nautilus

root@madw0lf-testlab:/home/madw0lf# nautilus
Initializing nautilus-gdu extension
WARNING:root:Configuration file: '/root/.config/groundcontrol/settings.yaml' doesn't exist
Traceback (most recent call last):
  File "/usr/lib/nautilus/extensions-2.0/python/nautilus-groundcontrol.py", line 38, in <module>
    from GroundControl.commiter import CommitChanges, RevertChanges
  File "/usr/lib/pymodules/python2.7/GroundControl/commiter.py", line 31, in <module>
    from bzrlib.plugins.gtk.diff import DiffView
ImportError: No module named gtk.diff
Ошибка сегментирования (core dumped)
root@madw0lf-testlab:/home/madw0lf#

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic i686
Architecture: i386
Date: Mon Mar 14 16:46:23 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
ProcCmdline: nautilus
ProcEnviron:
 SHELL=/bin/bash
 LANG=ru_RU.UTF-8
 LANGUAGE=ru_RU:en
SegvAnalysis:
 Segfault happened at: 0x29e24ba <PyThreadState_New+234>: mov 0x4(%edi),%eax
 PC (0x029e24ba) ok
 source "0x4(%edi)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 PyThreadState_New () from /usr/lib/libpython2.7.so.1.0
 PyGILState_Ensure () from /usr/lib/libpython2.7.so.1.0
 ?? () from /usr/lib/pymodules/python2.7/_dbus_bindings.so
 dbus_connection_dispatch () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: nautilus crashed with SIGSEGV in PyThreadState_New()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
madw0lf (madw0lf) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 new_threadstate (interp=0x0) at ../Python/pystate.c:200
 PyThreadState_New (interp=0x0) at ../Python/pystate.c:211
 PyGILState_Ensure () at ../Python/pystate.c:598
 ?? ()
 ?? () from /lib/libdbus-1.so.3

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
madw0lf (madw0lf)
visibility: private → public
Revision history for this message
hrhnick (hrhnick) wrote :

I found that if i removed the "groundcontrol" package, Nautilus worked fine. So if you have it installed, try removing it.

affects: nautilus → groundcontrol
Revision history for this message
Martin Owens (doctormo) wrote :

groundcontrol does not maintain it's own python interpreter or nautilus version. For this reason it is impossible for groundcontrol's python code to cause C code errors unless there is really an error in python or nautilus.

Although I notice an error with bzrlib gtk.diff (which wouldn't cause the crash) but which should be reported as a separate bug. It's probably the changing namespace of bzr-gtk.

Changed in groundcontrol:
importance: Undecided → Critical
status: New → Won't Fix
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Is the issue reproducible with Nautilus 3.1.90 or newer? There's no recent comments on this report indicating that, could you please test and comment back?. Thanks again and we appreciate your help.

Changed in nautilus (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
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.