nautilus crashed with SIGSEGV in g_str_hash() (SSH mounted folder)

Bug #227145 reported by Kevin_b_er
36
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

This may be slightly related to #185441, where uploading SSH files causes a crash, but I'm getting crashes while trying to open the mounted SSH folder, and I'm running a later version than when 185441 was fixed.

1) Ubuntu 8.04

2)
nautilus:
  Installed: 1:2.22.2-0ubuntu4
  Candidate: 1:2.22.2-0ubuntu4
  Version table:
 *** 1:2.22.2-0ubuntu4 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

3) See mounted folder contents

4) Nautilus closes, taking out all of its windows and the desktop file lists, restarts with a home folder open (Where home folder refers to ~)

More info can be gathered, if needed, and decent instructions can be given on what I need to do. (I'm an embedded software developer, but I don't mess with debugging or programming for linux)

This looks like someone's making an error in calling a string function, and memory faulting on an out of bounds read or write.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon May 5 20:33:58 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: fglrx
Package: nautilus 1:2.22.2-0ubuntu4
PackageArchitecture: i386
ProcCmdline: nautilus --sm-client-id 117f000101000121003733100000074210001 --screen 0
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_str_hash () from /usr/lib/libglib-2.0.so.0
 g_hash_table_lookup_extended ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_str_hash()
Uname: Linux 2.6.24-16-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev vboxusers video

Revision history for this message
Kevin_b_er (ktbvz2) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Kevin_b_er (ktbvz2) wrote :

I couldn't install libglib2.0-0-dbgsym, because, as synaptic affectionately puts it:
libglib2.0-0-dbgsym:
  Depends: libglib2.0-0 (=2.16.3-1ubuntu1) but 2.16.3-1 is to be installed.

I installed the Canonical-supported libglib2.0-0-dbg, instead.
I also installed the Canonical supported nautilus-dbg

This is a SSH server (without an interactive shell) designed for doing nothing but SFTP. I don't control the SSH I worry slightly because 1 level down from the root (and default) directory is a folder with over 20000 sub-directories each 5-6 (on average) characters long

Revision history for this message
Kevin_b_er (ktbvz2) wrote :

At this point, I'd like to point out that despite the libglib2.0-0-dbg package (I did a full restart after installing both the debugging symbol packages), there's no symbols for the last few actions before the segfault.

Revision history for this message
A. Walton (awalton) wrote :

Thanks for getting the slightly better stacktrace, it should be enough for us to work with on this one. We're crashing on a bad symlink state, which is related to a known upstream bug. I've forwarded the relevant information to this upstream. If you can still regularly reproduce this crash, can you install the symbols for GVFS and try it again, so that we may have a better idea of where the bad GFileInfos are coming from? Thanks in advance.

Changed in nautilus:
status: Incomplete → New
status: New → Confirmed
Changed in nautilus:
status: Unknown → Confirmed
Revision history for this message
Kevin_b_er (ktbvz2) wrote :

Alright. I do believe I've got plenty of symbols in this one. Took quite a bit to track down the correct symbols to get this.

Changed in nautilus:
status: Confirmed → Triaged
Revision history for this message
Zephyrcat (egyptianmua) wrote :

This problem is not specific to SSH mounted folders, it seems to apply to FTP (with password) folders as well.

I am using Ubuntu 9.04 and haven't had this problem until this week.

Changed in nautilus:
status: Confirmed → Incomplete
Changed in nautilus:
importance: Unknown → Medium
Changed in nautilus:
status: Incomplete → Confirmed
Revision history for this message
Barry Drake (b-drake) wrote :

Nautilus runs fine - except when it is launched from the Unity shell. I suspect that this is caused by the Compiz/Unity problem in Natty well reported elsewhere. Apport wouldn't let me report this except under Nautilus, so here I am. Today's snapshot of Natty has improved on yesterdays. Yesterday, the window that was launched by clicking the top left panel 'Ubuntu' icon gave a black window only. Today that same black window contains icons. The Nautilus ones all crash. The Firefox one doesn't.

Revision history for this message
Barry Drake (b-drake) wrote :

CoreDump.gz above is what apport sent from me. Have attached output from lshw.

Changed in nautilus:
importance: Medium → Critical
Changed in nautilus:
status: Confirmed → Incomplete
Changed in nautilus:
status: Incomplete → Expired
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.

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: Triaged → 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.