** Changed in: network-manager (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579915
Title:
network-manager 1.2 uses more power
To manage
The feature itself is there now. What will follow is support for new
devices, performance improvements and additional features like audio
support.
That FlymeOS 5 will be available for the MX 4 doesn't mean anything for
the version running Ubuntu which will be still based on an BSP with
Android
Everything landed in the overlay ppa on last Friday.
** Changed in: aethercast
Status: In Progress => Fix Released
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Released
** Changed in: ubuntu-system-settings (Ubuntu)
Status: In Progress => Fix Released
Wireless Display supported landed in the overlay ppa last Friday.
** Changed in: aethercast (Ubuntu)
Status: In Progress => Fix Released
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1575184 ***
https://bugs.launchpad.net/bugs/1575184
** This bug has been marked a duplicate of bug 1575184
ubuntu-push is flooding dbus with NameOwnerChanged signals
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: aethercast (Ubuntu)
Status: New => In Progress
** Changed in: aethercast (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513020
Title:
** Changed in: mtp (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472789
Title:
libmtp error copying big files
To manage notifications about
Assignee: (unassigned) => Simon Fels (morphis)
** Changed in: wpa (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
connman does a really good job here in implementing WiSPr
(https://en.wikipedia.org/wiki/WISPr) support to deal with captive
portals.
If you want to check if you're really not on an captive portral you want
to implement something like this to perform a check if you're "online"
or not:
1. Setup a
@Jonas: Seems to be a problem with BlueZ (either kernel or userland).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519718
Title:
Screen doesn't change after connecting a BT mouse and no cursor
Public bug reported:
Testing on turbo without having the urfkill.hybris.wlan property set to
'1':
Steps:
1. Turn off WiFi
2. Reboot
Expected:
WiFi still turned off
Actual:
WiFi showed as turned on the UI. The actual rfkill is soft-blocked and urfkill
reports it as not blocked.
See
@Evan: I suspect the problem is similar. However Tony is currently
working on a big overhaul of the NetworkManager stack to bring us back
in par with the upcoming 1.2 upstream release which will have some
fundamental changes of how the whole scan management is implemented.
There is a good chance
** 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 Ubuntu
Bugs,
@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
** Changed in: android (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553657
Title:
Clicking on camera & microphone settings crashes app on mako
Landing request for a fix is at https://requests.ci-
train.ubuntu.com/#/ticket/1145
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553657
Title:
Clicking on camera & microphone settings crashes app
@Olivier: No, the android package doesn't have any effect on frieza. But
we've just merged an upgrade for platform-api/libhybris for frieza,
which should fix the same problem. Alfonso will release a new image on
rc-proposed with this change included later today.
--
You received this bug
@David: Not sure, but you can take a look at
$ pactl list sources
That lists all properties pulse reports for the source devices. However
from the Android side (that is where we're reading the list of available
devices from) we only get 'primary' as the name of the source and not
further
** Tags removed: bluez snap
** Tags added: bluez-snappy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560094
Title:
Starting bluez service is denied
To manage notifications about this bug go to:
There are two things:
1. The incorrect named "Droid source primary" element which is something
we could easily fix from pulseaudio by just adding a better description
for the source.
2. The null input should be never listed as its useless for the user and
just used internally to allow proper
Public bug reported:
When opening the "Camera & microphone" settings in the webbrowser-app I
get the following list of Microphone devices I can select one from:
- Default
- Droid source primary
- Null input
The last two ones are incorrect and should never reach the user. The
user doesn't know
Public bug reported:
When opening the "Camera & microphone" settings in the webbrowser-app I
get the following list of Microphone devices I can select one from:
- Default
- Droid source primary
- Null input
The last two ones are incorrect and should never reach the user. The
user doesn't know
Updated the descriptions with the steps I used to reproduce this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551811
Title:
Opening the camera for the first time leads to reboot
To manage
Just reproduce the crash again. Still caused by the same kernel panic as
mentioned in comment 7.
** Description changed:
Test case.
- Flash the phone.
- Open Telegram app.
- Fill the account details.
- Add a contact (if needed).
- Select a contact to send a message.
- Tap on the
@Cemil: Also that the syslog's don't show the actual crash I've seen is
likely because this is a kernel panic and syslog might not get the
kernel output before the device is rebooted. Use something like
$ cat /proc/last_kmsg
on the next boot to get the kernel side output only which is stored in
@Kevin: I've seen it only on arale so far and also Dave says that is the
only device he saw this so far on. So suspecting an issue on the device
side is valid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: android (Ubuntu)
Importance: Undecided
Status: New
** Changed in: android (Ubuntu)
Status: New => In Progress
** Changed in: android (Ubuntu)
Importance: Undecided => Critical
** Changed in: android (Ubuntu)
Assignee: (unassigned) => Simon Fels
@David: Remember that for HFP you need a mobile telephony connection
which is currently only supported through ofono which we don't ship on
the desktop. What you more want here is HSP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to p
libhybris/android related problem. Nothing with camera-app
** Changed in: webbrowser-app (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553657
Title:
We're clearly missing symbols in libcamera_compat_layer.so in the device
tarball on the Android side but I don't have a clue yet why. A local
build of the package we have in the overlay ppa show me that the symbols
ends up in the .so. Doing a no-change rebuild in silo 38
** Also affects: aethercast (Ubuntu)
Importance: Undecided
Status: New
** Changed in: aethercast (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
@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:
** Branch linked: lp:~morphis/indicator-bluetooth/fix-lp1530807
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530807
Title:
[FHD] Bluetooth cannot be activated on several devices
To manage
*** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs,
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 Ubu
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]:
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]:
*** 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536493
Title:
Call/SMS
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519681
Title:
Some media keys on keyboards do not work as expected
To manage notifications about this bug go to:
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543179
Title:
Audio does not get routed to BT headset/speaker
To manage notifications about this bug go to:
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546310
Title:
In CAR bluetooth not working
To manage notifications about this bug go to:
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488170
Title:
Bluetooth initiated after quitting airplane mode
To manage notifications about this bug go to:
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494230
Title:
Audio is not routed to A2DP sink when connected
To manage notifications about this bug go to:
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494225
Title:
Call audio is not routed to headset with HFP
To manage notifications about this bug go to:
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479438
Title:
IN CAR: Battery levels not shared via bluetooth for in car experience
To manage notifications about this
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
To manage
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521671
Title:
Bluetooth is turned off on every reboot
To manage notifications about this bug go to:
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552128
Title:
Music audio is not transferred to headset after it is connected
To manage notifications about this bug
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
@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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550050
Title:
** 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 Ubuntu
Bugs, 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527354
Title:
[Jawbone ERA] HFP
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551858
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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]:
** 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
** 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
New release of the android package including this fix is now in progress
at https://requests.ci-train.ubuntu.com/#/ticket/1081
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506887
Title:
New release for the android package is in progress now at
https://requests.ci-train.ubuntu.com/#/ticket/1081
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517597
Title:
[regression] mouse pointer
@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
** Changed in: android (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517597
Title:
[regression] mouse pointer support on emulator is broken
To
@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
Possible related to https://bugs.launchpad.net/ubuntu/+source/indicator-
sound/+bug/1538703
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398193
Title:
The bluetooth headset can not control the
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545174
Title:
can
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
@Pat: Did you saved any logs from that attempt?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531925
Title:
Can't connect Logitech Living Room Keyboard [LE]
To manage notifications about this bug
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
@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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546310
Title:
In CAR bluetooth not
@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
@Gregory: Sure. I was just trying to get this right from the technical
point of view. Its a matter of just being able to set the alias from
the settings app nothing else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you add required debug information by following
https://wiki.ubuntu.com/DebuggingBluetooth ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552128
Title:
Music audio is not transferred to
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
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)
** Changed in: pulseau
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551858
Title:
[bluetooth] Connecting to Apple
Just for the correct wording: The user can't change the device name.
What he can only do is to set an alias which is then passed next to the
actual device name. The alias is also known as the "Bluetooth device
friendly name". See
https://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/adapter-
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
This is not necessarily a settings app failure. Can you follow
https://wiki.ubuntu.com/DebuggingBluetooth and attach the necessary log
files here so that we know what is going on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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 becau
** Changed in: android (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540120
Title:
[camera] fix manual focus point and metering
To manage
** Changed in: bluez (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500242
Title:
Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550050
Title:
repeating phantom key when bt disconnects
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 Ubuntu
Bugs, which is
Its a problem in ofono where still creates a modem instance (exposed as
/ril_0) without any interfaces registered when the connection to the
ril-daemon fails. IMHO ofono should not create the modem instance as
long as it can't connect to rild. We agreed on keeping ofono running
even on devices
BlueZ will react either on the "Powered" property of its
org.bluez.Adapter1 interface being switch (false/true) or the bluetooth
rfkill being changed. If none of both happen the Bluetooth power status
will not change and the device will be kept discoverable if the
"Discoverable" property was set
Public bug reported:
location-service currently seems to require ofono to be around as its
otherwise doesn't give us any location updates. Was found on a device
without a cellular modem (no rild running) so ofono was never started at
boot time. This seem to irritate location-service in what ever
101 - 200 of 469 matches
Mail list logo
