nautilus crashed with SIGSEGV in fm_directory_view_update_menus()

Bug #328966 reported by Jens on 2009-02-13
38
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
nautilus (Ubuntu)
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

jens@neo:~$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04
jens@neo:~$ apt-cache policy nautilus
nautilus:
  Installed: 1:2.25.4-0ubuntu1
  Candidate: 1:2.25.4-0ubuntu1
  Version table:
 *** 1:2.25.4-0ubuntu1 0
        500 http://be.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

This crash happened after 2nd reboot after some updates.
It had to do with a couple of dir's not being in place, I had a private folder set up and linked .gnome .gnome2 and some other dirs to it, but since the last reboot it seems to be broken, (passphrase invalid, I'll file a bug for that on the right place)

But these unaccessible dir's seemded to cause nautilus to fail causing me to be able do nothing after login...
I have a bunch of
[ 377.554482] nautilus[6601]: segfault at 0 ip 000000000047b21e sp 00007fff38956af0 error 4 in nautilus[400000+1ac000]
[ 378.729275] nautilus[6604]: segfault at 0 ip 000000000047b21e sp 00007fffb815d2f0 error 4 in nautilus[400000+1ac000]
[ 379.920533] nautilus[6607]: segfault at 0 ip 000000000047b21e sp 00007fff22a33bd0 error 4 in nautilus[400000+1ac000]
[ 381.102477] nautilus[6611]: segfault at 0 ip 000000000047b21e sp 00007fffaefb8150 error 4 in nautilus[400000+1ac000]
[ 382.267958] nautilus[6615]: segfault at 0 ip 000000000047b21e sp 00007fff538aaa40 error 4 in nautilus[400000+1ac000]
 in dmesg.

after deleting my symlinks to all private folders and restarting x and loging in again nautilus and the gnome menu's are working again...

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.25.4-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 fm_directory_view_update_menus ()
Title: nautilus crashed with SIGSEGV in fm_directory_view_update_menus()
Uname: Linux 2.6.28-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Jens (jens.timmerman) wrote :

StacktraceTop:update_scripts_menu (view=0x251b490)
real_update_menus (view=0x251b490)
fm_icon_view_update_menus (view=0x251b490)
real_update_menus (view=0x251b490)
fm_directory_view_update_menus (view=0x251b490)

Changed in nautilus:
importance: Undecided → Medium
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=571611

Changed in nautilus:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in nautilus:
status: Unknown → New
Changed in nautilus:
importance: Unknown → Critical
madbiologist (me-again) on 2011-05-21
tags: added: jaunty
madbiologist (me-again) wrote :

Is this still occurring in Ubuntu 10.04 "Lucid Lynx"?

Changed in nautilus (Ubuntu):
status: Triaged → Incomplete
Pedro Villavicencio (pedro) wrote :

Please test with Natty instead, it's always better to check with the latest stable release, thanks in advance.

madbiologist (me-again) wrote :

Does this mean that if there is a fix in Natty it could potentially be backported to Lucid if necessary? (Hopefully it wasn't fixed in Lucid and then regressed in Natty). Should Jens test with Oneiric yet?

Given that Lucid is an LTS, testing with Lucid first could be a faster way to close this bug.

Pedro Villavicencio (pedro) wrote :

Depending on how much work it requires, but if it's a small fix that doesn't require dependencies not available on Lucid, yes it could be backported. And no, we always recommend to test with latest stable not latest LTS, Lucid is already 1 year old and things on free software are changing pretty fast, so we prefer and recommend to test with latest stable, thanks much.

Jens (jens.timmerman) wrote :

I just tested this again on a new install of ubuntu and the bug is still in place

jens@morpheus:~$ lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

jens@morpheus:~$ apt-cache policy nautilus
nautilus:
  Installed: 1:2.32.2.1-0ubuntu13
  Candidate: 1:2.32.2.1-0ubuntu13
  Version table:
 *** 1:2.32.2.1-0ubuntu13 0
        500 http://archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status

and I am still getting the same errors from nautilus. Gnome panel does come up now, but seems to restart every second or so.

how to reproduce:
(re)move your .gnome2 (and gnome2_private) folder
create a symlink to an nonexistent file named .gnome2 (and .gnome2_private)
try to log in.

madbiologist (me-again) wrote :

Thanks Pedro and Jens. I don't seem to be able to set the bug status back to Triaged.

tags: added: natty
Changed in nautilus:
status: New → Incomplete
Changed in nautilus:
status: Incomplete → Expired
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in nautilus (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.