nautilus crashed with SIGSEGV in PyThreadState_New()

Bug #526365 reported by Gavin Chappell
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus-python (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: nautilus

I just upgraded my laptop from Karmic x64 to Lucid Alpha 2 x64 (via sudo do-release-upgrade -d). All packages installed with no errors, after the first reboot and booting into Lucid's kernel, I logged in and was told that Nautilus had crashed. My taskbar has repeated "Starting File Manager" windows (4 at the moment, although it will occasionaly drop down to three, I don't know whether this is the oldest instances of these timing out or the newest one opening and closing repeatedly) even though I haven't asked Nautilus to open. Also my mouse cursor is constantly in the spinning "busy" state.

If I click on Places->Home, I just get an "Opening gavin" window in the taskbar but no Nautilus window opens up.

gavin@elgac-laptop:~$ lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04

gavin@elgac-laptop:~$ apt-cache policy nautilus
nautilus:
  Installed: 1:2.29.91-0ubuntu1
  Candidate: 1:2.29.91-0ubuntu1
  Version table:
 *** 1:2.29.91-0ubuntu1 0
        500 http://gb.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
Date: Tue Feb 23 10:41:41 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.29.91-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x7f1bda09be3f <PyThreadState_New+239>: mov 0x8(%rbp),%rax
 PC (0x7f1bda09be3f) 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 ()
 ?? ()
 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()
Uname: Linux 2.6.32-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1536): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1565): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:1567): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion `GTK_IS_ACTION (action)' failed
 (gnome-power-manager:1562): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed

Revision history for this message
Gavin Chappell (g-a-c) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 PyThreadState_New (interp=0x0) at ../Python/pystate.c:201
 PyGILState_Ensure () at ../Python/pystate.c:581
 ?? ()
 dbus_connection_dispatch (connection=0x2e69d60)
 message_queue_dispatch (

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-amd64-retrace
Revision history for this message
Gavin Chappell (g-a-c) wrote :

I just noticed that once I closed all my open windows, my desktop background still appears to be that of the gdm login screen, I can't right click it, and the folders on my desktop are invisible (although still on the filesystem). Is nautilus still responsible for rendering the "desktop" as a clickable, interactive entity? This may explain why nautilus was crashing even though I hadn't actually opened any nautilus windows.

Revision history for this message
Gavin Chappell (g-a-c) wrote :

My mistake, I thought I'd removed any unnecessary PPA software before I release-upgraded. However, I'd forgotten that I recently installed groundcontrol from DoctorMo's PPA. I've now purged this and nautilus is working correctly again.

visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, is this still an issue with latest package on Lucid?

Changed in nautilus (Ubuntu):
status: New → Incomplete
Revision history for this message
Gavin Chappell (g-a-c) wrote :

I haven't tried reinstalling Ground Control to replicate the bug after removing it in my last report, if that's what you're asking.

If you or doctormo would like me to do so and test it, I can do this for you however.

affects: nautilus (Ubuntu) → nautilus-python (Ubuntu)
affects: nautilus-python (Ubuntu) → nautilus (Ubuntu)
affects: nautilus (Ubuntu) → nautilus-python (Ubuntu)
affects: nautilus-python (Ubuntu) → nautilus (Ubuntu)
affects: nautilus (Ubuntu) → nautilus-python (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus-python (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.