** Changed in: anbox-cloud
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2081745
Title:
Anbox 1.23 Version Application failing
Status in A
The issue can be easily reproduce inside a LXD VM running Ubuntu 22.04,
e.g.
$ lxc init ubuntu:j vm0 -c limits.cpu=4 -c limits.memory=4GiB --vm
$ lxc config device override vm0 root size=80GiB
$ lxc start vm0
Switch to the generic kernel first:
$ lxc shell vm0
vm0$ apt-get update
vm0$ env DEBIA
This looks a lot like you have the no longer maintained anbox-modules
(https://github.com/anbox/anbox-modules) installed, at least according
to the dpkg output:
dkms autoinstall on 6.5.0-15-generic/x86_64 succeeded for anbox-ashmem
dkms autoinstall on 6.5.0-15-generic/x86_64 failed for anbox-binde
I gave this another spin today with 6.5.0-17-generic #17~22.04.1 and the
LRM modules of the 535 driver (6.5.0-17.17~22.04.1+1 of linux-modules-
nvidia-535-server-generic-hwe-22.04) on our Altra system with 2x L4 GPUs
and the same problem exists as with the DKMS modules:
[ 39.437849] watchdog: BU
Verified that with linux-aws-edge 6.5.0.1012.12~22.04.1 the DKMS
installation via
$ sudo apt install -y nvidia-driver-535-server
on an AWS g5g.xlarge goes through the driver comes up fine.
Trying the same with linux-generic-hwe-22.04-edge 6.5.0-17-generic
#17~22.04.1 on an Ampere Altra with 2x N
Trying the same with the linux-nvidia-hwe-22.04-edge kernel from
proposed linux-image-6.5.0-1011-nvidia wit the same NVIDIA driver
(535.154.05-0ubuntu0.22.04.1 of nvidia-utils-535-server) and loading
kernel driver and running nvidia-smi works fine without problems.
--
You received this bug notifi
Verified that the issue does not exist with 535.154.05-0ubuntu0.22.04.1
of nvidia-utils-535-server on 6.2.0-1017-aws or 6.2.0-1018-aws of linux-
aws.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchp
I can reproduce the the same with the latest 535.154.05-0ubuntu0.22.04.1
on jammy with the 6.5 HWE kernel on an arm64 machine. The same happens
with the -server driver 535.154.05-0ubuntu0.22.04.1.
Reproducing is pretty simple:
1. Boot plain Ubuntu 24.04 with either HWE already installed or manual
Anbox Cloud is affected by this too. We used shiftfs by default until
our 1.14 release in May 2022. According to the metrics we have there are
still a few users around with the 1.13 release which enables shiftfs on
ZFS.
--
You received this bug notification because you are a member of Kernel
Pack
Marking as "invalid" as it's not a bug in nvidia-graphics-drivers-510
but an external NVIDIA component.
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Public bug reported:
On a fresh arm64 system I failed to start LXD containers with NVIDIA
GPUs attached. The error message LXD / nvidia-container-cli fails with
is:
lxc t0 20220506112123.475 DEBUGconf - conf.c:run_buffer:310 - Script exec
/snap/lxd/current/lxc/hooks/nvidia produced output: +
** Description changed:
# Overview
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000 r-xp 00:51 14509
/var/snap/lxd/common/lxd/storage-pools/default/co
Public bug reported:
After leaving the system for a while and it turning the screen off the
kernel crashes in the NVIDIA driver with the following:
Apr 06 17:24:56 kore kernel: BUG: kernel NULL pointer dereference, address:
0070
Apr 06 17:24:56 kore kernel: #PF: supervisor read acces
** Description changed:
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000 r-xp 00:51 14509
/var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/
Attaching logs fails when `apport-collect 1968027` wants to authorized
with my LP with an "Not allowed error".
** Description changed:
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000 r
Public bug reported:
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000 r-xp 00:51 14509
/var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/ca
I can confirm that running the HWE kernel 5.11.0-27-generic
#29~20.04.1-Ubuntu from proposed on our Ubuntu 20.04 test system
resolves the problem. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
I've verified on my end that with the patch from
https://paste.ubuntu.com/p/TPsjfCpnD5/ the failing sendfile syscall on
top of shiftfs is gone.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
With the 5.11 HWE kernel landing for Ubuntu 20.04 we noticed that LXC
tools we're using in bionic containers as part of Anbox Cloud start to
fail when executed on the 5.11 kernel.
A simple reproducer looks like this:
1. Run Ubuntu 20.04 with HWE kernel (linux-generic-hwe-20.
** Tags added: anbox-cloud
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1925246
Title:
binderfs support is not enabled
Status in linux-azure package in Ubuntu:
New
Bug descri
** Tags added: anbox-cloud
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1937987
Title:
Latest GCP kernel has Android related config options disabled
Status in linux-gcp package in
Public bug reported:
In LP:1849493 we enabled support for CONFIG_ANDROID_* on the gcp kernels
to support Anbox Cloud. However checking on the latest rolling kernel on
GCP (5.8.0-1038-gcp #40~20.04.1-Ubuntu ) gives
morphis@anbox0:~$ cat /boot/config-5.8.0-1038-gcp | grep CONFIG_AND
# CONFIG_ANDRO
No, 4.15 isn't needed. We only need 5.4+
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1928686
Title:
Oracle kernel has Android related config options disabled
Status in linux-o
Public bug reported:
For Anbox Cloud we require certain CONFIG_ANDROID_* options to be
enabled in the kernel. We do this already for most of our cloud kernels
(GCE, AWS, Azure) and the generic kernel and should do so for the oracle
(and possible others too). We have customers looking at running An
Yes, it's fixed with 460.73.01-0ubuntu0.20.04.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1922599
Title:
fails to create a new context
Status in nvidia
Executing a cudaDeviceSynchronize() instead of using cuCtxCreate gives
"all CUDA-capable devices are busy or unavailable" which seems to hint
to something incorrectly setup in the system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvi
I can reproduce this here on the focal 5.4 kernel (5.4.0-72-generic)
with 460.32.03 (deb 460.32.03-0ubuntu0.20.04.2) too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460-server in
Ubuntu.
https://bugs.launchpad.
Public bug reported:
Hey,
in https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1914568 we
got binder support enabled but the configuration is completely different
from what we have in our other cloud and generic kernels:
ubuntu@machine-1:~$ cat /boot/config-5.4.0-1046-azure | grep BINDE
Public bug reported:
For the purpose of Anbox Cloud we package both the binder and ashmem
kernel modules in the Ubuntu kernel. The generic kernel ships it and all
clouds specific kernels should too. However the azure kernel doesn't
include the prebuilt binder_linux.ko and ashmem_linux.ko modules:
Public bug reported:
For quite a while the Ubuntu kernel now ships the Ashmem and Binder
drivers as part of linux-modules-extra-*. They were available on
previous linux-aws kernels but seem to have dropped with the 5.3.0 based
edge kernel.
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
Just checked on my bionic GCE instance today that the binder driver is
now there:
ubuntu@juju-1dfb8c-4:~$ find /lib | grep binder
/lib/modules/5.0.0-1025-gcp/kernel/drivers/android/binder_linux.ko
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which i
Public bug reported:
The rolling GCP kernel for bionic is missing CONFIG_ANDROID_BINDER_IPC=m
which is enabled in the standard Ubuntu kernel since 19.04 and available
through the HWE kernels in Bionic.
As we require CONFIG_ANDROID_BINDER_IPC=m for a not released product in
our kernels it would be
@Jonas: Seems to be a problem with BlueZ (either kernel or userland).
--
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/1519718
Title:
Screen doesn't change after connecting a BT mouse and
** Changed in: bluez (Ubuntu)
Status: New => In Progress
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Scott Sweeny (ssweeny)
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, w
@kgunn: it looks like you're enabling the pairing mode on your BT
keyboard again (long press of the connect button) in your video. If that
is the case the keyboard will erase its part of the pairing where the
phone will still keep its part. If the phone now tries to reconnect the
connection simply
** Tags removed: bluez snap
** Tags added: bluez-snappy
--
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/1560094
Title:
Starting bluez service is denied
Status in bluez package in Ubuntu:
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: Simon Fels (morphis) => Ken VanDine (ken-vandine)
--
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/1539158
Title:
Unable
@Stunts: Do the following on your HOST system:
$ sudo add-apt-repository ppa:phablet-team/ubuntu/tools
$ sudo apt-get install phablet-tools-citrain
Now connect the phone over adb (make sure developer mode is enabled):
Still from the HOST system:
$ citrain device-upgrade
PLEASE KEEP IN MIND:
*** This bug is a duplicate of bug 1491340 ***
https://bugs.launchpad.net/bugs/1491340
This isn't a problem with bluez or the bluetooth stack. There is work in
progress to select the right keyboard layout as this isn't working no
matter through which technology the keyboard is connected with.
** Changed in: urfkill (Ubuntu)
Status: Confirmed => Invalid
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.laun
MP with a possible fix is linked now.
@Stunts: I've put the MP into silo 67 (https://requests.ci-
train.ubuntu.com/#/ticket/1102). Can you install that one on your device
and try if that fixes the problem for you?
--
You received this bug notification because you are a member of Kernel
Packages,
s (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Branch linked: lp:~morphis/ubuntu-system-settings/fix-lp1539158
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Pac
Analyzed the latest log files and came to following conclusion about
that is going on here:
The key point here is that the car initiates the pairing with the phone
which then leads to a timing problem in ubuntu-system-settings. But step
by step:
Feb 23 09:43:45 ubuntu-phablet bluetoothd[880]:
sr
Looked through Pat's log file and it actually shows that the HFP profile
is never correctly connected due to
Mar 1 13:26:27 ubuntu-phablet bluetoothd[739]: src/profile.c:ext_connect()
hfp_ag connected to 00:18:16:20:00:FE
Mar 1 13:26:27 ubuntu-phablet bluetoothd[739]: src/service.c:change_state
*** This bug is a duplicate of bug 1552128 ***
https://bugs.launchpad.net/bugs/1552128
** Description changed:
Expected Result:
All audio from the phone should play in the bluetooth headset when it is
connected.
Actual Result:
The music and other audio plays on the bluetooth heads
** Tags added: bluetooth-ota10
--
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/1519681
Title:
Some media keys on keyboards do not work as expected
Status in The Avila project:
Confirme
** Tags added: bluetooth-ota10
--
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/1494225
Title:
Call audio is not routed to headset with HFP
Status in Canonical System Image:
Confirmed
S
Possible duplicate of https://bugs.launchpad.net/canonical-devices-
system-image/+bug/1552128
** Tags added: bluetooth-ota10
--
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/1536493
Title:
** Tags added: bluetooth-ota10
--
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/1500242
Title:
Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
with BQ Aquaris 4.5
** Tags added: bluetooth-ota10
--
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/1543179
Title:
Audio does not get routed to BT headset/speaker
Status in Canonical System Image:
Confirme
** Tags added: bluetooth-ota10
--
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/1494230
Title:
Audio is not routed to A2DP sink when connected
Status in Canonical System Image:
In Progr
** Tags added: bluetooth-ota10
--
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/1479438
Title:
IN CAR: Battery levels not shared via bluetooth for in car experience
Status in Canonical Sy
** Tags removed: bluetooth
** Tags added: bluetooth-ota10bluetooth
** Tags removed: bluetooth-ota10bluetooth
** Tags added: bluetooth bluetooth-ota10
** Tags added: bluez-touch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubu
** Tags added: bluetooth-ota10
--
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/1546310
Title:
In CAR bluetooth not working
Status in Canonical System Image:
Fix Committed
Status in blu
** Tags added: bluetooth-ota10
--
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/1552128
Title:
Music audio is not transferred to headset after it is connected
Status in Canonical System I
** Tags added: bluetooth-ota10
--
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/1488170
Title:
Bluetooth initiated after quitting airplane mode
Status in Canonical System Image:
Confirm
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
** Tags added: bluez-touch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https:
@Matthias: Yes lets take the disconnection as separate bug so that we
can close this one. The bug you've tested now landed in rc-proposed and
will be part of OTA10.
That the connection times out smells really like a different problem so
another bug is the right way. Can you attach the log files th
Marked as invalid for bluez until we prove there is still a problem.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
--
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/155005
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@Tony: With your last comment: BlueZ 5.37 doesn't fix that problem too?
Or do you still see this with bluez 5.37?
--
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/1527354
Title:
[Jawbone E
@Tony: Can you reproduce this once again and record the HCI packets by
running
$ sudo btmon -w test.cap
Then attach test.cap here.
--
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/1551858
Just as a additional note: The actual pairing method is selected in the
kernel. See
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/smp.c#n859
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubun
And there we go:
Mar 7 15:08:44 ubuntu-phablet bluetoothd[890]: src/device.c:new_auth()
Requesting agent authentication for 04:69:F8:C2:A0:09
Mar 7 15:08:44 ubuntu-phablet bluetoothd[890]: src/agent.c:agent_ref()
0xb8c78950: ref=3
Mar 7 15:08:44 ubuntu-phablet bluetoothd[890]:
src/agent.c:ag
Because what pairing method is selected is chosen further down the stack
so settings only reacts on what bluez tells it should do. I suspect the
keyboard uses pairing capability KeyboardOnly which then should lead to
passkey entry where the initiator displays and the responder inputs the
PIN (we us
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Critical
--
You r
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Status: New => Invalid
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Critical
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
** Also affects
@Christopher: You say you connected two BT devices at the same time and
expect audio being played on both?
Can you also please follow https://wiki.ubuntu.com/DebuggingBluetooth
and provide some log files here?
** Description changed:
STEPS:
1. Flash the latest daily rc-proposed image to a ph
@Pat: One important thing: Don't use hciconfig up anymore. Even if
its still there and works to some degree that will only initialize the
controller partly as its using an old kernel API. Use bluetoothctl only
to power on/off bluetooth:
$ bluetoothctl
[bluetooth]# power on
Changing power on succe
Possible related to https://bugs.launchpad.net/ubuntu/+source/indicator-
sound/+bug/1538703
--
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/1398193
Title:
The bluetooth headset can not co
@Jamie: Can you follow https://wiki.ubuntu.com/DebuggingBluetooth to
give us some more details about what is happening on your end?
--
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/1545174
T
For a mouse and a keyboard this for sure intended. Both act as input
device like the power key and therefore can activate the device. For
example when I have the tablet or the phone working as a converged
device I as a user want the device to go to sleep when I wake up but be
back when I active eit
@Pat: Did you saved any logs from that attempt?
--
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/1531925
Title:
Can't connect Logitech Living Room Keyboard [LE]
Status in Canonical System
The bluetooth HID driver itself is the same on all our devices. If only
a could be in the generic HID driver stack inside the kernel
(drivers/hid/)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net
** Changed in: bluez (Ubuntu)
Assignee: Simon Fels (morphis) => (unassigned)
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bl
@Matthias: Yes let take #1500242 separately to not confuse things.
Sounds good that this seems to be an improvement for you. However lets
monitor this for a bit as it could be a thing which only happens after
some (however in your logs I never saw it detecting the sink.fake.sco
sink from pulse whi
This isn't a bluez thing. Either pulseaudio or telepathy-ofono (which is
currently fully controlling when we switch between the different audio
outputs).
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status:
Ok, pushed a "possible" fix to silo 47.
@Matthias: Can you try if the problem goes away after installing silo
47?
--
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/1546310
Title:
In CAR bl
@Pat: With which device you see this still broken? For my two headsets
this working fine now. As I were the initial reporter I would like to
close this as we have other bugs with the same symptoms and this is then
just a duplicate.
--
You received this bug notification because you are a member of
Can you add required debug information by following
https://wiki.ubuntu.com/DebuggingBluetooth ?
--
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/1552128
Title:
Music audio is not transfer
I got this down to pulseaudio not being able to find the sink.fake.sco
sink element we have in place to do the suspend/resume handling of the
SCO stream. Trying some small tweaks to see if they bring the same
effect here. If they do I will push those changes to silo 47 to see if
that helps to fix t
e
essential for the audio setup to work properly. Will do some more
investigation to see if I find a reason for this.
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Chan
There was a bug in pulseaudio which was brought in while we added
support for Android 5.x. This is only valid for current rc-proposed. A
fix is available in silo 47 (see https://requests.ci-
train.ubuntu.com/#/ticket/1059 for details). If you want to help
verifying the fix feel free to install the
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags added: bluez-touch
--
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/1551858
Title:
[bluetooth] Connecti
Ok, there seems to be another problem I didn't respected yet. Powering a
controller with hciconfig will bring it into a state where not all
subsystems are initialized required for LE support. We still have a udev
rule in our bluez package included which will try to power a bluetooth
controller via
I went again through the logs and came across the following:
[ 1044.196326] Bluetooth: SMP security requested but not available
which is then followed by a lot messages like:
Jan 20 08:53:28 samsung930X3G bluetoothd[3988]: Report Map read failed:
Attribute requires authentication before read/
** Changed in: bluez (Ubuntu)
Status: New => In Progress
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you
** Changed in: bluez (Ubuntu)
Status: Incomplete => Confirmed
--
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/1500242
Title:
Bluetooth devices (Jabra BT250, Audi A3 car kit) can no
I looked a bit through the logs files this morning and will enumerate my
findings per device.
1. Audio A3
The paring attempt is clearly visible in the log files. It first tries
to use the automatic-pin-guesser which fails after one attempt and then
switches back to ask the connected agent (aka se
Can someone who experience the problem please follow
https://wiki.ubuntu.com/DebuggingBluetooth and attach the requested logs
file for further investigation here?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bug
Generally I don't think this is because of a lacking key event. If the
keyboard goes away also its corresponding input device node will
disappear. If that happens the upper input stack should take care about
that. Adding mir as component here too to get their view on this while
doing some more inve
Got this reproduced after following the steps to turn off the keyboard
while holding a key.
--
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/1550050
Title:
repeating phantom key when bt di
It hardly depends on what the keyboard supports. Check via bluetoothctl
which profiles it supports. If its only HID then its not AVRCP but
otherwise it could and then we have to fix this differently.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
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/1525320
Title:
Aquaris E4.5 can't connect
@Nicola: Last release is ota9 which fixes this problem for you?
** Changed in: bluez (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
** Changed in: linux-mako (Ubuntu Vivid)
Status: New => Fix Released
** Changed in: linux-flo (Ubuntu Vivid)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-mako in Ubuntu.
https:/
Please note that trusty still comes with bluez5 which doesn't support BT
LE HOG devices like the mouse referenced here. I've tested with John
that the mouse is working fine on >= wily.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
I ruled out that this is a bug with bluez. Actually system-settings does
show the mouse as its falling into the device-type "Network" which we
don't display in settings. We should actually stop limiting the number
of devices we're displaying and allow them all.
** Also affects: ubuntu-system-setti
** Tags added: bluez5
--
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/1531925
Title:
bluetoothd crash with BTLE keyboard
Status in bluez package in Ubuntu:
New
Bug description:
Tryi
** Changed in: bluez (Ubuntu)
Status: In Progress => Invalid
** Changed in: bluez (Ubuntu)
Status: Invalid => Won't Fix
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
** Changed in: canonical-devices-system-image
Status: Fix Committ
1 - 100 of 308 matches
Mail list logo
