[Kernel-packages] [Bug 1713017] Re: Enable MIDI support

2021-01-12 Thread wvengen
As far as I can see, it is still disabled by default [in kernel bluez](https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/configure.ac#n243) nor [in launchpad](https://git.launchpad.net/bluez/tree/configure.ac#n239), neither do I find in being enabled explicitely in a package (but could not so

[Kernel-packages] [Bug 1713017] Re: Enable MIDI support

2021-01-10 Thread wvengen
@henning that sounds great! In which version did you see this? I expect the build would also need the libasound2-dev dependency, which should be in the control file. I remember that indeed an alsa sequencer device was created on connection; I only tested (when submitting this bug) midi controllers

[Kernel-packages] [Bug 1713017] Re: Enable MIDI support

2017-08-28 Thread wvengen
For those seeking a workaround, see instructions here: https://gist.github.com/wvengen/7ebd29da38c08540832fb228c4628171#bluez-546 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1713017

[Kernel-packages] [Bug 1713017] Re: Enable MIDI support

2017-08-28 Thread wvengen
Thanks, I agree that 18.04 would be good. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1713017 Title: Enable MIDI support Status in bluez package in Ubuntu: Triaged Bug description

[Kernel-packages] [Bug 1713017] [NEW] Enable MIDI support

2017-08-25 Thread wvengen
Public bug reported: Now that bluez has landed with 5.46-0ubuntu2, it would be nice to enable Bluetooth MIDI support. This did not seem to be enabled by default in the build from https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE MIDI devices, gatttool could talk to them, but n

[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

2016-10-14 Thread wvengen
I'm seeing this issue after desktop upgrade to yakkety with kernel 4.8.0-22-generic but not with kernel 4.4.16-040416-generic. NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [ps:3908] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS MBP111.88Z.0138.B07.1402121134 02/12/2

[Kernel-packages] [Bug 1284085] Re: unable to boot after install on 2013 macbook air

2014-10-17 Thread wvengen
My problem of comment #27 was solved by picking a 14.10 daily-live amd64 image (without mac suffix - 14.10 beta-2 happened to only have images with the mac suffix). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://b

[Kernel-packages] [Bug 1284085] Re: unable to boot after install on 2013 macbook air

2014-10-16 Thread wvengen
On my MacBookPro11,1 I installed 14.10 beta-2 and have the same problem. Booting from usb works, booting from harddisk not (after installation), booting from harddisk while passing nr_cpus=1 on kernel cmdline works (but only works with 1 core, obviously). -- You received this bug notification bec

[Kernel-packages] [Bug 544469] Re: iSight webcam on Macbook Pro does not work

2013-09-30 Thread wvengen
submitted #1233260 -- 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/544469 Title: iSight webcam on Macbook Pro does not work Status in “linux” package in Ubuntu: Expired Bug descriptio

[Kernel-packages] [Bug 1226119] [NEW] "SMART is not enabled" in disks, according to smartctl it is

2013-09-16 Thread wvengen
Public bug reported: When opening gnome-disks and selecting my internal hard disk, it tells me that "SMART is not enabled". After enabling it with smartctl, I could see its values using the command-line. Still gnome-disks keeps telling me that "SMART is not enabled", even after several reboots. $