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
No, 4.15 isn't needed. We only need 5.4+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928686
Title:
Oracle kernel has Android related config options disabled
To manage notifications about this bu
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922599
Title:
fails to create
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, it's fixed with 460.73.01-0ubuntu0.20.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922599
Title:
fails to create a new context
To manage notifications about this bug go to:
https://bugs
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
** Tags added: anbox-cloud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937987
Title:
Latest GCP kernel has Android related config options disabled
To manage notifications about this bug go to:
h
** Tags added: anbox-cloud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925246
Title:
binderfs support is not enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
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 Ubuntu
Bugs, which is su
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
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:
I've just applied the package from
https://launchpad.net/ubuntu/+source/haproxy/1.8.8-1ubuntu0.11 to our
deployment and the crash is fixed. I will keep it running for a while to
see if it remains that way.
Thanks for all the work!
--
You received this bug notification because you are a member of
Public bug reported:
Version 1.8.8-1ubuntu0.10 of haproxy in Ubuntu 18.04 (bionic) crashes
with
Thread 2.1 "haproxy" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf77b1010 (LWP 17174)]
__pool_get_first (pool=0xaac6ddd0, pool=0xaa
Thanks Christian! I was planing to bisect today as I still have the
environment up and can easily reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884149
Title:
haproxy crashes on in __pool
Just ran through the bisect:
git bisect start '--term-new=fixed' '--term-old=unfixed'
# fixed: [ebf033b47d58aa04ae9913038c9369dab8740411] [RELEASE] Released version
1.8.19
git bisect fixed ebf033b47d58aa04ae9913038c9369dab8740411
# unfixed: [cd117685f0cff4f2f5577ef6a21eaae96ebd9f28] [RELEASE] Rel
Thanks Christian! Will give the PPA a go tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884149
Title:
haproxy crashes on in __pool_get_first if unique-id-header is used
To manage notifica
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/
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
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
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.
https://b
@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:
[bl
@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 featu
** 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 Ubu
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:
r
@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
** 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.
https://bugs.launch
** 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 go
** 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 not
** 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/1521671
Title:
Bluetooth is turned off on every reboot
To manage notifications about this bug go to:
https://bugs.launch
** 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:
https://bugs.l
** 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:
https://bug
** 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:
https:
** 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:
https://bug
** 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.
https://
** 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:
https://bugs.launchpad.net/can
** 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:
https://bu
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 Al
*** 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
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
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
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 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, whi
** 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.
https://bugs.launchpad.net/bug
*** 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.
** 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 notific
@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:
** 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
** Changed in: wpa (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/1528173
Title:
org.freedesktop.DBus.Properties.GetAll fails always for
fi.w1.wp
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.l
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 /etc/systemd/network/
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 '/etc
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
https://
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 IFLA_AF_
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: systemd
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1630586/+attachment/4755050/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630586
Title:
P
Public bug reported:
Build an image today with
$ sudo ubuntu-image --channel edge -o pi3.img pi3.model
$ cat pi3.model
type: model
authority-id: 4BKZlf4WMNBKgQfij0rftmp5BzDdVhlf
series: 16
brand-id: 4BKZlf4WMNBKgQfij0rftmp5BzDdVhlf
model: pi3
architecture: armhf
gadget: pi3
kernel: pi2-kernel
** Attachment added: "IMG_20161005_153003.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1630586/+attachment/4755051/+files/IMG_20161005_153003.jpg
** Description changed:
Build an image today with
- $ sudo ubuntu-image --channel edge -o pi3.img pi3.model
- $ cat pi3.
@Paolo: Will give this image a try tomorrow morning. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630586
Title:
Pi3 kernel crash and is unreliable
To manage notifications about this bug g
Just for interest I did such a simple interfaces some time ago for
playing:
dbus-name:
https://github.com/morphis/snappy/commit/0489b6f23b190d817975247d460990f67e0c4d5c
Allows you to bind a by attribute specified dbus name on the system bus.
This was meant for snap internal communication but coul
I've pushed the TPM snap now into a common repository on
https://code.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/tpm
If you're back from holiday lets quickly sync up on your work here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: libhybris (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662866
Title:
libhybris blocks migration to libglvnd
To man
I see this as well on various arm based devices. Any more ideas what
could be the reason or a possible fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638537
Title:
snapd eats 100% CPU for about
See https://paste.ubuntu.com/24318397/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679774
Title:
snapd-glib doesn't read full json response from snapd
To manage notifications about this bug go t
As an additional note, this happens with snapd 2.23.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679774
Title:
snapd-glib doesn't read full json response from snapd
To manage notifications abou
Public bug reported:
The code submitted to gnome-software upstream still doesn't use snapd-
glib exclusively but has parts of the snapd REST API which are handled
by its own. The HTTP REST API logic should be only implemented once and
that in snapd-glib. See https://git.gnome.org/browse/gnome-
sof
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
** Tags added: cross-distro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679774
Title:
snapd-glib doesn't read full json res
Public bug reported:
Searching for specific snaps (e.g. rocket, wifi-ap or network-manager)
through the UI is often canceled internally.
Logs print:
11:16:42:0596 Gs failed to get search apps: Operation was cancelled
11:16:42:0596 Gs not handling error cancelled for action search: Operation wa
** Description changed:
The code submitted to gnome-software upstream still doesn't use snapd-
glib exclusively but has parts of the snapd REST API which are handled
by its own. The HTTP REST API logic should be only implemented once and
that in snapd-glib. See https://git.gnome.org/browse
Public bug reported:
The snap plugin implemented in gnome-software upstream does not have any
self tests yet which were requested by upstream to get the plugin into a
better shape.
Tested with latest gnome-software from https://git.gnome.org/browse
/gnome-software/ on Ubuntu 17.04 against snapd 2
** Summary changed:
- Snap plug for gnome-software misses self tests
+ Snap plugin for gnome-software misses self tests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680030
Title:
Snap plugin for
Btw. you guys should see if the more modern btattach utility does the
job instead of hciattach too. See
http://manpages.ubuntu.com/manpages/xenial/man1/btattach.1.html for a
few details. Sooner or later btattach will replace hciattach as the way
to attach serial lines to the kernel bluetooth stack.
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Also affects: snapd (Fedora)
Importance: Undecided
Status: New
** Changed in: snapd (Fedora)
Assignee: (unassigned) => S
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
** Changed in: snappy
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to fin
** 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 notifications
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
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 noti
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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
@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 n
Public bug reported:
When I try to install the TPM snap from the edge channel I get the
following output:
$ snap install tpm --channel=edge
error: cannot perform the following tasks:
- Download snap "tpm" from channel "edge" (snap not found)
The mistake here is that I forgot --devmode as the sn
@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: [puls
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: "pa-sn
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: N
Saw this some times too. Not sure yet which error this triggers but
likely we're not handling one error code in u-s-s yet.
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) => Ken VanDine (ken-vandine)
--
You received this bug notification because you are a member of Ubu
** Changed in: trust-store (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/1596951
Title:
[CTA] CameraService in trust prompt should be translated
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: ubuntu-touch/rc-proposed/bq-
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602950
Title:
Unity8 crashes when switching back
@John: Yes, fix was released with the last urfkilld landing:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-
phone-overlay/+sourcepub/6411875/+listing-archive-extra
** Changed in: urfkill (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: canonical-devices-syste
** 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
Bugs, which is subs
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 a
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
(https://launchpad.net/~ci-
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:
Cl
** 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 pair with
@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.
ht
** 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
@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.
https://bugs.launchpad.net/
@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
m
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 notifi
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 cli
1 - 100 of 471 matches
Mail list logo
