[Bug 1968175] Re: Allow runtime configuration of pkcs11 modules through config file

[Ondrej Kubik]

Attached examples with changes to address this bug:

https://git.launchpad.net/~ondrak/ubuntu/+source/opensc/commit/?h=ubuntu/focal=5866e8c8397b896f002e784ecc3d03005943e00a
https://git.launchpad.net/~ondrak/ubuntu/+source/libp11/commit/?h=ubuntu/focal=6df6a659416fcc1c3ffc46346e7edb38eb10b3d4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968175

Title:
  Allow runtime configuration of pkcs11 modules through config file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libp11/+bug/1968175/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968175] Re: Allow runtime configuration of pkcs11 modules through config file

[Ondrej Kubik]

** Also affects: libp11 (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/1968175

Title:
  Allow runtime configuration of pkcs11 modules through config file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libp11/+bug/1968175/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968175] [NEW] Allow runtime configuration of pkcs11 modules through config file

[Ondrej Kubik]

Public bug reported:

To be able to switch modules at runtime via configuration file change the 
default module from opensc-pkcs11 to p11-proxy module, which by default loads 
opensc-pkcs11 module unless configured by administrator to use something else.
This also allows configuration where multiple modules can be used together 
through the p11-proxy module.

This aligns Ubuntu closer with other distributions, and allows using the
same builds of opensc in embedded configurations on Ubuntu Core with
specialized modules

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: opensc 0.20.0-3
ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174
Uname: Linux 5.4.0-107-generic aarch64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp prl_fs_freeze 
prl_fs prl_tg
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: arm64
Date: Thu Apr  7 14:50:08 2022
InstallationDate: Installed on 2021-11-08 (150 days ago)
InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release arm64 
(20210824)
SourcePackage: opensc
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: opensc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug arm64 focal uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968175

Title:
  Allow runtime configuration of pkcs11 modules through config file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/1968175/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1954564] Re: "linux-modules-extra" module missing in pc-kernel snap for 20/track

[Ondrej Kubik]

OK this would mean that kernel modules in the linux-modules-extra packages are 
not signed.
kernel enforces kernel module signature check if SB is enabled.
But our modules should be signed.
@Renat, can you confirm exact versions of all the stage packages?
As those need to be aligned for signing keys to match.
Cheers
Ondra

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954564

Title:
  "linux-modules-extra" module missing in pc-kernel snap for 20/track

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954564/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776725] Re: snapdragon: LEDs on dragonboard 410c does not work correctly

[Ondrej Kubik]

** Summary changed:

- snapdragon: wcn36xx connection error
+ snapdragon: LEDs on dragonboard 410c does not work correctly

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776725

Title:
  snapdragon: LEDs on dragonboard 410c does not work correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1776725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776714] Re: raspi2: Pi3B plus is not supported

[Ondrej Kubik]

** Summary changed:

- raspi2: snapcraft scriptlet syntax outdated
+ raspi2: Pi3B plus is not supported

** Summary changed:

- raspi2: Pi3B plus is not supported
+ raspi2: Pi3 B plus is not supported

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776714

Title:
  raspi2: Pi3 B plus is not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1776714/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776723] Re: snapdragon: cross snap build broken

[Ondrej Kubik]

** Summary changed:

- snapdragon: wcn36xx connection error
+ snapdragon: cross snap build broken

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776723

Title:
  snapdragon: cross snap build broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1776723/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776725] [NEW] snapdragon: wcn36xx connection error

[Ondrej Kubik]

Public bug reported:

SRU Justification

Impact:
LEDs on dragonboard401c are not fully supported. Particularly WiFi and BT 
activity LEDs, heartbeat user LEDs

Step to reproduce:
 - Boot DragonBoard 410c and observer BT, WiFI LEDs and User LEDs

Expected result:
 LEDs are switched ON correctly

Actual result:
 BT, WiFi and some user LEDs are now switched ON

TEST CASE:
 - boot device
 - BT, WiFi and User LEDs should be switched ON accordingly

** Affects: linux-snapdragon (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  SRU Justification
  
  Impact:
- LEDs on dragonboard401c are not fully supported. Particularly WiFi and BT 
activity LEDS and User LEDs
+ LEDs on dragonboard401c are not fully supported. Particularly WiFi and BT 
activity LEDs, heartbeat user LEDs
  
  Step to reproduce:
-  - Boot DragonBoard 410c and observer BT, WiFI LEDs and User LEDs
+  - Boot DragonBoard 410c and observer BT, WiFI LEDs and User LEDs
  
  Expected result:
-  LEDs are switched ON correctly
+  LEDs are switched ON correctly
  
  Actual result:
-  BT, WiFi and some user LEDs are now switched ON
+  BT, WiFi and some user LEDs are now switched ON
  
  TEST CASE:
-  - boot device
-  - BT, WiFi and User LEDs should be switched ON accordingly
+  - boot device
+  - BT, WiFi and User LEDs should be switched ON accordingly

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776725

Title:
  snapdragon: wcn36xx connection error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1776725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776723] [NEW] snapdragon: wcn36xx connection error

[Ondrej Kubik]

Public bug reported:

SRU Justification

Impact:
snap cross building is broken and snap package can only build natively 
additionally snapcraft.yaml is using deprecated scriptlet syntax for 
install overrides
this syntax has been deprecated by snapcraft and should be replaced with 
new one to future proof builds

Step to reproduce:
 - cross build with snapcraft on x86_64 host by calling: snapcraft 
--targer-arch=arm64

Expected result:
 snap package builds without warnings

Actual result:
 build fails

TEST CASE:
 - cross build with snapcraft on x86_64 host by calling: snapcraft 
--targer-arch=arm64
 - build should complete without errors and snapcraft warnings

** Affects: linux-snapdragon (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/1776723

Title:
  snapdragon: wcn36xx connection error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1776723/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776720] [NEW] snapdragon: wcn36xx connection error

[Ondrej Kubik]

Public bug reported:

SRU Justification

Impact:
WiFi connection is unstable for connections over 2 hours

Step to reproduce:
 - Config device to connect to wifi AP
 - ssh into device and ping the 8.8.8.8

expected result: Wifi connection can continue ping to target ip over 2 hours
actual result: wifi disconnected/reconnected in about 5~10 mins, can not obtain 
ip address sometimes and no ip address after reboot, the failed rate are 1/5 
(reboot to get ip address)

TEST CASE:
 - Config device to connect to wifi AP
 - ssh into device and ping the 8.8.8.8
 connections should not break

** Affects: linux-snapdragon (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/1776720

Title:
  snapdragon: wcn36xx connection error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1776720/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776714] [NEW] raspi2: snapcraft scriptlet syntax outdated

[Ondrej Kubik]

Public bug reported:

SRU Justification

Impact:
  Newly released hardware Raspberry Pi3 B plus is not currently supported. Pi3 
B+ is very similar to existing Pi3B+ and requires only new dtb file describing 
differences from Pi3B

TEST CASE:
  Pi3B+ hw should be fully booting and all peripherals on board should be 
functioning

** Affects: linux-raspi2 (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/1776714

Title:
  raspi2: snapcraft scriptlet syntax outdated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1776714/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776708] [NEW] raspi2: snapcraft scriptlet syntax outdated

[Ondrej Kubik]

Public bug reported:

SRU Justification

Impact:
  current snapcraft.yaml is using deprecated scriptlet syntax. To make snap 
builds more future proof, snapcraft.yaml should migrate to new snapcraft syntax

TEST CASE:
  kernel snap should build without snapcraft complaining about deprecated 
functionality warnings

** Affects: linux-raspi2 (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/1776708

Title:
  raspi2: snapcraft scriptlet syntax outdated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1776708/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1698223] [NEW] add support for CM3 image creation

[Ondrej Kubik]

Public bug reported:

Start building ubuntu core images for Compute Module 3
Signed model assertion can be found attached to this ticket:
https://portal.admin.canonical.com/103446#

I have already requested store to upload the assertion to the store, so 
eventually it should be available under:
curl -H "Accept: application/x.ubuntu.assertion" 
"https://assertions.ubuntu.com/v1/assertions/model/16/canonical/cm3;

** Affects: livecd-rootfs (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/1698223

Title:
  add support for CM3 image creation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1698223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1672747] [NEW] configure hook missing reason it was invoked

[Ondrej Kubik]

Public bug reported:

when configure hook is invoked, there are several reasons leading to it, just 
to mention:
 - user calling snap set =
 - installing snap first time
 - updating snap
 - rollback

Each of this situation requires potentially different way to be be handled. At 
the moment it's left down to snap configure implementation to determine this, 
based on some custom storing of version/revisions values and comparing them.
This is 
  a) fragile as changes in snapd break it (own experience)
  b) tricky thanks to other snapd bugs (config entries not being wiped at snap 
remove)
  c) each snap with configure hook needs to reimplement same workaround

** Affects: snapd (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/1672747

Title:
  configure hook missing reason it was invoked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1672747/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1636934] [NEW] snapctl seem to cache values even if snap is removed and then installed again

[Ondrej Kubik]

Public bug reported:

preconditions:
$ snap install 
$ snap set  KEY1="VALUE"
$ snap set  KEY2="VALUE"
$ snap remove 
$ snap install 
$ snap set  KEY1="VALUE"

expected result:
when calling last $ snap set, configure hook associated to this "snap set" I'd 
expect snapctl only to return value for KEY1

actual result:
snapctl return values for both, KEY1 and KEY2

Are we cleaning snapctl cache when we remove snap?

tested on Ubuntu 16.04 classing
snapd version:
snap2.16ubuntu3
snapd   2.16ubuntu3
series  16
ubuntu  16.04

** Affects: snapd (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/1636934

Title:
  snapctl seem to cache values even if snap is removed and then
  installed again

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1636934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1636930] [NEW] uninstalling snap does not remove all user data

[Ondrej Kubik]

Public bug reported:

precondition:
calling $ snap remove 

expected result:
 all snap data are removed, this included all the user snap data for snap 
registered user, root, any other local user, and snap service data under 
/var/snap/

actual result:
 some snap data are left behind, /root// is not cleaned

** Affects: snapd (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/1636930

Title:
  uninstalling snap does not remove all user data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1636930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1636927] [NEW] upgrading kernel/gadget snap on Pi3 did not update dtb files

[Ondrej Kubik]

Public bug reported:

when calling snap refresh on raspberry pi3 from stable to edge device broke.
I refreshed core, gadget and kernel snap at the same time, in this order: 
core->gadget->kernel

closer investigation showed that dtb files from new kernel snap were not
copied over to boot/uboot

this making kernel upgrades dangerous

** Affects: snapd (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/1636927

Title:
  upgrading kernel/gadget snap on Pi3 did not update dtb files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1636927/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1636929] [NEW] edge -> stable refresh broken network settings

[Ondrej Kubik]

Public bug reported:

running snap refresh  from stable to edge for core, gadget, kernel snap seem to 
brake netplan configuration
this happened on raspberry pi3
core changes from 933->939
gadget from 5 -> 6
kernel from 21 -> 22

** Affects: snapd (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/1636929

Title:
  edge -> stable refresh broken network settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1636929/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1579961] [NEW] browser does not display selector

[Ondrej Kubik]

Public bug reported:

channel: rc-proposed/meizu.en/turbo v 70
url: http://www.crossrail.co.uk/route/improved-journeys

In "JOURNEY TIME CALCULATOR" Departure and arrival station selectors
fault to show list of stations to select from

** Affects: webbrowser-app (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/1579961

Title:
  browser does not display selector

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1579961/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

so I did use new script for LXC
Now I can see that Android init process is started but it fails quite soon,
with not much logs indicating actual issue.
This is just speculation, but probably still issue how /proc and /dev are
mounted to container?
Here are all the logs I get from Android init:

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.107370] init: cannot find
'/system/etc/install-recovery.sh', disabling 'flash_recovery'

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.107523] init: cannot find
'/system/bin/ubuntuappmanager.disabled', disabling 'ubuntuappmanager'

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.112345] binder: 1064:1064
transaction failed 29189, size 0-0

Jan  1 02:02:38 ubuntu-phablet dbus[862]: [system] Successfully activated
service 'org.freedesktop.login1'

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.190172] pil pil4: gss: Failed
to locate gss.mdt

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.214710] pil pil4: gss: Failed
to locate gss.mdt

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.220051] pil pil4: gss: Failed
to locate gss.mdt

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.231191] pil pil4: gss: Failed
to locate gss.mdt

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.243003] init: using
deprecated syntax for specifying property 'ro.serialno', use ${name} instead

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.243277] init: using
deprecated syntax for specifying property 'ro.product.manufacturer', use
${name} instead

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.243552] init: using
deprecated syntax for specifying property 'ro.product.model', use ${name}
instead

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.250572] usbcore: registered
new interface driver rmnet_usb

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.257042] rmnet usb ctrl
Initialized.

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.347413] init: property
'sys.powerctl' doesn't exist while expanding '${sys.powerctl}'

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.347627] init: powerctl:
cannot expand '${sys.powerctl}'

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.347840] init: property
'sys.sysctl.extra_free_kbytes' doesn't exist while expanding
'${sys.sysctl.extra_free_kbytes}'

Jan  1 02:02:38 ubuntu-phablet kernel: [   10.348023] init: cannot expand
'${sys.sysctl.extra_free_kbytes}' while writing to
'/proc/sys/vm/extra_free_kbytes'

On Fri, Apr 15, 2016 at 2:25 PM, Łukasz Zemczak <1551...@bugs.launchpad.net>
wrote:

> Can we get some traction on this? devel-proposed has been unbootable for
> too long. With xenial going into Final Freeze it would be nice to get
> this working around release-time. In touch we're not following the
> standard Ubuntu cycles, but it would be nice to have a bootable baseline
> when using xenial.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1551150
>
> Title:
>   devel-proposed - android lxc container fails to start
>
> Status in Canonical System Image:
>   Confirmed
> Status in lxc package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446
>
>   ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and
>   equivalent images on other devices do not boot and hang on the boot
>   logo.
>
>   From the list of changes, it could be lxc:
>   446: lxc 2.0.0~rc2-0ubuntu2
>   447: lxc 2.0.0~rc3-0ubuntu1
>
>   Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either.
>
>   lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium
>
> * New upstream release (2.0.0~rc3)
>   - Make the cgfs backend and cgns work without cgmanager
>   - Manpage updates
>   - Mark lxc-clone and lxc-start-ephemeral deprecated (still included)
> * Set --enable-deprecated so we still ship lxc-clone and
> lxc-start-ephemeral
>
>   lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium
>
> * Use versioned dependencies against the various binary packages.
> * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136)
> * Move the lxcfs recommends from lxc-templates to liblxc1.
> * Drop cgmanager, use the cgfs backend instead.
> * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend.
>
>   Device tarballs between 446 and 447 are the same.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

Finally some time to check more.
Using new  /etc/init/lxc-android-config.conf from Stephane 
http://paste.ubuntu.com/15264484/

When running manually $ lxc-start -n android -F -- /init
I can see init process be created, but then it exits. Also there are no logs in 
syslog or /proc/kmesg
So looks like init is super unhappy inside the container and does not do much.

But because it actually tries to run, following passes fine
lxc-wait -n android -s RUNNING -t 30
containerpid="$(lxc-info -n android -p -H)"
if [ -n "$containerpid" ]; then

and tries to continue with boot, while container actually fails to boot.
Is there way we can get more logs from running container, I tried this:
lxc-start -l 0 -n android -F -- /init
rm: cannot remove '/var/lib/lxc/android/rootfs/sbin/adbd': No such file or 
directory
run-parts: /var/lib/lxc/android/pre-start.d/10-no-adbd exited with return code 1
sed: can't read /var/lib/lxc/android/rootfs/init.manta.usb.rc: No such file or 
directory
cp: cannot stat '/var/lib/lxc/android/overrides/*': No such file or directory
mkfifo: cannot create fifo '/dev/socket/micshm': File exists

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

Finally some time to check more.
Using new  /etc/init/lxc-android-config.conf from Stephane 
http://paste.ubuntu.com/15264484/

When running manually $ lxc-start -n android -F -- /init
I can see init process be created, but then it exits. Also there are no logs in 
syslog or /proc/kmesg
So looks like init is super unhappy inside the container and does not do much.

But because it actually tries to run, following passes fine
lxc-wait -n android -s RUNNING -t 30
containerpid="$(lxc-info -n android -p -H)"
if [ -n "$containerpid" ]; then

and tries to continue with boot, while container actually fails to boot.
Is there way we can get more logs from running container, I tried this:
lxc-start -l 0 -n android -F -- /init
rm: cannot remove '/var/lib/lxc/android/rootfs/sbin/adbd': No such file or 
directory
run-parts: /var/lib/lxc/android/pre-start.d/10-no-adbd exited with return code 1
sed: can't read /var/lib/lxc/android/rootfs/init.manta.usb.rc: No such file or 
directory
cp: cannot stat '/var/lib/lxc/android/overrides/*': No such file or directory
mkfifo: cannot create fifo '/dev/socket/micshm': File exists

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

missing android signal was caused by double mounting of cgroup cpu,
which was already mounted. Fixing that did take boot further, now
lightdm becomes alive, still boot fails, and kills adb in the process...

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

missing android signal was caused by double mounting of cgroup cpu,
which was already mounted. Fixing that did take boot further, now
lightdm becomes alive, still boot fails, and kills adb in the process...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

more debugging and android signal is still not emitted, though android init 
process is running
Will keep debugging to get closer to the issue
we are progressing

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

more debugging and android signal is still not emitted, though android init 
process is running
Will keep debugging to get closer to the issue
we are progressing

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

lxc-container is now running, system still does not boot, but container is no 
more issue
needed changes:
install 
https://launchpad.net/ubuntu/+source/cgroup-lite/1.10/+build/6001591/+files/cgroup-lite_1.10_all.deb
and modify /etc/init/lxc-android-config.conf to this:
http://paste.ubuntu.com/15261714/

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

lxc-container is now running, system still does not boot, but container is no 
more issue
needed changes:
install 
https://launchpad.net/ubuntu/+source/cgroup-lite/1.10/+build/6001591/+files/cgroup-lite_1.10_all.deb
and modify /etc/init/lxc-android-config.conf to this:
http://paste.ubuntu.com/15261714/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

update from running system:
$  cat /proc/cgroups 
#subsys_namehierarchy   num_cgroups enabled
debug   3   1   1
cpu 1   1   1
cpuacct 2   1   1
freezer 4   1   1

$ cat /proc/self/cgroup 
5:name=systemd:/
4:freezer:/
3:debug:/
2:cpuacct:/
1:cpu:/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Ondrej Kubik]

update from running system:
$  cat /proc/cgroups 
#subsys_namehierarchy   num_cgroups enabled
debug   3   1   1
cpu 1   1   1
cpuacct 2   1   1
freezer 4   1   1

$ cat /proc/self/cgroup 
5:name=systemd:/
4:freezer:/
3:debug:/
2:cpuacct:/
1:cpu:/

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551150

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1506887] [NEW] vulnerability in OTA signature check mechanism

[Ondrej Kubik]

Public bug reported:

Cleverly constructed key signature tarball can bypass signature check.
If tarball contains symbolic link to the directory outside of the working 
folder followed then by file based on this symbolic link , tar will follow the 
link and creates new file outside of the working folder, which is not desired 
and can alter behaviour of the system.

** Affects: android (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/1506887

Title:
  vulnerability in OTA signature check mechanism

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1506887/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location

[Ondrej Kubik]

Not sure if that is best way to tackle this problem.
Using inspiration from another OS, I think best strategy is to use
indicator which makes distinction between different modes location service
is running in.
like this user can easily see when phone actually uses accurate location,
and then check which app is guilty.
>From my experience on iOS using network based location on all the time,
does not impact on battery that much.
Forbidding GPS all together to all apps would be quite drastic measure, and
a bit cumbersome to use.

On Wed, Sep 23, 2015 at 9:20 AM, Rex Tsai 
wrote:

> I believe "only wifi + cellular" is needed for user. Since that many
> apps are not designed for "preserve battery" but for best performance,
> which these apps will try to access to most accurate location
> information anytime, which consumed battery from gps sensors.
>
> That option is needed to allow a user put the phone into power-saving
> mode.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1421623
>
> Title:
>   Welcome wizard claims GPS is less accurate than wifi based location
>
> Status in Canonical System Image:
>   New
> Status in Ubuntu UX:
>   Invalid
> Status in ubuntu-system-settings package in Ubuntu:
>   Invalid
> Status in unity8 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   First boot welcome wizard in location sections claims GPS is less
> accurate than network based location service from HERE.
>   While this can be theoretically true in some insane corner case, in
> normal life GPS is far more accurate.
>
>   To help form correct text here are main differences.
>
>   GPS - more accurate, but slow to acquire fix, does not work indoors,
>   drains battery more, no need for internet connection, does not send
>   any data out.
>
>   Network based location - almost instant to get coarse location, works
>   indoors, accuracy depends on network coverage in the area, more power
>   efficient, requires internet connection. To get location data about
>   visible GSM network and wifi networks needs to be send to 3rd party
>   server.
>
>   tested on krillin vivid-proposed r107
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421623

Title:
  Welcome wizard claims GPS is less accurate than wifi based location

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1493663] Re: updates not downloading

[Ondrej Kubik]

Having exactly same issue on MX4, there was lot's of app for update before 
release 4, now after updating to release 4, there are 5 apps which refuse to 
update. Reboot, attempt to manually update them on by one, all fails.
Device: MX4
Release: 4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493663

Title:
  updates not downloading

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1493663/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1493663] Re: updates not downloading

[Ondrej Kubik]

So issue is caused by Ubuntu one account being invalid though still listed in 
online accounts.
Workaround is to remove Ubuntu one account and then add it again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493663

Title:
  updates not downloading

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1493663/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location

[Ondrej Kubik]

Option for only wifi + cellular is not really needed for user to chose from.
It is still used by the device, when application does not require precise
location, in order to preserve battery, but this is not to be controlled by
user. In my option no need to have any option like this here.

Still your statement is wrong, you are not referring to accuracy in your
examples but to actual availability, yes when you cannot get GPS lock, then
your wifi will get "better" location, in comparison to no location at all.
Yes wifi is more "accurate" while GPS is acquiring lock. But this is not
accuracy, but speed. It is like saying motorbike is faster than car,
because it can accelerate faster from still, even though car can actually
develop greater top speed.

But do you have case, where GPS is accessible and your option GPS+wifi is
more accurate in comparison? to back up "less accurate" statement?

So adjusting my example with data connections to your logic:
- 4G only (slower)
- 2G/3G/4G

This is obviously wrong, yet by your logic, it is correct. Combined
4G/3G/2G will never be faster than option 4G only, yet there will be cases
without 4G coverage when it will be "faster" compare to no 4G signal. By
your logic 4G is then slower.


On Tue, Sep 1, 2015 at 10:42 AM, Matthew Paul Thomas 
wrote:

> "From all location providers available, GPS is most accurate one,
> unfortunately also most power hungry and slowest to gain lock. This is
> reason we use all other providers to get faster, though less accurate,
> coarse location using combination os visible wifi access point and
> cellular cells."
>
> As I have said three times now, just Wi-Fi + cellular network info is
> not one of the options. It is in Android, and both Rex and I have
> mentioned here the possibility of adding it to Ubuntu -- but right now,
> it is not one of the options. If it was, you would be correct: you could
> save power by not using GPS. But the choice is between GPS only, or GPS
> + Wi-Fi + cellular network info. Since both of them use GPS, neither of
> them save power by not using GPS. And after seven months, you have still
> not given a single example of any moment where GPS only could possibly
> be more accurate than GPS + Wi-Fi + cellular network info, while I've
> given multiple examples where the opposite is true.
>
> Your GPRS analogy fails for the same reason: "GPRS only" is not one of
> the available options, just like "Wi-Fi and cellular networks only" is
> not one of the available options.
>
> The reason we provide multiple options, as explained in the UI, is
> nothing to do with power use. It is simply that the HERE option requires
> you to accept HERE's terms and conditions, while the GPS-only option
> does not. If we didn't care about providing location detection for
> people who don't want to accept the terms and conditions, we could just
> use HERE as the only option, make location detection an on/off toggle
> (like in iOS), and not need any further settings.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1421623
>
> Title:
>   Welcome wizard claims GPS is less accurate than wifi based location
>
> Status in Canonical System Image:
>   New
> Status in Ubuntu UX:
>   Invalid
> Status in ubuntu-system-settings package in Ubuntu:
>   Invalid
> Status in unity8 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   First boot welcome wizard in location sections claims GPS is less
> accurate than network based location service from HERE.
>   While this can be theoretically true in some insane corner case, in
> normal life GPS is far more accurate.
>
>   To help form correct text here are main differences.
>
>   GPS - more accurate, but slow to acquire fix, does not work indoors,
>   drains battery more, no need for internet connection, does not send
>   any data out.
>
>   Network based location - almost instant to get coarse location, works
>   indoors, accuracy depends on network coverage in the area, more power
>   efficient, requires internet connection. To get location data about
>   visible GSM network and wifi networks needs to be send to 3rd party
>   server.
>
>   tested on krillin vivid-proposed r107
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421623

Title:
  Welcome wizard claims GPS is less accurate than wifi based location

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location

[Ondrej Kubik]

I disagree with statement that GPS (less accurate)
this is simply not true.
It gives impression that GPS is less accurate, and when selecting second
option (with wifi) user will get better accuracy. But this is not true.
From all location providers available, GPS is most accurate one,
unfortunately also most power hungry and slowest to gain lock. This is
reason we use all other providers to get faster, though less accurate,
coarse location using combination os visible wifi access point and cellular
cells.
And this is essentially what that that second option should tell user, and
remove less accurate info from first option.

Using corner cases like in the building wifi is more accurate then GPS,
because GPS cannot get lock at all does not stand. That's like saying GPRS
is faster than 3G or LTE, because that is true in the areas without LTE or
3G signal where GPRS still functions. Anything is always grater than 0. Yet
you don't say GPRS is faster than 3G, or do you?


On Tue, Aug 11, 2015 at 3:59 PM, Rex Tsai rex.t...@canonical.com wrote:

 +1 on Ondrej's comment.

 The wizard UI imply that GPS is less accurate, which  is simply
 misleading if the user has no knowledge on GPS fix. Even the user know
 about GPS fix, there is no other UI indicate the phone has locked the
 GPS.

 To make sure setting more friendly, my suggestion is
 O High accuracy (Using GPS, anonymized Wi-Fi and cellular network info)
 O Power saving (Using anonymized Wi-Fi and cellular network info)
 O Device only (Using only GPS, without sharing network info for privacy)
 O Disable Location Service

 Does it make sense to user, and explain a bit more why a user need to
 make a choice ?

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1421623

 Title:
   Welcome wizard claims GPS is less accurate than wifi based location

 Status in Canonical System Image:
   New
 Status in Ubuntu UX:
   Invalid
 Status in ubuntu-system-settings package in Ubuntu:
   Invalid
 Status in unity8 package in Ubuntu:
   Incomplete

 Bug description:
   First boot welcome wizard in location sections claims GPS is less
 accurate than network based location service from HERE.
   While this can be theoretically true in some insane corner case, in
 normal life GPS is far more accurate.

   To help form correct text here are main differences.

   GPS - more accurate, but slow to acquire fix, does not work indoors,
   drains battery more, no need for internet connection, does not send
   any data out.

   Network based location - almost instant to get coarse location, works
   indoors, accuracy depends on network coverage in the area, more power
   efficient, requires internet connection. To get location data about
   visible GSM network and wifi networks needs to be send to 3rd party
   server.

   tested on krillin vivid-proposed r107

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421623

Title:
  Welcome wizard claims GPS is less accurate than wifi based location

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location

[Ondrej Kubik]

So is this it? Are we sticking to the version that Wifi based location is more 
accurate than GPS.
I strongly disagree to mark this as invalid.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421623

Title:
  Welcome wizard claims GPS is less accurate than wifi based location

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1468311] [NEW] recovery update screen lacks warning

[Ondrej Kubik]

Public bug reported:

When in recovery installing OTA updates, screen only shows infinite
progress and animation.

There should be also warning to user, not to disturb update in any way, such as 
trying to power phone off, removing battery.
Preferably progress or more verbose could be added.

Tested on Stable arale v2

** Affects: android (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/1468311

Title:
  recovery update screen lacks warning

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1468311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1468311] Re: recovery update screen lacks warning

[Ondrej Kubik]

Interesting question is if text in English is enough.
Because in recovery we don't have language variants, also in case of factory 
reset operations, we won't even have any settings to determine language.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468311

Title:
  recovery update screen lacks warning

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1468311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1454444] Re: Storage view does not count correctly space used by app

[Ondrej Kubik]

That makes sense and I have no preference where it should be implemented.
If there is better home for this bug, we should move it there.
I assigned this bug to Settings app since there it's visible, so it was
good starting point :)
If we create new bug please add it here, so we can track it for krillin.

On Tue, May 19, 2015 at 9:14 AM, Sebastien Bacher seb...@ubuntu.com
wrote:

 @Ondrej, well, my point is that libclick could provide a function that
 does that, it would be a better place because other codebase might have
 to get the same information and a common function in the framework used
 would make more sense that local implementation in every software

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/145

 Title:
   Storage view does not count correctly space used by app

 Status in the base for Ubuntu mobile products:
   New
 Status in click package in Ubuntu:
   New
 Status in ubuntu-system-settings package in Ubuntu:
   Incomplete

 Bug description:
   When going to Settings-About phone - Storage
   Storage used per app count does not include space used by app in
 ~/.local/app/
   This makes is hard to determine which app is actually eating all the
 storage.
   It also makes whole list kinda pointless, since we can have easily app
 easting 1G or more  and never see it in the lis.
   Apps like podcast, browser, twitter can easily eat hundreds of MB
 without being spotted in the list.

   Expected result:
   space occupied by all is calculated from the size of application itself,
 plus data used by application under ~/.local/app/

   tested on RTM krillin (stable/bq-aquaris.en/krillin) v22

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/canonical-devices-system-image/+bug/145/+subscriptions


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/145

Title:
  Storage view does not count correctly space used by app

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[Ondrej Kubik]

Just to confirm. I just received another device exhibiting boot loop issue and 
after quick investigation it was same problem, race of chid process continuing 
logging after parent died but before writable disk signal.
Once I used patched upstart binary, device booted normally, so all good.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756

Title:
  segfault in log.c code causes phone reboot loops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1454444] Re: Storage view does not count correctly space used by app

[Ondrej Kubik]

I'm not expert in click manifest, but that surely cannot have something as 
dynamic as size of application data which do change as user uses application.
I can imagine manifest having actual path to where application data should be 
stored, but it still should be calculated as we enter settings-storage view. 
So the settings app should parse manifest and calculated space occupied by all 
associated directories.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/145

Title:
  Storage view does not count correctly space used by app

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1454448] Re: Uninstalling app does not delete its data

[Ondrej Kubik]

I'm not sure what is best component to file this bug against. If there
is better home for this bug, please advice :)

I'm not sure how much logic click should have, but surely uninstaller
daemon should not rely on information in click package, it should clean
application data even if it has broken click manifest. Otherwise we are
relying on app developers to do something system should be responsible
for.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454448

Title:
  Uninstalling app does not delete its data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1454448/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[Ondrej Kubik]

I think I have nailed it down now, here is brief description what is happening 
(if I read code right)
There seems to be race, when we get new log data for one of the jobs after job 
has been terminated, and while processing it we call log_io_reader and 
eventually log_file_write which will try to flash unflashed buffer to drive.
This succeeds, mind this is before we got disk writable signal.
Since it succeeds, unflashed-len becomes 0, but we don't remove that log 
instance from list of logs which needs to be flashed (log_unflushed_files).
So next time when we get signal that disk is writable, we try again to flash 
that log and BOOM it panics on assert checking that log has something to be 
flashed, but it was already flashed.


Actual change of unfleshed log len changes on line 562, that's where we shrink 
unflashed buffer by amount we managed to write to disk, which in our case if 
full len, making buffer after shrinking zero length.
So I can see at least three fixes:
1) we should after calling nih_io_buffer_shrink (log-unflushed, (size_t)wlen); 
try to check and if log-unflashed-len is 0, and if so  then remove it from 
the log_unflushed_files list.
2) we need to make log_clear_unflushed more tolerant to logs which has been 
already flushed successfully before reaching to this point.
3) we don't try to flash unfleshed buffers till we get disk writable signal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756

Title:
  segfault in log.c code causes phone reboot loops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[Ondrej Kubik]

Sorry for spamming, but I guess that log_io_reader is called by nih_io_watcher 
which has been initialised by nih_io_reopen
which I suppose is called when job starts?

So that would go back to my original finding, job dies and is restarted before 
we get signal about disk being writable, but at the time job has been restarted 
it succeeds in writing unflushed logs to the disk while calling log_io_reader
Makes sense?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756

Title:
  segfault in log.c code causes phone reboot loops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[Ondrej Kubik]

So when job gets terminated we don't succeed to write to to the disk and it is 
added to the unflushed list.
Problem is another call to write function later on, but before we get writable 
disk signal:
[7.460627]init: log_handle_unflushed:778:len=32673, 
path='/var/log/upstart/ureadahead-touch.log'
[7.460682]init: unflushed-len=32673
[7.460736]init: job_process_terminated:1877:adding job ureadahead-touch to 
unflushed list

but then later one we get:
[7.968094]init: log_io_reader:368:
[7.968158]init: log_file_write:552:unflashed:61817, new_len:150, 
path:/var/log/upstart/ureadahead-touch.log
[7.975087]init: log_file_write:579:unflashed-len:61817, written_len:61817
calling nih_io_buffer_shrink (log-unflushed, (size_t)wlen);
[7.975167]init: log_file_write:581:unflashed-len:0

and eventually we get:
[8.369166]init: control_notify_disk_writeable
[8.369239]init: log_clear_unflushed
[8.369280]init: OK checking assert:unflashed-len = 46
[8.369435]init: log_clear_unflushed:888:
[8.369492]init: log_file_write:552:unflashed-len=46, new:0, 
path:/var/log/upstart/container-detect.log
[8.370305]init: log_file_write:579:len:46, wlen:46
[8.370359]init: log_file_write:581:len:0
[8.370450]init: OK checking assert:unflashed-len = 0
[8.370509]init: log.c:874: Assertion failed in log_clear_unflushed: 
log-unflushed-len

As you can see call to write in the middle is one causing the issue,
since it flushes log buffer, but does not remove it from unflushed list.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756

Title:
  segfault in log.c code causes phone reboot loops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[Ondrej Kubik]

So one thing which I still cannot track down is how is that unidentified 
log_io_reader called. Or who is calling it.
I have put traces to log_read_watch under condition if (io-recv_buf-len) { 
where we call log_io_reader but call is not coming from there.
So what are other options for log_io_reader to be called?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756

Title:
  segfault in log.c code causes phone reboot loops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1454448] [NEW] Uninstalling app does not delete its data

[Ondrej Kubik]

Public bug reported:

When app is uninstalled it's data under ~/.local is preserved.
This makes it impossible to track where all the free space went, since app is 
not even installed to be shown in storage view in the Settings app, and yet it 
can happily leave behind hundreds of MB of obsolete data.

Expected result:
when app is uninstalled, its linked private storage (~/.local/app/) is also 
freed. Uninstall should be preferably accompanied with warning dialog about all 
application data being deleted as well.

tested on RTM krillin (stable/bq-aquaris.en/krillin) v22

** Affects: ubuntu-system-settings (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/1454448

Title:
  Uninstalling app does not delete its data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1454448/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1454444] Re: Storage view does not count correctly space used by app

[Ondrej Kubik]

** Description changed:

  When going to Settings-About phone - Storage
  Storage used per app count does not include space used by app in 
~/.local/app/
- This makes is hard to determine which app is actually eating all the storage. 
+ This makes is hard to determine which app is actually eating all the storage.
  It also makes whole list kinda pointless, since we can have easily app 
easting 1G or more  and never see it in the lis.
  Apps like podcast, browser, twitter can easily eat hundreds of MB without 
being spotted in the list.
  
- Tested on RTM, krillin stable v 22
+ Expected result:
+ space occupied by all is calculated from the size of application itself, plus 
data used by application under ~/.local/app/
+ 
+ tested on RTM krillin (stable/bq-aquaris.en/krillin) v22

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/145

Title:
  Storage view does not count correctly space used by app

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1454444] [NEW] Storage view does not count correctly space used by app

[Ondrej Kubik]

Public bug reported:

When going to Settings-About phone - Storage
Storage used per app count does not include space used by app in ~/.local/app/
This makes is hard to determine which app is actually eating all the storage.
It also makes whole list kinda pointless, since we can have easily app easting 
1G or more  and never see it in the lis.
Apps like podcast, browser, twitter can easily eat hundreds of MB without being 
spotted in the list.

Expected result:
space occupied by all is calculated from the size of application itself, plus 
data used by application under ~/.local/app/

tested on RTM krillin (stable/bq-aquaris.en/krillin) v22

** Affects: ubuntu-system-settings (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/145

Title:
  Storage view does not count correctly space used by app

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[Ondrej Kubik]

I can confirm fix: http://paste.ubuntu.com/11095313/ does the job.
It will safely ignore entries of log_unflushed_files list which have 
log-unflushed-len set to zero. Since we know how this state is reached it 
seems like previous nih_assert (log-unflushed-len); was too aggressive.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756

Title:
  segfault in log.c code causes phone reboot loops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[Ondrej Kubik]

Sorry in previous comment, replace all flash with flush
Actually one more issue I can see there is this:
Job dies - it's added to log_unflushed_files when it has unflushed data
but if job is restarted before we get disk writable signal, it will mess up the 
things, job will still remain in log_unflushed_files
and once we  call log_file_write it will try to flush unflushed data, without 
removing job from log_unflushed_files list

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756

Title:
  segfault in log.c code causes phone reboot loops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[Ondrej Kubik]

Agreed, either we open new bug to track this, or we don't mark this as
fixed. This is the time one could use state workaround

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756

Title:
  segfault in log.c code causes phone reboot loops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[Ondrej Kubik]

hi James
So one way is to disable upstart logging all together with --no-log kern 
command option. We are going with this option for next OTA, till we can crack 
actual root cause of this issue.
As for restore, best bet is with MTK flash_tool

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756

Title:
  segfault in log.c code causes phone reboot loops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1435784] Re: SMS and calls working, but no mobile internet

[Ondrej Kubik]

Yep, we don't support dualboot on Nexus 7 anymore, it has too small partition 
for recovery where Ubuntu boot.img does not fit anymore.
So when you try to reboot to Ubuntu it will fail. Only way out would be some 
sort of repacking of Ubuntu boot image on the device and slimming it down to 
fit in Nexus 7 (2013) recovery partition. 
I think there is probably existing bug for this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435784

Title:
  SMS and calls working, but no mobile internet

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435784/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1435784] Re: SMS and calls working, but no mobile internet

[Ondrej Kubik]

Ups sorry wrong bug. Ignore my comment.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435784

Title:
  SMS and calls working, but no mobile internet

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435784/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location

[Ondrej Kubik]

GPS is most accurate positioning system we have on the phone. However it
comes with price, here are some of the bad features of GPS: drains
battery, does not work indoors, takes long to get initial location when
used first time (or long after last use)

Therefore number of supporting used to leverage those bad features of GPS, 
however those other technologies come at the price.
Namely network based location (wifi, GSM cells) is faster and less power hungry 
than GPS, but it has lot worse accuracy.

HERE location service uses network based location in order to show user coarse 
location quickly, while GPS is working on the background to acquire precise 
location. This can be observer in here maps when actual circle representing 
accuracy shrinks in the moment GPS location is acquired.
In short we get between 1m to 15m for GPS location, based on number of visible 
satellites.
but 25m to 30km! accuracy for network based location. 30km is extreme with no 
visible wifi and only one visible GSM cell tower. Still valid example.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421623

Title:
  Welcome wizard claims GPS is less accurate than wifi based location

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1429988] Re: Preview and photos are unfocused

[Ondrej Kubik]

there seems to be two issues:
One is focus-mode getting stacked in auto mode and not returning back to 
continuous-picture mode.
This could be reproduced by letting camera settle in continuous-picture mode, 
then tasking camera away and back, camera is restarted in auto mode. Not sure 
what is best way to reproduce but I was moving camera away while it was trying 
to refocus at this point and it'd get stacked in auto mode and never return 
to continuous-picture mode. Problem can be removed by simply tapping to 
screen to few objects to initialise auto focus to object and then moving camera 
around. It will usually go back to continuous-picture mode.

Second bug which is described here is when auto detection of macro mode fails 
to recognise when macro mode should be switched off. camera will still focus 
correctly when doing closeups but will fail to focus to faraway pictures.
I did not find consistent way to reproduce this or how to recover from that 
state. Sometimes tasking camera away and then resuming after some time does 
restores right state.
How to get phone in that state is also not reliable, but at least once I got 
camera to that state by simply focusing (with tab) to close up objects and then 
trying far away object, and camera would be in macro mode and no matter what 
would not focus to infinity.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429988

Title:
  Preview and photos are unfocused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1429988/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1429988] Re: Preview and photos are unfocused

[Ondrej Kubik]

To observe focus_mode do following:
$ adb shell
$ sudo /system/bin/logcat | grep focus-mode
Tapping on the screen switched focus-mode to auto focus to defined coordinates
When moving phone around, phone should default to 
focus-mode=continuous-picture
This is not always done when resuming camera app.
Again not same issue as one reported by John when phone would never focus and 
be stacked in macro mode. 
!! Macro here does not mean focus-mode=macro

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429988

Title:
  Preview and photos are unfocused

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1429988/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1421623] [NEW] Welcome wizard claims GPS is less accurate than wifi based location

[Ondrej Kubik]

Public bug reported:

First boot welcome wizard in location sections claims GPS is less accurate than 
network based location service from HERE.
While this can be theoretically true in some insane corner case, in normal life 
GPS is far more accurate.

To help form correct text here are main differences.

GPS - more accurate, but slow to acquire fix, does not work indoors,
drains battery more, no need for internet connection, does not send any
data out.

Network based location - almost instant to get coarse location, works
indoors, accuracy depends on network coverage in the area, more power
efficient, requires internet connection. To get location data about
visible GSM network and wifi networks needs to be send to 3rd party
server.

tested on krillin vivid-proposed r107

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: unity8 (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/1421623

Title:
  Welcome wizard claims GPS is less accurate than wifi based location

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1419928] [NEW] format user data does not do format

[Ondrej Kubik]

Public bug reported:

Formatting user data from settings app or from recovery does not actually 
format userdata partition.
This is not what user expects from function description.
- One would expect to be able to use this functionality as recovery from 
corrupted fs
- if filesystem is corrupted and mounted read only as fallback, then no files 
would be ever deleted, leading to user's deadlock
- hidden files or directories in the root of user data are not deleted.

Expected result:
user data partition is formatted and new fs is created

Actual result:
non hidden files are deleted, if there are any hidden files or directories, 
those are not deleted. Same happens for some 'special files'

Tested on krillin RTM r16

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: android (Ubuntu)
 Importance: Critical
 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/1419928

Title:
  format user data does not do format

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419928/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1385382] Re: Clock set to past confuses AppArmor cache validation

[Ondrej Kubik]

Conf file without double assignment.

** Attachment added: custom-apparmor-cache.override
   
https://bugs.launchpad.net/apparmor/+bug/1385382/+attachment/4261047/+files/custom-apparmor-cache.override

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385382

Title:
  Clock set to past confuses AppArmor cache validation

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1385382/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1385382] Re: Clock set to past confuses AppArmour cache validation

[Ondrej Kubik]

I'm all up to move it to more appropriate config, even to separate config,
rather than override, this was just place where I was testing it, to make
sure time is adjusted before we start validating custom apparmor caches.
I did not managed to get working TIME_ROOTFS formula in one go, that's the
reason for double assignment. I attached modified config without double
assignment.

On Fri, Nov 14, 2014 at 8:24 PM, Jamie Strandboge ja...@ubuntu.com
wrote:

 Assigning to package that ships /etc/init/custom-apparmor-cache.conf.
 I'm not the owner of ubuntu-touch-customization-hooks so someone else
 needs to land it. That said, the approach seems reasonable and the
 script fine (though the double assignment for TIME_ROOTFS is not as
 clear as it could be). However, I question whether this should be a pre-
 start of custom-apparmor-cache.conf. On the one hand, we shouldn't need
 this at all but because we do for custom-apparmor-cache to work right so
 it makes sense, but on the other, perhaps this would be better placed in
 a more 'foundational/phondational' package. Can we get someone from
 Phonedations/Foundations to review and comment?

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1385382

 Title:
   Clock set to past confuses AppArmor cache validation

 Status in AppArmor Linux application security framework:
   Won't Fix
 Status in “ubuntu-touch-customization-hooks” package in Ubuntu:
   Triaged

 Bug description:
   During initial boot sometimes clock could be set to past, which will
 confuse logic validating precompiled AppArmour cache, causing cache
 recreation.
   If time is not set correct(valid) value, even consequent boots will fail
 to validate cache, forcing cache recreation.

   This bug affects Initial out of the box experience, since device clock
   is set in the factory to default value, for example 0:0am 1st of
   January 2014

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/apparmor/+bug/1385382/+subscriptions


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385382

Title:
  Clock set to past confuses AppArmor cache validation

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1385382/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1387708] Re: [TOPBLOCKER] Location services not getting location

[Ondrej Kubik]

Some breakthrough:
Problem is caused by corrupted nvram data, when gps stack fails to identify 
underlying hw and therefore does not know how to function.
Underlying hw info is stored in /userdata/android-data/misc/GPS_CHIP.cfg, which 
is empty on broken phones, it should have text with chipset name.
Empty file is consequence of corrupted nvram file.
I have seen this one already during gps bring up, which was done on PVT phone, 
so nvram there was formatted several time, but now have this on production hw, 
so we need to investigate this further.
This bug should be moved to barajas project, since location service is just 
place where it pops out.

Two issues should be addressed:
1) when gps interface is started, start function never returns. Even if gps 
stack fails to initialise, it should at least return. Or in other case location 
service needs to initialise providers asynchronously to prevent one misbehaving 
provider taking whole service down. Ideally both should be done, with priority 
on gps stack always returning from start. Thomas any opinion here?

2) this is real problem and solution, we need to identify what is
corrupting nvram data during OTA

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387708

Title:
  [TOPBLOCKER] Location services not getting location

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1387708] Re: [TOPBLOCKER] Location services not getting location

[Ondrej Kubik]

0x6582%s from /userdata/android-data/misc/GPS_CHIP.cfg is correct value.
6582 represents mtk platform m6582.
When nvram gets corrupted GPS_CHIP.cfg is empty, as gps stack was not able to 
determine underlying platform.
So this seems to be different issue what you are seeing Rick.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387708

Title:
  [TOPBLOCKER] Location services not getting location

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1387708] Re: [TOPBLOCKER] Location services not getting location

[Ondrej Kubik]

Corrupted nvram file issue is now tracked by new bug in specific to
krillin: Bug #1389865

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387708

Title:
  [TOPBLOCKER] Location services not getting location

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1353591] Re: Ubuntu Touch devices sometimes come up with hwclock set to 1970

[Ondrej Kubik]

I have investigated similar issue on krillin.
In case of krillin hw clock is set at the factory to 1st of January 2014, 
0:00am.
This causes first boot (out of the box experience) to last 2mins 40 seconds 
before welcome wizard appears, with over 2minutes of it being white screen with 
bootloader logo (Google in case of N4, BQ for krillin)
Proposed and tested fix is to have upstart job, which would check time stamps 
of installed custom and rootfs builds. HW clock is then adjusted to those time 
stamps. 
This will not set time to correct value, however it will set it to something 
more realistic and at least to time which is ahead of the time when images in 
the phone were built, and more importantly when apparmour caches were created.
This makes first boot accept precompiled apparmour caches.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353591

Title:
  Ubuntu Touch devices sometimes come up with hwclock set to 1970

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1353591/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1353591] Re: Ubuntu Touch devices sometimes come up with hwclock set to 1970

[Ondrej Kubik]

Related bug: https://bugs.launchpad.net/bugs/1385382

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353591

Title:
  Ubuntu Touch devices sometimes come up with hwclock set to 1970

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1353591/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1379850] Re: [system-settings] should allow switching 2nd SIM to 3G data

[Ondrej Kubik]

Jonas: HW we are using is capable of switching active technology used on
each SIM slot. There is hw limitation that only one SIM slot can have 3G
technology enabled at the time, since phone has only one rf module.

Radio Interface Daemon can alter technologies used on each SIM slot,
this operation require modem to reboot in the background, but it is
totally possible to do it. We have also successfully tested this with
Android build.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379850

Title:
  [system-settings] should allow switching 2nd SIM to 3G data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1379850/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1372555] Re: [system-settings] Settings application should run only in portrait

[Ondrej Kubik]

About prettiness: for example Orientation lock and Flight mode could
be easily put on same row, making space for other icons.

About need to rotate itself. Here I'd answer with question, why don't we rotate 
indicator bar then?  Because you can argue that indicator bar is probably first 
place user will go to check and change basic settings, especially movie related 
(brightness, volume), using settings application for more complex tasks, when 
rotation won't be anymore hindrance anyway. 
Few more points to support the idea of not rotating:
 - as it happens setting from first page of the settings application is 
landscape mode are all accessible from indicator bar 
 - just the process to task away from one application and to start/task to 
Settings application will probably make user to rotate the phone anyway, since 
gestures will not be in natural place

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372555

Title:
  [system-settings] Settings application should run only in portrait

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1372555/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1373388] Re: Allow user to change SIM slot technologies ( ex. 2G vs. 3G )

[Ondrej Kubik]

Idea for this bug was to provide task to implement support in ofono to switch 
SIM slot technologies.
It is not intention of this bug to tackle whole user experience, and under 
which condition technology in SIM slots should be altered.
This is only to provide foundation in case UX requires to do so, task which can 
be done independently.

In bigger picture, UX should be designed first to decide if and when
such a cal is needed, if needed at all.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373388

Title:
  Allow user to change SIM slot technologies ( ex. 2G vs. 3G )

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libqofono/+bug/1373388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1373388] Re: Allow user to change SIM slot technologies ( ex. 2G vs. 3G )

[Ondrej Kubik]

Tony are you sure it's as simple as writing 'TechnologyPreference' for each 
slot?
How does it handle fact that there are hw limitations to and only one slot at 
the time can have 3G enabled.
Also when I tried this on Android, it seems like this actually reboots modem. 
While I believe you can downgrade/upgrade technology on slot without need to 
reboot modem.

I was hopping there is specific call to rild which is handling this, and
doing all necessary checks ( making sure only one slot is 3G, rebooting
modem if needed)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373388

Title:
  Allow user to change SIM slot technologies ( ex. 2G vs. 3G )

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libqofono/+bug/1373388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1366132] Re: SIM card definitively disappeared - ofonod crashed with SIGABRT in raise()

[Ondrej Kubik]

*** This bug is a duplicate of bug 1321627 ***
https://bugs.launchpad.net/bugs/1321627

Tony I have observer same issue on Krillin. It was up to date on rtm channel.
Same symptoms, phone was not detecting any SIM card, ofonod crashing. And only 
way out was to wipe the phone and start from the start.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366132

Title:
  SIM card definitively disappeared - ofonod crashed with SIGABRT in
  raise()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1366132/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1319213] Re: keeping user data keeps files in /var/crash which makes little sense

[Ondrej Kubik]

Oli where do we delete /data/system-data with ubuntu-device-flash?
Are we actually calling adb shell rm -rf /data/system-data from 
ubuntu-device-flash?
I just checked latest bootable/recovery/system-image-upgrader and we do not 
delete system-data unless you format /data partition. And in that case dualboot 
will also delete system-data (var) when we format user data.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319213

Title:
  keeping user data keeps files in /var/crash which makes little sense

To manage notifications about this bug go to:
https://bugs.launchpad.net/humpolec/+bug/1319213/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1070377] Re: Empathy change to Online Accounts no longer supports SIPE

[Ondrej Kubik]

Upgraded from 12.04 where I was using sipe pluging, my account kept working 
after upgrade, though I could not actually see it in my online accounts.
I had to change sipe account's password, so now I'm buggered, since there is no 
way I can update my account settings.

It's definitely bug. My existing account turned after upgrade to 12.10
into zombie, can't delete it, can't update it, it's just there nagging
about wrong credentials

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070377

Title:
  Empathy change to Online Accounts no longer supports SIPE

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/1070377/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1066208] Re: Battery indicator shows mouse battery instead of notebook battery

[Ondrej Kubik]

Not exactly this bug, but potentially related.
Since mouse battery is shown as default, it raised interesting question, what 
is active power mode On Battery Power or When Plugged in?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066208

Title:
  Battery indicator shows mouse battery instead of notebook battery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1066208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs