[00:30] <lamont> jsalisbury: fail
[00:32] <lamont> andbug updated, afk for a while
[09:18] <who_me> hello. is there a known issue with kernel 4.4 that it automounts volumes without them being mentioned in fstab? The system also shows ntfs volumes as mounted but they are not
[09:19] <who_me> I've seen this using both the Xenial ISOs and by compiling the kernel using the patches in the mainline ppa
[09:28] <apw> who_me, that would not be expected i don't think, mount decisions are almost exclusivly driven by userspace
[09:29] <apw> who_me, where do they get mounted on?
[09:29] <apw> the kernel would know about the volumes as it discovers them, but it has no idea where they are meant
[09:29] <apw> to be mounted, so its not clear to me how it could be responsible
[09:30] <who_me> ah heck, I never checked where the mount points were. will be right to report on that. brb. reboot. will also get a dmesg to pastebin it.
[09:33] <who_me> alright, I'm on 4.4 now
[09:34] <who_me> apw, they get mounted in /media/my_user_name/random_directory_name
[09:35] <apw> who_me, that is gvfs that decides to do that, which is a part of the login session
[09:35] <apw> thats the thing which mounts usb sticks and the like
[09:35] <who_me> yes but this does not happen with anything earlier than 4.4
[09:35] <apw> though i have not noticed it doing that spectacularly more than it did before
[09:36] <apw> so i guess we need to find out what type of volumes it is finding now it did not before
[09:36] <who_me> with the 4.3 series and earlier it mounts volumes when I click on them in the file manager
[09:37] <apw> so, could you file a bug aginst the kernel "ubuntu-bug linux" 
[09:37] <apw> and record that info, with some clear examples of the volumes it is now mounting it did not before
[09:37] <apw> and perhaps include the output of blkid for those in 4.3 and 4.4
[09:38] <apw> who_me, what sort of physical volumes are they ?
[09:38] <apw> it is probabally something like the volumes are reporting themselves removable now
[09:38] <apw> so gnome thing thinks they are sticks you rammed in, and mounts them without checking
[09:38] <who_me> ummm they are on internal SATA SSD and HDDs
[09:41] <who_me> apw, this is blkid shows: http://pastebin.com/bHTUwgpf
[09:42] <who_me> in Disks they do indeed appear as removable drives...
[09:42] <who_me> so weird
[09:43] <apw> try this but sub in one of the drives that got mounted that you didn't expect: cat /sys/class/block/sda/removable
[09:43] <who_me> returns "1"
[09:44] <who_me> for some reason the kernelthinks they're removable?
[09:45] <who_me> even my main drive shows up as removable
[09:46] <who_me> so sda, sdb, sdc, sdd, sde and sdf show up as removable
[09:49] <who_me> so yea, ubuntu bug respectfully invites me to report this upstream... oh well... will do
[09:52] <apw> who_me, they may well be removable ... what are they connected to
[09:53] <who_me> to internal SATA connectors on the mainboard
[09:53] <apw> who_me, which kernel version is this
[09:53] <who_me> 4.4.2 but also had this happen with 4.4.0
[09:53] <smb> might be that ahci with hotswap support
[09:53] <apw> right, it may be "true" in a literal sense
[09:54] <apw> on 4.4.0-2.16 my sata drive is not removable
[09:55] <who_me> at least it did not disable the read/write caches... as far as I can tell
[09:56] <smb> apw, well don't nail me on this but at least on some boxes I think one could twiddle something in BIOS/UEFI to say a port is hotswap enabled or not
[09:56] <who_me> [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[09:57] <who_me> smb, the UEFI on this mobo has such a setting, yes
[09:58] <who_me> going to see whether it's on or off and flip it to off if that's the case then
[09:58] <who_me> but I think gvfs should still not automount this stuff
[09:58] <smb> who_me, so in theory if you say yes there the disk is potentially removable 
[09:58] <who_me> anyway, brbr
[10:07] <who_me> right, that solved it for most of my drives
[10:07] <who_me> the one connected to the Marvell controlled port still shows up as removable
[10:17] <who_me> but it's still weird, why would it do this now. No previous kernel caused this in the past :/
[10:20] <smb> might be a "fix" even (to support now to read what the controller thinks it can handle)
[10:23] <who_me> the problem is that I can only enable or disable the Marvell controller and set its mode like AHCI, IDE or RAID. And I also would not turn off the hotswap on that because I have an eSATA disk drive which I use on and off to store things long term
[10:27] <apw> who_me, it sounds like it needs some thought, 1) to know why the kernel now is saying they are removable, and 2) to think about if this has a knock on effect for gvfs
[10:27] <apw> who_me, did you file a bug in the end ?  if so what was the $
[10:27] <apw> #
[10:29] <who_me> I did, kernel bug #112681 on the kernel bugzilla
[10:29] <who_me> https://bugzilla.kernel.org/show_bug.cgi?id=112681
[11:13] <who_me> udev rule took care of the drive connected to Marvell controller...
[11:34] <zkanda> Hello, anyone here can help me debug my sound card issue? I hear static noise for Ubuntu while this is not present in windows.
[13:10] <Madkiss> apw: Are you there? We're getting back to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505948 once again
[15:28] <bjf> hallyn, can you verify LP: #1539349 for wily
[16:12] <hallyn> bjf: ok
[16:28] <lamont> jsalisbury: ready for another kernel, though I expect it;ll be 5 or 6 hours before I can test it
[16:28] <jsalisbury> lamont, good timing, I'm building it now.  I'll post it to the bug when it's ready
[16:30] <lamont> jsalisbury: the lxc where I do 99% of my testing for the actual core-work is on the machine that I have to reboot each time to test this, so it's frequently blocked by EBUSY_PRIMARY_WORKSURFACE
[16:30] <jsalisbury> lamont, gotcha
[20:58] <rtg_> kamal, this bug fix might be suitable for stable for all our kernels: https://bugs.launchpad.net/bugs/1547207
[20:59] <rtg_> bug #1547207
[21:02] <kamal> rtg_, already applied to all of our stable kernels :-)
[21:04] <kamal> rtg_, ... and pending in all of the Ubuntu master-next branches
[21:04] <rtg_> kamal, cool
[21:06] <rtg_> kamal, I don't see it pending in precise master-next
[21:44] <kamal> rtg_, you're right -- I'll see if it applies
[21:45] <rtg_> kamal, it does, I was just about to email out the patch
[21:45] <kamal> rtg_, in that case, I'll ack it
[21:48] <kamal> rtg_, you marked the bug "Fix Released" for T, V, W, and X, but its actually only "Fix Committed" for all of those (except X? i dunno)
[21:49] <rtg_> kamal, I guess they'll be fix released soon enough
[21:49]  * kamal looks the other way ;-)
[21:49] <rtg_> kamal, good move
[21:50] <rtg_> kamal, what about utopic ?
[21:50] <kamal> rtg_, yeah, just looking at that
[21:50] <kamal> rtg_, its "Fix Committed" in trusty/lts-backport-utopic-next
[21:50] <rtg_> good
[22:19] <kamal> 555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555
[22:19] <kamal> 555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555
[22:19] <kamal> 555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555
[22:19] <kamal> 555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555
[22:19] <kamal> 55555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555
[22:30] <arges> kamal: did a cat jump on your laptop?
[22:32] <lamont> jsalisbury: fail, updating the bug
[22:42] <kamal> whoa
[22:42] <kamal> but now everyone knows my password!  ;-)