[00:30] jsalisbury: fail [00:32] andbug updated, afk for a while [09:18] 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] I've seen this using both the Xenial ISOs and by compiling the kernel using the patches in the mainline ppa [09:28] who_me, that would not be expected i don't think, mount decisions are almost exclusivly driven by userspace [09:29] who_me, where do they get mounted on? [09:29] the kernel would know about the volumes as it discovers them, but it has no idea where they are meant [09:29] to be mounted, so its not clear to me how it could be responsible [09:30] 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] alright, I'm on 4.4 now [09:34] apw, they get mounted in /media/my_user_name/random_directory_name [09:35] who_me, that is gvfs that decides to do that, which is a part of the login session [09:35] thats the thing which mounts usb sticks and the like [09:35] yes but this does not happen with anything earlier than 4.4 [09:35] though i have not noticed it doing that spectacularly more than it did before [09:36] so i guess we need to find out what type of volumes it is finding now it did not before [09:36] with the 4.3 series and earlier it mounts volumes when I click on them in the file manager [09:37] so, could you file a bug aginst the kernel "ubuntu-bug linux" [09:37] and record that info, with some clear examples of the volumes it is now mounting it did not before [09:37] and perhaps include the output of blkid for those in 4.3 and 4.4 [09:38] who_me, what sort of physical volumes are they ? [09:38] it is probabally something like the volumes are reporting themselves removable now [09:38] so gnome thing thinks they are sticks you rammed in, and mounts them without checking [09:38] ummm they are on internal SATA SSD and HDDs [09:41] apw, this is blkid shows: http://pastebin.com/bHTUwgpf [09:42] in Disks they do indeed appear as removable drives... [09:42] so weird [09:43] 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] returns "1" [09:44] for some reason the kernelthinks they're removable? [09:45] even my main drive shows up as removable [09:46] so sda, sdb, sdc, sdd, sde and sdf show up as removable [09:49] so yea, ubuntu bug respectfully invites me to report this upstream... oh well... will do [09:52] who_me, they may well be removable ... what are they connected to [09:53] to internal SATA connectors on the mainboard [09:53] who_me, which kernel version is this [09:53] 4.4.2 but also had this happen with 4.4.0 [09:53] might be that ahci with hotswap support [09:53] right, it may be "true" in a literal sense [09:54] on 4.4.0-2.16 my sata drive is not removable [09:55] at least it did not disable the read/write caches... as far as I can tell [09:56] 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] [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [09:57] smb, the UEFI on this mobo has such a setting, yes [09:58] going to see whether it's on or off and flip it to off if that's the case then [09:58] but I think gvfs should still not automount this stuff [09:58] who_me, so in theory if you say yes there the disk is potentially removable [09:58] anyway, brbr [10:07] right, that solved it for most of my drives [10:07] the one connected to the Marvell controlled port still shows up as removable [10:17] but it's still weird, why would it do this now. No previous kernel caused this in the past :/ [10:20] might be a "fix" even (to support now to read what the controller thinks it can handle) [10:23] 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] 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] who_me, did you file a bug in the end ? if so what was the $ [10:27] # [10:29] I did, kernel bug #112681 on the kernel bugzilla [10:29] bug 112681 in kdelibs (Ubuntu) "[apport] kdeinit crashed with SIGSEGV" [Undecided,Invalid] https://launchpad.net/bugs/112681 [10:29] https://bugzilla.kernel.org/show_bug.cgi?id=112681 [10:29] bugzilla.kernel.org bug 112681 in Other "kernel marks internal drives as being removable" [Normal,New] [11:13] udev rule took care of the drive connected to Marvell controller... [11:34] 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] apw: Are you there? We're getting back to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505948 once again [13:10] Launchpad bug 1505948 in linux (Ubuntu Wily) "Memory arena corruption with FUSE (was Memory allocation failure crashes kernel hard, presumably related to FUSE)" [High,Confirmed] [15:28] hallyn, can you verify LP: #1539349 for wily [15:28] Launchpad bug 1539349 in linux (Ubuntu Wily) "sleep from invalid context in aa_move_mount" [Undecided,Fix committed] https://launchpad.net/bugs/1539349 [16:12] bjf: ok [16:28] jsalisbury: ready for another kernel, though I expect it;ll be 5 or 6 hours before I can test it [16:28] lamont, good timing, I'm building it now. I'll post it to the bug when it's ready [16:30] 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] lamont, gotcha [20:58] kamal, this bug fix might be suitable for stable for all our kernels: https://bugs.launchpad.net/bugs/1547207 [20:58] Error: Could not gather data from Launchpad for bug #1547207 (https://launchpad.net/bugs/1547207). The error has been logged [20:59] bug #1547207 [21:02] rtg_, already applied to all of our stable kernels :-) [21:04] rtg_, ... and pending in all of the Ubuntu master-next branches [21:04] kamal, cool [21:06] kamal, I don't see it pending in precise master-next [21:44] rtg_, you're right -- I'll see if it applies [21:45] kamal, it does, I was just about to email out the patch [21:45] rtg_, in that case, I'll ack it [21:48] 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] kamal, I guess they'll be fix released soon enough [21:49] * kamal looks the other way ;-) [21:49] kamal, good move [21:50] kamal, what about utopic ? [21:50] rtg_, yeah, just looking at that [21:50] rtg_, its "Fix Committed" in trusty/lts-backport-utopic-next [21:50] good [22:19] 555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555 [22:19] 555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555 [22:19] 555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555 [22:19] 555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555 [22:19] 55555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555555 [22:30] kamal: did a cat jump on your laptop? [22:32] jsalisbury: fail, updating the bug [22:42] whoa [22:42] but now everyone knows my password! ;-)