** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49268305/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/49268306/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/49268307/ProcStatus.txt
** Attachment
apport has not added the syslog, so I do it manually.
These are the error messages:
May 28 18:47:36 geuder-t40-u kernel: [ 1177.350646] end_request: I/O error, dev
fd0, sector 0
May 28 18:47:36 geuder-t40-u kernel: [ 1177.350661] Buffer I/O error on device
fd0, logical block 0
** Attachment
Here is how I decided to blame nautilus:
$ sudo lsof /dev/fd0
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
mount 1472 root3u BLK2,0 0t0 2108 /dev/fd0
pstree output is attached. It shows that nautilus has started mount
(1472).
** Attachment added: pstree output
Or should mount actually fail more quickly?
Hmm, which mount program is running actually? Now it has just finished
(about 30 minutes) after boot, need to restart my session to find out.
--
GNOME tries to mount non-existing floppy in Lucid
https://bugs.launchpad.net/bugs/586873
You received this
Correction: Starting a new GNOME session will not trigger the problem.
It happens only once until the machine is rebooted.
Further info:
The mount program running is really /bin/mount, checked from
/proc/nnn/maps (So source package would be util-linux)
The command line is
mount /media/floppy0
*** This bug is a duplicate of bug 539515 ***
https://bugs.launchpad.net/bugs/539515
Thanks for the bug report. This particular bug has already been
reported, but feel free to report any other bugs you find.
** Changed in: nautilus (Ubuntu)
Importance: Undecided = Low
** Changed in:
