[Kernel-packages] [Bug 1209124] Re: Support for Intel 7260 bluetooth [8087:07dc]
@Chronos: Our issue is distinct from this bug. I intend to file a bug upstream (kernel.org) once I finish working out how the ASUS platform driver handles Bluetooth and I have a reasonable idea to whom the bug report should be directed. I'll post a link back here when that's done. In the meantime, I've discovered the least intrusive (but still dirty) workaround yet: 1. In Unity's Bluetooth indicator, flip the "Bluetooth" toggle switch to "ON". Because of our bug, this causes the "hci0" Bluetooth device to be unregistered from the kernel's rfkill subsystem (see "rfkill list all"). 2. In a terminal do "sudo rfkill block N", where N is the ID number of the remaining "asus-bluetooth" WMI device as given by "rfkill list all". (In my case it's "sudo rfkill block 2".) This causes the "hci0" device to be registered with rfkill again, and it will be soft-unblocked. In the Bluetooth indicator menu you should now see both "Bluetooth" and "Visible" toggled to "ON". 3. Connect Bluetooth devices normally, but be careful; *don't* manually flip the "Bluetooth" or "Visible" switches, whether in the Bluetooth indicator or in "System Settings -> Bluetooth", because that causes the "hci0" adapter to disappear again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1209124 Title: Support for Intel 7260 bluetooth [8087:07dc] Status in linux package in Ubuntu: Fix Released Bug description: Some 7260 modules are found in the newly released systems. It needs external firmware to work. Support for this module can be found in 3.10 and need to be backported to 3.5 and 3.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371310] Re: docker.io doesn't work with apparmor 3.0 RC1 kernel
Yep, Docker works again with kernel 3.16.0-22.29. Thanks for fixing this so promptly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with apparmor 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: Invalid Status in “docker.io” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. FYI, 3.16.0-17.23 is in utopic-proposed now and on its way to utopic, which will affect docker.io in Ubuntu. Workaround until this bug is fixed is to boot into 3.16.0-16.22 or earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1209124] Re: Support for Intel 7260 bluetooth [8087:07dc]
@Anton: The fix that was released is the addition of Intel 7260 Bluetooth firmware for device ID 8087:07dc, which has been shipping in Ubuntu since at least Saucy. It doesn't mean that Bluetooth is fixed. Bluez (and/or the kernel's Bluetooth stack) still doesn't handle the setup properly because, thanks to bad design by ASUS, the Bluetooth hardware is poorly integrated on the UX301 models. See: http://askubuntu.com/questions/396021/what-is-causing-my-intel-7260 -bluetooth-device-to-disconnect-when-i-unblock-it-w The workaround given in the first post of the above link enables Bluetooth, but at the cost of disabling USB 3.0. Another workaround, which was a pain to set up and only gave me occasional success, is to uninstall the Bluez stack and replace it with the Blueman stack, but I really don't recommend that (I've switched back to Bluez). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1209124 Title: Support for Intel 7260 bluetooth [8087:07dc] Status in “linux” package in Ubuntu: Fix Released Bug description: Some 7260 modules are found in the newly released systems. It needs external firmware to work. Support for this module can be found in 3.10 and need to be backported to 3.5 and 3.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371310] Re: docker.io doesn't work with apparmor 3.0 RC1 kernel
@jdstrand: Sorry, I missed that bit. I rebooted into the old Trusty kernel and Docker works fine (although compiz/mesa don't like the old kernel, so I guess I'll try 3.16.0-16.22). Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with apparmor 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: Invalid Status in “docker.io” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Triaged Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. FYI, 3.16.0-17.23 is in utopic-proposed now and on its way to utopic, which will affect docker.io in Ubuntu. Workaround until this bug is fixed is to boot into 3.16.0-16.22 or earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371310] Re: docker.io doesn't work with apparmor 3.0 RC1 kernel
I just upgraded to Utopic final beta and am experiencing this bug. What is a workaround to get my docker containers working? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with apparmor 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: Invalid Status in “docker.io” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Triaged Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. FYI, 3.16.0-17.23 is in utopic-proposed now and on its way to utopic, which will affect docker.io in Ubuntu. Workaround until this bug is fixed is to boot into 3.16.0-16.22 or earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
