13-10 mounts all drives specified in /etc/fstab even with noauto specified

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1244232/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

This bug has been reassigned to the mountall package, but mountall definitely does not mount any filesystems that have been marked 'noauto'. This must be something kubuntu-specific; reassigning to kubuntu-meta.

Are they mounted before you log in?

Sorry I use auto login -btw how can I test for this?
i see this in the DMESG
[ 38.870678] EXT3-fs (sda3): using internal journal
[ 38.870682] EXT3-fs (sda3): mounted filesystem with ordered data mode
[ 38.873920] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[ 39.015726] EXT4-fs (dm-0): warning: mounting unchecked fs, running e2fsck is recommended
[ 39.019788] EXT4-fs (dm-0): mounted filesystem without journal. Opts: errors=remount-ro
[ 39.022825] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: errors=remount-ro
These are all the file systems marked "noauto"
Where this is sometime befor (the booted system sda1 and the sway sda5)
[ 3.277574] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 3.277579] EXT4-fs (sda1): write access will be enabled during recovery
[ 5.043649] EXT4-fs (sda1): recovery complete
[ 5.050895] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 10.006622] Adding 8376316k swap on /dev/sda5. Priority:-1 extents:1 across:8376316k FS
and later in the log (before the first above) is:
[ 11.889834] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 12.181231] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[ 12.242284] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[ 12.280840] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[ 12.348348] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: errors=remount-ro
This is the booted filesystem sda1, home sda6, storage sad7 and an lvm fs when the virtual machines disks are are
On the spash screen where the little picture of the disk followed by the other three icons as the boot takes place the time between the disk icon and the next now (booting 13-10) takes some 32-36 seconds where under 13-04 takes only a few seconds (it is still available if any data from that is needed).

Here is blkid and fstab to be more complete as I see from the dmsg that the third mount phase , the first section above, shows the opts without the noauto:
eric@eric-laptop:/$ sudo blkid
[sudo] password for eric:
/dev/sda1: LABEL="kubuntu" UUID="443d2dd9-b39b-4073-b929-0606aaf54397" TYPE="ext4"
/dev/sda2: LABEL="kubunt2" UUID="c007c863-6bc8-4bfb-bad7-3b6a7da5aa3c" TYPE="ext4"
/dev/sda3: LABEL="boot" UUID="d1b07952-aa4f-4648-bbd3-504e2e3d801a" TYPE="ext3"
/dev/sda5: UUID="32b23243-f6f2-4382-b08c-81afeef3cd8c" TYPE="swap"
/dev/sda6: LABEL="home" UUID="706e23bd-41c8-4a72-81ec-6375f4f78f98" TYPE="ext4"
/dev/sda7: LABEL="store" UUID="edd4b524-70cf-4d2a-8a6a-7515c8300944" TYPE="ext4"
/dev/sda8: UUID="8RdAv1-ZZmV-ppX9-uq14-JKP0-B6Y4-EjLN8c" TYPE="LVM2_member"
/dev/sda9: UUID="2D6aaj-S3iK-Mmhv-NerT-mR6N-N8dF-TgvcNK" TYPE="LVM2_member"
/dev/sda10: LABEL="server" UUID="ed027e6a-dc8c-43fa-aea4-bb17c097c2a2" TYPE="ext4"
/dev/mapper/lvmvg1-tail: LABEL="tail" UUID="14991fa8-9d50-42c0-836c-2c3af00e321a" TYPE="ext2"
/dev/mapper/lvmvg1-rescuecd: LABEL="rescuecd" UUID="3812954d-632b-4e92-94a4-1d7726cc52c7" TYPE="ext4"
/dev/mapper/lvmvg1-VMMStorage: LABEL="VMMStorage" UUID="5ad829e6-3c5b-4c2b-a5b4-4c3b449386e6" TYPE="ext4"
eric@eric-laptop:/$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' 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>
# / was on /dev/sda1 during installation
UUID=443d2dd9-b39b-4073-b929-0606aaf54397 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=32b23243-f6f2-4382-b08c-81afeef3cd8c none swap sw 0 0
#/dev/sda2 /kubunt2
UUID=c007c863-6bc8-4bfb-bad7-3b6a7da5aa3c /kubunt2 ext4 errors=remount-ro 0 1
#/dev/sda3 /boot
UUID=d1b07952-aa4f-4648-bbd3-504e2e3d801a /boot ext3 noauto,errors=remount-ro 0 1
#/dev/sda6 /home
UUID=706e23bd-41c8-4a72-81ec-6375f4f78f98 /home ext4 errors=remount-ro 0 1
#/dev/sda7 /store
UUID=edd4b524-70cf-4d2a-8a6a-7515c8300944 /store ext4 errors=remount-ro 0 1
#/dev/mapper/lvmvg1-tail /tail
UUID=14991fa8-9d50-42c0-836c-2c3af00e321a /tail ext4 noauto,errors=remount-ro 0 1
#/dev/mapper/lvmvg1-VMMStorage /VMMStorgae
UUID=5ad829e6-3c5b-4c2b-a5b4-4c3b449386e6 /VMMStorage ext4 errors=remount-ro 0 1
#/dev/mapper/server-rescucd /rescuecd
UUID=3812954d-632b-4e92-94a4-1d7726cc52c7 /rescuecd ext4 noauto,errors=remount-ro 0 1
#/dev/sda10 /server
UUID=ed027e6a-dc8c-43fa-aea4-bb17c097c2a2 /server ext4 noauto,errors=remount-ro 0 1
#

It seems that all the unmounted devices or what are marked "noauto" in /etc/fstab are being considered "Removable Devices" and listed in the connected part of the Removable Media system settings panel (Kubuntu) and are being mounted as per the "Enable Automatic mounting of removable devices" ("enabl...) selection. both partitions and LVM Logical Volumes are mounted.
When the "enabl.... Selection is disabled the file systems are not mounted (and the system does not hang on the disk icon during boot /auto login for the ~30 seconds).
Further testing comments:
When I plug in my usb drive it then is not auto mounted and must be mounted manually properly when "enabll... is deselected. When the "enabl.. is selected the usb drive is automatically mounted properly. Note: Even Though "Automount at login" and "Automount on attach" are deselected in the removable media panel they are mounted.

Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org/enter_bug.cgi?product=solid&format=guided, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Additionally please do the following and mention your findings in the report:
1. run `solid-hardware list`
2. find all /org/kde/fstab/... entries
3. run solid-hardware details /org/kde/fstab/... (... will be a more concrete id per partition).
4. if the output of step 3 suggests it was not an incorrectly mounted partition discard it otherwise make sure to attach/copy the information to the bug report