nautilus crashed with SIGSEGV in g_str_hash(), mounting ISO

Bug #259343 reported by plun
132
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
Critical
nautilus (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs
Nominated for Intrepid by Tim Fuchs
Nominated for Jaunty by Raúl Pedroche

Bug Description

Binary package hint: nautilus

Nautilus crashes when trying to view a mounted Iso (The archive mounter)

Intrepid running with latest updates.

Invalid bug without Apport report
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/259304

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.23.6.1-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: nautilus --no-desktop --browser
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.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.26-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse-access pulse-rt sambashare vboxusers video

Tags: apport-crash
Revision history for this message
plun (plun) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_str_hash () from /usr/lib/libglib-2.0.so.0
g_hash_table_lookup_extended ()
modify_link_hash_table (file=0xa1f7260,
update_info_internal (file=0xa1f7260, info=0xb6319460,
nautilus_file_new_from_info (directory=0x9fcc2e0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in nautilus:
importance: Undecided → Medium
Revision history for this message
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=548555

Changed in nautilus:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in nautilus:
status: Unknown → New
Changed in nautilus:
status: New → Unknown
Changed in nautilus:
status: Unknown → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

there was no iso mounting in hardy the tagging is wrong, unsetting the tag

Revision history for this message
plun (plun) wrote :

Well... this was discussed during Hardys development within another bug.
The archieve mounter was there but hidden. Fedora 9 enabled it and it works great when
I asked a couple of users.

What do you mean with "unsetting the tag" ?

Revision history for this message
nullack (nullack) wrote :

Hi Plun. When I originally tagged it regression-potential I thought this problem to be a regression over Hardy. Our maestro developer clarified the functionality was not implemented in Hardy, so therefore the tagging needed to be removed. Like errors in code, testers sometimes make errors too :)

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

the crash has been fixed upstream now

Changed in nautilus:
status: Triaged → Fix Committed
Revision history for this message
Jens-Christian (beauman) wrote :

Hi!

I still have the bug, even so I made a complete update of ibex yesterday.

The iso gets mounted under /home/user/.gvfs/filename.iso
If I click the hd-symbol on the desktop or in nautilus, nautilus will crash.

My version of gvfs/-backends/-bin/-fuse is 1.0.2-0ubuntu1.

Revision history for this message
plun (plun) wrote :

Yup the bug is still there....

But only CD isos... I tested with Foresights DVD iso and it works and also
with a mini-iso without any trouble.

Nautilus-scripts still works.

Changed in nautilus:
status: Confirmed → Fix Released
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

This was fixed upstream in version 2.25.1 and Jaunty is already shipping version 2.25.2. Marking as "fix released". Thanks.

Changed in nautilus:
status: Fix Committed → Fix Released
Revision history for this message
Tim Fuchs (tim-fuchs) wrote :

I don't think it is Ubuntu policy now to close bugs because they are fixed in the unstable version but not in the current stable release. I'm reopening this bug.

Also, I filed a new one with a full backtrace provied by apport:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/316747

Changed in nautilus:
status: Fix Released → Confirmed
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Tim - Martin was correct to set this as Fix Released, because it is fixed in Jaunty. If you think the fix should be ported to Intrepid, please use the "Nominate for release" button, which will add a bug watch for Intrepid (if approved).

Changed in nautilus:
status: Confirmed → Fix Released
Revision history for this message
Tim Fuchs (tim-fuchs) wrote :

Chris, thanks for clearing that up, my fault.

What do you think about my other bug report:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/316747

Technically it is a duplicate but if I had chosen not to open a new bug but just to subscribe to this one Launchpad wouldn't have attached my backtrace etc. (the files apport sent)

I fear if I mark it as a duplicate nobody will ever see that files.

Changed in nautilus:
importance: Unknown → Critical
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.