[Touch-packages] [Bug 1157643] Re: procps fail to start

[Chandrasekar P]

sudo /etc/init.d/procps restart
stop: Unknown instance: 
procps stop/waiting

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

Title:
  procps fail to start

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Precise:
  Fix Released
Status in procps source package in Quantal:
  Fix Released
Status in procps source package in Raring:
  Fix Released
Status in procps source package in Saucy:
  Fix Released
Status in procps source package in Trusty:
  Fix Released

Bug description:
  [SRU justification]
  In a container, the procps package fails to upgrade because sysctl will fail 
when it can't write to certain keys.  Since the procps has just been SRUed, 
this means anyone running Ubuntu in a container (12.04 or later) will have 
upgrade failures because of the procps upstart job failing to start.

  [Test case]
  1. Set up precise in an lxc container.
  2. Apply updates from the -updates pocket.
  3. Observe that the procps package fails to install.
  4. Enable -proposed.
  5. Install the procps package from -proposed.
  6. Observe that the package upgrades successfully.

  [Regression potential]
  This patch changes the behavior of the sysctl program and causes permission 
errors to be non-fatal.  Anything relying on the current behavior (e.g., when 
sysctl is run by a non-root user) will regress as a result of this change, but 
it's not obvious why anything would rely on this since sysctl is not meant to 
be invoked by non-root users.  
  root@x:~# lsb_release -rd
  Description:Ubuntu 12.04.2 LTS
  Release:12.04

  root@xxx:~# apt-cache policy procps
  procps:
    Installed: 1:3.2.8-11ubuntu6
    Candidate: 1:3.2.8-11ubuntu6
    Version table:
   *** 1:3.2.8-11ubuntu6 0
  500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  I have a VPS that i upgraded from Ubuntu 10.10 to 11.10 and then to 12.04.2 
LTS.
  But something is wrong and now i can't upgrade procps. I get the following 
output,

  root@xx:~# apt-get  upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue [Y/n]?
  Setting up procps (1:3.2.8-11ubuntu6) ...
  start: Job failed to start
  invoke-rc.d: initscript procps, action "start" failed.
  dpkg: error processing procps (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   procps
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  the /var/log/upstart/procps.log says,

  kernel.printk = 4 4 1 7
  net.ipv6.conf.all.use_tempaddr = 2
  net.ipv6.conf.default.use_tempaddr = 2
  error: permission denied on key 'kernel.kptr_restrict'
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1
  net.ipv4.tcp_syncookies = 1
  vm.mmap_min_addr = 65536

  And the output when i try to start procps is just the following,

  root@x:~# service procps start
  start: Job failed to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1157643/+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 1654707] [NEW] Cant upgrade: "add stricter shlib dependencies " ends with supposed broken dependencies

[dino99]

Public bug reported:

The upgrade to 3.3.5-2 is impossible: warns about broken dependecies,
but they are not identified.

fftw3 (3.3.5-2) unstable; urgency=medium

  * add stricter shlib dependencies for partial upgrades (Closes: #849593)
  * mark libfft3-mpi-dev m-a same and libfftw3-doc m-a foreign

 -- Julian Taylor   Fri, 06 Jan 2017
18:44:49 +0100

Looks like that " add stricter shlib dependencies for partial upgrades "
is the root cause of the upgrade failure.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libfftw3-double3 3.3.5-1
ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
Uname: Linux 4.9.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jan  7 06:02:28 2017
Dependencies:
 gcc-6-base 6.3.0-2ubuntu1
 libc6 2.24-7ubuntu2
 libgcc1 1:6.3.0-2ubuntu1
 libgomp1 6.3.0-2ubuntu1
SourcePackage: fftw3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

** Description changed:

  The upgrade to 3.3.5-2 is impossible: warns about broken dependecies,
- but they are no identified.
+ but they are not identified.
  
  fftw3 (3.3.5-2) unstable; urgency=medium
  
-   * add stricter shlib dependencies for partial upgrades (Closes: #849593)
-   * mark libfft3-mpi-dev m-a same and libfftw3-doc m-a foreign
+   * add stricter shlib dependencies for partial upgrades (Closes: #849593)
+   * mark libfft3-mpi-dev m-a same and libfftw3-doc m-a foreign
  
-  -- Julian Taylor   Fri, 06 Jan 2017
+  -- Julian Taylor   Fri, 06 Jan 2017
  18:44:49 +0100
  
  Looks like that " add stricter shlib dependencies for partial upgrades "
  is the root cause of the upgrade failure.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libfftw3-double3 3.3.5-1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan  7 06:02:28 2017
  Dependencies:
-  gcc-6-base 6.3.0-2ubuntu1
-  libc6 2.24-7ubuntu2
-  libgcc1 1:6.3.0-2ubuntu1
-  libgomp1 6.3.0-2ubuntu1
+  gcc-6-base 6.3.0-2ubuntu1
+  libc6 2.24-7ubuntu2
+  libgcc1 1:6.3.0-2ubuntu1
+  libgomp1 6.3.0-2ubuntu1
  SourcePackage: fftw3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Cant upgrade: "add stricter shlib dependencies " ends with supposed
  broken dependencies

Status in fftw3 package in Ubuntu:
  New

Bug description:
  The upgrade to 3.3.5-2 is impossible: warns about broken dependecies,
  but they are not identified.

  fftw3 (3.3.5-2) unstable; urgency=medium

    * add stricter shlib dependencies for partial upgrades (Closes: #849593)
    * mark libfft3-mpi-dev m-a same and libfftw3-doc m-a foreign

   -- Julian Taylor   Fri, 06 Jan 2017
  18:44:49 +0100

  Looks like that " add stricter shlib dependencies for partial upgrades
  " is the root cause of the upgrade failure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libfftw3-double3 3.3.5-1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan  7 06:02:28 2017
  Dependencies:
   gcc-6-base 6.3.0-2ubuntu1
   libc6 2.24-7ubuntu2
   libgcc1 1:6.3.0-2ubuntu1
   libgomp1 6.3.0-2ubuntu1
  SourcePackage: fftw3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1654707/+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 1522675] Re: Needless scary warning: Can't drop privileges for downloading : _apt user not allowed

[dino99]

** Changed in: apt (Ubuntu)
   Status: Fix Released => New

** Summary changed:

- Needless scary warning: Can't drop privileges for downloading : _apt user not 
allowed
+ Needless scary warning: Download is performed unsandboxed as root: _apt user 
not allowed

** No longer affects: dpkg (Ubuntu)

-- 
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/1522675

Title:
  Needless scary warning: Download is performed unsandboxed as root:
  _apt user not allowed

Status in apt package in Ubuntu:
  New
Status in apt package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1644651] Re: tracker file system miner misses most files on Ubuntu 16.10

[Richard]

As of 1/6/2017, this has somewhat improved
Tracker recurses but:
- without a reset only finds 90% of content
- with a reset, does not find everything anyway

1. Tracker still only finds 90% unless it is reset. So, reset like:
tracker reset --hard <

[Touch-packages] [Bug 1522190] Re: Permission denied (publickey) whereas the public key has been inserted into ~/.ssh/authorized_keys: "usePAM no" issue

[Launchpad Bug Tracker]

[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Permission denied (publickey) whereas the public key has been inserted
  into  ~/.ssh/authorized_keys: "usePAM no" issue

Status in openssh package in Ubuntu:
  Expired

Bug description:
  Security vulnerability because I cannot use SSH to connect to my Ubuntu host 
from a Ubuntu guest. Is Telnet the last option?
  However, I can connect through the same port at the same IP address from a 
Windows 10 guest using the latest WinSCP software.

  OpenSSH Server: 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  with openssh-server 6.9p1-2

  OpenSSH client: 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  with openssh-client 6.9p1-2

  Trace of the failed SSH connection:
  
  root@stack:~/.ssh# ssh -v -p  root@172.19.100.1
  OpenSSH_6.9p1 Ubuntu-2, OpenSSL 1.0.2d 9 Jul 2015
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 172.19.100.1 [172.19.100.1] port .
  debug1: Connection established.
  debug1: key_load_private_type: No such file or directory
  debug1: key_load_private_cert: No such file or directory
  debug1: key_load_private_cert: No such file or directory
  debug1: key_load_private_cert: No such file or directory
  debug1: key_load_private_cert: No such file or directory
  debug1: key_load_private_type: No such file or directory
  debug1: key_load_private_type: No such file or directory
  debug1: permanently_set_uid: 0/0
  debug1: identity file /root/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /root/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /root/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /root/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /root/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /root/.ssh/id_ecdsa-cert type -1
  debug1: identity file /root/.ssh/id_ed25519 type 4
  debug1: key_load_public: No such file or directory
  debug1: identity file /root/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_6.9p1 Ubuntu-2
  debug1: Remote protocol version 2.0, remote software version OpenSSH_6.9p1 
Ubuntu-2
  debug1: match: OpenSSH_6.9p1 Ubuntu-2 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 172.19.100.1: as 'root'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server->client aes192-ctr hmac-sha2-256-...@openssh.com none
  debug1: kex: client->server aes192-ctr hmac-sha2-256-...@openssh.com none
  debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<8192<8192) sent
  debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
  debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
  debug1: got SSH2_MSG_KEX_DH_GEX_REPLY
  debug1: Server host key: ssh-ed25519 
SHA256:xx
  debug1: checking without port identifier
  The authenticity of host '[172.19.100.1]: ([172.19.100.1]:)' can't be 
established.
  ED25519 key fingerprint is 
SHA256:xxx
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added '[172.19.100.1]:' (ED25519) to the list of 
known hosts.
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: Roaming not allowed by server
  debug1: SSH2_MSG_SERVICE_REQUEST sent
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  *
  NOTICE TO USERS

  This computer system is the private property of its owner, whether
  individual, corporate or government.  It is for authorized use only.
  Users (authorized or unauthorized) have no explicit or implicit
  expectation of privacy.

  Any or all uses of this system and all files on this system may be
  intercepted, monitored, recorded, copied, audited, inspected, and
  disclosed to your employer, to authorized site, government, and law
  enforcement personnel, as well as authorized officials of government
  agencies, both domestic and foreign.

  By using this system, the user consents to such interception, monitoring,
  recording, copying, auditing, inspection, and disclosure at the
  discretion of such personnel or officials.  Unauthorized or improper use
  of thi

[Touch-packages] [Bug 1639521] Re: package libsasl2-modules-db 2.1.27~72-g88d82a3+dfsg-1 [modified: usr/share/doc/libsasl2-modules-db/NEWS.Debian.gz usr/share/doc/libsasl2-modules-db/changelog.Debian.

[Launchpad Bug Tracker]

[Expired for cyrus-sasl2 (Ubuntu) because there has been no activity for
60 days.]

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libsasl2-modules-db 2.1.27~72-g88d82a3+dfsg-1 [modified:
  usr/share/doc/libsasl2-modules-db/NEWS.Debian.gz
  usr/share/doc/libsasl2-modules-db/changelog.Debian.gz
  usr/share/doc/libsasl2-modules-db/copyright] failed to
  install/upgrade: tentando sobrescrever compartilhamento
  '/usr/share/doc/libsasl2-modules-db/NEWS.Debian.gz', que é diferente
  de outras instâncias do pacote libsasl2-modules-db:i386

Status in cyrus-sasl2 package in Ubuntu:
  Expired

Bug description:
  weiller@weiller-MS-7641:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  libsasl2-modules-db:
Instalado: 2.1.27~72-g88d82a3+dfsg-1
Candidato: 2.1.27~72-g88d82a3+dfsg-1
Tabela de versão:
   *** 2.1.27~72-g88d82a3+dfsg-1 500
  500 http://cz.archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
Packages
  500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.1.26.dfsg1-15 500
  500 ftp://ubuntu.c3sl.ufpr.br/ubuntu yakkety/main amd64 Packages
  500 http://cz.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty/main amd64 Packages
   2.1.26.dfsg1-14build1 500
  500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libsasl2-modules-db 2.1.27~72-g88d82a3+dfsg-1 [modified: 
usr/share/doc/libsasl2-modules-db/NEWS.Debian.gz 
usr/share/doc/libsasl2-modules-db/changelog.Debian.gz 
usr/share/doc/libsasl2-modules-db/copyright]
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sat Nov  5 21:33:06 2016
  Dependencies:
   gcc-6-base 6.2.0-11ubuntu1
   libc6 2.24-3ubuntu1
   libdb5.3 5.3.28-12
   libgcc1 1:6.2.0-11ubuntu1
  ErrorMessage: tentando sobrescrever compartilhamento 
'/usr/share/doc/libsasl2-modules-db/NEWS.Debian.gz', que é diferente de outras 
instâncias do pacote libsasl2-modules-db:i386
  InstallationDate: Installed on 2016-02-11 (268 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: cyrus-sasl2
  Title: package libsasl2-modules-db 2.1.27~72-g88d82a3+dfsg-1 [modified: 
usr/share/doc/libsasl2-modules-db/NEWS.Debian.gz 
usr/share/doc/libsasl2-modules-db/changelog.Debian.gz 
usr/share/doc/libsasl2-modules-db/copyright] failed to install/upgrade: 
tentando sobrescrever compartilhamento 
'/usr/share/doc/libsasl2-modules-db/NEWS.Debian.gz', que é diferente de outras 
instâncias do pacote libsasl2-modules-db:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1639521/+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 1652520] Re: package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

-- 
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/1652520

Title:
  package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  using aptitutde safe-upgrade package returned error while installing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1468 F pulseaudio
  Date: Sun Dec 25 17:19:09 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=34908dcc-6c03-4983-b5a4-cc13533ffea4
  InstallationDate: Installed on 2016-06-22 (185 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite R630
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=10d412c8-368d-4b65-a14b-b01126287d68 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 2.20
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion2.20:bd12/22/2011:svnTOSHIBA:pnSatelliteR630:pvrPT31LE-01D00HGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: Satellite R630
  dmi.product.version: PT31LE-01D00HGR
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1652520/+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 1522675] Re: Needless scary warning: Can't drop privileges for downloading : _apt user not allowed

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.4~beta3

---
apt (1.4~beta3) unstable; urgency=medium

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ David Kalnischkies ]
  * reword "Can't drop priv" warning message (Closes: #813786) (LP: #1522675)
  * let {dsc,tar,diff}-only implicitly enable download-only
  * remove needless fork() in apt-get source
  * default to --no-check for dpkg-source call (Closes: 724744)
  * warn if clearsigned file has ignored content parts
  * ensure generation of valid EDSP error stanzas
  * add --indep-only for build-dep command (Closes: #845775)
  * allow default build-essentials to be overridden
  * expand -f to --fix-broken in error messages.
Thanks to Kristian Glass for initial patch! (Closes: #709092)
  * separating state variables regarding server/request (Closes: #440057)
  * fix minimum pkgs option for dpkg --recursive usage
  * allow warning generation for non-whitelisted options

  [ Oriol Debian ]
  * Catalan program translation update (Closes: #846514)

  [ Frans Spiesschaert ]
  * Dutch manpages translation update (Closes: #849235)

  [ Niels Thykier ]
  * ParseDepends: Support passing the desired architecture (Closes: #845969)

 -- Julian Andres Klode   Thu, 05 Jan 2017 20:50:01
+0100

** Changed in: apt (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1522675

Title:
  Needless scary warning: Can't drop privileges for downloading : _apt
  user not allowed

Status in apt package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1651518] Re: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create

[Steve Langasek]

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Steve Langasek (vorlon)

** Changed in: systemd (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.2

** Changed in: systemd (Ubuntu Yakkety)
 Assignee: (unassigned) => Steve Langasek (vorlon)

** Changed in: systemd (Ubuntu Yakkety)
Milestone: None => yakkety-updates

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

Title:
  systemd/logind parsing problem: HTX exercisers stopped on error: rc
  11, errno 11 from main(): pthread_create

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New

Bug description:
  == Comment: #1 - Application Cdeadmin  -
  2016-12-19 04:15:10 ==

  Configuration: IBM 8001-22C (S822LC), LSI SAS adapters, SMC 4U90 disk
  drawers, HDD (180) 7.3TB

  Problem: HTX exercisers stopped on error, with HTX log showing "rc 11,
  errno 11 from main(): pthread_create"

  htxubuntu-425

  lpar: busybee.aus.stglabs.ibm.com (root/ lab passwd)

  root@busybee:~# uname -a
  Linux busybee 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:27:59 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@busybee:~# cat /tmp/htxerr

  /dev/sdh  Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdh  Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  No errors logged in syslog after starting HTX:

   State: Open by: asperez on 16 December 2016 10:28:02 
  This error recreated on the smaller 1U Open Power system with the same 
smaller 1-adapter/1-4U90 drawer/90 HDD. There are 2 cables connected to the 
drawer (one to each ESM) that requires multipath enabled. 

  lpar: yellowbee

  root@yellowbee:~# cat /tmp/htxerr

  /dev/sdao Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdak Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdt  Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdaz Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdn  Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdv  Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdaj Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdal Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

   State: Open by: cde00 on 19 December 2016 02:48:46 

  This defect will go to Linux as even after making the below 2 changes
  in systemd resource limit, errors are seen:

  root@yellowbee:/etc/systemd/logind.conf.d# cat htxlogindcustom.conf
  [Login]
  UserTasksMax=infinity
  root@yellowbee:/etc/systemd/logind.conf.d# cat 
../system.conf.d/htxsystemdcustom.conf
  [Manager]
  DefaultTasksAccounting=yes
  DefaultTasksMax=infinity

  root@yellowbee:/etc/systemd/logind.conf.d#

  logind limit for MaxUserTask as well as systemd limit was made infinite.
  Please look defect SW363655 for more details and the suggestion given earlier 
by Linux team.

  errors are still seen. So, would ask Linux team to take a look and see if 
anything else is causing these
  errors.

  == Comment: #3 - Kevin W. Rudd  - 2016-12-19 17:34:27 ==
  It appears that the version of logind on this system does not support the 
value of "infinity", and is reverting to the default of 12288: 

  # cat /sys/fs/cgroup/pids/user.slice/user-0.slice/pids.max
  12288

  As a workaround until this can be resolved, specify an exact value.
  You can try using the current system thread-max va

[Touch-packages] [Bug 1654075] Re: multiarch support broken in yakkety-proposed

[Steve Langasek]

> libroken18-heimdal is already the newest version
(1.7~git20160703+dfsg-1).

This is not a bug in Ubuntu.  You have a locally-installed version that
is not from the Ubuntu archive.

You will need to downgrade libroken18-heimdal to the version from
Ubuntu, and then you can install the matching package for other
architectures.

** Changed in: heimdal (Ubuntu)
   Status: New => Invalid

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

Title:
  multiarch support broken in yakkety-proposed

Status in heimdal package in Ubuntu:
  Invalid

Bug description:
  In Ubuntu 16.10 amd64 system the 32-bit heimdal libraries packages
  cannot be installed together with 64-bit packages, i.e.:

  $ sudo apt install libroken18-heimdal libroken18-heimdal:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  libroken18-heimdal is already the newest version (1.7~git20160703+dfsg-1).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libroken18-heimdal : Breaks: libroken18-heimdal:i386 (!= 
1.7~git20160703+dfsg-1) but 1.7~git20150920+dfsg-4ubuntu1 is to be installed
   libroken18-heimdal:i386 : Breaks: libroken18-heimdal (!= 
1.7~git20150920+dfsg-4ubuntu1) but 1.7~git20160703+dfsg-1 is to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1654075/+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

Re: [Touch-packages] [Bug 1654416] Re: Requesting 2.4.44 build which includes fix for ITS#8185

[Ryan Tandy]

Hi Kartik and Hans,

I don't recommend merging the current unstable version as support for 
Heimdal was temporarily dropped. 2.4.44+dfsg-3 with Heimdal re-enabled 
will be uploaded soon on the Debian side and that should be a better 
candidate.

As usual, I will propose a merge once I'm happy with the state of the 
package in Debian, unless someone beats me to it. I can't make any 
promises with regards to the Zesty timeline, sorry.

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

Title:
  Requesting 2.4.44 build which includes fix for ITS#8185

Status in openldap package in Ubuntu:
  New

Bug description:
  I reported ITS#8185 to OpenLDAP which was fixed in the 2.4.43 release.
  There have been no OpenLDAP releases since 2.4.44 in February 2016, so
  it looks like things have been stable for a while. I'd like to request
  a refreshed slapd package for 2.4.44 (the most recent slapd package
  available on Ubuntu is 2.4.42 which dates back to August 2015). This
  would help me remove a manual workaround for the ITS#8185 issue, and
  users would also benefit from the number of fixes in 2.4.43 and
  2.4.44.

  http://www.openldap.org/software/release/changes.html

  purging stale pwdFailureTime attributes:
  
http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=8185;selectid=8185

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1654416/+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 1417309] Re: goa-daemon crashed with SIGSEGV in magazine_chain_pop_head()

[Bug Watch Updater]

** Changed in: gnome-online-accounts
   Status: Confirmed => Expired

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

Title:
  goa-daemon crashed with SIGSEGV in magazine_chain_pop_head()

Status in gnome-online-accounts:
  Expired
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Upgrade Ubuntu vidid and reboot and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-online-accounts 3.14.2-1
  Uname: Linux 3.19.0-031900rc7-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb  2 19:46:37 2015
  ExecutablePath: /usr/lib/gnome-online-accounts/goa-daemon
  InstallationDate: Installed on 2014-09-25 (130 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  ProcCmdline: /usr/lib/gnome-online-accounts/goa-daemon
  SegvAnalysis:
   Segfault happened at: 0x7f55b957e94d:mov(%rcx),%rax
   PC (0x7f55b957e94d) ok
   source "(%rcx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   __nptl_deallocate_tsd () at pthread_create.c:157
   start_thread (arg=0x7f5597182700) at pthread_create.c:322
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
  Title: goa-daemon crashed with SIGSEGV in __nptl_deallocate_tsd()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1417309/+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 1654688] [NEW] Printf does not properly justify non-ASCII characters

[William Andrea]

Public bug reported:

I have a script that outputs arbitrary Unicode characters in neat
columns, but for anything outside the Basic Latin range (i.e. codepoints
> 127), the justification is off. For example, both below commands
should output a leading space:

$ printf "%2s\n" 'a'
 a
$ printf "%2s\n" 'á'
á

The spacing problem starts between U+7F and U+80. If you try to print
two leading spaces, the same problem occurs between U+7FF and U+800.

This affects the binary /usr/bin/printf as well, but I'm not sure where
to report a bug for that.

Ubuntu version: 14.04.5
Bash version: 4.3-7ubuntu1.5 (latest)

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

** Description changed:

  I have a script that outputs arbitrary Unicode characters in neat
  columns, but for anything outside the Basic Latin range (i.e. codepoints
  > 127), the justification is off. For example, both below commands
  should output a leading space:
  
  $ printf "%2s\n" 'a'
-  a
+  a
  $ printf "%2s\n" 'á'
  á
  
- This seems to affect the binary /usr/bin/printf as well, but I'm not
- sure where to report a bug for that.
+ The spacing problem seems to start between U+7F and U+80, and occur
+ again between U+7FF and U+800.
+ 
+ This affects the binary /usr/bin/printf as well, but I'm not sure where
+ to report a bug for that.
  
  Ubuntu version: 14.04.5
  Bash version: 4.3-7ubuntu1.5 (latest)

** Description changed:

  I have a script that outputs arbitrary Unicode characters in neat
  columns, but for anything outside the Basic Latin range (i.e. codepoints
  > 127), the justification is off. For example, both below commands
  should output a leading space:
  
  $ printf "%2s\n" 'a'
   a
  $ printf "%2s\n" 'á'
  á
  
- The spacing problem seems to start between U+7F and U+80, and occur
- again between U+7FF and U+800.
+ The spacing problem starts between U+7F and U+80. If you try to print
+ two leading spaces, the same problem occurs between U+7FF and U+800.
  
  This affects the binary /usr/bin/printf as well, but I'm not sure where
  to report a bug for that.
  
  Ubuntu version: 14.04.5
  Bash version: 4.3-7ubuntu1.5 (latest)

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

Title:
  Printf does not properly justify non-ASCII characters

Status in bash package in Ubuntu:
  New

Bug description:
  I have a script that outputs arbitrary Unicode characters in neat
  columns, but for anything outside the Basic Latin range (i.e.
  codepoints > 127), the justification is off. For example, both below
  commands should output a leading space:

  $ printf "%2s\n" 'a'
   a
  $ printf "%2s\n" 'á'
  á

  The spacing problem starts between U+7F and U+80. If you try to print
  two leading spaces, the same problem occurs between U+7FF and U+800.

  This affects the binary /usr/bin/printf as well, but I'm not sure
  where to report a bug for that.

  Ubuntu version: 14.04.5
  Bash version: 4.3-7ubuntu1.5 (latest)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1654688/+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 1629782] Re: Hotspot crashes the device and reboots

[Jan Baarda]

E5 OTA-14 updated 7 Jan 2017: The hotspot problem as mentioned in #8
still exist. With exception of the fully loaded battery hang-up. The
battery can be fully loaded without hanging the system.

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

Title:
  Hotspot crashes the device and reboots

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  The device hangs and reboots after some tasks related to hotspot.

  There are a couple of ways that this bug occurred.

  1. While the hotspot is on, try to change hotspot settings like
  requiring passwords. Upon clicking the Change button, the bug occurs.
  (happens always)

  2. Turning on the hotspot from the settings app while the wifi is off
  the bug occurs. (happened once)

  
  Not sure what log will be helpful. Please let me know and I'll attach them.

  Device:
  bq E5 HD (OTA 13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629782/+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 1546223] Re: package openssh-client 1:6.9p1-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

[Joshua Powers]

>From log:

Dpkg: error processing package openssh-client (--configure):
 Package is in a very bad inconsistent state; You should
 Reinstall it before attempting configuration
Dpkg: dependency problems prevent configuration of ssh-askpass-gnome:
 Ssh-askpass-gnome depends on openssh-client | Ssh (> = 1: 1.2pre7-4) | 
Ssh-krb5; However:
  Package openssh-client is not configured yet.
  Package ssh is not installed.

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

Title:
  package openssh-client 1:6.9p1-2ubuntu0.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  At Start computer

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: openssh-client 1:6.9p1-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Feb  8 23:32:45 2016
  DuplicateSignature: package:openssh-client:1:6.9p1-2ubuntu0.1:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-03-27 (320 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.9p1-2ubuntu0.1
  SSHClientVersion: OpenSSH_6.9p1 Ubuntu-2ubuntu0.1, OpenSSL 1.0.2d 9 Jul 2015
  SourcePackage: openssh
  Title: package openssh-client 1:6.9p1-2ubuntu0.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to wily on 2015-10-23 (110 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1546223/+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 1546223] Re: package openssh-client 1:6.9p1-2ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

[Joshua Powers]

Thank you for your report.

This looks like a local configuration problem, rather than a bug in
Ubuntu. A dependency could not be satisfied and the openssh-client
package is in an inconsistent state. You should reinstall that package.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration problems, I'm marking this bug as 'Incomplete'. This helps
us to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then you may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package openssh-client 1:6.9p1-2ubuntu0.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  At Start computer

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: openssh-client 1:6.9p1-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Feb  8 23:32:45 2016
  DuplicateSignature: package:openssh-client:1:6.9p1-2ubuntu0.1:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-03-27 (320 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.9p1-2ubuntu0.1
  SSHClientVersion: OpenSSH_6.9p1 Ubuntu-2ubuntu0.1, OpenSSL 1.0.2d 9 Jul 2015
  SourcePackage: openssh
  Title: package openssh-client 1:6.9p1-2ubuntu0.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to wily on 2015-10-23 (110 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1546223/+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 1654416] Re: Requesting 2.4.44 build which includes fix for ITS#8185

[Hans Joachim Desserud]

Thanks for reporting.

I see that Debian has packaged openldap  2.4.44+dfsg-2
(https://tracker.debian.org/pkg/openldap). Normally it would be possible
to sync this package, but since the package includes some Ubuntu-
specific patches, someone will likely need to manually merge it.

** Tags added: needs-debian-merge upgrade-software-version

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

Title:
  Requesting 2.4.44 build which includes fix for ITS#8185

Status in openldap package in Ubuntu:
  New

Bug description:
  I reported ITS#8185 to OpenLDAP which was fixed in the 2.4.43 release.
  There have been no OpenLDAP releases since 2.4.44 in February 2016, so
  it looks like things have been stable for a while. I'd like to request
  a refreshed slapd package for 2.4.44 (the most recent slapd package
  available on Ubuntu is 2.4.42 which dates back to August 2015). This
  would help me remove a manual workaround for the ITS#8185 issue, and
  users would also benefit from the number of fixes in 2.4.43 and
  2.4.44.

  http://www.openldap.org/software/release/changes.html

  purging stale pwdFailureTime attributes:
  
http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=8185;selectid=8185

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1654416/+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 1654070] Re: sanity check can fail for packages missing dependencies

[Brian Murray]

** Changed in: unattended-upgrades (Ubuntu)
Milestone: None => ubuntu-17.03

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

Title:
  sanity check can fail for packages missing dependencies

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  I've been getting mail for days about pulseaudio-module-gconf and
  -module-zeroconf being upgraded, come to find out its not really
  happening.

  bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose
  Initial blacklisted packages: nvidia-304
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 
'o=Ubuntu,a=xenial-updates']
  Checking: pulseaudio-module-gconf ([])
  Checking: pulseaudio-module-zeroconf ([])
  pkgs that look like they should be upgraded: pulseaudio-module-gconf
  pulseaudio-module-zeroconf
  Fetched 0 B in 0s (0 B/s) 


  fetch.run() result: 0
  blacklist: ['nvidia-304']
  whitelist: []
  Checking the black and whitelist: pulseaudio-module-gconf
  Checking the black and whitelist: pulseaudio-module-zeroconf
  Packages that will be upgraded: pulseaudio-module-gconf 
pulseaudio-module-zeroconf
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  All upgrades installed
  InstCount=0 DelCount=0 BrokenCount=0
  Extracting content from 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 
12:27:12'
  Sending mail to 'bdmurray@bizarro.watchtower.local'
  mail returned: 0
  bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf
  pulseaudio-module-gconf:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3.1
Version table:
   1:8.0-0ubuntu3.1 500
  500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages
   *** 1:8.0-0ubuntu3 500
  500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Fnx]

Same issue her with an Acer VN7-572G:
Card: HDA Intel PCH 
   F1:  │ Chip: Realtek ALC255

lspci | grep -I audio
00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-LP HD 
Audio (rev 21)

cat /proc/asound/cards
 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xa432 irq 135

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1583088] Re: Randomly corrupt font / text / characters in Unity8

[dinamic]

hm.. ok.. so not sure it's Xmir, now i gedit corrupted my fonts, after
20h of using only ubuntu system apps and qt5 apps i just run "ubuntu-
app-launch gedit" and my fonts are corrupted now, i have to restart :D

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

Title:
  Randomly corrupt font / text / characters in Unity8

Status in Canonical System Image:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1583088] Re: Randomly corrupt font / text / characters in Unity8

[dinamic]

just my observation, i only see character corruption when using Xmir (on
desktop), i am now using unity8 for 20h and the fonts look ok, no
corruption.

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

Title:
  Randomly corrupt font / text / characters in Unity8

Status in Canonical System Image:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1651256] Re: add-apt-repository strangely adds in ubuntu

[Brian Murray]

** Changed in: software-properties (Ubuntu)
   Status: New => Triaged

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

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

Title:
  add-apt-repository strangely adds in ubuntu

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  bdmurray@flash:~$ sudo add-apt-repository ppa:graphics-drivers/ppa
  [sudo] password for bdmurray:
  Cannot add PPA: 'ppa:~graphics-drivers/ubuntu/ppa'.
  The team named '~graphics-drivers' has no PPA named 'ubuntu/ppa'
  Please choose from the following available PPAs:
   * 'ppa':  Proprietary GPU Drivers

  Notice how the first command was missing a ~ and while that got added
  so did "/ubuntu/".  Manually, adding in the ~ and the command worked.

  bdmurray@flash:~$ sudo add-apt-repository ppa:~graphics-drivers/ppa
   Fresh drivers from upstream, currently shipping Nvidia.
   ...

  This was on Ubuntu 16.04 with:

  bdmurray@flash:~$ apt-cache policy software-properties-common
  software-properties-common:
Installed: 0.96.20.4
Candidate: 0.96.20.4
Version table:
   *** 0.96.20.4 100
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1651256/+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 1654658] [NEW] package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[rusbunker]

Public bug reported:

setup printer samsumg scx-3200

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35
Uname: Linux 4.4.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Sat Jan  7 00:10:44 2017
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
InstallationDate: Installed on 2015-05-15 (601 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
MachineType: Gigabyte Technology Co., Ltd. GA-MA770-US3
Papersize: a4
PpdFiles: Samsung-SCX-3200-Series: Samsung SCX-3200, 2.0.0
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-58-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-58-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: cups
Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
UpgradeStatus: Upgraded to xenial on 2017-01-06 (0 days ago)
dmi.bios.date: 01/06/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FKb
dmi.board.name: GA-MA770-US3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFKb:bd01/06/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-US3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA770-US3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package package-from-proposed xenial

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in cups package in Ubuntu:
  New

Bug description:
  setup printer samsumg scx-3200

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35
  Uname: Linux 4.4.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Jan  7 00:10:44 2017
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2015-05-15 (601 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770-US3
  Papersize: a4
  PpdFiles: Samsung-SCX-3200-Series: Samsung SCX-3200, 2.0.0
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-58-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-58-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: Upgraded to xenial on 2017-01-06 (0 days ago)
  dmi.bios.date: 01/06/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FKb
  dmi.board.name: GA-MA770-US3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFKb:bd01/06/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-US3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770-US3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1654658/+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 1623666] Re: iOS10 will not connect to Ubuntu

[PascalC]

Temporary workaround from comment #27 works on kubuntu 16.10 to access
manually the iphone6S folders under ios10.2 .

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1654070] Re: sanity check can fail for packages missing dependencies

[Brian Murray]

Emails from unattended-upgrades are saner now with my patch:

Packages that were upgraded:

   
 libnss3 libnss3-nssdb  

   
Packages with upgradable origin but kept back:  

   
 pulseaudio-module-gconf pulseaudio-module-zeroconf

As opposed to:

Packages that were upgraded:

   
 libnss3 libnss3-nssdb pulseaudio-module-gconf  

   
 pulseaudio-module-zeroconf 

And then the pulseaudio packages not being installed.

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

Title:
  sanity check can fail for packages missing dependencies

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  I've been getting mail for days about pulseaudio-module-gconf and
  -module-zeroconf being upgraded, come to find out its not really
  happening.

  bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose
  Initial blacklisted packages: nvidia-304
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 
'o=Ubuntu,a=xenial-updates']
  Checking: pulseaudio-module-gconf ([])
  Checking: pulseaudio-module-zeroconf ([])
  pkgs that look like they should be upgraded: pulseaudio-module-gconf
  pulseaudio-module-zeroconf
  Fetched 0 B in 0s (0 B/s) 


  fetch.run() result: 0
  blacklist: ['nvidia-304']
  whitelist: []
  Checking the black and whitelist: pulseaudio-module-gconf
  Checking the black and whitelist: pulseaudio-module-zeroconf
  Packages that will be upgraded: pulseaudio-module-gconf 
pulseaudio-module-zeroconf
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  All upgrades installed
  InstCount=0 DelCount=0 BrokenCount=0
  Extracting content from 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 
12:27:12'
  Sending mail to 'bdmurray@bizarro.watchtower.local'
  mail returned: 0
  bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf
  pulseaudio-module-gconf:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3.1
Version table:
   1:8.0-0ubuntu3.1 500
  500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages
   *** 1:8.0-0ubuntu3 500
  500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+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 1654070] Re: sanity check can fail for packages missing dependencies

[Brian Murray]

** Summary changed:

- lies about upgrading pulseaudio-module-gconf
+ sanity check can fail for packages missing dependencies

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Triaged

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Medium

** Changed in: unattended-upgrades (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  sanity check can fail for packages missing dependencies

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  I've been getting mail for days about pulseaudio-module-gconf and
  -module-zeroconf being upgraded, come to find out its not really
  happening.

  bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose
  Initial blacklisted packages: nvidia-304
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 
'o=Ubuntu,a=xenial-updates']
  Checking: pulseaudio-module-gconf ([])
  Checking: pulseaudio-module-zeroconf ([])
  pkgs that look like they should be upgraded: pulseaudio-module-gconf
  pulseaudio-module-zeroconf
  Fetched 0 B in 0s (0 B/s) 


  fetch.run() result: 0
  blacklist: ['nvidia-304']
  whitelist: []
  Checking the black and whitelist: pulseaudio-module-gconf
  Checking the black and whitelist: pulseaudio-module-zeroconf
  Packages that will be upgraded: pulseaudio-module-gconf 
pulseaudio-module-zeroconf
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  All upgrades installed
  InstCount=0 DelCount=0 BrokenCount=0
  Extracting content from 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 
12:27:12'
  Sending mail to 'bdmurray@bizarro.watchtower.local'
  mail returned: 0
  bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf
  pulseaudio-module-gconf:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3.1
Version table:
   1:8.0-0ubuntu3.1 500
  500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages
   *** 1:8.0-0ubuntu3 500
  500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+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 1654651] [NEW] Dial-Pad often flickers up and down when opened - Aquaris E4.5

[Ragnar Dunbar]

Public bug reported:

When opening the Phone-App, about every second time, the dial-pad
initially flickers for about 1 to 2 seconds. It flickers up and down the
screen, like it is trying to find the right resolution for the screen. I
got the Aquaris E4.5 with OTA-12 and it has since then always been that
way (now OTA-14).

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1654651

Title:
  Dial-Pad often flickers up and down when opened - Aquaris E4.5

Status in dialer-app package in Ubuntu:
  New

Bug description:
  When opening the Phone-App, about every second time, the dial-pad
  initially flickers for about 1 to 2 seconds. It flickers up and down
  the screen, like it is trying to find the right resolution for the
  screen. I got the Aquaris E4.5 with OTA-12 and it has since then
  always been that way (now OTA-14).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1654651/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[Linuxrider]

Well of course it is not the default unlocking mechanism.
In my setup cryptroot-unlock is used to unlock remotely over dropbear.
Most probably the regex can adapted. But I have no experience with that.

When I encountered the issue I tested the script with standard busybox and it
worked. Then I compared the config of the two packages and found the two 
parameters
to be essential. It was the easiest way for me.
Of course I did not check for other side effects of the change.

A second command is not working with the initramfs busybox. It's "grep -Ez".
The z option is not present.

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Confirmed
Status in cryptsetup package in Ubuntu:
  Confirmed

Bug description:
  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

[Hans Joachim Desserud]

** Tags added: patch

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.

  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).

  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.

  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:

  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True

  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.

  Additional information:

  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2)
  unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeout)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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 1440294] Re: syncevolution - no export of tasks / memos Aquaris E4.5

[Ab]

This also affects contacts on Ubuntu Phone using baikal. Synchronization
works fine with Thunderbird an SoGO. But changes do not appear on the
Phone. Also changes are made on the phone won't be visible on baikal or
Thunderbird. Even if database of Ubuntu Phone is empty and doing a first
complete synchronization not all contacts will appear on the handset.
But deleting an item on Thunderbird and doing a synchonization with the
handset will bring the item back to thunderbird. After synchronizing
forward and backward (syncevolution displays changes that has been done)
no changes will be visible on the handset. Even deleting all the
contacts on the phone and doing a fresh synchronization will not bring
the entire data to the screen of the handset.

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

Title:
   syncevolution - no export of tasks / memos Aquaris E4.5

Status in syncevolution package in Ubuntu:
  Confirmed

Bug description:
  Phone: bq Aquaris E4.5 Ubuntu Edtion
  OS: Ubuntu 14.10(r20)
  SyncEvolution 1.5

  Can not export my Tasks and memos.
  Calendar and contacts export works!

  phablet@ubuntu-phablet:~$ syncevolution --print-databases
  CalDAV:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery ()

  CalDAVTodo:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery ()

  CalDAVJournal:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery ()

  CardDAV:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery ()

  Evolution Address Book = Evolution Contacts = evolution-contacts:
     Persönlich (system-address-book) 

  Evolution Calendar = evolution-calendar:
     Geburts- & Jahrestage (birthdays)
     Persönlich (system-calendar) 

  Evolution Task List = Evolution Tasks = evolution-tasks:
     Alarms (1427538744.24638.0@ubuntu-phablet)
     Persönlich (system-task-list) 
     Reminders (1427534898.18825.0@ubuntu-phablet)

  Evolution Memos = evolution-memos:
     Persönlich (system-memo-list) 

  phablet@ubuntu-phablet:~$ syncevolution --export tasks backend=evolution-tasks
  phablet@ubuntu-phablet:~$ file tasks
  tasks: empty

  phablet@ubuntu-phablet:~$ syncevolution --print-items backend
  =evolution-tasks

  

  phablet@ubuntu-phablet:~$ syncevolution --print-items backend
  =evolution-memos

  

  phablet@ubuntu-phablet:~$ click list
  com.canonical.payui   15.01.120
  com.canonical.scopes.bbc-sport1.03
  com.canonical.scopes.etsy 1.0.29
  com.canonical.scopes.euronews 0.5
  com.canonical.scopes.fitbit   1.0.40
  com.mikeasoft.podbird 0.5
  com.ubuntu.calendar   0.4.600
  com.ubuntu.camera 3.0.0.544
  com.ubuntu.developer.bobo1993324.qvbam0.1.3.1
  com.ubuntu.developer.liberavia.ardmediathek   0.1
  com.ubuntu.developer.majster-pl.utorch1.6
  com.ubuntu.developer.mzanetti.leo 0.2
  com.ubuntu.developer.ogra.rtv-de  0.3
  com.ubuntu.developer.tyrelparker0.metalhammer 0.2
  com.ubuntu.docviewer  0.3.109
  com.ubuntu.filemanager0.4.386
  com.ubuntu.gallery2.9.1.1183
  com.ubuntu.music  2.0.846
  com.ubuntu.reminders  0.5.380
  com.ubuntu.scopes.soundcloud  1.0.1-39
  com.ubuntu.scopes.vimeo   1.0.2-84
  com.ubuntu.telegram   1.1.2.95
  com.ubuntu.terminal   0.7.70
  dekko.dekkoproject0.5.1
  help.ubuntucoredev0.2
  noobslabscope.noobslab0.1.1
  omgubuntu-scope.mreese1.4
  com.canonical.scopes.bbc  1.7
  com.canonical.scopes.calls1.1
  com.canonical.scopes.cnet 0.6
  com.canonical.scopes.contacts 0.7
  com.canonical.scopes.dashboard1.6
  com.canonical.scopes.engadget 0.5
  com.canonical.scopes.events   1.0.11
  com.canonical.scopes.fbphotos 1.23
  com.canonical.scopes.flickr   1.0.24
  com.canonical.scopes.hints0.20
  com.canonical.scopes.holidays 1.1
  com.canonical.scopes.inrix1.0.28
  com.canonical.scopes.instagram1.0.15
  com.canonical.scopes.news 2.13
  com.canonical.scopes.photos   1.31
  com.canonical.scopes.photos-local 1.23
  com.canonical.scopes.poi  1.0.11
  com.canonical.scopes.shopping 1.9
  com.canonical.scopes.songkick 1.0.11
  com.canonical.scopes.tasks1.3
  com.canonical.scopes.texts1.0
  com.canonical.scopes.timeout  0.4.12
  com.canonical.scopes.transport-alerts 1.10
  com.canonical.scopes.twittertrending  1.0.9
  com.canonical.scopes.wikinear 1.0.9
  com.canonical.scopes.yelp 1.0.34
  com.canonical.unity-scope-nearby  0.8.8
  com.nokia.heremaps1.0.4
  com.ubuntu.developer.ken-vandine.pathwind 0.2.9
  com.ubuntu.developer.mzanetti.tagger  0.9.0.0
  com.ubuntu

[Touch-packages] [Bug 1654536] Re: unity-system-compositor crashed EGL_BAD_SURFACE

[Michał Sawicz]

Thing is this only ever happens on boot, and u-s-c gets restarted and
subsequently works fine, with `free` reporting 600MB memory free. The
leak would have to enormous as this happens within seconds from the
device booting.

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

Title:
  unity-system-compositor crashed EGL_BAD_SURFACE

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  unity-system-compositor sometimes aborts on latest xenial/arm64 on
  frieza:

  $ system-image-cli -i
  current build number: 116
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-06 09:43:26
  version version: 116
  version ubuntu: 20170106
  version device: 20161014.0
  version custom: 20170106

  /var/log/lightdm/unity-system-compositor.log has:
  ERROR: 
/build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233):
 Throw in function virtual void 
mir::graphics::android::FramebufferGLContext::swap_buffers() const
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Fri Jan  6 10:20:54 2017
  Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1480992789
  GraphicsCard:
   
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 11 --to-dm-fd 14 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ()
   std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 
<_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at 
../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121
   __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56
   __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42
   _dl_fini () at dl-fini.c:235
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.lightdm: lightdm 1.18.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+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 1652477] Re: Sync cpio 2.11+dfsg-6 (main) from Debian unstable (main)

[Dmitry Shachnev]

This bug was fixed in the package cpio - 2.11+dfsg-6
Sponsored for Jeremy Bicha (jbicha)

---
cpio (2.11+dfsg-6) unstable; urgency=medium

  * Man page for "mt" describes how to "fast erase"
Patch by Kees Cook
Add fix.mt-erase.manpage.patch
Closes: #770198
  * Backport "New options to create device and inode-independent
archives." from cpio 2.12
Patch by Chris Lamb
Add reproducible.patch
See #804063
  * Standards-Version: 3.9.8
  * Refresh patches

 -- Anibal Monsalve Salazar   Tue, 29 Nov 2016
12:31:53 +

** Changed in: cpio (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync cpio 2.11+dfsg-6 (main) from Debian unstable (main)

Status in cpio package in Ubuntu:
  Fix Released

Bug description:
  Please sync cpio 2.11+dfsg-6 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Resynchronise with Debian. Remaining changes:
  - Don't build a cpio-win32 package since mingw-w64 is in universe.

  cpio-win32 does not have any dependencies on universe packages:
  https://packages.debian.org/unstable/cpio-win32

  Changelog entries since current zesty version 2.11+dfsg-5ubuntu1:

  cpio (2.11+dfsg-6) unstable; urgency=medium

* Man page for "mt" describes how to "fast erase"
  Patch by Kees Cook
  Add fix.mt-erase.manpage.patch
  Closes: #770198
* Backport "New options to create device and inode-independent
  archives." from cpio 2.12
  Patch by Chris Lamb
  Add reproducible.patch
  See #804063
* Standards-Version: 3.9.8
* Refresh patches

   -- Anibal Monsalve Salazar   Tue, 29 Nov 2016
  12:31:53 +

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/1652477/+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 1651278] Re: systemd-sysv-generator does not fully translate facilities to targets

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

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

Title:
  systemd-sysv-generator does not fully translate facilities to targets

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  See the bug raised here:
  https://github.com/systemd/systemd/issues/4762

  and fixed upstream here:
  
https://github.com/systemd/systemd/commit/e932f5407ef5ad05d25d7dfefa4cda0fe81cc346

  In short, given a sysv-init script with valid LSB headers, one of which 
defines
  Required-Start: $foo
  and given that a foo.target target exists and is enabled, I would expect to 
see After=foo.target in the generated unit.

  In practice (on all versions of systemd prior to the unreleased v233)
  no other facilities beyond the pre-defined facilities ($network,
  $local_fs, etc) will be used in generating the systemd wrapper for the
  old sysv init script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1651278/+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 1654624] [NEW] dhcp apparmor profile comlains about lxd client

[Hadmut Danisch]

Public bug reported:

Hi,

strange problem recently occured:

I'm having some ubuntu machines running in LXD (nothing unusual, just
based on the regular ubuntu LXD images) on a ubuntu host. Worked well
for some time.

But now the host generates messages like


Jan  6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400
audit(1483726625.388:247): apparmor="DENIED" operation="file_perm"
namespace="root//lxd-rackadmin_" profile="/sbin/dhclient"
name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w"
denied_mask="w" fsuid=165536 ouid=0


in /var/log/kern.log. 

For some reason the apparmor running on the host interferes with the
containers.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-client 4.3.3-5ubuntu12.6
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Jan  6 19:19:12 2017
SourcePackage: isc-dhcp
UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago)

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  dhcp apparmor profile comlains about lxd client

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Hi,

  strange problem recently occured:

  I'm having some ubuntu machines running in LXD (nothing unusual, just
  based on the regular ubuntu LXD images) on a ubuntu host. Worked well
  for some time.

  But now the host generates messages like


  Jan  6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400
  audit(1483726625.388:247): apparmor="DENIED" operation="file_perm"
  namespace="root//lxd-rackadmin_" profile="/sbin/dhclient"
  name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w"
  denied_mask="w" fsuid=165536 ouid=0

  
  in /var/log/kern.log. 

  For some reason the apparmor running on the host interferes with the
  containers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12.6
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jan  6 19:19:12 2017
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1654624/+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 1654627] [NEW] Windows Rearrange and Resize without User Interactions

[bob]

Public bug reported:

!What I expected to happen

Windows stay in the same place with the same dimensions


!What happenes (happens) instead

Open windows will be re-arranged. Some will be resized, others maximized
and some hidden. If workspaces are enabled, some windows will be moved
to a different workspace.

Some of the ways to reproduce this:
* with workspaces enabled, merely switching workspaces (often but not always)
* with or without workspaces enabled, if the machine goes to sleep/suspend

$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

Problem reproduced on multiple machines less than a year old:
* System76 Lemur with external Dell monitor +
* 2016 HP Spectre x360 with a standard install of Ubuntu) with no external 
display

Frequency: very (essentially any time I'm away from a machine for more
than about ten minutes).


!Attempted Solutions

* Disable all hot corners/edges, etc. on both machines
* turned off the Lemur's internal display (the psuedo disable in System 
Settings > Display).
* turned off workspaces on Lemur

The only noticable difference was that it reduced the places I had to
hunt for the windows I need to move and resize to begin work again.

e.g. put my Development environment back in working order.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Jan  6 11:03:13 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.24, 4.4.0-51-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-53-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-57-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:2425]
InstallationDate: Installed on 2016-11-30 (37 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: System76, Inc. Lemur
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=5a96be43-7cc5-4afd-a77c-7269b753bae3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.06RS76
dmi.board.asset.tag: Tag 12345
dmi.board.name: Lemur
dmi.board.vendor: System76, Inc.
dmi.board.version: lemu6
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A:
dmi.product.name: Lemur
dmi.product.version: lemu6
dmi.sys.vendor: System76, Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Dec 26 09:27:59 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   41152 
 vendor DEL
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Windows Rearrange and Resize without User Interactions

Status in xorg package in Ubuntu:
  New

Bug description:
  !What I expected to happen

  Windows stay in the same place with the same dimensions

  
  !What happenes (happens) instead

  Open windows will be re-arranged. Some will be resized, others
  maximized and some hidden. If workspaces are enabled, some windows
  will be moved to a different workspace.

  Some of the ways t

[Touch-packages] [Bug 1654612] Re: Setting the event handler after the surface has been created does nothing

[Brandon Schaefer]

** Branch linked: lp:~brandontschaefer/mir/fix-spec-set-event-handle

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

Title:
  Setting the event handler after the surface has been created does
  nothing

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  In Progress

Bug description:
  Setting the surface spec for the event handler after the surface has
  been created does nothing.

  Reason:

  We dont set the event handler and recreate the input thread!

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1654612/+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 1643869] Re: Bluetooth wirh Citroen C4

[Cesar Herrera]

SORRY. The previous message was't to you.
Cesar

El viernes, 6 de enero de 2017 17:52:17 (CET), outlook  
escribió:
> In the past I said I wasn't able to pair the phone with a Citroen C4 and I 
> talked to you about it.
> I have reflashed the phone in Windows deleting personal data to an early 
> OTA (I don't remember now).
> I was able to pair the phone to the car. I tried to upgrade but it was no 
> possible, so I upgraded in Windows to another OTA mantaining the personal 
> data. Then it was possible to to upgrade to OTA 14. The  car continues 
> pairing. But when I receive or make a call it appears in the screen of the 
> car "SILENT" or something like that in Spaish and nor me nor the other 
> person ear anything.
> I don't know how to solve it.
> Cheers,
> Cesar
> 
> 


-- 
Enviado con Dekko desde mi dispositivo Ubuntu

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

Title:
  Cannot download files from hubic.com

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  With the hubiC app it is impossible to download a file. It is possible
  to send files there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1643869/+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 1654070] Re: lies about upgrading pulseaudio-module-gconf

[Brian Murray]

For some reason on this particular system libpulse0 from xenial-updates
isn't found.

bdmurray@flash:~$ apt-cache policy libpulse0
libpulse0:
  Installed: 1:8.0-0ubuntu3
  Candidate: 1:8.0-0ubuntu3
  Version table:
 *** 1:8.0-0ubuntu3 500
500 http://192.168.10.7/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

Although the gconf module update is found.

bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf
pulseaudio-module-gconf:
  Installed: 1:8.0-0ubuntu3
  Candidate: 1:8.0-0ubuntu3.1
  Version table:
 1:8.0-0ubuntu3.1 500
500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages
 *** 1:8.0-0ubuntu3 500
500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

Another system using the same mirror is fine.

 $ apt-cache policy libpulse0
libpulse0:
  Installed: 1:8.0-0ubuntu3.1
  Candidate: 1:8.0-0ubuntu3.1
  Version table:
 *** 1:8.0-0ubuntu3.1 500
500 http://192.168.10.7/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:8.0-0ubuntu3 500
500 http://192.168.10.7/ubuntu xenial/main amd64 Packages

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

Title:
  lies about upgrading pulseaudio-module-gconf

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  I've been getting mail for days about pulseaudio-module-gconf and
  -module-zeroconf being upgraded, come to find out its not really
  happening.

  bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose
  Initial blacklisted packages: nvidia-304
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 
'o=Ubuntu,a=xenial-updates']
  Checking: pulseaudio-module-gconf ([])
  Checking: pulseaudio-module-zeroconf ([])
  pkgs that look like they should be upgraded: pulseaudio-module-gconf
  pulseaudio-module-zeroconf
  Fetched 0 B in 0s (0 B/s) 


  fetch.run() result: 0
  blacklist: ['nvidia-304']
  whitelist: []
  Checking the black and whitelist: pulseaudio-module-gconf
  Checking the black and whitelist: pulseaudio-module-zeroconf
  Packages that will be upgraded: pulseaudio-module-gconf 
pulseaudio-module-zeroconf
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  All upgrades installed
  InstCount=0 DelCount=0 BrokenCount=0
  Extracting content from 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 
12:27:12'
  Sending mail to 'bdmurray@bizarro.watchtower.local'
  mail returned: 0
  bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf
  pulseaudio-module-gconf:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3.1
Version table:
   1:8.0-0ubuntu3.1 500
  500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages
   *** 1:8.0-0ubuntu3 500
  500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+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 1654612] Re: Setting the event handler after the surface has been created does nothing

[Brandon Schaefer]

** Changed in: mir
 Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)

** Changed in: mir
   Importance: Undecided => Medium

** Changed in: mir
   Status: New => In Progress

** Also affects: mir (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mir (Ubuntu)
   Status: New => In Progress

** Changed in: mir (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)

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

Title:
  Setting the event handler after the surface has been created does
  nothing

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  In Progress

Bug description:
  Setting the surface spec for the event handler after the surface has
  been created does nothing.

  Reason:

  We dont set the event handler and recreate the input thread!

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1654612/+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 1654070] Re: lies about upgrading pulseaudio-module-gconf

[Brian Murray]

Ah, running with --apt-debug is more informative.

bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade -v --apt-debug
Initial blacklisted packages: nvidia-304
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 
'o=Ubuntu,a=xenial-updates']
  pulseaudio-module-gconf:amd64 Depends on libpulse0 [ amd64 ] < 1:8.0-0ubuntu3 
> ( libs ) (= 1:8.0-0ubuntu3.1) can't be satisfied!
  pulseaudio-module-zeroconf:amd64 Depends on libpulse0 [ amd64 ] < 
1:8.0-0ubuntu3 > ( libs ) (= 1:8.0-0ubuntu3.1) can't be satisfied!
  pulseaudio-module-gconf:amd64 Depends on libpulse0 [ amd64 ] < 1:8.0-0ubuntu3 
> ( libs ) (= 1:8.0-0ubuntu3.1) can't be satisfied!
  pulseaudio-module-zeroconf:amd64 Depends on libpulse0 [ amd64 ] < 
1:8.0-0ubuntu3 > ( libs ) (= 1:8.0-0ubuntu3.1) can't be satisfied!
Packages that will be upgraded: pulseaudio-module-gconf 
pulseaudio-module-zeroconf
Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
All upgrades installed

If the dependencies can't be satisfied we shouldn't say that the package
will be upgraded.

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

Title:
  lies about upgrading pulseaudio-module-gconf

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  I've been getting mail for days about pulseaudio-module-gconf and
  -module-zeroconf being upgraded, come to find out its not really
  happening.

  bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose
  Initial blacklisted packages: nvidia-304
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 
'o=Ubuntu,a=xenial-updates']
  Checking: pulseaudio-module-gconf ([])
  Checking: pulseaudio-module-zeroconf ([])
  pkgs that look like they should be upgraded: pulseaudio-module-gconf
  pulseaudio-module-zeroconf
  Fetched 0 B in 0s (0 B/s) 


  fetch.run() result: 0
  blacklist: ['nvidia-304']
  whitelist: []
  Checking the black and whitelist: pulseaudio-module-gconf
  Checking the black and whitelist: pulseaudio-module-zeroconf
  Packages that will be upgraded: pulseaudio-module-gconf 
pulseaudio-module-zeroconf
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  All upgrades installed
  InstCount=0 DelCount=0 BrokenCount=0
  Extracting content from 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 
12:27:12'
  Sending mail to 'bdmurray@bizarro.watchtower.local'
  mail returned: 0
  bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf
  pulseaudio-module-gconf:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3.1
Version table:
   1:8.0-0ubuntu3.1 500
  500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages
   *** 1:8.0-0ubuntu3 500
  500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+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 1522675] Re: Needless scary warning: Can't drop privileges for downloading : _apt user not allowed

[Bug Watch Updater]

** Changed in: apt (Debian)
   Status: Fix Committed => Fix Released

-- 
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/1522675

Title:
  Needless scary warning: Can't drop privileges for downloading : _apt
  user not allowed

Status in apt package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1637731] Re: [SRU] Update to 2.48.2 in Xenial

[Brian Murray]

Hello Amr, or anyone else affected,

Accepted glib2.0 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.48.2-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  [SRU] Update to 2.48.2 in Xenial

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed

Bug description:
  [Description]
  Upstream have released a new bugfix release 2.48.2.

  [Changes]
  https://git.gnome.org/browse/glib/tree/NEWS?h=glib-2-48

  Bugs fixed:
   547200 g_utf8_find_next_char() issues
   673101 resource compiler dependency generation not working for generated 
files
   700756 GFile.new_for_path arguments misses (type filename) annotation
   725902 build: simplify dtrace configuration
   728207 gsocketservice: Documentation does not mention that is already 
active...
   730187 glocalfileoutputstream: Fix an FD leak in an error path
   746685 Doc: clarify that g_variant_get_data() can be used instead of 
g_varia...
   750257 GSettings changed signal should clearly state the order required
   753231 Memory is potentially used after free
   755439 Memory leak in gdbusproxy.c
   760115 gtestutils: add missing dash in seed argument's --help documentation
   760423 gio-querymodules prints error messages as question marks on some 
locales
   761810 gio: Support using GDBusObjectManagerServer at path ‘/’
   766211 Fix the upper bound in g_unichar_iswide_bsearch
   766899 Superflous HTML/XML comments in GDBusProxyTypeFunc documentation 
string
   766933 GSocketAddress leaks in 
gnetworkmonitornetlink.c:read_netlink_messages()
   767172 docs: Move GIO_USE_VFS to "okay for production" section
   767218 Remove a UTF-8 ellipsis from gsignal.h
   767824 Some UTC timezones incorrectly recognized on Windows 7
   767949 Typos in glib docs
   768453 Gdbus test: compilation fails due to -Werror=format-y2k errors
   768504 keyfile: g_key_file_get_double behavior doesn't follow documentation
   768551 Test failure: test_socket_address_to_string
   768560 gio/tests/gsettings: fix GSettings reference leaks in some tests
   768806 gdbus tool must swallow -- argument
   769027 Docs misleadingly imply G_CHECKSUM_SHA512 is available since 2.16

  Translations updated:
   Indonesian
   Portuguese
   Turkish

  [QA, testing, regression potential]
  Under the GNOME MRE, you can believe all bugs upstream says are fixed are 
really fixed. Just test the system and make sure there are no regressions (e.g. 
look at errors.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1637731/+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 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package

[Brian Murray]

Hello Sadi, or anyone else affected,

Accepted glib2.0 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.48.2-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  Files in the root of a folder on another partition symlinked to user's
  home cannot be moved to trash because of a patch in this package

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Yakkety:
  Fix Committed

Bug description:
  [ Description ]

  Can't trash files if the directory they are in is a symlink to another
  device

  [ QA ]

  Steps:
  1. Install system and partition disk into root and data partitions
  2. create ~/Data folder, and mount data partition on it
  3. create symlinks for ~/whatever/ to ~/Data/something/
  4. delete files directly inside ~/whatever/

  What happen:
  Then Nautilus says: "File can't be put in the trash. Do you want to delete it 
immediately?".

  What should happen:
  The files moved into Trash.

  [ Regression potential ]

  The proposed fix uses g_stat instead of g_stat to follow symlinks, so
  we know where to place the trash (you can't rename() across
  filesystems). If that is wrong, then it could regress trashing other
  kinds of files.

  [ Original ]

  I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1.

  I've reported this bug (or marked as "it affects me") in a couple of
  other places before I've finally discovered that this is the package
  that's causing this problem, which unfortunately has been around for a
  couple of years now.

  This bug has been reported upstream as well, but it's just taking very
  very long to arrive at a decision and take action it seems.

  Apparently one of the patches
  (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix-
  trashing-on-overlayfs.patch/) which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz)
  to the original package which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz)
  is the root cause of this annoying problem.

  As I prefer keeping one patition for the root filesystem (/), one
  partition for user settings (/home) and one partition for user data
  (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which
  are simply symlinked to my home folder for ease of use, I cannot move
  any file to the trash in the root of these folders when I access them
  from my home folder or nautilus sidebar.

  This problem doesn't affect folders at all, nor any other files in
  subfolders, etc.

  So I was wondering if Ubuntu devs can leave out that particular patch
  when building this package for Ubuntu - if it doesn't cause more harm,
  which I doubt.

  Otherwise, I would appreciate if I could learn how to do it myself:
  how can I (as an end-user) compile the contents of
  "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in
  "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on-
  overlayfs.patch"?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+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 1643869] Bluetooth wirh Citroen C4

[Cesar Herrera]

In the past I said I wasn't able to pair the phone with a Citroen C4 and I 
talked to you about it.
I have reflashed the phone in Windows deleting personal data to an early 
OTA (I don't remember now).
I was able to pair the phone to the car. I tried to upgrade but it was no 
possible, so I upgraded in Windows to another OTA mantaining the personal 
data. Then it was possible to to upgrade to OTA 14. The  car continues 
pairing. But when I receive or make a call it appears in the screen of the 
car "SILENT" or something like that in Spaish and nor me nor the other 
person ear anything.
I don't know how to solve it.
Cheers,
Cesar


-- 
Enviado con Dekko desde mi dispositivo Ubuntu

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

Title:
  Cannot download files from hubic.com

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  With the hubiC app it is impossible to download a file. It is possible
  to send files there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1643869/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

[Erik Mouw]

I have also tried to let the systemd unit file for this service WantedBy the 
umount.target.
According to the systemd documentation that should make it run before the 
filesystems
are unmounted, but apparently that doesn't work. systemctl list-dependencies 
still shows
that the unattended-upgrade.service reverse depends on the shutdown.target.

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.

  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).

  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.

  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:

  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True

  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.

  Additional information:

  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2)
  unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeout)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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 1654600] [NEW] unattended-upgrade-shutdown hangs when /var is a separate filesystem

[Erik Mouw]

Public bug reported:

The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
process during shutdown. This unit file is running together with all filesystem
unmount services.

The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in progress
and the service will wait until it finishes (and therefore automatically wait at
shutdown).

However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5 seconds, 
and
tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
exit and the system will continue shutdown.

The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:

while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True

The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
File descriptors are just C file descriptors, so they are always positive 
integers.
The code should check the result to be negative, not positive. I have attached 
a patch
to reverse the logic.

Additional information:

1)
Description:Ubuntu 16.04.1 LTS
Release:16.04

2)
unattended-upgrades:
  Installed: 0.90ubuntu0.3
  Candidate: 0.90ubuntu0.3
  Version table:
 *** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
100 /var/lib/dpkg/status
 0.90 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
3)
Fast reboot
4)
Very slow reboot (after a 10 minutes timeout)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "Reverse logic"
   
https://bugs.launchpad.net/bugs/1654600/+attachment/4800928/+files/unattended-upgrade-shutdown.diff

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.

  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).

  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.

  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:

  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True

  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.

  Additional information:

  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2)
  unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeo

[Touch-packages] [Bug 1450642] Re: seccomp missing many new syscalls

[Jamie Strandboge]

I've completed my verification of 2.1.1-1ubuntu1~trusty3 SRU for amd64
and i386.

I followed the test plan for this and bug #1653487 with additional
manual testing for lxc and docker debs along with various snaps (ufw,
lxd, docker (amd64 only since docker upstream doesn't provide 32 bit
images; also see unrelated bug #1654590), etc and found no regressions.

NOTE: I discovered that the systemd upstart job won't start if cgmanager
(pulled in by lxc) is installed. tvoss and I discussed and he will
followup with Foundations. This is unrelated to this SRU but may be
useful to know for testers.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  seccomp missing many new syscalls

Status in Snappy:
  Fix Released
Status in Snappy 15.04 series:
  Fix Released
Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Trusty:
  Fix Committed
Status in libseccomp source package in Vivid:
  Fix Released
Status in libseccomp source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Several syscalls were discovered to be missing when using the launcher on 
snappy. These should be added so we may properly support seccomp filtering.

  [Test Case]
  seccomp itself has a comprehensive testsuite, and while it doesn't fail the 
build, regressions can be seen by looking at the build log. Eg:

  Regression Test Summary
  tests run: 6494
  tests skipped: 52
  tests passed: 6494
  tests failed: 0
  tests errored: 0

  Furthermore, on a snappy system, perform:
  # Note, for the 14.04 SRU, you'll have to install snapd from trusty-proposed 
and reboot into the lts kernel that it installs
  $ sudo snap install hello-world
  $ hello-world.env

  It should show the environment. On an arm system with 2.1.1-1 from the 
archive, this will fail due to a seccomp denial:
  audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 
pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 
compat=0 ip=0xb6fb0bd6 code=0x0

  (note, snappy images have a ppa fix for this, see notes below).

  To test the segfault fix, do:
  $ scmp_sys_resolver 1024
  Segmentation fault

  It should return:
  $ scmp_sys_resolver 1024
  UNKNOWN

  For the new 3.19 syscalls:
  $ scmp_sys_resolver getrandom
  -1

  it should return something like (actual number depends on arch, this is on 
armhf):
  $ scmp_sys_resolver getrandom
  384

  For the 14.04 SRU, test the following syscalls (expected results on
  amd64 are shown):

  $ scmp_sys_resolver getrandom
  318
  $ scmp_sys_resolver membarrier
  324
  $ scmp_sys_resolver userfaultfd
  323
  $ scmp_sys_resolver mlock2
  325

  autopkgtests for libseccomp have been added as part of this update to verify 
that the library recognizes all the syscalls from 3.19 and the private 
syscalls. These tests can be run like so (assuming you are in the unpacked 
source and the binaries are in ../binary):
  $ export REL=vivid
  $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source 
../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot 
autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED"

  Alternatively, if you don't have autopkgtest setup, you can do:
  $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev 
seccomp
  $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter
  ...
  PASS
  $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh 
./debian/tests/test-scmp_sys_resolver
  ...
  PASS

  Lastly, seccomp is used by lxc. lxc can be tested by using the test
  case as outlined in step 4 of
  https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only.

  [Regression Potential]
  If the above tests, regression potential is considered low. Unknown syscalls 
will continue to be handled as before.

  Description of changes:
  add finit_module:
  
https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15

  sync the syscall table entries - 3.16
  
https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75
  
https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4
  
https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd
  
https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb
  
https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718
  
https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a

  sync the syscall table entries - 3.17
  
https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9

  sync the syscall table entries - 3.19
  
https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3

  This shou

[Touch-packages] [Bug 1653487] Re: seccomp argument filtering not working on trusty amd64

[Jamie Strandboge]

I've completed my verification of 2.1.1-1ubuntu1~trusty3 SRU for amd64
and i386.

I followed the test plan for this and bug #1653487 with additional
manual testing for lxc and docker debs along with various snaps (ufw,
lxd, docker (amd64 only since docker upstream doesn't provide 32 bit
images; also see unrelated bug #1654590), etc and found no regressions.

Build logs:

armhf:
Regression Test Summary
 tests run: 4115
 tests skipped: 79
 tests passed: 4115
 tests failed: 0
 tests errored: 0

i386:
Regression Test Summary
 tests run: 6573
 tests skipped: 51
 tests passed: 6573
 tests failed: 0
 tests errored: 0

amd64:
Regression Test Summary
 tests run: 6577
 tests skipped: 53
 tests passed: 6577
 tests failed: 0
 tests errored: 0


On amd64 and i386, the snapd testsuite passes with the updated seccomp packages:
$ debian/rules build
...
# TOTAL: 21
# PASS:  21
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
...

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

Title:
  seccomp argument filtering not working on trusty amd64

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was 
exposed in the snapd build testsuite when run on amd64. It has to do with 
libseccomp's state machine not always working correctly when using argument 
filtering and there were no tests for this particular failure in 2.1. Once 
19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is 
applied to 2.1, you see the failures. Simple seccomp filters that just use the 
syscall name are not affected by the bug and we (currently) only use seccomp 
arg filtering in one interface which is why Tyler's testing of 
2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do 
exercise it, but seccomp argument filtering wasn't added until series 16 and 
seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine 
and all of snap-confine's arg filtering tests to trusty revealed the bug in 
seccomp 2.1.

  [Test Case]
  A test case is included in the build in 
debian/patches/bpf-accumulator-check.patch 
(19e6c4aeca9818c4b288b09911dfa4be9a831236). You can check the amd64 build log 
to verify no failures.

  You can also run the snapd testsuite:
  0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev 
seccomp
  1. enable deb-src trusty-proposed to get snapd 2.20
  2. apt-get source snapd
  3. cd ./snapd-2.20*
  4. apt-get build-dep snapd
  5. install libseccomp2 libseccomp-dev from trusty release (to demonstrate the 
problem)
  6. debian/rules build # this should fail on amd64
  ...
  FAIL: test_restrictions_working_args
  ...
  7. install libseccomp2 libseccomp-dev from trusty-proposed
  8. debian/rules clean ; debian/rules build # this should pass

  In addition, follow the testing procedures as outlined in bug #1450642

  [Regression Potential]

  The patch to fix this issue required several other supporting patches.
  This patches applied cleanly to trusty and the patches themselves are
  well tested under upstream and 16.04+. The regression potential should
  be relatively low since the testsuite during the build shows no errors
  or failures and snapd has a big testsuite. Manually testing with snaps
  and lxc (the biggest consumers of libseccomp) and running the
  libseccomp autopkgtests also shows no issues.

  = Original description =
  The snapd build on trusty for amd64 fails with the following error:
  """
  make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests'
  ...
  PASS: test_restrictions_working
  FAIL: test_restrictions_working_args
  """
  (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913)

  The same build works for i386 and armhf.

  I can reproduce this in a trusty chroot, upon further investigation it looks
  like the version of libseccomp (2.1.1) in trusty-proposed is the culprit.

  When I upgrade:
  """
  Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 
2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 
2.2.3-2ubuntu1~ubuntu14.04.1)
  
  all tests run fine. It looks like an issue with seccomp argument filtering 
(bpf) on 64 bit systems.
  This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include 
the missing fix,
  however I have not looked in detail what patch exactly we may need.

  Fwiw, we don't see this in spread because we build the package in the
  spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg-
  buildpackage` and we do not run the integration tests of snap-confine
  in anything else beside the package build (until
  https://github.com/snapcore/snapd/pull/2433/files is merged).

To manage notifications about this bug go to:
h

[Touch-packages] [Bug 1653487] Re: seccomp argument filtering not working on trusty amd64

[Jamie Strandboge]

Furthermore, I triggered a rebuild for snapd/amd64, it succeeded and is
in trusty-proposed now.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  seccomp argument filtering not working on trusty amd64

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was 
exposed in the snapd build testsuite when run on amd64. It has to do with 
libseccomp's state machine not always working correctly when using argument 
filtering and there were no tests for this particular failure in 2.1. Once 
19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is 
applied to 2.1, you see the failures. Simple seccomp filters that just use the 
syscall name are not affected by the bug and we (currently) only use seccomp 
arg filtering in one interface which is why Tyler's testing of 
2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do 
exercise it, but seccomp argument filtering wasn't added until series 16 and 
seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine 
and all of snap-confine's arg filtering tests to trusty revealed the bug in 
seccomp 2.1.

  [Test Case]
  A test case is included in the build in 
debian/patches/bpf-accumulator-check.patch 
(19e6c4aeca9818c4b288b09911dfa4be9a831236). You can check the amd64 build log 
to verify no failures.

  You can also run the snapd testsuite:
  0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev 
seccomp
  1. enable deb-src trusty-proposed to get snapd 2.20
  2. apt-get source snapd
  3. cd ./snapd-2.20*
  4. apt-get build-dep snapd
  5. install libseccomp2 libseccomp-dev from trusty release (to demonstrate the 
problem)
  6. debian/rules build # this should fail on amd64
  ...
  FAIL: test_restrictions_working_args
  ...
  7. install libseccomp2 libseccomp-dev from trusty-proposed
  8. debian/rules clean ; debian/rules build # this should pass

  In addition, follow the testing procedures as outlined in bug #1450642

  [Regression Potential]

  The patch to fix this issue required several other supporting patches.
  This patches applied cleanly to trusty and the patches themselves are
  well tested under upstream and 16.04+. The regression potential should
  be relatively low since the testsuite during the build shows no errors
  or failures and snapd has a big testsuite. Manually testing with snaps
  and lxc (the biggest consumers of libseccomp) and running the
  libseccomp autopkgtests also shows no issues.

  = Original description =
  The snapd build on trusty for amd64 fails with the following error:
  """
  make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests'
  ...
  PASS: test_restrictions_working
  FAIL: test_restrictions_working_args
  """
  (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913)

  The same build works for i386 and armhf.

  I can reproduce this in a trusty chroot, upon further investigation it looks
  like the version of libseccomp (2.1.1) in trusty-proposed is the culprit.

  When I upgrade:
  """
  Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 
2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 
2.2.3-2ubuntu1~ubuntu14.04.1)
  
  all tests run fine. It looks like an issue with seccomp argument filtering 
(bpf) on 64 bit systems.
  This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include 
the missing fix,
  however I have not looked in detail what patch exactly we may need.

  Fwiw, we don't see this in spread because we build the package in the
  spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg-
  buildpackage` and we do not run the integration tests of snap-confine
  in anything else beside the package build (until
  https://github.com/snapcore/snapd/pull/2433/files is merged).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1653487/+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 1654594] [NEW] Size set in Window{} when app running in a trust session is half accepted

[Florian Boucault]

Public bug reported:

When shown in a trust session, a Window {} of a QML app has its size set
externally. However if this app programatically sets the width/height of
the window then the contentItem is resized when in fact nothing should
happen.

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

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

Title:
  Size set in Window{} when app running in a trust session is half
  accepted

Status in unity8 package in Ubuntu:
  New

Bug description:
  When shown in a trust session, a Window {} of a QML app has its size
  set externally. However if this app programatically sets the
  width/height of the window then the contentItem is resized when in
  fact nothing should happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1654594/+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 1649932] Re: crashes when opening from the peer picker on unity8 desktop

[Launchpad Bug Tracker]

** Branch linked: lp:camera-app/staging

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

Title:
  crashes when opening from the peer picker on unity8 desktop

Status in camera-app package in Ubuntu:
  New

Bug description:
  If camera-app is already running when selected in the peer picker, it
  switches to picking mode just fine.  However if camera-app is not
  running, it crashes on startup when selected from the peer picker.

  In order to get camera-app to show up in the peer picker, you need a
  deb built from my branch[1] and run the hook[2] manually once after
  installing the deb.

  1. 
https://code.launchpad.net/~ken-vandine/camera-app/content-hub_and_add-profile/+merge/313232
  2. /usr/lib/x86_64-linux-gnu/content-hub/content-hub-peer-hook

  upstart log:

  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  Import path added "/usr/lib/x86_64-linux-gnu/camera-app"
  Camera app directory "/usr/share/camera-app/"
  qq= QDeclarativeCamera_QML_37(0x224) 0x248c610
  Focus mode selection is not supported
  No media control support for org.qt-project.qt.cameraflashcontrol/5.0
  No flash control support
  No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
  No exposure control support
  No media control support for org.qt-project.qt.cameraflashcontrol/5.0
  No flash control support
  No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
  No exposure control support
  QFileSystemWatcher::removePaths: list is empty
  DelegateModel::item: index out range 0 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1649932/+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 1649932] Re: crashes when opening from the peer picker on unity8 desktop

[Florian Boucault]

Fix is at http://bazaar.launchpad.net/~phablet-team/camera-
app/staging/revision/726

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

Title:
  crashes when opening from the peer picker on unity8 desktop

Status in camera-app package in Ubuntu:
  New

Bug description:
  If camera-app is already running when selected in the peer picker, it
  switches to picking mode just fine.  However if camera-app is not
  running, it crashes on startup when selected from the peer picker.

  In order to get camera-app to show up in the peer picker, you need a
  deb built from my branch[1] and run the hook[2] manually once after
  installing the deb.

  1. 
https://code.launchpad.net/~ken-vandine/camera-app/content-hub_and_add-profile/+merge/313232
  2. /usr/lib/x86_64-linux-gnu/content-hub/content-hub-peer-hook

  upstart log:

  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  Import path added "/usr/lib/x86_64-linux-gnu/camera-app"
  Camera app directory "/usr/share/camera-app/"
  qq= QDeclarativeCamera_QML_37(0x224) 0x248c610
  Focus mode selection is not supported
  No media control support for org.qt-project.qt.cameraflashcontrol/5.0
  No flash control support
  No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
  No exposure control support
  No media control support for org.qt-project.qt.cameraflashcontrol/5.0
  No flash control support
  No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
  No exposure control support
  QFileSystemWatcher::removePaths: list is empty
  DelegateModel::item: index out range 0 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1649932/+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 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647485/+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 1024765] Re: ipa-client-install fails at certutil stage because /etc/pki doesn't exist

[Bug Watch Updater]

** Changed in: nss (Debian)
   Status: Confirmed => Fix Released

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

Title:
  ipa-client-install fails at certutil stage because /etc/pki doesn't
  exist

Status in freeipa package in Ubuntu:
  Fix Released
Status in nss package in Ubuntu:
  Fix Released
Status in nss package in Debian:
  Fix Released

Bug description:
  Dear Colleagues,

  ipa-client-install fails at the import stage of the freeipa server
  cert.

  Created /etc/ipa/default.conf
  New SSSD config will be created.
  Configured /etc/sssd/sssd.conf
  Traceback (most recent call last):
File "/usr/sbin/ipa-client-install", line 1292, in 
  sys.exit(main())
File "/usr/sbin/ipa-client-install", line 1279, in main
  rval = install(options, env, fstore, statestore)
File "/usr/sbin/ipa-client-install", line 1124, in install
  run(["/usr/bin/certutil", "-A", "-d", "/etc/pki/nssdb", "-n", "IPA CA", 
"-t", "CT,C,C", "-a", "-i", "/etc/ipa/ca.crt"])
File "/usr/lib/python2.7/dist-packages/ipapython/ipautil.py", line 273, in 
run
  raise CalledProcessError(p.returncode, args)
  subprocess.CalledProcessError: Command '/usr/bin/certutil -A -d 
/etc/pki/nssdb -n IPA CA -t CT,C,C -a -i /etc/ipa/ca.crt' returned non-zero 
exit status 255

  
  It looks like the patch create_client_dirs.patch needs to be refreshed to:

  1. check if /etc/pki exists
  2. if not, create it

  this is important especially for debian and ubuntu, because /etc/pki
  is/was fedora/rhel specific

  Regards,

  \sh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1024765/+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 1654592] [NEW] package software-properties-gtk 0.96.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Marco]

Public bug reported:

no instala

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: software-properties-gtk 0.96.20.5
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Wed Jan  4 14:56:57 2017
DuplicateSignature:
 package:software-properties-gtk:0.96.20.5
 Setting up software-properties-gtk (0.96.20.5) ...
 Segmentation fault (core dumped)
 dpkg: error processing package software-properties-gtk (--configure):
  subprocess installed post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2017-01-04 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: software-properties
Title: package software-properties-gtk 0.96.20.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package software-properties-gtk 0.96.20.5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in software-properties package in Ubuntu:
  New

Bug description:
  no instala

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: software-properties-gtk 0.96.20.5
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Wed Jan  4 14:56:57 2017
  DuplicateSignature:
   package:software-properties-gtk:0.96.20.5
   Setting up software-properties-gtk (0.96.20.5) ...
   Segmentation fault (core dumped)
   dpkg: error processing package software-properties-gtk (--configure):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2017-01-04 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: software-properties
  Title: package software-properties-gtk 0.96.20.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1654592/+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 1266787] Re: Autopilot tests pass in emulator, please consider automating their execution with emulator

[Dimitri John Ledkov]

Hello from 2017. emulator does not work since about 2015 and this app
was removed from the archive after vivid.

** Changed in: friends-app (Ubuntu)
   Status: New => Invalid

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

Title:
  Autopilot tests pass in emulator, please consider automating their
  execution with emulator

Status in friends-app package in Ubuntu:
  Invalid

Bug description:
  I can execute autopilot address book app testsuite like so:

  $ bzr branch lp:~xnox/ubuntu-test-cases/touch-emulator
  $ cd touch-emulator
  $ ./scripts/provision-emulator.sh
  $ ./scripts/run-test.sh deb friends-app-autopilot friends_app

  On the desktop, on a headless server, on a cloud VM.

  Please consider automating test execution with emulator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1266787/+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 1654310] Re: lxcfs: update the 'btime' field in /proc/stat to reflect guest boot time not host

[Dimitri John Ledkov]

** Package changed: make-dfsg (Ubuntu) => lxcfs (Ubuntu)

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

Title:
  lxcfs: update the 'btime' field in /proc/stat to reflect guest boot
  time not host

Status in lxcfs package in Ubuntu:
  Triaged

Bug description:
  The 'btime' field in /proc/stat reflects the host boot time and not
  the time that the guest container has started.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1654310/+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 1654581] Re: unity8 crashed with SIGSEGV in Screen::makeCurrent()

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: qtmir (Ubuntu)
   Status: New => Confirmed

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

Title:
  unity8 crashed with SIGSEGV in Screen::makeCurrent()

Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using latest zesty, also reproduced in xenial+overlay.

  All I did is leave Unity 8 running for ~30 minutes and it crashed.
  This crash is reproducible with or without running Xmir. Unity 8 just
  suddenly restarts.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20161215-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Fri Jan  6 09:37:16 2017
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1481818649
  InstallationDate: Installed on 2016-06-24 (196 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160623)
  ProcCmdline: unity8 --mode=full-shell
  ProcCwd: /home/lrp
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   Screen::makeCurrent() () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
   MirOpenGLContext::makeCurrent(QPlatformSurface*) () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
   QOpenGLContext::makeCurrent(QSurface*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: unity8 crashed with SIGSEGV in Screen::makeCurrent()
  UpgradeStatus: Upgraded to zesty on 2016-10-27 (70 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1654581/+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 1654581] Re: unity8 crashed with SIGSEGV in Screen::makeCurrent()

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity8 (Ubuntu)
   Status: New => Confirmed

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

Title:
  unity8 crashed with SIGSEGV in Screen::makeCurrent()

Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using latest zesty, also reproduced in xenial+overlay.

  All I did is leave Unity 8 running for ~30 minutes and it crashed.
  This crash is reproducible with or without running Xmir. Unity 8 just
  suddenly restarts.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20161215-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Fri Jan  6 09:37:16 2017
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1481818649
  InstallationDate: Installed on 2016-06-24 (196 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160623)
  ProcCmdline: unity8 --mode=full-shell
  ProcCwd: /home/lrp
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   Screen::makeCurrent() () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
   MirOpenGLContext::makeCurrent(QPlatformSurface*) () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
   QOpenGLContext::makeCurrent(QSurface*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: unity8 crashed with SIGSEGV in Screen::makeCurrent()
  UpgradeStatus: Upgraded to zesty on 2016-10-27 (70 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1654581/+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 1654581] Re: unity8 crashed with SIGSEGV in Screen::makeCurrent()

[Stephen M. Webb]

** Also affects: qtmir (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  unity8 crashed with SIGSEGV in Screen::makeCurrent()

Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using latest zesty, also reproduced in xenial+overlay.

  All I did is leave Unity 8 running for ~30 minutes and it crashed.
  This crash is reproducible with or without running Xmir. Unity 8 just
  suddenly restarts.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20161215-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Fri Jan  6 09:37:16 2017
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1481818649
  InstallationDate: Installed on 2016-06-24 (196 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160623)
  ProcCmdline: unity8 --mode=full-shell
  ProcCwd: /home/lrp
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   Screen::makeCurrent() () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
   MirOpenGLContext::makeCurrent(QPlatformSurface*) () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
   QOpenGLContext::makeCurrent(QSurface*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: unity8 crashed with SIGSEGV in Screen::makeCurrent()
  UpgradeStatus: Upgraded to zesty on 2016-10-27 (70 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1654581/+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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Barry Warsaw]

I've tested the PPA package and am satisfied that it restores CNAME
resolution in schroots without any observed regression otherwise.  I
will upload it momentarily.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+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 1654581] Re: unity8 crashed with SIGSEGV in Screen::makeCurrent()

[Larry Price]

** Information type changed from Private to Public

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

Title:
  unity8 crashed with SIGSEGV in Screen::makeCurrent()

Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using latest zesty, also reproduced in xenial+overlay.

  All I did is leave Unity 8 running for ~30 minutes and it crashed.
  This crash is reproducible with or without running Xmir. Unity 8 just
  suddenly restarts.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20161215-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Fri Jan  6 09:37:16 2017
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1481818649
  InstallationDate: Installed on 2016-06-24 (196 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160623)
  ProcCmdline: unity8 --mode=full-shell
  ProcCwd: /home/lrp
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   Screen::makeCurrent() () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
   MirOpenGLContext::makeCurrent(QPlatformSurface*) () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
   QOpenGLContext::makeCurrent(QSurface*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: unity8 crashed with SIGSEGV in Screen::makeCurrent()
  UpgradeStatus: Upgraded to zesty on 2016-10-27 (70 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1654581/+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 1573322] Re: several packages failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: dpkg (Ubuntu)
   Status: New => Confirmed

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

Title:
  several packages failed to install/upgrade: triggers looping,
  abandoned

Status in dpkg package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Appeared as soon as the computer started

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 21 20:09:31 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-11-23 (150 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=2faac09b-9252-4043-85b9-c6bfed793b7c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu4 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 05/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: Z97 Killer
  dmi.board.vendor: ASRock
  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.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Killer:rvr: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: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1573322/+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 1654578] [NEW] webbrowser-app - Network error 301 protocol "filesystem" is unknown

[dinamic]

Public bug reported:

xenial + overlay PPA - unity8 session
webbrowser-app/xenial,now 0.23+16.04.20161202-0ubuntu1 amd64 
[installed,automatic]

when i try to download an image from telegram web
(https://web.telegram.org) i get this message "Network error 301
protocol "filesystem" is unknown" i checked to see if the image was
downloaded and it was not.

how to reproduce

1. use unity8 on desktop
2. go to https://web.telegram.org 
3. try to download an image from whatever group/chat you have with the 
webbrowser-app
4. you'll see the download with dialoge, choose with gallery or just download 
and then you'll see the notification whith this error

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

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  webbrowser-app - Network error 301 protocol "filesystem" is unknown

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  xenial + overlay PPA - unity8 session
  webbrowser-app/xenial,now 0.23+16.04.20161202-0ubuntu1 amd64 
[installed,automatic]

  when i try to download an image from telegram web
  (https://web.telegram.org) i get this message "Network error 301
  protocol "filesystem" is unknown" i checked to see if the image was
  downloaded and it was not.

  how to reproduce

  1. use unity8 on desktop
  2. go to https://web.telegram.org 
  3. try to download an image from whatever group/chat you have with the 
webbrowser-app
  4. you'll see the download with dialoge, choose with gallery or just download 
and then you'll see the notification whith this error

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654578/+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 1654568] [NEW] OSK transparent - buffer not updated

[Michał Sawicz]

Public bug reported:

The OSK is unusable on frieza_arm64/staging. It's just not displayed.

$ system-image-cli -i
current build number: 116
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu
last update: 2017-01-06 12:22:32
version version: 116
version ubuntu: 20170106
version device: 20161014.0
version custom: 20170106

Note you'll need to downgrade dbus and reboot (bug #1654365):

$ sudo apt install {dbus{,-x11},libdbus-1-3}=1.10.6-1ubuntu3.1
$ sudo reboot

[2017-01-06:14:06:06.521] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::MirSurface(type=input Method,state=restored)
[2017-01-06:14:06:06.522] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::registerSurface(surface=qtmir::MirSurface(0x1c4a0820))
[...]
[2017-01-06:14:06:06.630] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setInputBounds(QRect(0,1159 1200x761))
[2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4e2f00,"unity8-dash"]::setFocused(false)
[2017-01-06:14:06:06.862] qtmir.applications: 
Application["unity8-dash"]::focusedChanged(false)
[2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setFocused(true)
[2017-01-06:14:06:06.862] qtmir.surfaces: MirSurface[0x1c4a0820,"-"]::setReady()
[2017-01-06:14:06:06.863] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::prependSurface(surface=qtmir::MirSurface(0x1c4a0820))
[2017-01-06:14:06:06.863] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::setState(state=running)
[2017-01-06:14:06:06.863] toplevelwindowmodel: 
setFocusedWindow(Window[0x1c3958a0, id=3, 
MirSurface[0x1c4a0820,"MaliitOnScreenKeyboard"]])
[2017-01-06:14:06:06.864] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setKeymap("us")
[2017-01-06:14:06:07.120] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::dropPendingBuffer() dropped=0 left=1 - failed to 
upate texture

That last one suggests unity8 didn't properly pick the input method up.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity8 8.15+16.04.20161215-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
Uname: Linux 3.10.93+ aarch64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: arm64
Date: Fri Jan  6 14:05:11 2017
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 third-party-packages xenial

** Description changed:

  The OSK is unusable on frieza_arm64/staging. It's just not displayed.
  
  $ system-image-cli -i
  current build number: 116
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-06 12:22:32
  version version: 116
  version ubuntu: 20170106
  version device: 20161014.0
  version custom: 20170106
+ 
+ Note you'll need to downgrade dbus and reboot (bug #1654365):
+ 
+ $ sudo apt install {dbus{,-x11},libdbus-1-3}=1.10.6-1ubuntu3.1
+ $ sudo reboot
  
  [2017-01-06:14:06:06.521] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::MirSurface(type=input Method,state=restored)
  [2017-01-06:14:06:06.522] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::registerSurface(surface=qtmir::MirSurface(0x1c4a0820))
  [...]
  [2017-01-06:14:06:06.630] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setInputBounds(QRect(0,1159 1200x761))
  [2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4e2f00,"unity8-dash"]::setFocused(false)
  [2017-01-06:14:06:06.862] qtmir.applications: 
Application["unity8-dash"]::focusedChanged(false)
  [2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setFocused(true)
  [2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setReady()
  [2017-01-06:14:06:06.863] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::prependSurface(surface=qtmir::MirSurface(0x1c4a0820))
  [2017-01-06:14:06:06.863] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::setState(state=running)
  [2017-01-06:14:06:06.863] toplevelwindowmodel: 
setFocusedWindow(Window[0x1c3958a0, id=3, 
MirSurface[0x1c4a0820,"MaliitOnScreenKeyboard"]])
  [2017-01-06:14:06:06.864] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setKeymap("us")
  [2017-01-06:14:06:07.120] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::dropPendingBuffer() dropped=0 left=1 - failed to 
upate texture
  
  That last one suggests unity8 didn't properly pick the input method up.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.15+16.04.20161215-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Fri Jan  6 14:05:11 2017
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probabl

[Touch-packages] [Bug 1654563] [NEW] OSK jumping up and down on click/touch

[Michał Sawicz]

Public bug reported:

After having forced the OSK to show on a zesty desktop
(http://paste.ubuntu.com/23752185/) I found it jumping up and down on
input events.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubuntu-keyboard 0.100+17.04.20161223-0ubuntu1
ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
Uname: Linux 4.9.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan  6 14:51:55 2017
InstallationDate: Installed on 2016-05-06 (244 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: ubuntu-keyboard
UpgradeStatus: Upgraded to zesty on 2016-11-22 (45 days ago)

** Affects: ubuntu-keyboard (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

** Attachment added: "video20170106_145244626.mp4"
   
https://bugs.launchpad.net/bugs/1654563/+attachment/4800841/+files/video20170106_145244626.mp4

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

Title:
  OSK jumping up and down on click/touch

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  After having forced the OSK to show on a zesty desktop
  (http://paste.ubuntu.com/23752185/) I found it jumping up and down on
  input events.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-keyboard 0.100+17.04.20161223-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  6 14:51:55 2017
  InstallationDate: Installed on 2016-05-06 (244 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1654563/+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 1462489] Re: Allow apps to keep the screen on

[Gerry Boland]

** Tags added: unity8

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

Title:
  Allow apps to keep the screen on

Status in Canonical System Image:
  Fix Released
Status in Canonical Click Reviewers tools:
  Fix Released
Status in Ubuntu Developer Portal:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Support an interface in QML and HTML to allow an app to keep the
  screen on while the app is active. This has come up in several
  scenarios, such as an ebook reader, a clock in night mode.

  First step is to hook up QtSystemInfo screenSaverEnabled

  One solution to inhibit the screen blanking:

  Add a new dbus rule to the default template
  Provide a mediator (unity8) to control this, so it can restore the screen 
blanking when the app is not active or has been closed
  Prompt the user for confirmation the first time the app accesses it
  use the trust store to avoid prompts each time
  add to the System settings Other app access panel an entry for Screen or 
Display so the setting could be revoked

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462489/+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 1510968] Re: external monitor grid units are not set correctly

[Gerry Boland]

** Tags added: unity8

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

Title:
  external monitor grid units are not set correctly

Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  external monitor grid units are not set correctly so the desktop is
  incorectly scaled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510968/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Pham Hong Nhat]

** Description changed:

  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)
  
  Problem: Notebook subwoofer doesn't work.
  
  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  aljosa 1776 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-10-generic N/A
-  linux-backports-modules-4.4.0-10-generic  N/A
-  linux-firmware1.156
+  linux-restricted-modules-4.4.0-10-generic N/A
+  linux-backports-modules-4.4.0-10-generic  N/A
+  linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
P

[Touch-packages] [Bug 1558663] Re: Ubuntu Components is hard on the disk and CPU when loading images

[Gerry Boland]

** Tags added: unity8

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

Title:
  Ubuntu Components is hard on the disk and CPU when loading images

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
   * Take the following simple example of a listview with an image.
   * run it with strace qmlscene
   * scroll the list to the bottom

  
  When not including "import Ubuntu.Components 1.3" there is exactly one disk 
access to load the image
  open("/home/tsdgeos_work/test/face.png", O_RDONLY|O_CLOEXEC) = 19

  When including "import Ubuntu.Components 1.3" there are around 500
  disk access including stats for the file and listing the directory
  containing the file (see disk_access file).

  Also for each of those directory listings we're also creating and
  destroying the same QRegExp again and again.

  I understand that some of this overhead is needed since we have that
  thing that loads the best possible file for the given grid units, but
  doing it again and again for the same file seems a bit of overkill,
  maybe we could cache that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1558663/+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 1621370] Re: UITK on Intel i915 (atom)is very slow

[Gerry Boland]

** Tags added: unity8

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

Title:
  UITK on Intel i915 (atom)is very slow

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  use unity8 and mir on computers with processor based on i915 (ex.atom
  and old processors) is impossible because it is very slow due to UITK.
  when you open the application takes a long time and any action on the
  pop-up locks the computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1621370/+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 1647415] Re: units.gu() emits changed signal before completion

[Gerry Boland]

** Tags added: unity8

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

Title:
  units.gu() emits changed signal before completion

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Consider this snippet of code:

  ---
  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  property int bla: units.gu(10)
  onBlaChanged: print("bla changed", bla);

  property int blubb: 80
  onBlubbChanged: print("blubb changed", blubb);

  Component.onCompleted: print("completed", bla);
  }
  --

  The output of this is:

  qml: bla changed 80
  qml: completed 80

  the changed signal should not be emitted before completion, given it
  is its initial value and not actually changed.

  The current behavior triggers all the onChanged handlers when there's
  units.gu() involved, which results in things like change animations
  being played at startup and lots of wasted cpu cycles for evaluating
  all those changed events.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1647415/+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 1585723] Re: UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

[Gerry Boland]

** Tags added: unity8

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

Title:
  UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I'm digging into unity8 performance problems on older generation Intel
  GPUs - specifically i915 Atom GPUs.

  I've tested a simple QML file with a single empty UbuntuShape in it:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Rectangle {
  width: 400
  height: 300
  color: "blue"

  UbuntuShape {}
  }

  Running it with INTEL_DEBUG=perf env var set, I get this output:

  i915_program_error: Exceeded max ALU instructions (76 out of 64)
  ENTER FALLBACK 1: Program
  Mapping a busy BO, causing a stall on the GPU.

  which implies that MESA was unable to compile one of the UbuntuShape
  shaders as it created more ALU instructions than the GPU could deal
  with. MESA falls back to CPU rendering as a result.

  The GPU stall message I guess is related to that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1585723/+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 1654536] Re: unity-system-compositor crashed EGL_BAD_SURFACE

[Michał Sawicz]

This is what's shown in logcat when it crashes:

E/MALI( 1365): get_target_buffer:944: winsysp_window_buffer_get failed 12299
E/MALI( 1365): gles_state_set_error_internal:56: GLES ctx: 0x5572c08, error 
code:0x505
E/MALI( 1365): get_target_buffer:944: winsysp_window_buffer_get failed 12299

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

Title:
  unity-system-compositor crashed EGL_BAD_SURFACE

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  unity-system-compositor sometimes aborts on latest xenial/arm64 on
  frieza:

  $ system-image-cli -i
  current build number: 116
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-06 09:43:26
  version version: 116
  version ubuntu: 20170106
  version device: 20161014.0
  version custom: 20170106

  /var/log/lightdm/unity-system-compositor.log has:
  ERROR: 
/build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233):
 Throw in function virtual void 
mir::graphics::android::FramebufferGLContext::swap_buffers() const
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Fri Jan  6 10:20:54 2017
  Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1480992789
  GraphicsCard:
   
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 11 --to-dm-fd 14 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ()
   std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 
<_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at 
../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121
   __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56
   __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42
   _dl_fini () at dl-fini.c:235
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.lightdm: lightdm 1.18.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+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 1654536] Re: unity-system-compositor crashed EGL_BAD_SURFACE

[Michał Sawicz]

 Saviq: also can you get the value of the "ro.build.product property" 
and see if it matches "Aquaris_M10_FHD" - mir implements quirks which depend on 
that
 "frieza"
 Saviq: hmm that doesn't match what Mir expects
 could be a clue
 could you add --fb-ion-heap=false to USC's command line?

That seems to have helped with the E/MALI errors from logcat, I can't
see it crashing either.

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

Title:
  unity-system-compositor crashed EGL_BAD_SURFACE

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  unity-system-compositor sometimes aborts on latest xenial/arm64 on
  frieza:

  $ system-image-cli -i
  current build number: 116
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-06 09:43:26
  version version: 116
  version ubuntu: 20170106
  version device: 20161014.0
  version custom: 20170106

  /var/log/lightdm/unity-system-compositor.log has:
  ERROR: 
/build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233):
 Throw in function virtual void 
mir::graphics::android::FramebufferGLContext::swap_buffers() const
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Fri Jan  6 10:20:54 2017
  Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1480992789
  GraphicsCard:
   
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 11 --to-dm-fd 14 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ()
   std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 
<_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at 
../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121
   __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56
   __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42
   _dl_fini () at dl-fini.c:235
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.lightdm: lightdm 1.18.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+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 1654536] Re: unity-system-compositor crashed EGL_BAD_SURFACE

[Michał Sawicz]

Too little too soon, just got the same exception thrown.

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

Title:
  unity-system-compositor crashed EGL_BAD_SURFACE

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  unity-system-compositor sometimes aborts on latest xenial/arm64 on
  frieza:

  $ system-image-cli -i
  current build number: 116
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-06 09:43:26
  version version: 116
  version ubuntu: 20170106
  version device: 20161014.0
  version custom: 20170106

  /var/log/lightdm/unity-system-compositor.log has:
  ERROR: 
/build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233):
 Throw in function virtual void 
mir::graphics::android::FramebufferGLContext::swap_buffers() const
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Fri Jan  6 10:20:54 2017
  Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1480992789
  GraphicsCard:
   
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 11 --to-dm-fd 14 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ()
   std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 
<_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at 
../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121
   __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56
   __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42
   _dl_fini () at dl-fini.c:235
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.lightdm: lightdm 1.18.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+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 1654536] Re: unity-system-compositor crashed EGL_BAD_SURFACE

[Kevin DuBois]

I somewhat doubt that quirk would help, iirc, it was added after reports
that it helped from the bringup (but by the time it got released it
didn't seem to do anything in my local testing)

0x505 is GL_OUT_OF_MEMORY, perhaps a leak?

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

Title:
  unity-system-compositor crashed EGL_BAD_SURFACE

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  unity-system-compositor sometimes aborts on latest xenial/arm64 on
  frieza:

  $ system-image-cli -i
  current build number: 116
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-06 09:43:26
  version version: 116
  version ubuntu: 20170106
  version device: 20161014.0
  version custom: 20170106

  /var/log/lightdm/unity-system-compositor.log has:
  ERROR: 
/build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233):
 Throw in function virtual void 
mir::graphics::android::FramebufferGLContext::swap_buffers() const
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Fri Jan  6 10:20:54 2017
  Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1480992789
  GraphicsCard:
   
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 11 --to-dm-fd 14 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ()
   std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 
<_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at 
../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121
   __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56
   __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42
   _dl_fini () at dl-fini.c:235
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.lightdm: lightdm 1.18.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+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 1519007] Re: Ringtone not played on the speaker

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Ringtone not played on the speaker

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in telepathy-ofono package in Ubuntu:
  In Progress

Bug description:
  Test case.
  - Pair with a Bluetooth speaker.
  - Make a call to the device.

  Expected result.
  - A ringtone or wait sound is played on the speaker.

  Actual result.
  - Only the phone plays the ringtone.

  current build number: 186
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1519007/+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 204536] Re: sound volume always resets to 100% after reboot

[Martin Heine]

The bug is still there. Very annoying. Every time, you forget to torn
the Volume down of your Stereo, the Speakers almost blow when Ubuntu
starts. Can't be that heart to fix this?

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

Title:
  sound volume always resets to 100% after reboot

Status in One Hundred Papercuts:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Every time I reboot I get the sound volume back to 100%, but the sound
  works fine apart from this. It's just *very* annoying to have to reset
  the volume every time I boot the PC. I set the volume from the volume
  icon in the system tray. I have two sound cards installed on my system
  (one on the motherboard and a SB Audigy), but I'm using only the
  Audigy. Another thing is that the mixer applet often incorrectly shows
  volume as muted when it's not.

  I'm using the hardy beta (hardy-desktop-amd64) from march 19th 2008.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/204536/+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 1510225] Re: load() of a QDeclarativePlaylist does not fully work

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  load() of a QDeclarativePlaylist does not fully work

Status in Canonical System Image:
  In Progress
Status in qtmultimedia-opensource-src package in Ubuntu:
  Fix Released
Status in qtubuntu-media package in Ubuntu:
  Fix Released
Status in qtmultimedia-opensource-src package in Ubuntu RTM:
  Fix Released
Status in qtubuntu-media package in Ubuntu RTM:
  Fix Released

Bug description:
  * load(location) only works when a QDeclarativePlaylist is not read-only.
  * QMediaPlayer loads playlist items one by one instead of using the new 
addTracks for much greater efficiency and lower latency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510225/+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 1518157] Re: Need to be able todo Playlist.Random | Playlist.Loop in QML to accomodate or all playbackModes

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Need to be able todo Playlist.Random | Playlist.Loop in QML to
  accomodate or all playbackModes

Status in Canonical System Image:
  Confirmed
Status in qtmultimedia-opensource-src package in Ubuntu:
  Triaged
Status in qtubuntu-media package in Ubuntu:
  Triaged
Status in qtmultimedia-opensource-src package in Ubuntu RTM:
  Triaged
Status in qtubuntu-media package in Ubuntu RTM:
  Fix Released

Bug description:
  The Playlist.playbackMode property needs to be able to have the following 
modes:
  1. shuffle
  2. shuffle and loop
  3. shuffle with play once
  4. sequential
  5. sequential and loop
  6. sequential with play once

  Note that I do not believe we can currently do Playlist.Random |
  Playlist.Loop in QML, so we will need Playlist.RandomAndLopp etc

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518157/+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 1506511] Re: Second video playback results in white screen when replaying from indicator-sound

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Second video playback results in white screen when replaying from
  indicator-sound

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in mediaplayer-app package in Ubuntu:
  New
Status in qtubuntu-media package in Ubuntu:
  New
Status in qtubuntu-media package in Ubuntu RTM:
  New

Bug description:
  Test case.
  - Record a short video (10 seconds) with the camera.
  - Open video scope.
  - Play recorded video in mediaplayer.
  - After the video finishes playing, tap "play" in mediaplayer
- The video must playback a second time.
  - When the video is finished, open the indicator sound.
  - Tap play control in indicator sound.

  Expected result.
  - Video starts playing, but a white image is displayed. Sound is reproduced.

  Tested in arale with silo 55 (which is landing and will be available
  in a later image).

  current build number: 138
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506511/+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 1514344] Re: Upstream remaining bits and port to upstream QDeclarativePlaylist version

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Upstream remaining bits and port to upstream QDeclarativePlaylist
  version

Status in Canonical System Image:
  Confirmed
Status in qtmultimedia-opensource-src package in Ubuntu:
  Triaged
Status in qtmultimedia-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  Currently the qtmultimedia in stable overlay PPA contains several
  additions and changes compared to upstream qtmultimedia (5.6/5.7):
  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-009/+files/qtmultimedia-opensource-
  src_5.4.1-1ubuntu18.debian.tar.xz

  The remaining additions should be upstreamed at https://codereview.qt-
  project.org/#/q/project:qt/qtmultimedia,n,z

  After the upstreaming is complete, since our version has changes that
  are different in upstream, our components should be ported to the
  upstream API instead.

  Qt Multimedia in Ubuntu should be updated respectively for versions
  5.4.1 (overlay) and 5.5.1 (xenial/PPA), with backports from latest
  upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514344/+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 1430769] Re: Does not detect hidden WiFi on first attempt

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Does not detect hidden WiFi on first attempt

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  Confirmed

Bug description:
  The WiFi network I use at home is a hidden one. While it works with my
  Ubuntu Phone, I always have to toggle WiFi on and off about 3 times
  until it is detected.

  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 129
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-11 13:19:54
  version version: 129
  version ubuntu: 20150310.3
  version device: 20150210
  version custom: 20150310.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1430769/+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 1506340] Re: Multimedia audio is routed for half of a second through HFP SCO after call has ended

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Multimedia audio is routed for half of a second through HFP SCO after
  call has ended

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in telepathy-ofono package in Ubuntu:
  New

Bug description:
  When playing audio through A2DP and a call comes in, gets accepted and
  finishes after some time the multimedia audio will start again after
  the call but is played for half of a second either through the phone
  speaker or HFP SCO channel rather than only being played again through
  A2DP as it was before the call.

  This happens with BlueZ 4.x and 5.x and is related to how we handle
  the audio routing setup currently.

  The telepathy-ofono service currently switches the different ports,
  sinks, sources and profiles of our PulseAudio elements to enable
  everything needed to do a voicecall and to switch things back
  correctly once the voicecall is done. The issue described above is the
  result of either a incorrect sequence of enabling/disbling things or
  bound to timing issues when the switching is done.

  We need to do some more analysis on the routing in PulseAudio and how
  telepathy-ofono does things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506340/+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 1447515] Re: provide /sbin/resize2fs

[John McAleely]

** Changed in: initramfs-tools-ubuntu-touch (Ubuntu)
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  provide /sbin/resize2fs

Status in initramfs-tools-ubuntu-touch package in Ubuntu:
  In Progress

Bug description:
  In order to be able to resize the userdata partition on first boot, we
  need the resize2fs tool in the initramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-touch/+bug/1447515/+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 1283871] Re: Default mount points not suitable for photo import

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Default mount points not suitable for photo import

Status in Canonical System Image:
  Confirmed
Status in mtp package in Ubuntu:
  Triaged
Status in shotwell package in Ubuntu:
  Invalid

Bug description:
  When I plug my Ubuntu Phone into my desktop I want to be able to
  import photos easily into my photo manager of choice (Shotwell in my
  case but others are available apparently). The photos should be
  available via a "DCIM" folder, but they're in "Photos" which Shotwell
  doesn't find. While I could use the "Import from folder" and navigate
  my way to Photos, I'd rather it Just Worked.

  Could we export photos over the "standard" DCIM folder to make this
  easier for everyone?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mtp-server 0.0.2+14.04.20131205-0ubuntu1
  Uname: Linux 3.4.0-4-mako armv7l
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: armhf
  Date: Mon Feb 24 01:01:39 2014
  InstallationDate: Installed on 2014-02-23 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf 
(20140223.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: mtp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1283871/+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 1505213] Re: Multiple bluetooth audio devices break audio routing

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Multiple bluetooth audio devices break audio routing

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in telepathy-ofono package in Ubuntu:
  Confirmed

Bug description:
  When connecting multiple bluetooth audio devices the audio routing
  doesn't behave as it should.

  When multiple devices are connected which support A2DP for example we
  have to

  * Pick one which becomes the active one
  * When the active one disappears (disconnected, out-of-range) we need to pick 
the next one and set it as the active

  Right now the result is not constant when connecting multiple devices:

  * bluez and PA (mainly PA) try to setup all devices not respecting if one is 
already active
  * when disconnecting the active one the previously not-active one doesn't 
become active and stays unused

  Also we need to check if telepathy-ofono takes always the right audio
  card from PA to setup the audio routing for voicecalls.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505213/+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 1396973] Re: Audio not switched when headset disabled via bluetooth on/off

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Audio not switched when headset disabled via bluetooth on/off

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New

Bug description:
  Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r169 krillin

  Steps to reproduce:
   * Pair krillin with BT Headset (Sony MDR-10RBT used in test)
   * Call the handset
   * Answer call
   * Check headset input/output
   * Disable Bluetooth on the krillin
   * Audio routed to phone speaker/mic
   * Re-enable Bluetooth

  Expected result:
   - Bluetooth re-connects to headset audio routed back to headset input/output

  Actual result:
   - Audio seems to be routed badly - no audio on call at all from krillin

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1396973/+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 1523722] Re: Crash when deleting QMediaPlayer instance

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Crash when deleting QMediaPlayer instance

Status in Canonical System Image:
  Incomplete
Status in media-hub package in Ubuntu:
  Incomplete
Status in qtubuntu-media package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding telephony-service.  This problem was most recently seen with
  version 0.1+16.04.20151119-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/8f663af0b140859566ab5cf21a4ad6e5eb7b6fc0
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523722/+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 1579549] Re: Music stops playing from main speaker when a call comes in

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Music stops playing from main speaker when a call comes in

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Music App:
  New
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu RTM:
  Invalid
Status in pulseaudio package in Ubuntu RTM:
  Confirmed

Bug description:
  1. Start some music playback from the music-app
  2. It is ok with SMS notification and sound but whenever a call comes music 
stops playing during call but after the call is disconnected music resumes 
playing in low volume and i turned the volume to full and still the sound is 
low and then i noticed that music stopped playing from the phone's loud speaker 
instead it is playing from top talking speaker (my nexus 4).
  3. To resolve this issue i've to close and re open music app which is very 
frustrating.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579549/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1559201] Re: Bluetooth connection broken while autoconnect

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Bluetooth connection broken while autoconnect

Status in Bluez Utilities:
  New
Status in Canonical System Image:
  Confirmed
Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  When I set up phone and click connect - music plays fine. But when I
  turn off bluetooth (and mark 'connect automatically to that device'),
  turn it again - phone connect to that device again, but music don't
  play at all or plays with big disruptions. This issue does not occur
  when I've got 'automatically connect' turned off and manually click
  'connect'.

  Maybe this is related to bug [1]
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1494225 (because
  this problem happen to me only in device also affected by [1] - in
  other devices working correctly (not affected by [1]) there is no
  problem).

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1559201/+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 1543960] Re: virtual keyboard inserts endless "1" in text field

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  virtual keyboard inserts endless "1" in text field

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New

Bug description:
  Ubuntu Touch OTA 9 on BQ Aquarie E4.5
  When the phone runs for a while - as soon as a text-field is selected and the 
virtual keyboard shows up, it is automatically filled with 1 (number 1). No 
possibility to interrupt the process.  All applications using the virtual 
keyboard are affected.
  By example the dial-pad is not affected but browser, search button etc. 
everything gets filled with 1.

  Only fix so far is to reboot the phone.
  Cause yet unknown, and no direct way identified that triggers this behavior.
  Still searching.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543960/+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 1542542] Re: distance sensor sensitivity is slightly too aggressive

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  distance sensor sensitivity is slightly too aggressive

Status in Canonical System Image:
  Confirmed
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  When the display turns on because of notifications, the distance
  sensor is enabled. That makes sense, but it is a tiny bit too
  sensitive. Right now, it immediately turns the display off as soon as
  there is anything coming close. Depending on the items in the
  indicator (enable gps, bluetooth etc), this collides with the gesture
  to drag down the indicator on the messages icon. Trying to read the
  notification that just turned the screen on, the user often
  accidentally triggers the distance sensor and turns the screen off
  again.

  => The sensor should probably have a threshold to require detection of
  obstacles continuously for a second before triggering the screen off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542542/+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 1532437] Re: Switching off bluetooth do not disconnect bluetooth device gracefully

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Switching off bluetooth do not disconnect bluetooth device gracefully

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New

Bug description:
  Hi I have a belkin bluetooth ad2p dongle and i notice the following
  behaviour.

  When paired to my device and i switch off the bluetooth device. I can
  see that the ad2p dongle is still showing to be connected via its
  notification led and after re-pairing to this device is quite
  troublesome.

  If i do the same thing but disconnect first there is not that much problem to 
re-pair.
  I wonder if when switching off the bluetooth device its send the command to 
all the paired device to un-pair before switching off the bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532437/+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 1563768] Re: Bluetooth HFP indicates a permanent ongoing call

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Bluetooth HFP indicates a permanent ongoing call

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since the upgrade to Bluez5 I can't have my Phone connected to my car
  (BMW 1) any more.

  It pairs fine, but as soon as the connection is established, the car's
  head unit thinks there is a phone call ongoing to the number
  "" (yes, it displays asterisks as the target number on the
  car). This has the effect that I cannot listen to any music in the car
  while the phone is connected as the head unit obviously mutes all
  other sound and only relays the Hands-Free audio between the car and
  the phone. Pressing the hangup button on the car has no effect.
  Disconnecting the phone is the only way to make the phone call go
  away.

  This is a regression with OTA-9. It was working perfectly fine before
  the Bluez5 upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563768/+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 1579389] Re: wireless keeps freezing

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  wireless keeps freezing

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi there,

  After i did update my ubuntu to OTA 10.1 on my bq 4.5, my wireless
  began to freeze everytime the phone idles, it doesn't matter if i am
  home or at work or in a cafe, everytime the phone is doing nothing the
  wireless stop working, So i have to turn it off and then on and
  everything works fine till the phone idles again.

  I have asked on IRC and i was informed to come here report a bug. If
  you guys want me to send you files or anything just give me the
  commands i need to type in my terminal or what files i need to send to
  here.

  Regards,

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579389/+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 1537735] Re: SMS are sent (and charged for) multiple times

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  SMS are sent (and charged for) multiple times

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  When there is poor network coverage, it often happens that SMS are
  sent multiple times. They appear only once in the messages app, but
  the other end receives them multiple times (up to 5 times I believe).

  In the example of the attached screenshots, the sender never received
  the confirmation that it actually succeeded, the receiver however
  received the message multiple times. Also the operator will charge for
  each sent instance. I have seen other cases where eventually the
  confirmation comes through after, say, 3 attempts and it stops
  retrying.

  I'm not really sure about what to do if the confirmation doesn't come
  through the network, but as I've never seen this issue with other
  phones, I think it must be something like the retries being sent with
  a different ID, so the operator cannot match the message to previous
  attempts? Or perhaps the timeout for waiting for the reply is just too
  short?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537735/+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 1563342] Re: Broken cache partition can render the device unflashable

[John McAleely]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  Broken cache partition can render the device unflashable

Status in Canonical System Image:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  New

Bug description:
  This is not a common issue, but if the cache partition gets corrupted
  (it's writeable after all), you won't be able to flash your device.

  It's been reported by renato and ondra said he's seen that, too. We
  need to make sure we can recover from such a state by auto-formatting
  the cache partition on boot if it's found corrupt, or at the very
  least have options in recovery to wipe/format the cache partition, as
  android has.

  The problem is that the cache partition is mounted read-only:

  /dev/mmcblk0p15 on /android/cache type ext4 
(ro,nosuid,nodev,noatime,noauto_da_alloc,data=ordered)
  /dev/mmcblk0p15 on /var/lib/lxc/android/rootfs/cache type ext4 
(ro,nosuid,nodev,noatime,noauto_da_alloc,data=ordered)

  And so flashing fails:

  failed to copy '~/.cache/ubuntuimages/ubuntu-touch/rc-
  proposed/meizu.en/arale/version-289.tar.xz' to
  '/cache/recovery//version-289.tar.xz': Read-only file system

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563342/+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