Binary package hint: nautilus
Binary package hint: nautilus
(Rewrite of later bug documented in steps of 121817, which I did so badly that I invalidated it and am starting over)
Releases I've reproduced this on: Feisty (laptop) and Gutsy(desktop)
Summary of problem: Popups occur in a confusing fashion
Hardware:
[ 19.063689] ide1: BM-DMA at 0xde08-0xde0f, BIOS settings: hdc:DMA, hdd:pio
[ 21.063527] hdc: COMBO 52X32X52X, ATAPI CD/DVD-ROM drive
[ 21.845804] hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 1536kB Cache, UDMA(33)
The only thing (I hope) pertinent here is it may be a slower drive than that used by other testers.
uname -a
Linux choochoo 2.6.22-7-386 #1 Mon Jun 25 16:30:18 GMT 2007 i686 GNU/Linux
Steps:
0. Start with no disk in the drive.
1. Download an image like the Feisty install image I'm using to write to the disk. I have mine on the desktop so I can access it with the mouse.
2. Mouse over the icon for this image, and pressing the right mouse button to get the dropdown menu, press the "Write to disc" option with the left mouse button.
3. Insert a disk into the drive and quickly hit the "Write" button on the popup window.
My results: You will notice that a popup window will result instructing you to insert a disk in the drive. Hit the <OK> button, and the same popup will occur again. Until the disk has revved up, this popup window will reproduce.
Expected results:
1. At best, the program should discern that the drive is revving up, and not prompt the user unless something is wrong.
2. At worst, if the drive or device driver doesn't have the ability to give better information, the popup window should not immediately come up, but should at least pause long enough to give the result of the users disk insertion time to process.
Now it could be that this is just results on my two machines on Feisty and Gutsy, but I don't think so. Apparently there have been problems reproducing this, but I find it completely consistent. I also recommend trying older slower drives that take a while to come up to speed after insertion of the CD. Please also feel welcome to make constructive questions here or to my email directly.
Please see that this is not a duplicate of bug 123149, but is rather a sister bug. It is NOT THE SAME BUG. These bugs may be best handled together, but they are separate bugs. Please do not mark either of these bugs as duplicate anymore.
Thank you.