Choosing write to disc causes Nautilus to restart

Bug #793342 reported by Vince Kimball
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: nautilus

Just upgraded to Ubuntu 11.04 amd64. If I right-click on an ISO image and choose "Write to Disc" half the time Nautilus restarts with no error or entry in /var/log/messages. The folder window I'm looking at closes and for several seconds I get a blank screen except for the gnome panel at the top and bottom.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu13
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Sun Jun 5 22:52:15 2011
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to natty on 2011-06-05 (0 days ago)

Revision history for this message
Vince Kimball (vince-vkimball) wrote :
Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

Hi,

Do you have a disk in the drive when you select that option? Also, have you been able to test this behavior in an i386 build?

Thanks,

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in nautilus (Ubuntu):
status: New → Incomplete
Revision history for this message
Vince Kimball (vince-vkimball) wrote :

Yes, there is a DVD in the drive; it shows up on the desktop before I select an iso and select "write to disc"

I don't have an i386 install to test.

Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

OK, thanks for the info - just need a bit more.

I suppose it's a blank one that's in the drive? I'm only saying that because I only have e.g. movie DVD's with me at the moment, so can't check with a blank disc.

Probably you need to wait for someone to come along with a blank DVD and using a 64-bit build to be sure. For now I'll set it to 'New' since I can't reproduce it myself, but don't doubt you are having a problem.

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in nautilus (Ubuntu):
status: Incomplete → New
Revision history for this message
Robert Roth (evfool) wrote :

I guess it's not related to amd64, as there's a duplicate for this bug, reported from an i386 user, see bug #781239.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Roth (evfool) wrote :

Set this as Confirmed because it does have a valid duplicate reported by another user, and I'm also removing the amd64 tag, as the other bug is reported with i386.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
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.