date:20170320

** Branch linked: lp:mir

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

Title:
  cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev]
  due to libudev.so being in a different directory to where libudev.pc
  searches for it

Status in Mir:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  Mir fails to build on arm64 cross-compiled:

  [ 11%] Linking CXX shared library ../../lib/libmirplatform.so
  /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: 
cannot find -ludev
  /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: 
cannot find -ludev
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1674201/+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 1674201] Re: cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev]

** Package changed: udev (Ubuntu) => systemd (Ubuntu)

** Summary changed:

- cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev]
+ cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev] due to 
libudev.so being in a different directory to where libudev.so searches for it

** Summary changed:

- cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev] due to 
libudev.so being in a different directory to where libudev.so searches for it
+ cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev] due to 
libudev.so being in a different directory to where libudev.pc searches for it

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

Title:
  cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev]
  due to libudev.so being in a different directory to where libudev.pc
  searches for it

Status in Mir:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  Mir fails to build on arm64 cross-compiled:

  [ 11%] Linking CXX shared library ../../lib/libmirplatform.so
  /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: 
cannot find -ludev
  /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: 
cannot find -ludev
  collect2: error: ld returned 1 exit status

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

2017-03-20 Thread Steve Langasek

** Description changed:

+ [SRU justification]
+ Before systemd 232, UserTasksMax=infinity is not respected in logind.conf, 
despite the documentation referring to systemd.resource-control(5) for the 
definition of this field. This limits the use of Ubuntu 16.04 and later in 
contexts where a user session should be permitted to allocate large numbers of 
processes.
+ 
+ [Test case]
+ 1. Set UserTasksMax=infinity in /etc/systemd/logind.conf.
+ 2. Create a new login session.
+ 3. Check the ulimit for user processes with 'ulimit -u'.
+ 4. Verify that the limit has a numeric value.
+ 5. Upgrade to systemd from -proposed.
+ 6. Create a new login session.
+ 7. Check the ulimit for user processes with 'ulimit -u'.
+ 8. Verify that the limit is now set to 'unlimited'.
+ 
+ [Regression potential]
+ This is an upstream patch which is part of 232 and later without issues and 
clearly addresses the bug in question.  While the upstream commit includes code 
changes that are not strictly required in order to fix this bug, these are 
mostly cosmetic and should not carry significant additional risk.
+ 
+ 
  == 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. 
+ 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

[Touch-packages] [Bug 1674201] [NEW] cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev]

You have been subscribed to a public bug:

Mir fails to build on arm64 cross-compiled:

[ 11%] Linking CXX shared library ../../lib/libmirplatform.so
/usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: 
cannot find -ludev
/usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: 
cannot find -ludev
collect2: error: ld returned 1 exit status

** Affects: mir
 Importance: High
 Assignee: Daniel van Vugt (vanvugt)
 Status: In Progress

** Affects: systemd (Ubuntu)
 Importance: High
 Status: New


** Tags: regression xcompile
-- 
cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev]
https://bugs.launchpad.net/bugs/1674201
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

2017-03-20 Thread Khurshid Alam

I don't know if this is related but  now it simply could not resolve
https://www.aviationweather.gov and www.noaa.gov. The result is the same
through ping and wget.

However when I try ip address of www.aviationweather.gov in browser it
works.

---
$ systemd-resolve 140.90.101.207
140.90.101.207: resolve call failed: Address '140.90.101.207' does not have any 
RR of requested type


$ wget "https://140.90.101.207/adds/dataserver_current/httpparam;

Connecting to 140.90.101.207:443... connected.
ERROR: certificate common name ‘ncep.noaa.gov’ doesn't match requested host 
name ‘140.90.101.207’
---


I have libnssresolve installed. systemd-232-19, Ubuntu 17.04

-- 
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 Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ 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/nextcloud-snap/+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 1023277] Re: Please provide option to make NetworkManager verify only the root certificate of the signed cert chain (WPA2-Enterprise)

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Please provide option to make NetworkManager verify only the root
  certificate of the signed cert chain (WPA2-Enterprise)

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  I have to use a chain certificate, that had all certificates involved
  in the verification of the AP. this seems uncomfortable and breaks
  design (of at least the eduroam networks).

  The (German) eduroam networks are all signed with a certificate of the
  corresponding university or college CA, which is signed by the DFN
  (german scientific network) which is signed by Deutsche Telekom Root
  CA (installed by default on ubuntu)

  By opting to verify the complete chain, I have to set up various
  configurations for various locations.

  The eduroam network is designed to enable students from all over the
  world to log in to worldwide higher education networks with their
  home-university's login.

  There should be an option to only verify the root certificate of the
  signed cert chain.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1023277/+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 1653314] Re: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

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

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

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

Title:
  package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 1

Status in bluez package in Ubuntu:
  Expired

Bug description:
  i can'conekt bluetooth

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez:i386 5.37-0ubuntu5
  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
  Date: Fri Dec 30 19:39:34 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2016-11-29 (31 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: bnep bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=fb1fce69-ec71-4461-85dd-690d60245405 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: bluez
  Title: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CROSSHAIR V FORMULA-Z
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr1302:bd01/11/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVFORMULA-Z:rvrRev1.xx: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.
  hciconfig:
   
  rfkill:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1653314/+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 1674532] [NEW] Ubuntu 14.04 broken during PXE boot

2017-03-20 Thread Eric Horne

Public bug reported:

After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
the automated install of ubuntu 14.04.5, the system was suddenly unable
to resolve hostnames via dns. Installing -0ubuntu6.9 resolved the issue.
Reinstalling -ubuntu6.10 broke the system again.

I note that -ubuntu6.10 was recently added to the archive.

I am currently unable to install Ubuntu 14.04.5.

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

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  New

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

2017-03-20 Thread Eric Horne

"Suddenly" refers to the log in which it is happily downloading stuff
from the archive and after successfully downloading and installing the
libc6_2.19-0ubuntu6.10 package it is unable to download the next package
because it can no longer resolve the archive.ubuntu.com name that it had
been resolving prior to the installation of that libc6 library. I
unfortunately don't know how to get logs off the system to send in :(

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  New

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1623383] Re: Some restarts fail due to missing base devices

2017-03-20 Thread Po-Hsu Lin

journalctl log for kernel02 (s390x.zVM), which drops to emergency mode
as well

** Attachment added: "kernel02.log"

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623383/+attachment/4841328/+files/kernel02.log

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

Title:
Some restarts fail due to missing base devices

Status in systemd package in Ubuntu:
Confirmed

Bug description:
Arch: s390x
Release: Yakkety / 16.10

This happens on some (but not all) system starts with Yakkety. In
Xenial (which is using the same 4.4 kernel version the Yakkety systems
were using when the problem was first observed) this did not happen.
The system (LPAR) this was seen first was an upgrade from Xenial but
since then has been freshly installed with Yakkety. The same behaviour
is seen on a zVM guest running Yakkety.

The attached syslog shows a failed boot, followed by one that did work. Note
the "Found device .*(sclp|encc00).*" messages in the good boot. Those are
missing in the bad attempt and as a result networking and console fail to be
usable. Also note, those boots were 4.8 kernels but we saw this with 4.4
kernels, too.
This might be a systemd problem / race, I just filed it into udev for now as
that better matches the not finding basic devices symptom.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623383/+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 1597881] Re: Fix for CVE-2016-1234 in Ubuntu for eglibc 2.15-0ubuntu10.15

2017-03-20 Thread Steve Beattie

CVE-2016-1234 Has been addressed in Ubuntu 14.04 LTS in 2.19-0ubuntu6.10
as part of http://www.ubuntu.com/usn/usn-3239-1 . Marking the eglibc
task as closed.

Thanks!

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

** Changed in: eglibc (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Fix for CVE-2016-1234 in Ubuntu for eglibc 2.15-0ubuntu10.15

Status in Juniper Openstack:
  In Progress
Status in Juniper Openstack r2.20 series:
  In Progress
Status in Juniper Openstack r2.22.x series:
  In Progress
Status in Juniper Openstack r3.0 series:
  In Progress
Status in Juniper Openstack trunk series:
  In Progress
Status in eglibc package in Ubuntu:
  Fix Released

Bug description:
  CVE-2016-1234 has to be fixed for eglibc 2.15-0ubuntu10.15

  I have found Debian guys have patched this in wheezy
  (https://packages.debian.org/wheezy/all/eglibc-source/download)  which
  is on 2.13 , Couldn't find this for 2-15 in Ubuntu repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/1597881/+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 1674529] [NEW] Credentials expired on all accounts.

2017-03-20 Thread Cristhian Steven Echeverry Z.

Public bug reported:

Hello!
I can not synchronize any account, I already tried eliminating each one, 
removed the key from the "Passwords" app, restarting and nothing.
Any solution?
Pd: Some have two-step verification enabled, some do not.
GNOME Shell 3.20.4
Ubuntu GNOME 16.10

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-online-accounts 3.20.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Mar 20 22:10:02 2017
InstallationDate: Installed on 2017-03-18 (2 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages yakkety

** Attachment added: "screensht"
   
https://bugs.launchpad.net/bugs/1674529/+attachment/4841324/+files/Captura%20de%20pantalla%20de%202017-03-20%2011-46-44.png

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

Title:
   Credentials expired on all accounts.

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

Bug description:
  Hello!
  I can not synchronize any account, I already tried eliminating each one, 
removed the key from the "Passwords" app, restarting and nothing.
  Any solution?
  Pd: Some have two-step verification enabled, some do not.
  GNOME Shell 3.20.4
  Ubuntu GNOME 16.10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 20 22:10:02 2017
  InstallationDate: Installed on 2017-03-18 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1674529/+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 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

2017-03-20 Thread john nunnington

comparing pulseaudio configuration, some rtp modules were uncommented in
the failing environment so these were commented back out; result,
pulseaudio ran for about 26 minutes before failing. Daemon restarted (as
configured) and sound settings retained the selected output device...but
spotify is unable to restart or play.

...just failed after 3-4 minutes

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  julie 30342 F pulseaudio
   /dev/snd/controlC1:  julie 30342 F pulseaudio
   /dev/snd/controlC2:  julie 30342 F pulseaudio
   /dev/snd/controlC0:  julie 30342 F pulseaudio
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-05-19 (670 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  yakkety
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562
  mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1673942/+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 1674477] Re: gnome screenshot gtk-mir crashes on taking the shot

If we really want to support gnome-screenshot at all, it might be easier
to implement a Mir backend right inside it (perhaps after fixing bug
1660269).

** Tags added: gtk-mir

** Also affects: gnome-screenshot (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- gnome screenshot gtk-mir crashes on taking the shot
+ gnome screenshot gtk-mir crashes on taking the shot under Mir

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot under Mir

Status in Canonical System Image:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+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 1444656] Re: GnuTLS TLS 1.2 handshake failure

2017-03-20 Thread Samuel Leslie

Hi Seth,

I've attached a debdiff which is generated off the latest gnutls26
package: 2.12.23-12ubuntu2.7. That said, no changes to my earlier patch
were required to apply cleanly. Hopefully this is what you're after?

I should also add that this patch should ideally be reviewed by someone
knowledgeable about GnuTLS and C, as I don't consider myself to meet
either of those requirements! Particularly given this is a security
library.

Cheers,
-SDL

** Patch added: "gnutls26_2.12.23-12ubuntu2.8.debdiff"

https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1444656/+attachment/4841301/+files/gnutls26_2.12.23-12ubuntu2.8.debdiff

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

Title:
GnuTLS TLS 1.2 handshake failure

Status in gnutls26 package in Ubuntu:
Invalid
Status in gnutls26 source package in Trusty:
Triaged

Bug description:
I'm experiencing the same issue as here:

http://comments.gmane.org/gmane.network.gnutls.general/3713

I came across a SSL handshake problem with gnutls-cli when connecting to
some websites, see below. It is somehow specific to gnutls as
openssl/Chrome/Firefox can connect fine.

Is this is a bug in gnutls or do you have any ideas how to
troubleshoot it?

$ gnutls-cli --version
gnutls-cli (GnuTLS) 2.12.23
Packaged by Debian (2.12.23-12ubuntu2.1)

$ gnutls-cli www.openlearning.com
Resolving 'www.openlearning.com'...
Connecting to '119.9.9.205:443'...
*** Fatal error: A TLS fatal alert has been received.
*** Received alert [40]: Handshake failed
*** Handshake has failed
GnuTLS error: A TLS fatal alert has been received.

$ gnutls-cli sequencewiz.com
Resolving 'sequencewiz.com'...
Connecting to '50.112.144.117:443'...
*** Fatal error: A TLS packet with unexpected length was received.
*** Handshake has failed
GnuTLS error: A TLS packet with unexpected length was received.

Thank you,

Please back port the latest GnuTLS to Trusty as it is an LTS release and
clearly GnuTLS 2.12 is an old branch.

I've also attached packet captures of this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1444656/+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 1674262] Re: Windows are not sized correctly if an invalid size comes from the state storage.

** Tags added: unity8-desktop

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

Title:
  Windows are not sized correctly if an invalid size comes from the
  state storage.

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  The width/height of a windowed surface can be 0 if the initial size is
  loaded with 0 due to an invalid state storage size.

  http://paste.ubuntu.com/24195871/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674262/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Tags added: unity8-desktop

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

I spent a little time on this bug last week.

Was able to reproduce it, yes, but the spinning thread was apparently
the libmirclient input thread, and not in any Xmir code. I didn't have
sufficient libmirclient symbols to debug it further before running out
of time. I had assumed this was an Xmir bug but it looks like it might
actually be a Mir bug.

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

Title:
  [xmir] closing an app while a child window is opened leaves an Xmir
  process opened eating 100% CPU

Status in Canonical System Image:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity 8
  [xmir] closing an app while a child window is opened leaves an Xmir process 
opened eating 100% CPU

  launch solitaire (just click on the sol icon from launcher, it will just run 
on Xmir)
  open the about window from the menu (Help \ About)
  now close the main window 

  now top in a terminal (see attached)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671731/+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 1673725] Re: Alt+Left Click should not allow dragging in staged mode

** Tags added: unity8-desktop

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

Title:
  Alt+Left Click should not allow dragging in staged mode

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  You can't drag windows in staged mode, so having Alt+LeftClick change
  the cursor to the dragging cursor is strange and seems to imply you
  can actually drag them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673725/+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 1674263] Re: Window state storage should be using gu values rather than px

I'm not sure about this one. Legacy apps (actually all apps) that size
themselves by pixels might get their sizes rounded to something
inappropriate if you used 'int gu'. Or do you mean 'float gu'? The
latter would avoid the problem (despite lack of precision), but even
better would be to not fix this bug at all.

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

Title:
  Window state storage should be using gu values rather than px

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Store the size (and position?) in GU values rather than px.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674263/+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 1535297] Re: Unity8 reliably crashes on logout due to heap corruption (libprotobuf.so.9 called from libprotobuf-lite.so.9), causing delays while it dumps core and reports errors.

Not in progress any more; that was just an experiment in the branch
attached.

Although I have not verified this bug still happens. The last known
definite record of it was dupe bug 1654308 from 5 January.

** Changed in: canonical-devices-system-image
   Status: In Progress => Confirmed

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

Title:
  Unity8 reliably crashes on logout due to heap corruption
  (libprotobuf.so.9 called from libprotobuf-lite.so.9), causing delays
  while it dumps core and reports errors.

Status in Canonical System Image:
  Confirmed
Status in Mesa:
  New
Status in Mir:
  Triaged
Status in libphonenumber package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/72327e33abf9e9da2cd9ed1ac28b9d843c18b5bb

  This is happening on a fresh setup, which is basically:
  Xenial 17Jan iso + unity8-desktop-session-mir package

  When I logout, I get a black screen. Turns out unity8 is crashing with
  a "double free or linked list corruption"

  Please find unity8.log attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1535297/+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 1671072] Re: Child windows don't get focused

Remember we use the 'Mir' project for tracking bugs primarily and not
'mir (Ubuntu)'. Although I don't know if either is actually relevant to
this bug.

** Also affects: mir
   Importance: Undecided
   Status: New

** Changed in: mir
   Status: New => Incomplete

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

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

Title:
  Child windows don't get focused

Status in Canonical System Image:
  In Progress
Status in Mir:
  Incomplete
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  Incomplete
Status in miral package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671072/+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 1668053] Re: [unity8] kate, impossible to close "Print Preview" window

2017-03-20 Thread Чередниченко Виталий

** Changed in: canonical-devices-system-image
   Status: New => In Progress

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

Title:
  [unity8] kate, impossible to close "Print Preview" window

Status in Canonical System Image:
  In Progress
Status in Mir:
  Incomplete
Status in Ubuntu UX:
  New
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 Unity 8
  [unity8] kate, impossible to close "Print Preview" window

  see attached screenshot
  Print Preview window doesn't have windows controls or a close button

  Launch Kate, from the menu File > Print Preview
  try to close the window, you can't because doh

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668053/+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

2017-03-20 Thread Steve Langasek

** Description changed:

+ [SRU Justification]
+ Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.
+ 
+ [Test case]
+ 1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
+ 2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
+ 2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
+ 3. Install the iputils-ping package.
+ 4. ping www.freedesktop.org
+ 5. Confirm that the hostname does not resolve.
+ 6. Install the systemd package from yakkety-proposed onto the host system.
+ 7. ping www.freedesktop.org
+ 8. Confirm that the hostname does now resolve.
+ 
+ [Regression potential]
+ With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.
+ 
+ 
  $ 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.

-- 
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 Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ 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

[Touch-packages] [Bug 1674513] Re: package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить

2017-03-20 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет
  абсолютно неработоспособен; перед настройкой его  следует
  переустановить

Status in python-crypto package in Ubuntu:
  New

Bug description:
  xbgf

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-crypto 2.6.1-4build1
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptOrdering: python-crypto: Configure
  Architecture: amd64
  Date: Mon Mar 20 05:18:05 2017
  DuplicateSignature: package:python-crypto:2.6.1-4build1:пакет абсолютно 
неработоспособен; перед настройкой его  следует переустановить
  ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его  следует 
переустановить
  InstallationDate: Installed on 2017-02-06 (42 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет 
абсолютно неработоспособен; перед настройкой его  следует переустановить
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1674513/+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 1674515] Re: package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить

2017-03-20 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1674513, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1674513
   package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет 
абсолютно неработоспособен; перед настройкой его  следует переустановить

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

Title:
  package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет
  абсолютно неработоспособен; перед настройкой его  следует
  переустановить

Status in python-crypto package in Ubuntu:
  New

Bug description:
  xbgf

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-crypto 2.6.1-4build1
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptOrdering: python-crypto: Configure
  Architecture: amd64
  Date: Mon Mar 20 05:18:05 2017
  DuplicateSignature: package:python-crypto:2.6.1-4build1:пакет абсолютно 
неработоспособен; перед настройкой его  следует переустановить
  ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его  следует 
переустановить
  InstallationDate: Installed on 2017-02-06 (42 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет 
абсолютно неработоспособен; перед настройкой его  следует переустановить
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1674515/+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 1674515] [NEW] package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить

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

Public bug reported:

xbgf

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-crypto 2.6.1-4build1
ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
AptOrdering: python-crypto: Configure
Architecture: amd64
Date: Mon Mar 20 05:18:05 2017
DuplicateSignature: package:python-crypto:2.6.1-4build1:пакет абсолютно 
неработоспособен; перед настройкой его  следует переустановить
ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его  следует 
переустановить
InstallationDate: Installed on 2017-02-06 (42 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: python-crypto
Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет 
абсолютно неработоспособен; перед настройкой его  следует переустановить
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-crypto (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет
  абсолютно неработоспособен; перед настройкой его  следует
  переустановить

Status in python-crypto package in Ubuntu:
  New

Bug description:
  xbgf

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-crypto 2.6.1-4build1
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptOrdering: python-crypto: Configure
  Architecture: amd64
  Date: Mon Mar 20 05:18:05 2017
  DuplicateSignature: package:python-crypto:2.6.1-4build1:пакет абсолютно 
неработоспособен; перед настройкой его  следует переустановить
  ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его  следует 
переустановить
  InstallationDate: Installed on 2017-02-06 (42 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет 
абсолютно неработоспособен; перед настройкой его  следует переустановить
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1674515/+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 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

2017-03-20 Thread john nunnington

installed 16.04-02 onto an SSD this morning and Spotify/Pulseaudio has
been running for 2-3 hours with only a single hiccup where Spotify just
stopped - but pulseaudio daemon was still running and restarting Spotify
solved the lack of music.

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  julie 30342 F pulseaudio
   /dev/snd/controlC1:  julie 30342 F pulseaudio
   /dev/snd/controlC2:  julie 30342 F pulseaudio
   /dev/snd/controlC0:  julie 30342 F pulseaudio
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-05-19 (670 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  yakkety
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562
  mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1673942/+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 1674513] [NEW] package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить

2017-03-20 Thread Чередниченко Виталий

Public bug reported:

xbgf

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-crypto 2.6.1-4build1
ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
AptOrdering: python-crypto: Configure
Architecture: amd64
Date: Mon Mar 20 05:18:05 2017
DuplicateSignature: package:python-crypto:2.6.1-4build1:пакет абсолютно 
неработоспособен; перед настройкой его  следует переустановить
ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его  следует 
переустановить
InstallationDate: Installed on 2017-02-06 (42 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: python-crypto
Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет 
абсолютно неработоспособен; перед настройкой его  следует переустановить
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-crypto (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет
  абсолютно неработоспособен; перед настройкой его  следует
  переустановить

Status in python-crypto package in Ubuntu:
  New

Bug description:
  xbgf

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-crypto 2.6.1-4build1
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptOrdering: python-crypto: Configure
  Architecture: amd64
  Date: Mon Mar 20 05:18:05 2017
  DuplicateSignature: package:python-crypto:2.6.1-4build1:пакет абсолютно 
неработоспособен; перед настройкой его  следует переустановить
  ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его  следует 
переустановить
  InstallationDate: Installed on 2017-02-06 (42 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: пакет 
абсолютно неработоспособен; перед настройкой его  следует переустановить
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1674513/+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 1674455] Re: Keyboard input disables when laptop is rotated

2017-03-20 Thread tim474

UPDATE: Ctrl+alt+F1 and terminal doesn't work too.

But here is a workaround with disabling accelerometer:

echo "0" > "/sys/bus/usb/devices/1-2.4/power/autosuspend"
echo "auto" > "/sys/bus/usb/devices/1-2.4/power/level"
echo 1-2.4 > /sys/bus/usb/drivers/usb/unbind


(after power on and resume from suspend).

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

Title:
  Keyboard input disables when laptop is rotated

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Dell Inspirion 11-3168 with accelerometer. Now I don't want to
  use accelerometer. But if I turn the laptop to side, keyboard input
  become disabled. I can switch to console by ctrl+alt+F1 and type in
  console but I can't type in GUI when laptop is on it's side.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar 20 22:03:18 2017
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1674455/+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 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

2017-03-20 Thread Stephen M. Webb

** Changed in: canonical-devices-system-image
   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/1671731

Title:
  [xmir] closing an app while a child window is opened leaves an Xmir
  process opened eating 100% CPU

Status in Canonical System Image:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity 8
  [xmir] closing an app while a child window is opened leaves an Xmir process 
opened eating 100% CPU

  launch solitaire (just click on the sol icon from launcher, it will just run 
on Xmir)
  open the about window from the menu (Help \ About)
  now close the main window 

  now top in a terminal (see attached)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671731/+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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

2017-03-20 Thread Stephen M. Webb

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+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 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

2017-03-20 Thread Stephen M. Webb

This is simple to reproduce.  The application has disappeared from the
screen but continues to run.

It looks like qtmir is closing the window (as requested) but no word
gets out to the actual process (ie. there is no session management).
I'm suspecting the Unity 8 lifecycle for desktops is not in place yet.

Here's a snippet from $HOME/.cahe/upstart/unity8.log.

[2017-03-20:19:34:52.953] qtmir.sessions: TaskController::onSessionStarting - 
sessionName=sol^M
[2017-03-20:19:34:52.954] qtmir.applications: 
Application["sol"]::setSession(session=qtmir::Session(0x4ecb3290))^M
[2017-03-20:19:34:53.457] 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/Icon.qml:115:5: 
QML Image: Cannot open: file:///home/stephenw/.face^M
[2017-03-20:19:34:57.992] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::MirSurface(type=normal,state=restored,size=(480,376),parentSurface=QObject(0x0))^M
[2017-03-20:19:34:58.015] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::registerView(268052752) after=1^M
[2017-03-20:19:34:58.032] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setKeymap("us")^M
[2017-03-20:19:34:58.467] toplevelwindowmodel: prependSurface appId=sol 
surface=qtmir::MirSurface(0x3c828f80), filling out placeholder. after: 
(index=0,appId=sol,surface=0x3c828f80,id=11),(index=1,appId=unity8-dash,surface=0x225db2f0,id=4)^M
[2017-03-20:19:34:58.468] toplevelwindowmodel: setFocusedWindow(0x0)^M
[2017-03-20:19:34:58.499] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(true)^M
[2017-03-20:19:34:58.514] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setReady()^M
[2017-03-20:19:34:58.520] qtmir.applications: 
Application["sol"]::setInternalState(state=Running)^M
[2017-03-20:19:34:58.537] toplevelwindowmodel: 
setFocusedWindow(Window[0x28c28060, id=11, 
MirSurface[0x3c828f80,"AisleRiot"]])^M
[2017-03-20:19:34:58.664] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::requestState(restored)^M
[2017-03-20:19:34:58.673] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:19.651] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::MirSurface(type=menu,state=restored,size=(172,66),parentSurface=qtmir::MirSurface(0x3c828f80))^M
[2017-03-20:19:35:19.801] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::registerView(745266864) after=1^M
[2017-03-20:19:35:20.080] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(false)^M
[2017-03-20:19:35:20.093] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setFocused(true)^M
[2017-03-20:19:35:20.098] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setReady()^M
[2017-03-20:19:35:20.123] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:20.126] toplevelwindowmodel: 
setFocusedWindow(Window[0x33e53dc0, id=12, 
MirSurface[0x28beec90,"AisleRiot"]])^M
[2017-03-20:19:35:20.128] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setKeymap("us")^M
[2017-03-20:19:35:23.549] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setLive(false)^M
[2017-03-20:19:35:23.552] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::unregisterView(745266864) after=0 live=false^M
[2017-03-20:19:35:23.553] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::updateExposure(false)^M
[2017-03-20:19:35:23.555] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(true)^M
[2017-03-20:19:35:23.622] toplevelwindowmodel: 
setFocusedWindow(Window[0x28c28060, id=11, MirSurface[0x3c828f80,"Klondike"]])^M
[2017-03-20:19:35:23.625] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::~MirSurface() viewCount=0^M
[2017-03-20:19:35:23.684] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::MirSurface(type=dialog,state=restored,size=(468,353),parentSurface=qtmir::MirSurface(0x3c828f80))^M
[2017-03-20:19:35:23.711] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::registerView(744596304) after=1^M
[2017-03-20:19:35:23.893] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(false)^M
[2017-03-20:19:35:23.904] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setFocused(true)^M
[2017-03-20:19:35:23.911] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setReady()^M
[2017-03-20:19:35:23.921] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:23.923] toplevelwindowmodel: 
setFocusedWindow(Window[0x2e53a140, id=13, MirSurface[0x35577d70,"About 
Aisleriot"]])^M
[2017-03-20:19:35:23.924] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setKeymap("us")^M
[2017-03-20:19:35:26.995] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::activate()^M
[2017-03-20:19:35:57.911] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::close()^M
[2017-03-20:19:36:00.995] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::onCloseTimedOut()^M
[2017-03-20:19:36:01.013] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setLive(false)^M
[2017-03-20:19:36:01.018] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::unregisterView(268052752) after=0 live=false^M
[2017-03-20:19:36:01.020] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::updateExposure(false)^M
[2017-03-20:19:36:01.025] qtmir.surfaces:

[Touch-packages] [Bug 1673199] Re: Greeter shows "unknown" session if user has never logged in when it should show default.

** Branch linked: lp:~josharenson/unity8/fix-default-session

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

Title:
  Greeter shows "unknown" session if user has never logged in when it
  should show default.

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Create a new user
  2. Go to greeter
  3. Look at the session icon for the new user

  Expected: Ubuntu Icon
  Actual: Unknown Icon

  It should be noted that LightDM handles this fine and launches, what I
  presume is, the default session (ubuntu)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1673199/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

2017-03-20 Thread Phil

Hey Guys..noobie here so please be gentle.

I have a Asus X541U ... duel booting Ubuntu Studio 16.04 and Windows 10

Everything works fine in Windowswhen i boot up Ubuntu and sign into Skype, 
I can't get the mic working.  Same with other recording programs (Ie Audacity) 
I need to run JACK and IDJC as well with it...

Please any help would be amazing...everyone around me thinks I'm
speaking a different language

Thanks!

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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 1674501] [NEW] /usr/lib/bluetooth/bluetoothd:11:g_slist_find:avdtp_open:endpoint_open_cb:endpoint_reply:complete_pending_call_and_unlock

2017-03-20 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.41-0ubuntu3, 
the problem page at 
https://errors.ubuntu.com/problem/73af5b8f19bde06f5dbbfaf55c4448c1b48d637f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: wily xenial yakkety

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

Title:
  
/usr/lib/bluetooth/bluetoothd:11:g_slist_find:avdtp_open:endpoint_open_cb:endpoint_reply:complete_pending_call_and_unlock

Status in bluez package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.41-0ubuntu3, 
the problem page at 
https://errors.ubuntu.com/problem/73af5b8f19bde06f5dbbfaf55c4448c1b48d637f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674501/+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 1029289] Re: Need to authorize my google account each time I boot the computer

2017-03-20 Thread Eugene Lazutkin

This bug has started to appear for me in 16.10.

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  Fix Released
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in account-plugins package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in signon-plugin-oauth2 package in Ubuntu:
  Fix Released
Status in account-plugins source package in Quantal:
  Fix Released
Status in signon-plugin-oauth2 source package in Quantal:
  Fix Released
Status in account-plugins source package in Trusty:
  Fix Released
Status in evolution-data-server source package in Trusty:
  Fix Released
Status in signon-plugin-oauth2 source package in Trusty:
  Fix Released

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case] Disable/re-enable your Google account. When affected by
  this bug, a notification will appear and you'll be asked to enter your
  Google password in the Online Accounts panel in System Settings.

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  Old description
  ===

  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1674492] Re: cron: /etc/default/cron should not actually be deprecated

2017-03-20 Thread Matthew Hall

This bug is related to two other bugs:

Similar issue where /etc/default/cron is still relevant:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1078607

Inaccurate commit where file was wrongly marked deprecated, for a bad boot 
speed related reason, in the now deprecated Upstart system. This should 
probably be reverted in some way.
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/794082

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

Title:
  cron: /etc/default/cron should not actually be deprecated

Status in cron package in Ubuntu:
  New

Bug description:
  The /etc/default/cron file claims that it has been deprecated in its own
  comments, and refers to an upstart configuration file (which is deprecated in
  Ubuntu 15.10 and up, in favor of systemd):

  $ cat /etc/default/cron
  # This file has been deprecated. Please add custom options for cron to
  # /etc/init/cron.conf and/or /etc/init/cron.override directly. See
  # the init(5) man page for more information.
  EXTRA_OPTS="-L 15" *** (added on my system for debugging) ***

  Yet, the systemd cron.service actually respects the content of the
  file:

  $ cat /lib/systemd/system/cron.service
  [Unit]
  Description=Regular background program processing daemon
  Documentation=man:cron(8)

  [Service]
  EnvironmentFile=-/etc/default/cron
  ExecStart=/usr/sbin/cron -f $EXTRA_OPTS
  IgnoreSIGPIPE=false
  KillMode=process

  [Install]
  WantedBy=multi-user.target
  (venv) arceo@lab-dev-01:~/poc-connectors/scripts$

  So, the inaccurate comments in /etc/default/cron, and other such files (if
  this was perhaps an automated error by debhelper or similar tools), should be
  corrected accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1674492/+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 1674492] [NEW] cron: /etc/default/cron should not actually be deprecated

2017-03-20 Thread Matthew Hall

Public bug reported:

The /etc/default/cron file claims that it has been deprecated in its own
comments, and refers to an upstart configuration file (which is deprecated in
Ubuntu 15.10 and up, in favor of systemd):

$ cat /etc/default/cron
# This file has been deprecated. Please add custom options for cron to
# /etc/init/cron.conf and/or /etc/init/cron.override directly. See
# the init(5) man page for more information.
EXTRA_OPTS="-L 15" *** (added on my system for debugging) ***

Yet, the systemd cron.service actually respects the content of the file:

$ cat /lib/systemd/system/cron.service
[Unit]
Description=Regular background program processing daemon
Documentation=man:cron(8)

[Service]
EnvironmentFile=-/etc/default/cron
ExecStart=/usr/sbin/cron -f $EXTRA_OPTS
IgnoreSIGPIPE=false
KillMode=process

[Install]
WantedBy=multi-user.target
(venv) arceo@lab-dev-01:~/poc-connectors/scripts$

So, the inaccurate comments in /etc/default/cron, and other such files (if
this was perhaps an automated error by debhelper or similar tools), should be
corrected accordingly.

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

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

Title:
  cron: /etc/default/cron should not actually be deprecated

Status in cron package in Ubuntu:
  New

Bug description:
  The /etc/default/cron file claims that it has been deprecated in its own
  comments, and refers to an upstart configuration file (which is deprecated in
  Ubuntu 15.10 and up, in favor of systemd):

  $ cat /etc/default/cron
  # This file has been deprecated. Please add custom options for cron to
  # /etc/init/cron.conf and/or /etc/init/cron.override directly. See
  # the init(5) man page for more information.
  EXTRA_OPTS="-L 15" *** (added on my system for debugging) ***

  Yet, the systemd cron.service actually respects the content of the
  file:

  $ cat /lib/systemd/system/cron.service
  [Unit]
  Description=Regular background program processing daemon
  Documentation=man:cron(8)

  [Service]
  EnvironmentFile=-/etc/default/cron
  ExecStart=/usr/sbin/cron -f $EXTRA_OPTS
  IgnoreSIGPIPE=false
  KillMode=process

  [Install]
  WantedBy=multi-user.target
  (venv) arceo@lab-dev-01:~/poc-connectors/scripts$

  So, the inaccurate comments in /etc/default/cron, and other such files (if
  this was perhaps an automated error by debhelper or similar tools), should be
  corrected accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1674492/+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 1672555] Re: If srcpkg is in main but a binary package is in universe, `apt changelog` fails

2017-03-20 Thread Nish Aravamudan

Thanks to juliank on IRC: https://gist.github.com/julian-
klode/600237d0b61cf92b01748b25cf5921d7 A potential configuration-only
change for old clients backwards-compatiblity.

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

Title:
  If srcpkg is in main but a binary package is in universe, `apt
  changelog` fails

Status in extract-changelogs:
  In Progress
Status in apt package in Ubuntu:
  New

Bug description:
  $ apt changelog qemu
  Err:1 http://changelogs.ubuntu.com qemu 1:2.8+dfsg-3ubuntu2 Changelog
Changelog unavailable for qemu=1:2.8+dfsg-3ubuntu2 (404  Not Found)
  E: Failed to fetch 
http://changelogs.ubuntu.com/changelogs/pool/universe/q/qemu/qemu_2.8+dfsg-3ubuntu2/changelog
  Changelog unavailable for qemu=1:2.8+dfsg-3ubuntu2 (404  Not Found)

  This is because the binary package's component is used to generate the
  URI, but the source is in main and changelogs are organized by source.

  Based upon IRC conversation with slangasek and juliank, it possibly
  makes sense to flatten the pool/ changelogs to drop the component
  subdirectory (with symlinks for BC) and then change apt to not use the
  component in the URI generation

To manage notifications about this bug go to:
https://bugs.launchpad.net/extract-changelogs/+bug/1672555/+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 1674477] [NEW] gnome screenshot gtk-mir crashes on taking the shot

2017-03-20 Thread kevin gunn

Public bug reported:

Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
then export GDK_BACKEND=mir
launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

Attempt to take a screen shot in any form and it will crash (see
attached log)


according to attente: 
gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
so i think the solution is to have u8 implement that interface...
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

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

** Affects: gtk+3.0 (Ubuntu)
 Importance: High
 Status: New

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


** Tags: unity8-desktop

** Attachment added: "screenshot.log"
   
https://bugs.launchpad.net/bugs/1674477/+attachment/4841196/+files/screenshot.log

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Tags added: unity8-desktop

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+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 1579819] Re: package linux-image-extra-3.16.0-41-generic 3.16.0-41.57~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

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

Title:
  package linux-image-extra-3.16.0-41-generic 3.16.0-41.57~14.04.1
  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:
  most of the applications like okular,flash are crashing..not able to
  open any file and unable to detect its location.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.16.0-41-generic 3.16.0-41.57~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-62.83~14.04.1-generic 3.16.7-ckt23
  Uname: Linux 3.16.0-62-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon May  9 21:23:28 2016
  DuplicateSignature: 
package:linux-image-extra-3.16.0-41-generic:3.16.0-41.57~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2015-06-06 (337 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.16.0-41-generic 3.16.0-41.57~14.04.1 
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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1579819/+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 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"

** Description changed:

  Mouse event compression stopped working in Qt 5, a regression from Qt 4:
  
-https://bugreports.qt.io/browse/QTBUG-40889
+    https://bugreports.qt.io/browse/QTBUG-40889
  
  The bug was fixed in Qt 5.6 https://codereview.qt-
- project.org/#/c/126136/ where it has been thoroughly tested by now.
+ project.org/#/c/126136/ where the fix has been thoroughly tested by now.
  
  Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a
  backport of the 5.6 patch (only one trivial hunk failed, which was
  easily fixed).
  
  [Impact]
  
  The bug affects any program that relies on the event compression Qt
  normally does. For example, VTK programs (ParaView, Tomviz, ...) do
  their rendering in response to mouse events during camera movements, and
  with event compression at the Qt level suddenly gone, camera movements
  become very slow, since the application is now flooded with mouse events
  and the rendering lags behind.
  
  The problem is not limited to these programs however; it can be observed
  by simply putting two regular, slightly slow-to-render, widgets into a
  QSplitter and moving the splitter handle. The result is a syrup-like
  experience as the widgets try to keep up with the onslaught of resize
  events due to the lack of mouse event compression.
  
  [Test Case]
  
  The attached test application can be used to check if event compression
  is functioning. It performs some artificial work on each mouse move and
  prints a message. Click and drag the mouse a little. After releasing the
  mouse, you'll notice that the printouts keeps coming for quite a while,
  as the program is catching up with the flood of events.
  
  With the attached patch (and with Qt 4), the problem is gone - the mouse
  event stream is compressed and the printouts are no longer lagging
  behind.
  
  [Regression Potential]
  
  There's a small risk that some applications have made workarounds for
  the faulty behavior, and that unwanted behavior is introduced if this
  bug is fixed. But chances are high that such workarounds will keep
  working, as the obvious workaround is to do timer based rendering
  instead of event based. The workarounds will then simply become
  unnecessary, but shouldn't cause problems.
  
  I'm asking for someone to nominate this bug for an SRU of 16.04 LTS.

** Description changed:

  Mouse event compression stopped working in Qt 5, a regression from Qt 4:
  
     https://bugreports.qt.io/browse/QTBUG-40889
  
  The bug was fixed in Qt 5.6 https://codereview.qt-
  project.org/#/c/126136/ where the fix has been thoroughly tested by now.
  
  Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a
  backport of the 5.6 patch (only one trivial hunk failed, which was
  easily fixed).
  
  [Impact]
  
  The bug affects any program that relies on the event compression Qt
- normally does. For example, VTK programs (ParaView, Tomviz, ...) do
+ normally performs. For example, VTK programs (ParaView, Tomviz, ...) do
  their rendering in response to mouse events during camera movements, and
  with event compression at the Qt level suddenly gone, camera movements
  become very slow, since the application is now flooded with mouse events
  and the rendering lags behind.
  
  The problem is not limited to these programs however; it can be observed
  by simply putting two regular, slightly slow-to-render, widgets into a
  QSplitter and moving the splitter handle. The result is a syrup-like
  experience as the widgets try to keep up with the onslaught of resize
  events due to the lack of mouse event compression.
  
  [Test Case]
  
  The attached test application can be used to check if event compression
  is functioning. It performs some artificial work on each mouse move and
  prints a message. Click and drag the mouse a little. After releasing the
  mouse, you'll notice that the printouts keeps coming for quite a while,
  as the program is catching up with the flood of events.
  
  With the attached patch (and with Qt 4), the problem is gone - the mouse
  event stream is compressed and the printouts are no longer lagging
  behind.
  
  [Regression Potential]
  
  There's a small risk that some applications have made workarounds for
  the faulty behavior, and that unwanted behavior is introduced if this
  bug is fixed. But chances are high that such workarounds will keep
  working, as the obvious workaround is to do timer based rendering
  instead of event based. The workarounds will then simply become
  unnecessary, but shouldn't cause problems.
  
  I'm asking for someone to nominate this bug for an SRU of 16.04 LTS.

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

Title:
  Please consider SRU of "xcb: Compress mouse motion and touch update
  events"

Status in qtbase-opensource-src package in Ubuntu:

[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"

** Patch added: "debdiff for 5.5.1+dfsg-16ubuntu7.3 with backported fix from Qt
5.6"

https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+attachment/4841178/+files/fix-qtbug-40889.debdiff

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

Title:
Please consider SRU of "xcb: Compress mouse motion and touch update
events"

Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Status in qtbase-opensource-src source package in Xenial:
New

Bug description:
Mouse event compression stopped working in Qt 5, a regression from Qt
4:

https://bugreports.qt.io/browse/QTBUG-40889

The bug was fixed in Qt 5.6 https://codereview.qt-
project.org/#/c/126136/ where the fix has been thoroughly tested by
now.

Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a
backport of the 5.6 patch (only one trivial hunk failed, which was
easily fixed).

[Impact]

The bug affects any program that relies on the event compression Qt
normally performs. For example, VTK programs (ParaView, Tomviz, ...)
do their rendering in response to mouse events during camera
movements, and with event compression at the Qt level suddenly gone,
camera movements become very slow, since the application is now
flooded with mouse events and the rendering lags behind.

The problem is not limited to these programs however; it can be
observed by simply putting two regular, slightly slow-to-render,
widgets into a QSplitter and moving the splitter handle. The result is
a syrup-like experience as the widgets try to keep up with the
onslaught of resize events due to the lack of mouse event compression.

[Test Case]

The attached test application can be used to check if event
compression is functioning. It performs some artificial work on each
mouse move and prints a message. Click and drag the mouse a little.
After releasing the mouse, you'll notice that the printouts keeps
coming for quite a while, as the program is catching up with the flood
of events.

With the attached patch (and with Qt 4), the problem is gone - the
mouse event stream is compressed and the printouts are no longer
lagging behind.

[Regression Potential]

There's a small risk that some applications have made workarounds for
the faulty behavior, and that unwanted behavior is introduced if this
bug is fixed. But chances are high that such workarounds will keep
working, as the obvious workaround is to do timer based rendering
instead of event based. The workarounds will then simply become
unnecessary, but shouldn't cause problems.

I'm asking for someone to nominate this bug for an SRU of 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+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 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"

Dmitry: I've updated the description with the SRU template. I also
attached a test case and a debdiff.

I've tested that the updated package fixes the problem.

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

Title:
Please consider SRU of "xcb: Compress mouse motion and touch update
events"

Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Status in qtbase-opensource-src source package in Xenial:
New

Bug description:
Mouse event compression stopped working in Qt 5, a regression from Qt
4:

https://bugreports.qt.io/browse/QTBUG-40889

The bug was fixed in Qt 5.6 https://codereview.qt-
project.org/#/c/126136/ where the fix has been thoroughly tested by
now.

Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a
backport of the 5.6 patch (only one trivial hunk failed, which was
easily fixed).

[Impact]

[Test Case]

With the attached patch (and with Qt 4), the problem is gone - the
mouse event stream is compressed and the printouts are no longer
lagging behind.

[Regression Potential]

I'm asking for someone to nominate this bug for an SRU of 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+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 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"

** Description changed:

- A fix for QTBUG-40889 was worked out and submitted at
+ Mouse event compression stopped working in Qt 5, a regression from Qt 4:

- https://codereview.qt-project.org/#/c/115531/
+https://bugreports.qt.io/browse/QTBUG-40889

- but due to coming in a bit late, was moved to Qt 5.6
+ The bug was fixed in Qt 5.6 https://codereview.qt-
+ project.org/#/c/126136/ where it has been thoroughly tested by now.

- https://codereview.qt-project.org/#/c/126136/
+ Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a
+ backport of the 5.6 patch (only one trivial hunk failed, which was
+ easily fixed).

- The bug is about mouse motion event compression malfunctioning, and it
- has grave consequences for some applications, where the flood of events
- make rendering sluggish (e.g. anything based on VTK, but probably
- others).
+ [Impact]

- ParaView developer Ben Boeckel has tried the patch [2] against 5.5 and
- confirmed it fixes rendering/interaction in VTK applications.
+ The bug affects any program that relies on the event compression Qt
+ normally does. For example, VTK programs (ParaView, Tomviz, ...) do
+ their rendering in response to mouse events during camera movements, and
+ with event compression at the Qt level suddenly gone, camera movements
+ become very slow, since the application is now flooded with mouse events
+ and the rendering lags behind.

- It is not possible to work around the bug at the application level in a
- satisfactory way, only by resorting to timer-based rendering.
+ The problem is not limited to these programs however; it can be observed
+ by simply putting two regular, slightly slow-to-render, widgets into a
+ QSplitter and moving the splitter handle. The result is a syrup-like
+ experience as the widgets try to keep up with the onslaught of resize
+ events due to the lack of mouse event compression.

- I suggest an SRU to patch the Ubuntu Qt package with the patch that was
- originally meant for the 5.x branch (first URL above). The patch was
- later integrated in 5.6 where it has been well tested.
+ [Test Case]

- [1] https://bugreports.qt.io/browse/QTBUG-40889
- [2]
http://vtk.1045678.n5.nabble.com/Delayed-mouse-interaction-due-to-event-loop-bug-in-Qt5-tp5730474p5732870.html
+ The attached test application can be used to check if event compression
+ is functioning. It performs some artificial work on each mouse move and
+ prints a message. Click and drag the mouse a little. After releasing the
+ mouse, you'll notice that the printouts keeps coming for quite a while,
+ as the program is catching up with the flood of events.
+
+ With the attached patch (and with Qt 4), the problem is gone - the mouse
+ event stream is compressed and the printouts are no longer lagging
+ behind.
+
+ [Regression Potential]
+
+ There's a small risk that some applications have made workarounds for
+ the faulty behavior, and that unwanted behavior is introduced if this
+ bug is fixed. But chances are high that such workarounds will keep
+ working, as the obvious workaround is to do timer based rendering
+ instead of event based. The workarounds will then simply become
+ unnecessary, but shouldn't cause problems.
+
+ I'm asking for someone to nominate this bug for an SRU of 16.04 LTS.

** Attachment added: "Test case to demonstrate the bug"

https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+attachment/4841177/+files/qtbug40889.zip

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

Title:
Please consider SRU of "xcb: Compress mouse motion and touch update
events"

Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Status in qtbase-opensource-src source package in Xenial:
New

Bug description:
Mouse event compression stopped working in Qt 5, a regression from Qt
4:

https://bugreports.qt.io/browse/QTBUG-40889

The bug was fixed in Qt 5.6 https://codereview.qt-
project.org/#/c/126136/ where the fix has been thoroughly tested by
now.

Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a
backport of the 5.6 patch (only one trivial hunk failed, which was
easily fixed).

[Impact]

[Touch-packages] [Bug 1652785] Re: package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

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

Title:
  package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Was playing a game in fullscreen mode while the updates ran, in case
  that affects things.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Tue Dec 27 09:26:49 2016
  DuplicateSignature:
   package:unattended-upgrades:0.90ubuntu0.2
   Installing new version of config file /etc/logrotate.d/unattended-upgrades 
...
   frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server 
:0.
   dpkg: error processing package unattended-upgrades (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-09-04 (844 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-12-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1652785/+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 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

2017-03-20 Thread Spike

fwiw a lot of people here are talking about failing to pairing, but
pairing for me actually works just fine, however the keyboard won't
connect (it's a mac wireless keyboard).

BT adapter works fine as I have a wireless mouse connected through it.

thanks,

Spike

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

Title:
  [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+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 1028115] Re: Gdk.cairo_region_create_from_surface() raises an error in GI

2017-03-20 Thread Bug Watch Updater

** Changed in: pygobject
   Status: Confirmed => Fix Released

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

Title:
  Gdk.cairo_region_create_from_surface() raises an error in GI

Status in pygobject:
  Fix Released
Status in py3cairo package in Ubuntu:
  Fix Released
Status in pygobject package in Ubuntu:
  Fix Released
Status in py3cairo package in Debian:
  Fix Released

Bug description:
  This happens on current 12.10 daily:

  >>> from gi.repository import Gdk
  >>> import cairo
  >>> surface = cairo.ImageSurface(0, 100, 100)
  >>> Gdk.cairo_region_create_from_surface(surface)
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python2.7/dist-packages/gi/types.py", line 47, in function
  return info.invoke(*args, **kwargs)
  TypeError: Couldn't find conversion for foreign struct 'cairo.Region'

  Upstream has some additional info and a couple of patches for this:
  https://bugzilla.gnome.org/show_bug.cgi?id=667959
  https://bugs.freedesktop.org/show_bug.cgi?id=44336

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/1028115/+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 1672722] Re: Unclickable gap between adjacent titlebar menus in Unity8

2017-03-20 Thread Daniel d'Andrada

** Description changed:

  Ubuntu 17.04 unity8
  
- i'm starting to hit more and more the gab in the menu (space between the
+ i'm starting to hit more and more the gap in the menu (space between the
  menu strings). clicking there won't open the submenu.
  
  launch kate native, hover the menu, click on the space between the menu
  strings. should not be such a thing. the space between the hitboxes
  should be 0 so you don't end up in situations like this
  
  see screenshot

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

Title:
  Unclickable gap between adjacent titlebar menus in Unity8

Status in Canonical System Image:
  In Progress
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 17.04 unity8

  i'm starting to hit more and more the gap in the menu (space between
  the menu strings). clicking there won't open the submenu.

  launch kate native, hover the menu, click on the space between the
  menu strings. should not be such a thing. the space between the
  hitboxes should be 0 so you don't end up in situations like this

  see screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672722/+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 1674459] [NEW] Restart daemon after upgrade

2017-03-20 Thread Gustavo Pichorim Boiko

Public bug reported:

It is important that the daemon is restarted after package upgrades so
that clients are always running the latest version.

Note that currently this might cause clients that are already running to
fail (in case the dbus interfaces are changed).

** Affects: history-service (Ubuntu)
 Importance: Medium
 Assignee: Gustavo Pichorim Boiko (boiko)
 Status: New

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

Title:
  Restart daemon after upgrade

Status in history-service package in Ubuntu:
  New

Bug description:
  It is important that the daemon is restarted after package upgrades so
  that clients are always running the latest version.

  Note that currently this might cause clients that are already running
  to fail (in case the dbus interfaces are changed).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1674459/+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 1674455] [NEW] Keyboard input disables when laptop is rotated

2017-03-20 Thread tim474

Public bug reported:

I have Dell Inspirion 11-3168 with accelerometer. Now I don't want to
use accelerometer. But if I turn the laptop to side, keyboard input
become disabled. I can switch to console by ctrl+alt+F1 and type in
console but I can't type in GUI when laptop is on it's side.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Mar 20 22:03:18 2017
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Keyboard input disables when laptop is rotated

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Dell Inspirion 11-3168 with accelerometer. Now I don't want to
  use accelerometer. But if I turn the laptop to side, keyboard input
  become disabled. I can switch to console by ctrl+alt+F1 and type in
  console but I can't type in GUI when laptop is on it's side.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar 20 22:03:18 2017
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1674455/+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 1672804] Re: can't login to dropbox.com on desktop

** Branch linked: lp:~ci-train-bot/webbrowser-app/webbrowser-app-ubuntu-
zesty-2615

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

Title:
  can't login to  dropbox.com on desktop

Status in Canonical System Image:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  when I try to access dropbox.com on webbrowser-app on desktop I get an
  banner saying our browser is not supported, and it's displayed on top
  of the login button so there is no way to login.

  Guessing we need an override for this site

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672804/+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 1673404] Re: maximized button stays in the hover state until you move the mouse if you right click on maximize

2017-03-20 Thread kevin gunn

** Tags added: unity8-desktop

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

Title:
  maximized button stays in the hover state until you move the mouse if
  you right  click on maximize

Status in Canonical System Image:
  Triaged
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  ubuntu 17.04 unity 8

  maximized button stays in the hover state until you move the mouse if
  you right  click on maximize

  open random app, right click on maximize button in title bar. the
  button looks like the mouse pointer is over (hover) but the mouse
  pointer is not there, remains like this until you move the mouse.

  see attached screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673404/+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 1674058] Re: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-03-20 Thread Phillip Susi

Have you modified your /etc/init.d/cups file?  Can you show its contents
and the output of apt-cache policy cups-daemon?


** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  I tried to install updates for the system upgrades. It doesn't seem to
  be installing properly.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.2
  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
  Date: Sat Mar 18 23:05:35 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-26 (297 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2017-03-20 Thread Geoff Short

Follow-up to #34, on a system where unattended-upgrades happens to be
running when shutdown is called, the shutdown does not wait, therefore
any running dpkg is killed and the package left in an inconsistent
state.

 - Xenial with single partition, InstallOnShutdown not defined.

This may be a separate issue, but I'll investigate further before
raising it as such.

-- 
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:
  In Progress
Status in unattended-upgrades source package in Xenial:
  Triaged
Status in unattended-upgrades source package in Yakkety:
  Triaged
Status in unattended-upgrades package in Debian:
  New

Bug description:
  [SRU justification]
  This fix is needed to make sure that the system does not hang on shutdown 
when /var is a speparate file system

  [Impact]
  System can hang up to 10 minutes if not fixed.

  [Fix]
  Change the systemd unit's ExecStart to an ExecStop so the unit is correctly 
sequenced.

  [Test Case]
  In a VM with /var separated from the / file system, shutdown the VM. It will 
hang for 10 minutes

  [Regression]
  None to be expected. A ExecStop unit will be sequenced before the Before= 
units which is earlier than previously.

  [Original description of the problem]
  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 1659534] Re: userdel doesn't supports extrausers

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

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

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  New
Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659534/+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 1669643] Re: Wifi WPA2-PSK 4-Way Handshake Faliure

2017-03-20 Thread Dhruv Ramdev

I am facing issue almost similar to your. I have ubuntu gnome 17.04 .I
can connect to wifi but the wifi does not seem to work even though it
shows connected. I dont have much knowledge of troubleshooting . What
file will be needed?

Chrome Shows : DNS PROBE BAD CONFIG .

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

Title:
  Wifi WPA2-PSK 4-Way Handshake Faliure

Status in network-manager package in Ubuntu:
  New

Bug description:
  After I upgraded to Ubuntu 17.04 yesterday, I started having this
  problem. My device will only connect to unsecured (public) WiFi
  networks. I tried booting into an older series kernel (4.8.0) and the
  issue persisted.

  I ran `sudo systemctl status network-manager` and got this:

  device (wlx501ac505fcbc): supplicant interface state: associating -> 4-way 
handshake
  sup-iface[0x55eb41e5bc20,wlx501ac505fcbc]: connection disconnected (reason 15)
  device (wlx501ac505fcbc): supplicant interface state: 4-way handshake -> 
disconnected
  device (wlx501ac505fcbc): Activation: (wifi) disconnected during association, 
asking for new key
  device (wlx501ac505fcbc): state change: config -> need-auth (reason 
'supplicant-disconnect') [50 60 8]
  device (wlx501ac505fcbc): supplicant interface state: disconnected -> inactive

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  2 20:55:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-04 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  IpRoute:
   default via 192.168.42.129 dev enp0s20u2 proto static metric 100 
   169.254.0.0/16 dev enp0s20u2 scope link metric 1000 
   192.168.42.0/24 dev enp0s20u2 proto kernel scope link src 192.168.42.246 
metric 100
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   enp0s20u2  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/4  Wired connection 1  
474aac38-e4d8-4102-b2eb-c5cc6bdb17aa  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   AC:37:43:7C:B4:57  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   wlx501ac505fcbcwifi  disconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1669643/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

2017-03-20 Thread Daniel d'Andrada

Don't know what's different in my system but here vlc won't launch. I
can launch firefox though which displays the same bug (menus immediately
disappearing) but it doesn't cause unity8 to crash.

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

Title:
  Unity8 crashed right clicking on vlc [terminate called after throwing
  an instance of 'std::out_of_range' what(): map::at]

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in Mir 0.26 series:
  Incomplete
Status in MirAL:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8

  install vlc, launch it from app drawer or launcher
  try to use the menu, the menu shows for a split second and closes 
  try to right click on vlc, here it just crashes/restarts unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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)

2017-03-20 Thread Denys Vitali

Same problem here, Acer Aspire VN7-792G

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

dvitali@denvit-ws1:~ $ aplay -L 
  -1-
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
sysdefault:CARD=PCH
HDA Intel PCH, ALC255 Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
Front speakers
surround21:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=PCH,DEV=0
HDA Intel PCH, ALC255 Digital
IEC958 (S/PDIF) Digital Audio Output
hdmi:CARD=PCH,DEV=0
HDA Intel PCH, HDMI 0
HDMI Audio Output
hdmi:CARD=PCH,DEV=1
HDA Intel PCH, HDMI 1
HDMI Audio Output
hdmi:CARD=PCH,DEV=2
HDA Intel PCH, HDMI 2
HDMI Audio Output

--
Linux denvit-ws1 4.10.3-1-ARCH #1 SMP PREEMPT Wed Mar 15 09:17:17 CET 2017 
x86_64 GNU/Linux
--
dvitali@denvit-ws1:~ $ cat /proc/asound/cards   
  -1-
 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 129
-
pacman -Q | grep ^alsa
alsa-lib 1.1.3-1
alsa-plugins 1.1.1-1
alsa-utils 1.1.3-2
alsaequal 0.6-16

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

[Touch-packages] [Bug 1636564] Re: Segfault from libX11.so.6.3.0

2017-03-20 Thread Jan Lachnitt

Another report and some thoughts below

HW: Asus Vivobook (touchscreen, Intel graphics), external monitor attached.
OS: Linux Mint 18 Cinnamon x64.
State before crash: Running X session using both displays ("big desktop"), 
several applications, Vivaldi browser active.
My aim: Lock the computer.
Course of action, the USUAL part: Pressed Ctrl+Alt+L, not locked - Vivaldi 
displayed its menu (to be displayed upon pressing Alt), tapped the touchscreen 
to get rid of the menu and thus actually lock the computer.
Course of action, the UNUSUAL part: Black screen for a few seconds, then login 
screen, old X session gone.

syslog:
Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]:   after 2925 
requests (2925 known processed) with 0 events remaining.
Mar 20 14:43:20 VivoBook cinnamon-session[1640]: Gdk-WARNING: t+4492,79569s: 
cinnamon-session: Fatal IO error 11 (Prostředek je dočasně nepřístupný) on X 
server :0.
Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus 
can't be made
Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus 
can't be made
Mar 20 14:43:20 VivoBook mdm[1212]: WARNING: mdm_slave_xioerror_handler: 
Kritická chyba X - Restartování :0
Mar 20 14:43:20 VivoBook kernel: [ 4538.677519] vivaldi-bin[4100]: segfault at 
968 ip 7f61ac384643 sp 7ffc09f25b50 error 4 in 
libX11.so.6.3.0[7f61ac35c000+135000]
Mar 20 14:43:20 VivoBook ag[4118]: mdm-superpost Starting...
Mar 20 14:43:20 VivoBook ag[4122]: mdm-superpost Finished
Mar 20 14:43:20 VivoBook console-kit-daemon[1566]: (process:4128): 
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Mar 20 14:43:21 VivoBook acpid: client 1219[0:0] has disconnected
Mar 20 14:43:21 VivoBook acpid: client connected from 4131[0:0]
Mar 20 14:43:21 VivoBook acpid: 1 client rule loaded
Mar 20 14:43:22 VivoBook ag[4139]: mdm-superinit Starting...
Mar 20 14:43:22 VivoBook ag[4140]: mdm-superinit Finished

Xorg.0.log covers the new session, Xorg.0.log.old has no record of the
event.

The segfault really seems to affect multiple users, especially with 
Chromium-based browsers, e.g.:
https://bbs.archlinux.org/viewtopic.php?id=131328 - from 2011 already
https://bbs.archlinux.org/viewtopic.php?id=221888 - solution?

I don't know if syslog preserves the order of events (within a second), but if 
yes, then the segfault is just a consequence of another problem, e.g.:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/999191

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

Title:
  Segfault from libX11.so.6.3.0

Status in libx11 package in Ubuntu:
  Confirmed

Bug description:
  Something went wrong with my Ubuntu 16.04 LTS desktop today.  When I
  got back to the system Mattermost and a Chrome were indicating that
  the network was not working.  I started to look about and it seemed
  that my main ethernet network connection had lost its IPv4 address
  somehow.  ifconfig and the GUI network manager confirmed this.

  To try and resolve this I physically removed the connector and the
  plugged it back in.  Shortly after I did this my GUI seemed to die out
  and I ended up back at the login screen.

  Once everything had calmed down I logged back in.  After some digging
  about in the logs I noticed the following in /var/log/kern.log

  Oct 25 13:01:09 thorne-ul-dt kernel: [694321.877561] Mattermost[744]: 
segfault at 968 ip 7f8a9e257643 sp 7ffe72a3b510 error 4 in 
libX11.so.6.3.0[7f8a9e22f000+135000]
  Oct 25 13:01:09 thorne-ul-dt kernel: [694322.029362] chrome[745]: segfault at 
968 ip 7fd4b5c73643 sp 7fff94f78d90 error 4 in 
libX11.so.6.3.0[7fd4b5c4b000+135000]

  That seemed to be the correct time for the problem I noticed.   What
  exactly caused it I am not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libx11-6 2:1.6.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Tue Oct 25 17:07:28 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on

[Touch-packages] [Bug 1673934] Re: when gsfonts is installed the browser will render the pages badly

2017-03-20 Thread ET

Sure, here you go. The first picture is with gsfonts package installed,
the second (in which you can actually read the page) is with gsfonts
package removed.

** Attachment added: "screenshot20170320_193744013.png"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1673934/+attachment/4841094/+files/screenshot20170320_193744013.png

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

Title:
  when gsfonts is installed the browser will render the pages badly

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  In ubuntu touch OTA15 on a meizu pro5.
  After installing gsfonts package. Meaning that you make the root readwrite 
and run: sudo apt-get install gsfont.
  At least some pages will render badly: the numbers are rendered as bubbles 
and there are no spaces between words.
  example:https://en.m.wikipedia.org/wiki/Capacitive_power_supply

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1673934/+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 1673934] Re: when gsfonts is installed the browser will render the pages badly

2017-03-20 Thread ET

This is the second good render with the gsfonst package uninstalled.

** Attachment added: "screenshot20170320_193924073.png"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1673934/+attachment/4841095/+files/screenshot20170320_193924073.png

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

Title:
  when gsfonts is installed the browser will render the pages badly

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  In ubuntu touch OTA15 on a meizu pro5.
  After installing gsfonts package. Meaning that you make the root readwrite 
and run: sudo apt-get install gsfont.
  At least some pages will render badly: the numbers are rendered as bubbles 
and there are no spaces between words.
  example:https://en.m.wikipedia.org/wiki/Capacitive_power_supply

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1673934/+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 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-03-20 Thread Eric Desrochers

Here's some context after a conversation about this bug on channel :
#ubuntu-release

...
[10:01:50]  hi SRU, I'm currently working on a case (no LP bug yet) 
about an OpenSSL bug on new AMD CPU (Ryzen) released last Feb ... where the SHA 
Extension routine is not called on AMD Ryzen cores. My question is since this 
look like H/W enablement ... do you think this could be eligible for SRU in 
stable release such like Xenial ? or this will only be accepted for devel 
release ? This is a new CPU but Xenial is there for a couple of years still so 
maybe future Xenial user running Ryzen CPU may benefit on this eventually...
[10:03:20]  slashd, for me some new functionality like that is ok as long 
as it is very self-contained so easy to review and confirm is only used on the 
new h/w
[10:03:52] one of our main goals is to avoid regressions
[10:04:41] apw, make sense, thanks for your input
[10:12:24]  The SRU policy does explicitly permit hardware enablement 
in an LTS IIRC, though I'd expect ~ubuntu-sru to be involved in mitigating risk 
and making the final risk decision, FWIW.
[10:16:11]  rbasak, right, it would have to be carefully considered once 
we can see what the diff actually is
[10:16:34]  rbasak, apw ack, will communite the info with the proper 
group
[10:16:50]  with a much greater level of testing and scrutiny than a 
regular fix only sru
[10:17:12]  apw, rbasak, FYI I have requested the new CPU from our 
partner to test in deep
...

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

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  Triaged

Bug description:
  It has been brought to my attention that :
  "CPUID detection in OpenSSL does not properly detect potential optimizations 
for AMD processors."

  After further verification on my side :

  Extended feature flags were not pulled on AMD processors, as result a
  number of extensions were effectively masked on Ryzen CPUs. It should
  have been reported for Excavator since it implements AVX2 extension,
  but apparently nobody noticed ...

  The GitHub PR:
  https://github.com/openssl/openssl/pull/2849

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/+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 103436] Re: sshd not reconfigured by /etc/network

2017-03-20 Thread Martin Pitt

Hey Perry,

Perry E. Metzger [2017-03-20 13:11 -0400]:
> That bug report was a decade ago.

Yeah, I know :-)

> So far as I know, this is still an issue for your users, because sshd
> does not, on its own, change its network address when one changes
> networks. I would not remove this because if you remove it you're
> going to harm anyone who changes addresses frequently.

That's what I've thought, but it am puzzled that I cannot actually produce this
situation (when removing the script). That, and the fact that Fedora or SUSE
don't have this indicate that this was dealt with by something else in the
meantime.

> However, I have not used Ubuntu in many years (this is 2017, the bug
> report was 2007) and I am no longer in a position to help you.

No worries, it was a long shot anyway. Thanks for your fast response!

Martin

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

Title:
  sshd not reconfigured by /etc/network

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: openssh-server

  If you have a device that roams a lot (like a laptop), you want
  daemons like sshd to be tweaked/restarted by scripts in /etc/network
  so that they re-open the socket they listen on when the network
  address changes. (Yes, some of us really do want to be able to
  remotely log in to our laptops after we bring them home and they roam
  onto the home WiFi network etc.)

  Right now there is no sshd script in /etc/network/* but it would be
  trivial to create one and add it to the package. For sshd, it would be
  simplest just to restart the daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/103436/+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 1673461] Re: [regression] BorderImage no longer displays

2017-03-20 Thread Adnane Belmadiaf

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

Dup of bug 1671449

** This bug has been marked a duplicate of bug 1671449
   Unity8 window shadows have gone missing

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

Title:
  [regression] BorderImage no longer displays

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

Bug description:
  BorderImages no longer display at all with the latest UITK release.
  This can be reproduced with the following simple QML and the attached
  png/sci files:

  import QtQuick 2.2
  import Ubuntu.Components 1.3

  MainView {

  width: units.gu(20)
  height: units.gu(20)

  Rectangle {
  color: "black"
  anchors.fill: parent

  BorderImage {
  anchors.fill: parent
  source: "magnified_key.sci"
  }
  }

  }

  This appears to have been introduced in revision 1000.1114.3, if the
  above is tested with revision 1000.1114.2 it displays correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1673461/+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 1673491] Re: [Zesty] libnl3 Segmentation fault in sriov environments

2017-03-20 Thread Talat Batheesh

Thank you ,
The update is passed and libnl updated to libnl-3-200:amd64 (3.2.29-0ubuntu2).

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

Title:
  [Zesty] libnl3 Segmentation fault in sriov environments

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  New

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #4  0x7f980bfbdc1c in nl_recvmsgs_report () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #5  0x7f980bfbe049 in nl_recvmsgs () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #6  0x7f980bfb6aab in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #7  0x7f980bfb763d in nl_cache_pickup () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #8  0x7f980bfb7871 in nl_cache_refill () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #9  0x7f97fa926975 in

[Touch-packages] [Bug 1673461] Re: [regression] BorderImage no longer displays

2017-03-20 Thread Adnane Belmadiaf

I believe the regression was fixed here https://bazaar.launchpad.net
/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/revision/2185

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

Title:
  [regression] BorderImage no longer displays

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

Bug description:
  BorderImages no longer display at all with the latest UITK release.
  This can be reproduced with the following simple QML and the attached
  png/sci files:

  import QtQuick 2.2
  import Ubuntu.Components 1.3

  MainView {

  width: units.gu(20)
  height: units.gu(20)

  Rectangle {
  color: "black"
  anchors.fill: parent

  BorderImage {
  anchors.fill: parent
  source: "magnified_key.sci"
  }
  }

  }

  This appears to have been introduced in revision 1000.1114.3, if the
  above is tested with revision 1000.1114.2 it displays correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1673461/+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 103436] Re: sshd not reconfigured by /etc/network

2017-03-20 Thread Perry E. Metzger

On Mon, 20 Mar 2017 13:18:54 - Martin Pitt
 wrote:
> Perry, I just revisited this:

That bug report was a decade ago.

So far as I know, this is still an issue for your users, because sshd
does not, on its own, change its network address when one changes
networks. I would not remove this because if you remove it you're
going to harm anyone who changes addresses frequently.

However, I have not used Ubuntu in many years (this is 2017, the bug
report was 2007) and I am no longer in a position to help you.

Perry
-- 
Perry E. Metzgerpe...@piermont.com

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

Title:
  sshd not reconfigured by /etc/network

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: openssh-server

  If you have a device that roams a lot (like a laptop), you want
  daemons like sshd to be tweaked/restarted by scripts in /etc/network
  so that they re-open the socket they listen on when the network
  address changes. (Yes, some of us really do want to be able to
  remotely log in to our laptops after we bring them home and they roam
  onto the home WiFi network etc.)

  Right now there is no sshd script in /etc/network/* but it would be
  trivial to create one and add it to the package. For sshd, it would be
  simplest just to restart the daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/103436/+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 1674330] [NEW] Please consider dropping /etc/network/if-up.d/openssh-server

2017-03-20 Thread Perry E. Metzger

On Mon, 20 Mar 2017 13:26:35 - Launchpad Bug Tracker
<1674...@bugs.launchpad.net> wrote:
> You have been subscribed to a public bug by Martin Pitt (pitti):
> 
> The /etc/network/if-up.d/openssh-server hack was introduced ten
> years ago [1] as a response to bug 103436. At least from today's
> perspective this isn't justified:
> 
> I can't seem to be able to actually reproduce that issue: I can
> start a VM with no network interfaces, remove the above hack, then
> start sshd, then bring up an ethernet interface, and I can connect
> to ssh via ethernet just fine.

sshd has no internal support to open and close listening addresses on
its own, so I suspect you're wrong. Why don't you try the actual use
case, which is changing addresses rather than an initial open.

However, I haven't used ubuntu in at least eight years and have no
way to help you.

> Also, e. g. Fedora has no
> counterpart of this hack, and these days a lot of people would
> complain if that would cause problems,

How many people regularly ssh into their laptops on multiple
networks? I would guess very few.

> The hack introduces a race: you run into connection errors after
> bringing up a new interface as sshd stops listening briefly while
> being reloaded.

Well, yah, but when you change networks you're also not listening to
the network. This isn't a race, this is just expected behavior. Even
if sshd did this on its own this would happen.

And it isn't a "hack", this is exactly what ifup/down scripts are for.

Perry
-- 
Perry E. Metzgerpe...@piermont.com

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

Title:
  Please consider dropping /etc/network/if-up.d/openssh-server

Status in openssh package in Ubuntu:
  New

Bug description:
  The /etc/network/if-up.d/openssh-server hack was introduced ten years ago [1] 
as a response to bug 
  103436. At least from today's perspective this isn't justified:

  I can't seem to be able to actually reproduce that issue: I can start
  a VM with no network interfaces, remove the above hack, then start
  sshd, then bring up an ethernet interface, and I can connect to ssh
  via ethernet just fine. Also, e. g. Fedora has no counterpart of this
  hack, and these days a lot of people would complain if that would
  cause problems, as hotpluggable/roaming network devices are
  everywhere.

  The hack introduces a race: you run into connection errors after
  bringing up a new interface as sshd stops listening briefly while
  being reloaded. That's the reason why I looked at it, as this
  regularly happens in upstream's cockpit integration tests.

  Also, /etc/network/if-up.d/ isn't being run when using
  networkd/netplan, i. e. in more recent Ubuntnu cloud instances. So far
  this doesn't seem to have caused any issues.

  I asked the original reporter of bug 103436 for some details, and to
  check whether that hack is still necessary. There is actually a
  proposed patch upstream [2] to use IP_FREEBIND, which is the modern
  solution to listening to all "future" interfaces as well. But at least
  for the majority of cases it seems to work fine without that even.

  So I wonder if it's time to bury that hack?

  [1] https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=ba6b55ed6
  [2] https://bugzilla.mindrot.org/show_bug.cgi?id=2512

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1674330/+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 1668428] Re: gnome screen shot behaves strange on zesty unity8

2017-03-20 Thread kevin gunn

retested, overhauled description based on the latest findings (at least
I no longer see the u8 lockup now)

** Summary changed:

- gnome screen shot full lock up on zesty unity8
+ gnome screen shot behaves strange on zesty unity8

** Changed in: canonical-devices-system-image
   Status: Incomplete => New

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => New

** No longer affects: unity8 (Ubuntu)

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

** Description changed:

- Feb 27 iso build of zesty, clean u8 exploration
+ Updated Mar 20 zesty, clean u8 exploration
  
- gnome screenshot completely locks up the shell and eventually unity8 just 
restarts
+ gnome screenshot will seemingly quit, and will not capture the desired screen
  to repro:
  1) launch screenshot app from the app drawer
  2) make indications to take a screenshot ( i selected custom area to select)
  3) "take screenshot"
- result: complete lock up along with windowing oddity, frozen until unity8 res
+ result: application bail out, in the instance of "select area" case, it will 
take a screen shot in the instance of "full screen".
+ expected: get a screen shot of desired and the application should remain on 
screen.
+ 
+ I suspect this is due to screenshot's reliance on X and our use of Xmir
+ not being completely worked out in terms of what the applications
+ perception of the screen vs it's own window is.

** Changed in: canonical-devices-system-image
 Assignee: kevin gunn (kgunn72) => Stephen M. Webb (bregma)

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => William Hua (attente)

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  gnome screen shot behaves strange on zesty unity8

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Updated Mar 20 zesty, clean u8 exploration

  gnome screenshot will seemingly quit, and will not capture the desired screen
  to repro:
  1) launch screenshot app from the app drawer
  2) make indications to take a screenshot ( i selected custom area to select)
  3) "take screenshot"
  result: application bail out, in the instance of "select area" case, it will 
take a screen shot in the instance of "full screen".
  expected: get a screen shot of desired and the application should remain on 
screen.

  I suspect this is due to screenshot's reliance on X and our use of
  Xmir not being completely worked out in terms of what the applications
  perception of the screen vs it's own window is.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668428/+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 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

2017-03-20 Thread Adam Monsen

I think this may be a regression. I installed 16.04.1 a few weeks ago
and it was working fine (dnsmasq worked after resume). I now have a 100%
repro of the bug.

Workaround: sudo pkill dnsmasq

I'm now running 16.04.2 (64-bit). I'm using a Dell XPS laptop. CPU is an
Intel Core i7-6560U. Plenty of free disk & RAM.

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

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  
  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1673550] Re: Windows not remembering previous size on unity8

2017-03-20 Thread Bill Filler

this is not a general unity8 bug. Window sizes are remembered correclty.
It's specific to settings app and ken's branch addresses it.

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Incomplete => In Progress

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

** Summary changed:

- Windows not remembering previous size on unity8
+ system-settings not remembering previous size on 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/1673550

Title:
  system-settings not remembering previous size on unity8

Status in Canonical System Image:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  running u8 desktop session

  Steps to reproduce:
  - open u-s-s
  - resize the window to 2 column mode
  - close the app with X from window control
  - restart the app

  Expected results:
  - u-s-s should open at the size it was last closed at

  Actutual results:
  - u-s-s window is smaller only showing one column

  This may be related to limiting the max size which we used to have? I
  think we should remove all max sizing restrictions on the app, and
  bring back the maximize button which is not displayed either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673550/+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 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-03-20 Thread David A. Desrosiers

** Changed in: openssl (Ubuntu)
   Importance: Low => Medium

** Changed in: openssl (Ubuntu)
   Status: New => Triaged

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

** Changed in: openssl (Ubuntu)
 Assignee: (unassigned) => Eric Desrochers (slashd)

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  Triaged

Bug description:
  It has been brought to my attention that :
  "CPUID detection in OpenSSL does not properly detect potential optimizations 
for AMD processors."

  After further verification on my side :

  Extended feature flags were not pulled on AMD processors, as result a
  number of extensions were effectively masked on Ryzen CPUs. It should
  have been reported for Excavator since it implements AVX2 extension,
  but apparently nobody noticed ...

  The GitHub PR:
  https://github.com/openssl/openssl/pull/2849

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/+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 1671458] Re: Unity8 window restore animation goes to an old location, then jumps to the correct one

2017-03-20 Thread Albert Astals Cid

** Branch linked: lp:~aacid/unity8/fixUnminimizePosition

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

Title:
  Unity8 window restore animation goes to an old location, then jumps to
  the correct one

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8
  [unity8] minimizing/restoring strange behaviour 

  on restoring the animation is jumpy it goes trough 2 paths, first
  minimized position and then to the actual position.

  open some random app, minimize, click on the icon (launcher) to
  restore. works fine. now move the window a bit, minimize, restore, now
  the animation is broken. first it goes to the first min pos and then
  jumps to the actual pos. repeat

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671458/+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 1568296] Re: Make JS dialogs app modal

** Branch linked: lp:~oxide-developers/oxide/packaging.zesty

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

Title:
  Make JS dialogs app modal

Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Chrome only supports app-modal JS dialogs, and so does Blink
  (window.alert blocks the calling process).

  Oxide pretends to support tab-modal JS dialogs by having a per-WebContents 
dispatch queue. However, the behaviour is quite broken:
  - It's really app-modal in single process because there's only a single 
RenderThread.
  - In multi-process it's not really tab-modal - it's render-process modal (ie, 
only a single tab in a render process can show a JS dialog). So, if 2 tabs live 
in separate processes then they can display JS dialogs at the same time. But if 
they're from the same SiteInstance and live in the same process, they can't.

  We should just change the dispatch of JS dialogs to be application
  modal instead, so it behaves consistently in all configurations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1568296/+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 1434986] Re: Not working network connection after boot

2017-03-20 Thread Erwin van Diermen

Above comment is partly true... after reboot it doesn't work anymore.

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1665726] Re: MouseArea too close to the top indicators bar cannot be activated by touch

2017-03-20 Thread Lukáš Tinkl

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

** This bug has been marked a duplicate of bug 1670361
   Area near the top edge of window not clickable when in tablet mode

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

Title:
  MouseArea too close to the top indicators bar cannot be activated by
  touch

Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  I’m testing the browser with redesigned tabs bar on M10, and I can’t
  activate any tab. The new tabs bar is 3GU tall, if I increase its
  height I’m able to activate the bottom half of the tabs.

  Also, if I plug in a bluetooth mouse so that the app gets windowed, I
  have no problems activating the tabs.

  It looks like a mouse area at the top of a maximized window, too close
  to the indicators bar, is not activatable. As if the indicators bar
  itself was swallowing touch/click events just below itself.

  I’ve been able to confirm with a simple standalone QML scene with a
  thin MouseArea at the top of the scene. If I make it thin enough (3GU
  or less), it’s impossible to activate by touching it.

  This is on M10 running arm64 xenial (revision 147) from the ubuntu-
  touch/staging/ubuntu channel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1665726/+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 1668641] Re: Error message: pam_systemd(su:session): Cannot create session: Already running in a session

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

Title:
  Error message: pam_systemd(su:session): Cannot create session: Already
  running in a session

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

Bug description:
  Hi,

  here is how to reproduce this error:

  1. log in to the root account with ssh
  2. run "su - some_user_account"

  Here is what I see in the logs:

  Feb 28 15:21:45 xeelee su[9843]: Successful su for bonnaudl by root
  Feb 28 15:21:45 xeelee su[9843]: + /dev/pts/10 root:bonnaudl
  Feb 28 15:21:45 xeelee su[9843]: pam_unix(su:session): session opened for 
user bonnaudl by root(uid=0)
  Feb 28 15:21:45 xeelee su[9843]: pam_systemd(su:session): Cannot create 
session: Already running in a session
  Feb 28 15:21:48 xeelee su[9843]: pam_unix(su:session): session closed for 
user bonnaudl

  In another usage scenario of "su -" there is no error message and the
  creation of a new session:

  févr. 28 15:08:15 vougeot su[18962]: Successful su for bonnaudl by root
  févr. 28 15:08:15 vougeot su[18962]: + /dev/pts/0 root:bonnaudl
  févr. 28 15:08:15 vougeot su[18962]: pam_unix(su:session): session opened for 
user bonnaudl by bonnaudl(uid=0)
  févr. 28 15:08:15 vougeot systemd-logind[1162]: New session c9 of user 
bonnaudl.
  févr. 28 15:08:15 vougeot systemd[1]: Started Session c9 of user bonnaudl.
  févr. 28 15:08:17 vougeot su[18962]: pam_unix(su:session): session closed for 
user bonnaudl
  févr. 28 15:08:17 vougeot systemd-logind[1162]: Removed session c9.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libpam-systemd 231-9ubuntu3
  Uname: Linux 4.10.1-041001-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 28 15:21:09 2017
  EcryptfsInUse: Yes
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668641/+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 1669819] Re: [unity8] Strange behavior when restoring snapped windows

2017-03-20 Thread Lukáš Tinkl

** Changed in: canonical-devices-system-image
   Status: Triaged => In Progress

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

Title:
  [unity8] Strange behavior when restoring snapped windows

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 17.04 Unity8

  open random app (terminal app), snap it randomly on the screen (right
  buttom corner) by draging the app by the title bar (see screenshot1).
  now click on maximize window, the window almost leaves the screen
  (screenshot2).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669819/+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 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"

Hi Dimitry!

No problem. In fact, I've cherry picked the fix from Qt 5.6 and created
an updated package. I'm building it at the moment to test. I'll fill out
the SRU template as well, and attach a debdiff if it seems to work OK.

Sorry for not sticking to the SRU procedure to begin with, I know I was
a bit busy when I filed this.

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

Title:
  Please consider SRU of "xcb: Compress mouse motion and touch update
  events"

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  New

Bug description:
  A fix for QTBUG-40889 was worked out and submitted at

  https://codereview.qt-project.org/#/c/115531/

  but due to coming in a bit late, was moved to Qt 5.6

  https://codereview.qt-project.org/#/c/126136/

  The bug is about mouse motion event compression malfunctioning, and it
  has grave consequences for some applications, where the flood of
  events make rendering sluggish (e.g. anything based on VTK, but
  probably others).

  ParaView developer Ben Boeckel has tried the patch [2] against 5.5 and
  confirmed it fixes rendering/interaction in VTK applications.

  It is not possible to work around the bug at the application level in
  a satisfactory way, only by resorting to timer-based rendering.

  I suggest an SRU to patch the Ubuntu Qt package with the patch that
  was originally meant for the 5.x branch (first URL above). The patch
  was later integrated in 5.6 where it has been well tested.

  [1] https://bugreports.qt.io/browse/QTBUG-40889
  [2] 
http://vtk.1045678.n5.nabble.com/Delayed-mouse-interaction-due-to-event-loop-bug-in-Qt5-tp5730474p5732870.html

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

2017-03-20 Thread Kyle Fazzari

** Changed in: nextcloud-snap
   Importance: Unknown => High

-- 
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 Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  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/nextcloud-snap/+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 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-03-20 Thread Eric Desrochers

* Repository : https://github.com/openssl/openssl.git

* Commits :

1aed5e1 crypto/x86*cpuid.pl: move extended feature detection.
f8418d8 crypto/x86_64cpuid.pl: move extended feature detection upwards.

- Eric

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  New

Bug description:
  It has been brought to my attention that :
  "CPUID detection in OpenSSL does not properly detect potential optimizations 
for AMD processors."

  After further verification on my side :

  Extended feature flags were not pulled on AMD processors, as result a
  number of extensions were effectively masked on Ryzen CPUs. It should
  have been reported for Excavator since it implements AVX2 extension,
  but apparently nobody noticed ...

  The GitHub PR:
  https://github.com/openssl/openssl/pull/2849

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/+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 1674399] [NEW] OpenSSL CPU detection for AMD Ryzen CPUs

2017-03-20 Thread Eric Desrochers

Public bug reported:

It has been brought to my attention that :
"CPUID detection in OpenSSL does not properly detect potential optimizations 
for AMD processors."

After further verification on my side :

Extended feature flags were not pulled on AMD processors, as result a
number of extensions were effectively masked on Ryzen CPUs. It should
have been reported for Excavator since it implements AVX2 extension, but
apparently nobody noticed ...

The GitHub PR:
https://github.com/openssl/openssl/pull/2849

** Affects: openssl (Ubuntu)
 Importance: Low
 Status: New


** Tags: sts

** Changed in: openssl (Ubuntu)
   Importance: Undecided => Low

** Description changed:

- I has been brought to my attention that :
+ It has been brought to my attention that :
  "CPUID detection in OpenSSL does not properly detect potential optimizations 
for AMD processors."
  
  After further verification on my side :
  
  Extended feature flags were not pulled on AMD processors, as result a
  number of extensions were effectively masked on Ryzen CPUs. It should
  have been reported for Excavator since it implements AVX2 extension, but
  apparently nobody noticed ...
  
  The GitHub PR:
  https://github.com/openssl/openssl/pull/2849

** Tags added: sts

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  New

Bug description:
  It has been brought to my attention that :
  "CPUID detection in OpenSSL does not properly detect potential optimizations 
for AMD processors."

  After further verification on my side :

  Extended feature flags were not pulled on AMD processors, as result a
  number of extensions were effectively masked on Ryzen CPUs. It should
  have been reported for Excavator since it implements AVX2 extension,
  but apparently nobody noticed ...

  The GitHub PR:
  https://github.com/openssl/openssl/pull/2849

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/+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 1668053] Re: [unity8] kate, impossible to close "Print Preview" window

2017-03-20 Thread Alan Griffiths

>From my perspective it is incorrect to say 'impossible to close "Print
Preview" window' I can run kate in miral-shell, open the print-preview
and close it (Alt-F4) fine.

Now I do agree it seems daft that there's neither a "Close" button (or
equivalent) on the window, nor an "X" in the titlebar, but isn't that
down to a design issue?

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

Title:
  [unity8] kate, impossible to close "Print Preview" window

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in Ubuntu UX:
  New
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 Unity 8
  [unity8] kate, impossible to close "Print Preview" window

  see attached screenshot
  Print Preview window doesn't have windows controls or a close button

  Launch Kate, from the menu File > Print Preview
  try to close the window, you can't because doh

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668053/+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 1615209] Re: ip crashes after a few times adding and removing network namespaces

2017-03-20 Thread ChristianEhrhardt

Hi KJH,
I appreciate all your help and I really think Jon is really trying to help.

And also from the source I agree.
But the rules dictate that one is supposed to verify the issue and the fix of 
it.

So a question might be "how often is often" and "how long is long".
Because for me as well e.g. the following just runs fine.
$ for i in $(seq 1 10); do echo $i; name=$(cat /dev/urandom | tr -dc 
'a-zA-Z0-9' | fold -w 32 | head -n 1); echo "${i}:${name}"; for j in $(seq 1 
100); do printf "%s " $j; sudo ip netns add ${name}; sudo ip netns del ${name}; 
done; printf "\n"; done;

Which is 10x100 add/removes of rather long names.

I'd have expected a segfault there, and running valgrind against them
does not change a bit.

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

Title:
  ip crashes after a few times adding and removing network namespaces

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  # which ip
  /sbin/ip
  # valgrind ip netns add black2
  ==22804== Memcheck, a memory error detector
  ==22804== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==22804== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==22804== Command: ip netns add black2
  ==22804== 
  ==22804== Invalid write of size 1
  ==22804==at 0x4031F43: memcpy (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==22804==by 0x8059C83: ??? (in /bin/ip)
  ==22804==by 0x805AF9A: netns_map_init (in /bin/ip)
  ==22804==by 0x805B01F: do_netns (in /bin/ip)
  ==22804==by 0x804DF67: ??? (in /bin/ip)
  ==22804==by 0x804DA11: main (in /bin/ip)
  ==22804==  Address 0x4227094 is 0 bytes after a block of size 28 alloc'd
  ==22804==at 0x402D17C: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==22804==by 0x8059C5E: ??? (in /bin/ip)
  ==22804==by 0x805AF9A: netns_map_init (in /bin/ip)
  ==22804==by 0x805B01F: do_netns (in /bin/ip)
  ==22804==by 0x804DF67: ??? (in /bin/ip)
  ==22804==by 0x804DA11: main (in /bin/ip)
  ==22804== 
  Cannot create namespace file "/var/run/netns/black2": File exists
  ==22804== 
  ==22804== HEAP SUMMARY:
  ==22804== in use at exit: 28 bytes in 1 blocks
  ==22804==   total heap usage: 2 allocs, 1 frees, 32,824 bytes allocated
  ==22804== 
  ==22804== LEAK SUMMARY:
  ==22804==definitely lost: 0 bytes in 0 blocks
  ==22804==indirectly lost: 0 bytes in 0 blocks
  ==22804==  possibly lost: 0 bytes in 0 blocks
  ==22804==still reachable: 28 bytes in 1 blocks
  ==22804== suppressed: 0 bytes in 0 blocks
  ==22804== Rerun with --leak-check=full to see details of leaked memory
  ==22804== 
  ==22804== For counts of detected and suppressed errors, rerun with: -v
  ==22804== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1615209/+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 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"

2017-03-20 Thread Dmitry Shachnev

Elvis: sorry for not responding. Sometimes pinging the bug *is* helpful.

I will not have time to do a SRU in the next days, but I might take a
look a bit later if nobody beats me to it. In the meantime, it would
help if you could fill the SRU bug template, see
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.

** Also affects: qtbase-opensource-src (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please consider SRU of "xcb: Compress mouse motion and touch update
  events"

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  New

Bug description:
  A fix for QTBUG-40889 was worked out and submitted at

  https://codereview.qt-project.org/#/c/115531/

  but due to coming in a bit late, was moved to Qt 5.6

  https://codereview.qt-project.org/#/c/126136/

  The bug is about mouse motion event compression malfunctioning, and it
  has grave consequences for some applications, where the flood of
  events make rendering sluggish (e.g. anything based on VTK, but
  probably others).

  ParaView developer Ben Boeckel has tried the patch [2] against 5.5 and
  confirmed it fixes rendering/interaction in VTK applications.

  It is not possible to work around the bug at the application level in
  a satisfactory way, only by resorting to timer-based rendering.

  I suggest an SRU to patch the Ubuntu Qt package with the patch that
  was originally meant for the 5.x branch (first URL above). The patch
  was later integrated in 5.6 where it has been well tested.

  [1] https://bugreports.qt.io/browse/QTBUG-40889
  [2] 
http://vtk.1045678.n5.nabble.com/Delayed-mouse-interaction-due-to-event-loop-bug-in-Qt5-tp5730474p5732870.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package

2017-03-20 Thread Mathieu Trudel-Lapierre

Don't get me wrong, the upgrade issue this causes has to get fixed.

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

Title:
  10-globally-managed-devices.conf contained in wrong package

Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is
  installed from network-manager but without nplan it has no benefit,
  and breaks networking until you override it.  Since the config is
  there to change how NetworkManager behaves in the presence of nplan,
  the configuration file itself should actually be contained in the
  nplan package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1671072] Re: Child windows don't get focused

2017-03-20 Thread Daniel d'Andrada

qtmir sends a key event to mir::scene::Surface->consume() without any
modifiers but it still arrives with a modifier when it surfaces from the
mir client lib in the client process.

Looks like some sort of key input validation in mir got confused and is
adding the modifier back even though the key ctrl got released.

** Changed in: qtmir (Ubuntu)
   Status: Invalid => In Progress

** Also affects: mir (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/1671072

Title:
  Child windows don't get focused

Status in Canonical System Image:
  In Progress
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  New
Status in miral package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671072/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package

2017-03-20 Thread Brian Murray

I upgraded from 16.04 to 16.10 recently and ran into an issue where
networking did not work until I created an empty file in
/run/NetworkManager/conf.d/10-globally-managed-devices.conf.

nplan was installed after the upgrade:

 $ apt-cache policy nplan
nplan:
  Installed: 0.12
  Candidate: 0.12
  Version table:
 *** 0.12 500
500 http://192.168.10.7/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  10-globally-managed-devices.conf contained in wrong package

Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is
  installed from network-manager but without nplan it has no benefit,
  and breaks networking until you override it.  Since the config is
  there to change how NetworkManager behaves in the presence of nplan,
  the configuration file itself should actually be contained in the
  nplan package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1673215] Re: Second unity8 user session hangs with a black screen

2017-03-20 Thread Michael Terry

** No longer affects: unity8 (Ubuntu)

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

Title:
  Second unity8 user session hangs with a black screen

Status in Canonical System Image:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  10-globally-managed-devices.conf contained in wrong package

Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is
  installed from network-manager but without nplan it has no benefit,
  and breaks networking until you override it.  Since the config is
  there to change how NetworkManager behaves in the presence of nplan,
  the configuration file itself should actually be contained in the
  nplan package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1674262] Re: Windows are not sized correctly if an invalid size comes from the state storage.

2017-03-20 Thread Lukáš Tinkl

** Changed in: canonical-devices-system-image
   Status: Triaged => In Progress

** Branch linked: lp:~lukas-kde/unity8/protect-window-storage-against-
invalid-geometry-lp1674262

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

Title:
  Windows are not sized correctly if an invalid size comes from the
  state storage.

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  The width/height of a windowed surface can be 0 if the initial size is
  loaded with 0 due to an invalid state storage size.

  http://paste.ubuntu.com/24195871/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674262/+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 1671072] Re: Child windows don't get focused