nautilus segfault with blank dvd or cd in a drive

Bug #297642 reported by p0ssum
2
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

I see a number of threads reporting this problem:

http://start.ubuntuforums.org/showthread.php?t=844990&page=2
http://ubuntuforums.org/showthread.php?t=820564&page=7

All on hardy, all saying the same thing. Here is a bug that was opened, but was reported as Invalid, yet there is no explanation:

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/245931

There is even a backtrace available in that bug report. There are known workarounds:

http://www.hightechsister.com/559/nautilus-segmentation-fault-with-blank-cd/
(sudo dbus-launch nautilus)

but this is NOT an acceptable solution. The problem is an obvious bug and needs to be addressed.

Here's the version info:

paul@blackhole:/etc/rc0.d$ lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04

This is supposed to be "Hardy", why is a bug like this being marked as Invalid. If there truely is a duplicate of this problem being reported, please let us know what that bug is so we can track it. I updated this very morning and the problem still occurs.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Changed in nautilus:
status: New → Invalid
Revision history for this message
p0ssum (pstroud) wrote :

I believe the invalid status on this problem is incorrect. The bug I was pointed to as a duplicate shows a problem where sudo nautilus runs the CPU to 100% until manually killed. While sudo and nautilus may be a common thread, the problem here is a segfault, which should NEVER happen, especially one so easy to reproduce. The difference between pushing the CPU to 100% and a segfault should not be ignored. I can almost guarantee, based on my experience, that fixing the CPU 100% bug is extremely unlikely to resolve this issue also. I find it troubling that this issue is truely being ignored.

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.