from:"stuart"

2015-09-29 10:30:55,881 INFO cache.commit()
2015-09-29 10:30:55,881 DEBUG failed to SystemUnLock() (E:Not locked) 
2015-09-29 11:04:11,358 ERROR got an error from dpkg for pkg: 'lxc': 
'subprocess installed post-installation script returned error exit status 100'
2015-09-29 11:04:11,358 DEBUG running apport_pkgfailure() lxc: subprocess 
installed post-installation script returned error exit status 100
2015-09-29 11:04:11,362 ERROR got an error from dpkg for pkg: 'lxc': 
'subprocess installed post-installation script returned error exit status 100'
2015-09-29 11:04:36,574 ERROR got an error from dpkg for pkg: 'lxc-templates': 
'dependency problems - leaving unconfigured'
2015-09-29 11:04:36,574 DEBUG running apport_pkgfailure() lxc-templates: 
dependency problems - leaving unconfigured
2015-09-29 11:04:36,574 DEBUG dpkg error because of dependency problems, not 
reporting against lxc-templates 
2015-09-29 11:04:36,574 ERROR got an error from dpkg for pkg: 'lxc-templates': 
'dependency problems - leaving unconfigured'
2015-09-29 11:04:38,001 ERROR got an error from dpkg for pkg: 'juju-local': 
'dependency problems - leaving unconfigured'
2015-09-29 11:04:38,001 DEBUG running apport_pkgfailure() juju-local: 
dependency problems - leaving unconfigured
2015-09-29 11:04:38,001 DEBUG dpkg error because of dependency problems, not 
reporting against juju-local 
2015-09-29 11:04:38,001 ERROR got an error from dpkg for pkg: 'juju-local': 
'dependency problems - leaving unconfigured'
2015-09-29 11:05:14,645 ERROR got an error from dpkg for pkg: 'lxc': 
'subprocess installed post-installation script returned error exit status 100'
2015-09-29 11:05:14,645 DEBUG running apport_pkgfailure() lxc: subprocess 
installed post-installation script returned error exit status 100
2015-09-29 11:05:14,650 ERROR got an error from dpkg for pkg: 'lxc': 
'subprocess installed post-installation script returned error exit status 100'
2015-09-29 11:05:18,267 ERROR not handled expection:
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1), 
E:Sub-process /usr/bin/dpkg returned an error code (1)

2015-09-29 11:05:18,267 DEBUG running apport_crash()
2015-09-29 11:05:23,083 ERROR SystemError from cache.commit(): 
installArchives() failed
2015-09-29 11:05:39,322 ERROR not handled expection:
Traceback (most recent call last):

  File 
"/tmp/ubuntu-release-upgrader-fr1j7u5b/DistUpgrade/DistUpgradeController.py", 
line 1137, in doDistUpgrade
res = self.cache.commit(fprogress,iprogress)

  File "/tmp/ubuntu-release-upgrader-fr1j7u5b/DistUpgrade/DistUpgradeCache.py", 
line 267, in commit
apt.Cache.commit(self, fprogress, iprogress)

  File "/usr/lib/python3/dist-packages/apt/cache.py", line 505, in commit
if fetch_progress is None:

SystemError: installArchives() failed


During handling of the above exception, another exception occurred:


TypeError: wait_for_child() takes 1 positional argument but 2 were given

2015-09-29 11:05:39,322 DEBUG running apport_crash()

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1490110

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

Upgrade to wily failed here with this error.  Possible trigger was
having juju-local installed, which seemed to create a bit of a
dependency mess with juju-local, lxc-templates and lxc.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1490110

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

** Attachment added: "apt-term.log"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+attachment/4478083/+files/apt-term.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1490110

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in lxc package in Ubuntu:
  New

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

** Attachment added: "main.log"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+attachment/4478084/+files/main.log

** Changed in: lxc (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1490110

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in lxc package in Ubuntu:
  New

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1504496] Re: package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-10-10 Thread Stuart Bishop

Is this Bug #1490110 ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1504496

Title:
  package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lxc package in Ubuntu:
  New

Bug description:
  A dist-upgrade failed in the maintainer scripts while trying to
  restart the lxc networking, I think:

  Reading package lists... Done
  The following NEW packages will be installed:
linux-image-3.19.0-31-generic{a} linux-image-extra-3.19.0-31-generic{a} 
linux-signed-image-3.19.0-31-generic{a} 
  The following packages will be upgraded:
juju juju-core juju-local liblxc1 linux-image-generic linux-libc-dev 
linux-signed-image-generic 
lxc lxc-templates mutt python3-lxc 
  The following packages are RECOMMENDED but will NOT be installed:
citadel-mta courier-mta dma dma:i386 esmtp-run exim4-daemon-heavy 
exim4-daemon-light 
lsb-invalid-mta masqmail msmtp-mta nullmailer opensmtpd postfix qmail-run 
sendmail-bin ssmtp 
xmail 
  11 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/90.5 MB of archives. After unpacking 259 MB will be used.
  Do you want to continue? [Y/n/?] 
  (Reading database ... 357199 files and directories currently installed.)
  Preparing to unpack .../python3-lxc_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking python3-lxc (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Preparing to unpack .../lxc-templates_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking lxc-templates (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Preparing to unpack .../liblxc1_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking liblxc1 (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Preparing to unpack .../lxc_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking lxc (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Selecting previously unselected package linux-image-3.19.0-31-generic.
  Preparing to unpack .../linux-image-3.19.0-31-generic_3.19.0-31.36_amd64.deb 
...
  Done.
  Unpacking linux-image-3.19.0-31-generic (3.19.0-31.36) ...
  Selecting previously unselected package linux-image-extra-3.19.0-31-generic.
  Preparing to unpack 
.../linux-image-extra-3.19.0-31-generic_3.19.0-31.36_amd64.deb ...
  Unpacking linux-image-extra-3.19.0-31-generic (3.19.0-31.36) ...
  Preparing to unpack .../linux-image-generic_3.19.0.31.30_amd64.deb ...
  Unpacking linux-image-generic (3.19.0.31.30) over (3.19.0.30.29) ...
  Preparing to unpack .../linux-libc-dev_3.19.0-31.36_amd64.deb ...
  Unpacking linux-libc-dev:amd64 (3.19.0-31.36) over (3.19.0-30.34) ...
  Selecting previously unselected package linux-signed-image-3.19.0-31-generic.
  Preparing to unpack 
.../linux-signed-image-3.19.0-31-generic_3.19.0-31.36_amd64.deb ...
  Unpacking linux-signed-image-3.19.0-31-generic (3.19.0-31.36) ...
  Preparing to unpack .../linux-signed-image-generic_3.19.0.31.30_amd64.deb ...
  Unpacking linux-signed-image-generic (3.19.0.31.30) over (3.19.0.30.29) ...
  Preparing to unpack .../mutt_1.5.23-3ubuntu1_amd64.deb ...
  Unpacking mutt (1.5.23-3ubuntu1) over (1.5.23-3) ...
  Preparing to unpack .../juju-core_1.24.6-0ubuntu1~15.04.1_amd64.deb ...
  Unpacking juju-core (1.24.6-0ubuntu1~15.04.1) over 
(1.23.2-0ubuntu1~14.10.1~juju1) ...
  Preparing to unpack .../juju_1.24.6-0ubuntu1~15.04.1_all.deb ...
  Unpacking juju (1.24.6-0ubuntu1~15.04.1) over (1.23.2-0ubuntu1~14.10.1~juju1) 
...
  Preparing to unpack .../juju-local_1.24.6-0ubuntu1~15.04.1_all.deb ...
  Unpacking juju-local (1.24.6-0ubuntu1~15.04.1) over 
(1.23.2-0ubuntu1~14.10.1~juju1) ...
  Processing triggers for man-db (2.7.0.2-5) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for doc-base (0.10.6) ...
  Processing 1 changed doc-base file...
  Registering documents with scrollkeeper...
  Processing triggers for gnome-menus (3.10.1-0ubuntu5) ...
  Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
  Processing triggers for bamfdaemon (0.5.1+15.04.20150202-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for mime-support (3.58ubuntu1) ...
  Setting up liblxc1 (1.1.4-0ubuntu0.1) ...
  Setting up python3-lxc (1.1.4-0ubuntu0.1) ...
  Setting up lxc (1.1.4-0ubuntu0.1) ...
  Installing new version of config file 
/etc/apparmor.d/lxc/lxc-default-with-nesting ...
  Installing new version of config file /etc/bash_completion.d/lxc ...
  Installing new version of config file /etc/init/lxc.conf ...
  Job for lxc-net.service failed. See "systemctl status lxc-net.service" and 
"journalctl -xe" for details.
  invoke-rc.d: initscript lxc-net, action "start" failed.
  dpkg: error processing package lxc (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of

[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

2015-10-13 Thread Stuart Bishop

stub@aargh:~$ sudo systemctl status lxc
● lxc.service - LXC Container Initialization and Autoboot Code
   Loaded: loaded (/lib/systemd/system/lxc.service; enabled; vendor preset: 
enabled)
   Active: active (exited) since Mon 2015-10-12 16:57:31 ICT; 20h ago
  Process: 1190 ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-containers start 
(code=exited, status=0/SUCCESS)
  Process: 1175 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load 
(code=exited, status=0/SUCCESS)
  Process: 1166 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-devsetup 
(code=exited, status=0/SUCCESS)
 Main PID: 1190 (code=exited, status=0/SUCCESS)
   Memory: 0B
  CPU: 0
   CGroup: /system.slice/lxc.service

Oct 12 16:57:31 aargh systemd[1]: Starting LXC Container Initialization and 
Autoboot Code...
Oct 12 16:57:31 aargh lxc-devsetup[1166]: Creating /dev/.lxc
Oct 12 16:57:31 aargh lxc-devsetup[1166]: /dev is devtmpfs
Oct 12 16:57:31 aargh lxc-devsetup[1166]: Creating /dev/.lxc/user
Oct 12 16:57:31 aargh systemd[1]: Started LXC Container Initialization and 
Autoboot Code.
stub@aargh:~$ sudo service lxc status
● lxc.service - LXC Container Initialization and Autoboot Code
   Loaded: loaded (/lib/systemd/system/lxc.service; enabled; vendor preset: 
enabled)
   Active: active (exited) since Mon 2015-10-12 16:57:31 ICT; 20h ago
  Process: 1190 ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-containers start 
(code=exited, status=0/SUCCESS)
  Process: 1175 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load 
(code=exited, status=0/SUCCESS)
  Process: 1166 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-devsetup 
(code=exited, status=0/SUCCESS)
 Main PID: 1190 (code=exited, status=0/SUCCESS)
   Memory: 0B
  CPU: 0
   CGroup: /system.slice/lxc.service

Oct 12 16:57:31 aargh systemd[1]: Starting LXC Container Initialization and 
Autoboot Code...
Oct 12 16:57:31 aargh lxc-devsetup[1166]: Creating /dev/.lxc
Oct 12 16:57:31 aargh lxc-devsetup[1166]: /dev is devtmpfs
Oct 12 16:57:31 aargh lxc-devsetup[1166]: Creating /dev/.lxc/user
Oct 12 16:57:31 aargh systemd[1]: Started LXC Container Initialization and 
Autoboot Code.
stub@aargh:~$

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1490110

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1495120] Re: No function to explicitly enable Caller ID

2015-11-20 Thread Stuart McQuade

This is really basic phone functionality, so there any chance of raising
this bug's priority? I'm more than happy to help with testing if needed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1495120

Title:
  No function to explicitly enable Caller ID

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  My phone network uses a secret Caller ID by default. There should bean
  option in Ubuntu Touch to explicitly enable a public caller ID.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1537920] [NEW] package linux-image-4.3.0-7-generic 4.3.0-7.18 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2016-01-25 Thread Stuart Inglis

Public bug reported:

do-release-upgrade -d from 15.10 crashes.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-7-generic 4.3.0-7.18
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lightdm1259 F pulseaudio
 /dev/snd/controlC1:  lightdm1259 F pulseaudio
Date: Tue Jan 26 11:06:43 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
InstallationDate: Installed on 2016-01-21 (3 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
IwConfig:
 enp5s0no wireless extensions.
 
 enp0s31f6  no wireless extensions.
 
 lono wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=fe44bf75-72d1-4ed4-9e15-191bbd1c47cf ro nomdmonddf nomdmonisw
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-4.3.0-7-generic 4.3.0-7.18 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to xenial on 2016-01-25 (0 days ago)
dmi.bios.date: 01/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7g
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170X-Gaming 7
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7g:bd01/18/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming7:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1537920

Title:
  package linux-image-4.3.0-7-generic 4.3.0-7.18 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  do-release-upgrade -d from 15.10 crashes.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-7-generic 4.3.0-7.18
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1259 F pulseaudio
   /dev/snd/controlC1:  lightdm1259 F pulseaudio
  Date: Tue Jan 26 11:06:43 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  InstallationDate: Installed on 2016-01-21 (3 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   enp5s0no wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=fe44bf75-72d1-4ed4-9e15-191bbd1c47cf ro nomdmonddf nomdmonisw
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.3.0-7-generic 4.3.0-7.18 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2016-01-25 (0 days ago)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7g
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-Gaming 7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version:

[Touch-packages] [Bug 1489395] [NEW] Single star means "this number is the rating", but looks like app has a low rating

Public bug reported:

App ratings are displayed as ☆ 4.5. Every time I glance at an app's
rating my first thought is that it's been rated low, because it's only
got one star. Then I read the number and realise that the app is rated
highly and that star means "here is the rating", not "it's got a one-
star rating". As far as I can tell everywhere a star rating is displayed
it's on a line on its own, so there ought to be room to write ☆ 4.5
(nine characters) -- there is room to fit the developer name
horizontally, or the app name -- and this would avoid the confusion.

** Affects: unity-scope-click (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1489395

Title:
  Single star means "this number is the rating", but looks like app has
  a low rating

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  App ratings are displayed as ☆ 4.5. Every time I glance at an app's
  rating my first thought is that it's been rated low, because it's only
  got one star. Then I read the number and realise that the app is rated
  highly and that star means "here is the rating", not "it's got a one-
  star rating". As far as I can tell everywhere a star rating is
  displayed it's on a line on its own, so there ought to be room to
  write ☆ 4.5 (nine characters) -- there is room to fit the
  developer name horizontally, or the app name -- and this would avoid
  the confusion.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1489642] [NEW] With only one payment method available, app purchase dropdown seems to do nothing

Public bug reported:

When paying for an app from the store, if there is only one payment
method available (for example, Paypal), then the "dropdown" of payment
methods does not actually drop down in any way. Instead, all that
happens is that the "this drops down" chevron on the right hand side
(see attached screenshot 1) changes to a tick mark (screenshot 2). This
change is almost imperceptible, and I had to do it two or three times
before I understood what was going on. If there is only one option for
payment, perhaps it should not be presented as a drop down list, or
perhaps drop down lists should do something more obvious to indicate
that they're working when they are tapped?

** Affects: unity-scope-click (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "screenshot 1"
   
https://bugs.launchpad.net/bugs/1489642/+attachment/4453545/+files/screenshot20150827_230833324.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1489642

Title:
  With only one payment method available, app purchase dropdown seems to
  do nothing

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  When paying for an app from the store, if there is only one payment
  method available (for example, Paypal), then the "dropdown" of payment
  methods does not actually drop down in any way. Instead, all that
  happens is that the "this drops down" chevron on the right hand side
  (see attached screenshot 1) changes to a tick mark (screenshot 2).
  This change is almost imperceptible, and I had to do it two or three
  times before I understood what was going on. If there is only one
  option for payment, perhaps it should not be presented as a drop down
  list, or perhaps drop down lists should do something more obvious to
  indicate that they're working when they are tapped?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1489642] Re: With only one payment method available, app purchase dropdown seems to do nothing

** Attachment added: "screenshot 2"
   
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1489642/+attachment/4453546/+files/screenshot20150827_230837710.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1489642

Title:
  With only one payment method available, app purchase dropdown seems to
  do nothing

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  When paying for an app from the store, if there is only one payment
  method available (for example, Paypal), then the "dropdown" of payment
  methods does not actually drop down in any way. Instead, all that
  happens is that the "this drops down" chevron on the right hand side
  (see attached screenshot 1) changes to a tick mark (screenshot 2).
  This change is almost imperceptible, and I had to do it two or three
  times before I understood what was going on. If there is only one
  option for payment, perhaps it should not be presented as a drop down
  list, or perhaps drop down lists should do something more obvious to
  indicate that they're working when they are tapped?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1489643] [NEW] Paypal login cannot be assured to be from paypal

Public bug reported:

When paying for an app with Paypal, the Paypal login screen is presented
in an Ubuntu wrapper. There is no indication on this page that I'm
actually looking at paypal.com rather than being phished or that some
bad DNS has pointed me to a wrong site. The padlock in the top corner
doesn't indicate anything I'm inclined to believe -- is it showing that
the connection is https? Has it verified that I'm really talking to
Paypal? How can I know that? This is encouraging people to type their
Paypal password into phishing sites. The previous step in the purchase
process, where I'm choosing which payment system to use, also displays a
padlock, and that hasn't connected to any payment site at all.

** Affects: unity-scope-click (Ubuntu)
Importance: Undecided
Status: New

** Attachment added: ""Paypal" login in Ubuntu wrapper"

https://bugs.launchpad.net/bugs/1489643/+attachment/4453547/+files/screenshot20150827_230910161.png

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1489643

Title:
Paypal login cannot be assured to be from paypal

Status in unity-scope-click package in Ubuntu:
New

Bug description:
When paying for an app with Paypal, the Paypal login screen is
presented in an Ubuntu wrapper. There is no indication on this page
that I'm actually looking at paypal.com rather than being phished or
that some bad DNS has pointed me to a wrong site. The padlock in the
top corner doesn't indicate anything I'm inclined to believe -- is it
showing that the connection is https? Has it verified that I'm really
talking to Paypal? How can I know that? This is encouraging people to
type their Paypal password into phishing sites. The previous step in
the purchase process, where I'm choosing which payment system to use,
also displays a padlock, and that hasn't connected to any payment site
at all.

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492783] [NEW] GPS does not work on my Bq E5

Public bug reported:

I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
SensorsStatus app shows GPS as returning no results for location (every
reading ("Latitude", "Longitude", etc) is shown as a dash, except
"Method" which is "Satellite" and "Speed" which is "nan") . I have
attached various logfiles in the hope that they will help. I have tried
turning off location detection and GPS and turning them back on again,
to no avail. I have also tried turning off wifi, to no avail.

** Affects: location-service (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  New

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5

** Attachment added: "ubuntu-location-service-trust-stored.log"
   
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+attachment/4458351/+files/ubuntu-location-service-trust-stored.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  New

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5

** Attachment added: 
"com.ubuntu.location.ubuntu-phablet.invalid-user.log.ERROR.20150904-101710.3687"
   
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+attachment/4458356/+files/com.ubuntu.location.ubuntu-phablet.invalid-user.log.ERROR.20150904-101710.3687

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  New

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5

** Attachment added: "com.ubuntu.location.WARNING"
   
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+attachment/4458355/+files/com.ubuntu.location.WARNING

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  New

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5

** Attachment added: 
"com.ubuntu.location.ubuntu-phablet.invalid-user.log.ERROR.20150904-101710.3687"
   
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+attachment/4458358/+files/com.ubuntu.location.ubuntu-phablet.invalid-user.log.ERROR.20150904-101710.3687

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  New

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5

** Attachment added: "com.ubuntu.location.INFO"
   
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+attachment/4458354/+files/com.ubuntu.location.INFO

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  New

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5

** Attachment added: "com.ubuntu.location.ERROR"
   
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+attachment/4458353/+files/com.ubuntu.location.ERROR

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  New

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5

** Attachment added: "ubuntu-location-service-trust-stored.log.1.gz"
   
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+attachment/4458352/+files/ubuntu-location-service-trust-stored.log.1.gz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  New

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5

** Attachment added: 
"com.ubuntu.location.ubuntu-phablet.invalid-user.log.INFO.20150904-114017.1719"
   
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+attachment/4458357/+files/com.ubuntu.location.ubuntu-phablet.invalid-user.log.INFO.20150904-114017.1719

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  New

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5

It was suggested that I add logfile  /var/log/upstart/ubuntu-espoo-
service.log but I don't seem to have that at all.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  New

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1495120] Re: No function to explicitly enable Caller ID

2015-11-28 Thread Stuart McQuade

Related to 1469506

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1495120

Title:
  No function to explicitly enable Caller ID

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  My phone network uses a secret Caller ID by default. There should bean
  option in Ubuntu Touch to explicitly enable a public caller ID.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1469506] Re: [Dialer] Implement "Hide Phone Number" setting in dialer app

2015-11-28 Thread Stuart McQuade

Related to 1495120

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1469506

Title:
  [Dialer] Implement "Hide Phone Number" setting in dialer app

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Please implement the phone number hiding option in the dialer app's
  settings. I know I can hide my phone number when making a call if I
  enter a code number (For example: UK: 141) before the phone number.
  Other OS-es, like Android or iOs have these feature already.

  -- UX comment -

  Indeed, this should be part of the dialer settings, the recommendation
  is a ListItem with a switch/toggle.

  Wireframes are work in progress.
  https://canonical.leankit.com/Boards/View/107963243/116425188

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1295247] Re: Cheese says "There was an error playing video from webcam"

2015-09-26 Thread Stuart Campbell

Same error - still doesn't work on Wily.

guvcview works fine, cheese and skype do not work.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu.
https://bugs.launchpad.net/bugs/1295247

Title:
  Cheese says "There was an error playing video from webcam"

Status in cheese package in Ubuntu:
  Confirmed
Status in libjpeg-turbo package in Ubuntu:
  Confirmed

Bug description:
  Whenever I open Cheese in Ubuntu 14.04 beta 1 (Unity), my webcam's light once 
turns on, then it turns off and Cheese turns black, written "There was an error 
playing video from webcam". This never happened in any previous versions of 
Ubuntu. 
  The problem is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cheese 3.10.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Mar 20 22:29:57 2014
  InstallationDate: Installed on 2014-03-20 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1809174] Re: apt doesn't detect file corruption in /var/lib/apt/lists

The problem with deferring the situation to the clean command is that
the system appears to be working properly with no problem, and the user
will have to _guess_ that cleanup is required.

Running md5sum on the packages is not expensive:

ubuntu@T00-tx2b:/var/lib/apt/lists$ time md5sum 
ports.ubuntu.com_ubuntu-ports_dists_xenial_universe_binary-arm64_Packages
005695bf761c4719325927b5a236a77e  
ports.ubuntu.com_ubuntu-ports_dists_xenial_universe_binary-arm64_Packages

real0m0.166s
user0m0.136s
sys 0m0.036s

Certainly it's much faster than the downloading of the indexes in the
first place.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1809174

Title:
  apt doesn't detect file corruption in /var/lib/apt/lists

Status in apt package in Ubuntu:
  New

Bug description:
  The Problem
  ==

  /var/lib/apt/lists contains the repository index caches or similar;
  I'm not sure what the correct  apt-terminology is.

  I've installed Chrome on my laptop, so I have:

  smacdonald@L247:/var/lib/apt/lists$ dir *goog*
  -rw-r--r-- 1 root root  943 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_Release
  -rw-r--r-- 1 root root  819 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_Release.gpg
  -rw-r--r-- 1 root root 4457 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages

  for example.

  
  dl.google.com_linux_chrome_deb_dists_stable_Release contains checksums for 
the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file:

  smacdonald@L247:/var/lib/apt/lists$ cat 
dl.google.com_linux_chrome_deb_dists_stable_Release
  Origin: Google LLC
  Label: Google
  Suite: stable
  Codename: stable
  Version: 1.0
  Date: Wed, 19 Dec 2018 18:51:54 UTC
  Architectures: amd64
  Components: main
  Description: Google chrome-linux software repository
  MD5Sum:
   9e0d0ad6a4f5ccf8e3971c32e9bb22d3 4457 main/binary-amd64/Packages
   a17f6de0ef487b82af58ccd91df52d04 1109 main/binary-amd64/Packages.gz
   156e5ea7a0c6bed5973a68a45e546dc9 151 main/binary-amd64/Release
  SHA1:
   4c2cde4f71476d7881262d9a07e33cf4506232a7 4457 main/binary-amd64/Packages
   e002924c9ddfe41ee2033594ec768ed9e4545909 1109 main/binary-amd64/Packages.gz
   0f4348c2d4d7cc1f8e59b5934d87f1ca872f6e34 151 main/binary-amd64/Release
  SHA256:
   fb0e586c2b5ec5afa17965d0bbc6bd46c2071336f75e2b0f0c7f3e7b090a7844 4457 
main/binary-amd64/Packages
   2462cff732765679a56373a7ca9a5b8b029fdb445e707b1aba10d01fbdb853b3 1109 
main/binary-amd64/Packages.gz
   c1e3c9318381862306adcdc4fd4fe2d85be8aa4c4f3dcbb40fce80413f588286 151 
main/binary-amd64/Release

  
  If the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages 
file has become corrupt in the specific manner of being 0 bytes in length, apt 
does not detect this, and the repository is effectively unreachable until one 
of two things occurs: a) the repository has an update causing apt to re-fetch 
the repository information and accidentally fix-by-over-writing the corrupt 0 
byte file, or, b) the user removes the corrupt 0-byte file and does an apt 
update to refetch the repository information.

  
  The Context
  ==

  Our IoT devices run Ubuntu 16.04, and their main storage is eMMC.
  Sometimes there are catastrophic power cuts, and, despite other
  precautions, files are occasionally corrupted in the manner of
  becoming 0 bytes in length. We're not sure exactly why or how.

  Today a deployed device suffered the above scenario. We maintain a
  debian package repository for updating our devices in the field, and
  we suddenly couldn't install packages from it. A bit of investigation
  turned up the 0 byte *_Packages file for our repo, and we worked
  around the problem.

  Part of the situation is our debian repository doesn't have updates
  very often, so 'sudo apt-get update' was giving a Hit: instead of a
  Get: result all the time, and everything from the "normal user command
  line" side of things looked okay. There were no logs in
  /var/log/syslog either. We just could not see our packages from our
  repo, despite 'apt-get update' looking good.

  
  What I Expected to Happen
  ==

  Given that the the *_Release file contains checksums for the *_Package
  file, I would expect that apt verifies the checksum, and if it fails,
  refetches the repository information even if there hasn't been an
  update, during any given 'apt update' operation.

  
  Further Information
  ==

  I checked apt's project in Debian at https://bugs.debian.org/cgi-
  bin/pkgreport.cgi?pkg=apt and there don't appear to be any bugs about
  this filed already

[Touch-packages] [Bug 1809174] Re: apt doesn't detect file corruption in /var/lib/apt/lists

Filesystem is ext4

ubuntu@T00-tx2b:~$ mount
/dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1809174

Title:
  apt doesn't detect file corruption in /var/lib/apt/lists

Status in apt package in Ubuntu:
  New

Bug description:
  The Problem
  ==

  /var/lib/apt/lists contains the repository index caches or similar;
  I'm not sure what the correct  apt-terminology is.

  I've installed Chrome on my laptop, so I have:

  smacdonald@L247:/var/lib/apt/lists$ dir *goog*
  -rw-r--r-- 1 root root  943 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_Release
  -rw-r--r-- 1 root root  819 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_Release.gpg
  -rw-r--r-- 1 root root 4457 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages

  for example.

  
  dl.google.com_linux_chrome_deb_dists_stable_Release contains checksums for 
the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file:

  smacdonald@L247:/var/lib/apt/lists$ cat 
dl.google.com_linux_chrome_deb_dists_stable_Release
  Origin: Google LLC
  Label: Google
  Suite: stable
  Codename: stable
  Version: 1.0
  Date: Wed, 19 Dec 2018 18:51:54 UTC
  Architectures: amd64
  Components: main
  Description: Google chrome-linux software repository
  MD5Sum:
   9e0d0ad6a4f5ccf8e3971c32e9bb22d3 4457 main/binary-amd64/Packages
   a17f6de0ef487b82af58ccd91df52d04 1109 main/binary-amd64/Packages.gz
   156e5ea7a0c6bed5973a68a45e546dc9 151 main/binary-amd64/Release
  SHA1:
   4c2cde4f71476d7881262d9a07e33cf4506232a7 4457 main/binary-amd64/Packages
   e002924c9ddfe41ee2033594ec768ed9e4545909 1109 main/binary-amd64/Packages.gz
   0f4348c2d4d7cc1f8e59b5934d87f1ca872f6e34 151 main/binary-amd64/Release
  SHA256:
   fb0e586c2b5ec5afa17965d0bbc6bd46c2071336f75e2b0f0c7f3e7b090a7844 4457 
main/binary-amd64/Packages
   2462cff732765679a56373a7ca9a5b8b029fdb445e707b1aba10d01fbdb853b3 1109 
main/binary-amd64/Packages.gz
   c1e3c9318381862306adcdc4fd4fe2d85be8aa4c4f3dcbb40fce80413f588286 151 
main/binary-amd64/Release

  
  If the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages 
file has become corrupt in the specific manner of being 0 bytes in length, apt 
does not detect this, and the repository is effectively unreachable until one 
of two things occurs: a) the repository has an update causing apt to re-fetch 
the repository information and accidentally fix-by-over-writing the corrupt 0 
byte file, or, b) the user removes the corrupt 0-byte file and does an apt 
update to refetch the repository information.

  
  The Context
  ==

  Our IoT devices run Ubuntu 16.04, and their main storage is eMMC.
  Sometimes there are catastrophic power cuts, and, despite other
  precautions, files are occasionally corrupted in the manner of
  becoming 0 bytes in length. We're not sure exactly why or how.

  Today a deployed device suffered the above scenario. We maintain a
  debian package repository for updating our devices in the field, and
  we suddenly couldn't install packages from it. A bit of investigation
  turned up the 0 byte *_Packages file for our repo, and we worked
  around the problem.

  Part of the situation is our debian repository doesn't have updates
  very often, so 'sudo apt-get update' was giving a Hit: instead of a
  Get: result all the time, and everything from the "normal user command
  line" side of things looked okay. There were no logs in
  /var/log/syslog either. We just could not see our packages from our
  repo, despite 'apt-get update' looking good.

  
  What I Expected to Happen
  ==

  Given that the the *_Release file contains checksums for the *_Package
  file, I would expect that apt verifies the checksum, and if it fails,
  refetches the repository information even if there hasn't been an
  update, during any given 'apt update' operation.

  
  Further Information
  ==

  I checked apt's project in Debian at https://bugs.debian.org/cgi-
  bin/pkgreport.cgi?pkg=apt and there don't appear to be any bugs about
  this filed already, so I'm starting by filing one here.

  The situation occurred on an Ubuntu 16.04 system, but is 100%
  reproducible with Google's chrome repository on my Ubuntu 18.04.1
  laptop. I can provide a set of reproduction steps if needed, but it's
  fairly straight-forward.

  The fact that this corruption appears to be "everything working okay"
  to the end user, except that apt doesn't know about packages it says
  it knows about, and there is no error logging for any sort, is partly
  why I'm filing thi

[Touch-packages] [Bug 1809174] Re: apt doesn't detect file corruption in /var/lib/apt/lists

I was picturing scenario (1); if there are updates or the checksum on
the existing doesn't match, download the index.

apt has trained users to "apt update" before doing anything else, so
this would be okay.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1809174

Title:
  apt doesn't detect file corruption in /var/lib/apt/lists

Status in apt package in Ubuntu:
  New

Bug description:
  The Problem
  ==

  /var/lib/apt/lists contains the repository index caches or similar;
  I'm not sure what the correct  apt-terminology is.

  I've installed Chrome on my laptop, so I have:

  smacdonald@L247:/var/lib/apt/lists$ dir *goog*
  -rw-r--r-- 1 root root  943 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_Release
  -rw-r--r-- 1 root root  819 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_Release.gpg
  -rw-r--r-- 1 root root 4457 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages

  for example.

  
  dl.google.com_linux_chrome_deb_dists_stable_Release contains checksums for 
the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file:

  smacdonald@L247:/var/lib/apt/lists$ cat 
dl.google.com_linux_chrome_deb_dists_stable_Release
  Origin: Google LLC
  Label: Google
  Suite: stable
  Codename: stable
  Version: 1.0
  Date: Wed, 19 Dec 2018 18:51:54 UTC
  Architectures: amd64
  Components: main
  Description: Google chrome-linux software repository
  MD5Sum:
   9e0d0ad6a4f5ccf8e3971c32e9bb22d3 4457 main/binary-amd64/Packages
   a17f6de0ef487b82af58ccd91df52d04 1109 main/binary-amd64/Packages.gz
   156e5ea7a0c6bed5973a68a45e546dc9 151 main/binary-amd64/Release
  SHA1:
   4c2cde4f71476d7881262d9a07e33cf4506232a7 4457 main/binary-amd64/Packages
   e002924c9ddfe41ee2033594ec768ed9e4545909 1109 main/binary-amd64/Packages.gz
   0f4348c2d4d7cc1f8e59b5934d87f1ca872f6e34 151 main/binary-amd64/Release
  SHA256:
   fb0e586c2b5ec5afa17965d0bbc6bd46c2071336f75e2b0f0c7f3e7b090a7844 4457 
main/binary-amd64/Packages
   2462cff732765679a56373a7ca9a5b8b029fdb445e707b1aba10d01fbdb853b3 1109 
main/binary-amd64/Packages.gz
   c1e3c9318381862306adcdc4fd4fe2d85be8aa4c4f3dcbb40fce80413f588286 151 
main/binary-amd64/Release

  
  If the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages 
file has become corrupt in the specific manner of being 0 bytes in length, apt 
does not detect this, and the repository is effectively unreachable until one 
of two things occurs: a) the repository has an update causing apt to re-fetch 
the repository information and accidentally fix-by-over-writing the corrupt 0 
byte file, or, b) the user removes the corrupt 0-byte file and does an apt 
update to refetch the repository information.

  
  The Context
  ==

  Our IoT devices run Ubuntu 16.04, and their main storage is eMMC.
  Sometimes there are catastrophic power cuts, and, despite other
  precautions, files are occasionally corrupted in the manner of
  becoming 0 bytes in length. We're not sure exactly why or how.

  Today a deployed device suffered the above scenario. We maintain a
  debian package repository for updating our devices in the field, and
  we suddenly couldn't install packages from it. A bit of investigation
  turned up the 0 byte *_Packages file for our repo, and we worked
  around the problem.

  Part of the situation is our debian repository doesn't have updates
  very often, so 'sudo apt-get update' was giving a Hit: instead of a
  Get: result all the time, and everything from the "normal user command
  line" side of things looked okay. There were no logs in
  /var/log/syslog either. We just could not see our packages from our
  repo, despite 'apt-get update' looking good.

  
  What I Expected to Happen
  ==

  Given that the the *_Release file contains checksums for the *_Package
  file, I would expect that apt verifies the checksum, and if it fails,
  refetches the repository information even if there hasn't been an
  update, during any given 'apt update' operation.

  
  Further Information
  ==

  I checked apt's project in Debian at https://bugs.debian.org/cgi-
  bin/pkgreport.cgi?pkg=apt and there don't appear to be any bugs about
  this filed already, so I'm starting by filing one here.

  The situation occurred on an Ubuntu 16.04 system, but is 100%
  reproducible with Google's chrome repository on my Ubuntu 18.04.1
  laptop. I can provide a set of reproduction steps if needed, but it's
  fairly straight-forward.

  The fact that this corruption appears to be "everything working okay"
  to the end user, except that apt doesn't know about package

[Touch-packages] [Bug 1809174] Re: apt doesn't detect file corruption in /var/lib/apt/lists