Hey Mauricio,
> Could you please confirm if from the Anbox perspective, for a
> workaround, is it OK to temporatily unmask/start the unit
> (due to restart), then upgrade the package, and stop/mask again?
It's not that simple. We have prebuilt images we ship to users which run
through an
** Description changed:
The Anbox Cloud LXD images are based of the standard Ubuntu cloud images
- for LXD but have the systemd-udev.service unit masked (`systemctl mask
- systemd-udev.service`) as we do not need udev.
+ for LXD but have the systemd-udevd.service unit masked (`systemctl mask
+
Public bug reported:
The Anbox Cloud LXD images are based of the standard Ubuntu cloud images
for LXD but have the systemd-udev.service unit masked (`systemctl mask
systemd-udev.service`) as we do not need udev.
With the latest security patch on Ubuntu 22.04 upgrading the udev
package fails:
** Changed in: wpa (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1528173
Title:
org.freedesktop.DBus.Properties.GetAll
** Changed in: libhybris (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1662866
Title:
libhybris blo
Sorry, for seeing this one a bit late.
First of all the relevant problem is
( 15.152| 0.000) E: [pulseaudio] volume.c: Assertion
'pa_channels_valid(channels)' failed at pulse/volume.c:74, function
pa_cvolume_set(). Aborting.
Which basically means there is a volume level being set for an
That patch works but there are now more problems with the DHCP stack
inside networkd. See https://paste.ubuntu.com/23178198/ Needs more
investigation. To unblock our work we're now using a static ifupdown
configuration but need to fix this bug here for real networkd support.
** Changed in:
Yes, the kernel has IPv6 support enabled so socket_ipv6_is_supported()
returns true and with that it tries to setup the IPv6 part of the
interface.
The two problems which I've found so far are:
- an empty IFLA_AF_SPEC seems to cause the kernel to return EINVAL
- having IPv6 enabled and
The actual error message comes from
https://github.com/systemd/systemd/blob/95adafc428b5b4be0ddd4d43a7b96658390388bc/src/network
/networkd-link.c#L1441 and due to the nature of this the problem only
occurs when the network interface isn't already up.
If lines 1391 to 1420 are commented on
** Attachment added: "systemd-networkd-on-3.4.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+attachment/4740099/+files/systemd-networkd-on-3.4.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Knowing that a 3.4 based kernel is unsupported we have to get it working
for a specific customer.
Systemd itself boots up nicely already but networkd fails to configure a
network device with the following configuration file in
/etc/systemd/network
$ cat
Output of
sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
ubuntu@nirvana:~$ sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
sudo: unable to resolve host nirvana: Connection refused
Failed to connect to bus, trying again in 5s: No such file or directory
timestamp of
** Changed in: libhybris (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1318360
Title:
Poor microphone quality (mako)
** Changed in: libhybris (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1318360
Title:
Poor microphone quality (mako)
Status
** Changed in: libhybris (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1318360
Title:
Poor microph
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed => Invalid
** Also affects: libhybris (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
@K1773R: It does not have to be in the milestone list to land. The
package is already part of the overlay ppa and in rc-proposed so it will
be automatically land with OTA 13.
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: pulseaudio
This landed with 0.1.0+git20151016+6d424c9-0ubuntu18 in the overlay ppa.
Can't say if that went out with OTA 12 or will come with OTA 13.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
@Danial: You can easily do that with the attached crash file. So what
also would a ubuntu-bug provide?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1602950
Title:
Unity8
Public bug reported:
Testing new aethercast changes (https://requests.ci-
train.ubuntu.com/#/ticket/1620) and found unity8 is crashing when it
switches after a timeout automatically to the lock screen.
This is on
current build number: 142
device name: frieza
channel:
This is nothing related to aethercast. Must be something wrong in
unity8.
** Changed in: aethercast
Status: New => Invalid
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status:
Updated the patch. We now add snappy-policy always to default.pa. I
couldn't figure out what I have to change to make the ifelse statement
work properly to add the snappy policy module only conditionally to
default.pa
Also fixed the compiler warnings and other small things.
** Patch added:
@Jamie: Works fine here for me. Using a simple snap
name: pulseaudio-clients
version: 8.0-1
summary: Clients for PulseAudio
description: |
Contains PulseAudio client utilities
apps:
pactl:
command: usr/bin/pactl
plugs: [pulseaudio]
paplay:
command: usr/bin/paplay
plugs:
@Jamie: Attached is a debdiff to update the pulse pacakge with snappy
support.
** Patch added: "pulseaudio-snappy-deny-recording.diff"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+attachment/4695115/+files/pulseaudio-snappy-deny-recording.diff
--
You received this bug
@Luke: How did you test the change before landing it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583057
Title:
Deny audio recording for all snap applications
Public bug reported:
Until we have a proper trust-store implementation with snappy and on the
desktop/ubuntu core we want pulseaudio to simply deny any audio
recording request coming from an app shipped as part of a snap.
The implementation adds a module-snappy-policy module to pulseaudio
which
** Package changed: aethercast (Ubuntu) => aethercast
** Changed in: aethercast
Assignee: (unassigned) => Simon Fels (morphis)
** Changed in: aethercast
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Checked this on krillin with
current build number: 329
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-10 03:25:03
version version: 329
version ubuntu: 20160510
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9
Device doesn't go to sleep
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1579915
Title:
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1579915
Title:
network-manager 1.2
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
Touch seeded
** 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
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Changed in: mtp (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mtp in Ubuntu.
https://bugs.launchpad.net/bugs/1472789
Title:
libmtp error copying big files
Status in
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
Touch seeded packages, which is sub
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
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1519718
Title:
Screen doesn't change after connecting a
@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
Touch
@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
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1553657
Title:
Clicking on camera &
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
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1553657
Title:
Clicking on camera &
@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
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1560094
Title:
Starting bluez service is denied
Status in bluez
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
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
Updated the descriptions with the steps I used to reproduce this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1551811
Title:
Opening the camera for the first time leads to
@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
Touch seeded packages, which is subscribed to mir in Ubuntu.
@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
** 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
Touch seeded packages, which is
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
** 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
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Ti
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
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
** 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
Touch seeded packages, which is subscribed to
@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
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1530807
Title:
[FHD] Bluetooth cannot be
*** 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
Touch seeded packages, which is subscribed to bluez in 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
Touch
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 Ubun
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
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
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
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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
** 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
Touch seeded packages, which is subscribed
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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
** Tags added: bluetooth-ota10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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
** 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
Touch seeded packages, which is subscribed to bluez in
@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
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** 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
Touch seeded packages, which is
@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
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1527354
@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
Touch seeded packages, which is subscribed to bluez in Ubuntu.
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
Touch seeded packages, which is subscribed to
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]:
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
** 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 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
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597
Title:
@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
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1517597
Title:
[regression] mouse pointer support on
@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
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1398193
Title:
The bluetooth
@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
Touch seeded packages, which is subscribed to bluez in Ubuntu.
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
Touch seeded 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
1 - 100 of 363 matches
Mail list logo
