Comment 5 for bug 470037

Ah. I understand the source of all those lines. They're from my /etc/fstab file, which contains:

(File starts on the next line.)
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda7 during installation
UUID=ee08e8b3-dffd-45c0-bd04-b74dd72a705b / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda5 during installation
UUID=445891f8-3505-4c88-815c-fb4340f7791a /boot ext2 defaults 0 2
# swap was on /dev/sda6 during installation
UUID=a95988d3-98aa-4a18-b21a-93f606808fb2 none swap sw 0 0

# mount Windows 7 partition
#/dev/sda3 /media/Wingardium ntfs rw,nosuid,nodev,allow_other,default_permissions 0 2
(File ends on the previous line.)

Besides the first suggestion given "// New\ Volume", I don't think the others have anything to do with this bug. Tab-completion on "umount " first produces "umount /" and then produces the following list (which I believe is good, correct, and intended behavior):

/
/boot
/dev
/dev/disk/by-uuid/ee08e8b3-dffd-45c0-bd04-b74dd72a705b
/dev/pts
/dev/sda3
/dev/sda5
/dev/sdb1
/dev/shm
/home/ek/.gvfs
/media/Alucard
/media/Wingardium
/proc
/proc/fs/vmblock/mountPoint
/proc/sys/fs/binfmt_misc
/sys
/sys/fs/fuse/connections
/sys/kernel/debug
/sys/kernel/security
/var/lock
/var/run

The original issue, and its apparent selectivity with respect to which command is used with sudo, remains.