GNOME tries to mount non-existing floppy in Lucid

[Uwe Geuder]

Binary package hint: nautilus

Each time when starting a GNOME session, the system tries to mount /dev/fd0. This machine has no floppy disk drive (but obviously an FD controller)

Symptoms:

- "disk light" is permanently on for at least 20 minutes
- mount process is hanging there
- errors are written to /var/log/syslog all the time

Problem exists in Ubuntu Lucid, but it did not exist in Ubuntu Intrepid (I have not used Jaunty and Karmic on this machine)

Problem does not exist in Kubuntu Lucid on the same machine.

I'm not sure whether nautilus is the culprit. I picked it, because according to pstree nautilus calls mount.

Work-around: disable Floppy Disk support in BIOS

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Fri May 28 18:37:48 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: nautilus
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1284): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:1485): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

[Uwe Geuder (ubuntulp-ugeuder)]

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

[Uwe Geuder (ubuntulp-ugeuder)]

Here is how I decided to blame nautilus:

$ sudo lsof /dev/fd0
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
mount 1472 root 3u BLK 2,0 0t0 2108 /dev/fd0

pstree output is attached. It shows that nautilus has started mount (1472).

[Uwe Geuder (ubuntulp-ugeuder)]

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.

[Uwe Geuder (ubuntulp-ugeuder)]

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

and the corresponding /etc/fstab line is

/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

(That line was created by the Lucid installer. No upgrade history or manual editing. My Kubuntu installation on the same machine has exactly the same fstab entry, but it doesn't suffer from the problem)

[Sebastien Bacher (seb128)]

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.