[Touch-packages] [Bug 1627800] Re: Xorg crash

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The error occurred when playing streams, such as youtube, soundcloud
  and others by web browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-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: Mon Sep 26 14:55:07 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   i915-4.6.3-4.4.0, 1, 4.4.0-31-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2010]
  InstallationDate: Installed on 2016-09-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 2571:4101  
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation HuronRiver Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=2465629d-ee53-4759-bbc2-a56450823561 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2011
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 1.05_
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: Intel Corp.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr1.05_:bd03/05/2011:svnIntelCorporation:pnHuronRiverPlatform:pvr0.1:rvnIntelCorp.:rnEmeraldLake:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:
  dmi.product.name: HuronRiver Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Sep 25 22:43:46 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id  19 
   vendor INL
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1627800/+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 1680687] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocesul script pre-removal nou a returnat starea de eroare la ieșire 1

[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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1680687

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocesul
  script pre-removal nou a returnat starea de eroare la ieșire 1

Status in cups package in Ubuntu:
  New

Bug description:
  Verificați dacă utilizați arhive de la terțe părți. Dacă utilizați acest tip 
de arhive, dezactivați-le, fiind o sursă comună de probleme.
  Apoi rulați următoarea comandă în Terminal: apt-get install -f

  ...and nothing ..

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Apr  7 06:04:18 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-07  06:04:09
   Commandline: apt-get -f install
   Requested-By: lm (1000)
   Upgrade: libcups2:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), libcups2:i386 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-server-common:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-common:amd64 (2.1.3-4ubuntu0.1, 
2.1.3-4ubuntu0.2), libcupsmime1:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
libcupsppdc1:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-bsd:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-core-drivers:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-daemon:amd64 (2.1.3-4, 
2.1.3-4ubuntu0.2), libcupsimage2:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
cups:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), libcupscgi1:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-client:amd64 (2.1.3-4ubuntu0.1, 
2.1.3-4ubuntu0.2)
  ErrorMessage: subprocesul script pre-removal nou a returnat starea de eroare 
la ieșire 1
  InstallationDate: Installed on 2016-08-19 (230 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK Computer Inc. F5Z
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=dc47f504-a912-4f47-8aa5-e840ae89f8b5 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=dc47f504-a912-4f47-8aa5-e840ae89f8b5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocesul 
script pre-removal nou a returnat starea de eroare la ieșire 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/20/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: F5Z
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr209:bd03/20/2009:svnASUSTeKComputerInc.:pnF5Z:pvr1.0:rvnASUSTeKComputerInc.:rnF5Z:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.name: F5Z
  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/cups/+bug/1680687/+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 1680687] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocesul script pre-removal nou a returnat starea de eroare la ieșire 1

[LM]

Public bug reported:

Verificați dacă utilizați arhive de la terțe părți. Dacă utilizați acest tip de 
arhive, dezactivați-le, fiind o sursă comună de probleme.
Apoi rulați următoarea comandă în Terminal: apt-get install -f

...and nothing ..

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
Uname: Linux 4.4.0-49-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 
Date: Fri Apr  7 06:04:18 2017
DpkgHistoryLog:
 Start-Date: 2017-04-07  06:04:09
 Commandline: apt-get -f install
 Requested-By: lm (1000)
 Upgrade: libcups2:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), libcups2:i386 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-server-common:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-common:amd64 (2.1.3-4ubuntu0.1, 
2.1.3-4ubuntu0.2), libcupsmime1:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
libcupsppdc1:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-bsd:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-core-drivers:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-daemon:amd64 (2.1.3-4, 
2.1.3-4ubuntu0.2), libcupsimage2:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
cups:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), libcupscgi1:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-client:amd64 (2.1.3-4ubuntu0.1, 
2.1.3-4ubuntu0.2)
ErrorMessage: subprocesul script pre-removal nou a returnat starea de eroare la 
ieșire 1
InstallationDate: Installed on 2016-08-19 (230 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: ASUSTeK Computer Inc. F5Z
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=dc47f504-a912-4f47-8aa5-e840ae89f8b5 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=dc47f504-a912-4f47-8aa5-e840ae89f8b5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocesul 
script pre-removal nou a returnat starea de eroare la ieșire 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/20/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: F5Z
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr209:bd03/20/2009:svnASUSTeKComputerInc.:pnF5Z:pvr1.0:rvnASUSTeKComputerInc.:rnF5Z:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: F5Z
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: amd64 apport-package xenial

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocesul
  script pre-removal nou a returnat starea de eroare la ieșire 1

Status in cups package in Ubuntu:
  New

Bug description:
  Verificați dacă utilizați arhive de la terțe părți. Dacă utilizați acest tip 
de arhive, dezactivați-le, fiind o sursă comună de probleme.
  Apoi rulați următoarea comandă în Terminal: apt-get install -f

  ...and nothing ..

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Apr  7 06:04:18 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-07  06:04:09
   Commandline: apt-get -f install
   Requested-By: lm (1000)
   Upgrade: libcups2:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), libcups2:i386 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-server-common:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-common:amd64 (2.1.3-4ubuntu0.1, 
2.1.3-4ubuntu0.2), libcupsmime1:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
libcupsppdc1:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-bsd:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-core-drivers:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-daemon:amd64 (2.1.3-4, 
2.1.3-4ubuntu0.2), libcupsimage2:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
cups:amd64 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), libcupscgi1:amd64 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-client:amd64 (2.1.3-4ubuntu0.1, 
2.1.3-4ubuntu0.2)
  ErrorMessage: subprocesul script pre-removal nou a returnat starea de eroare 
la ieșire 1
  InstallationDate: Installed on 2016-08-19 (230 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: 

[Touch-packages] [Bug 1319338] Re: Default boost v1.54 has broken asio while available 1.55 is fixed

[Bug Watch Updater]

** Changed in: boost
   Status: Fix Released => New

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

Title:
  Default boost v1.54 has broken asio while available 1.55 is fixed

Status in Boost:
  New
Status in boost-mpi-source1.54 package in Ubuntu:
  Fix Released
Status in boost1.54 package in Ubuntu:
  Fix Released
Status in boost-mpi-source1.54 source package in Trusty:
  Fix Released
Status in boost1.54 source package in Trusty:
  Fix Released

Bug description:
  [Test Case]
  1) g++ chat_client.cpp -std=gnu++11 -lboost_system -lpthread -o chat_client

  You will need the header chat I will attach in the following comment
  in order to make it to compile.

  Bug in current boost Trusty libraries, while trying to connect to non
  existing server.

  * Bug:
  ./chat_client localhost 2423424
  Success

  * Expected:
  ./chat_client localhost 2423424
  Connection refused

  Original Description
  
  Release: 14.04 LTS
  Version: 1.54.0.1ubuntu1
  Expected: Depend on working version of boost
  Happened: Depends on boost 1.54

  Here is a bug that was fixed in boost 7 months ago: 
https://svn.boost.org/trac/boost/ticket/8795
  Due to that, working with boost/asio seems impossible.

  The bug is still present in boost1.54 but fixed in boost1.55.
  Therefore I consider it a bug to use version 1.54 as default, as other
  libraries' dev-packages depend on boost-default and hence cannot be
  installed together with libboost1.55-dev without being rebuild.

  Of course, other possibilities would be to ask upstream if version 1.54 could 
be patched or add this patch to boost1.54.
  But there might be more benefits in boost1.55 and as both versions are not 
perfect I see no reason to stick with the older one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/boost/+bug/1319338/+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 1603898] Re: DNS resolution fails when using VPN and routing all traffic over it

[Aron Xu]

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

** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

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

Title:
  DNS resolution fails when using VPN and routing all traffic over it

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Confirmed

Bug description:
  When using our company VPN, the Network Manager configured dnsmasq
  ends up in a weird state where its unable to answer queries because
  it's (incorrectly) sending them to 127.0.0.1:53 where nothing is
  listening.

  | root@ornery:~# nmcli con show 'Canonical UK - All Traffic' | grep -i dns
  | ipv4.dns:
  | ipv4.dns-search:
  | ipv4.dns-options:   (default)
  | ipv4.ignore-auto-dns:   no
  | ipv6.dns:
  | ipv6.dns-search:
  | ipv6.dns-options:   (default)
  | ipv6.ignore-auto-dns:   no
  | IP4.DNS[1]: 10.172.192.1
  | root@ornery:~# ps auxfw | grep [4]035
  | nobody4035  0.0  0.0  52872  1620 ?SJun29   6:39  \_ 
/usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
  | root@ornery:~# 

  Querying the DNS server provided by the VPN connection works; querying
  dnsmasq doesn't:

  | root@ornery:~# dig +short @10.172.192.1 www.openbsd.org
  | 129.128.5.194
  | root@ornery:~# dig @127.0.1.1 www.openbsd.org
  | 
  | ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @127.0.1.1 www.openbsd.org
  | ; (1 server found)
  | ;; global options: +cmd
  | ;; Got answer:
  | ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 6996
  | ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
  | 
  | ;; QUESTION SECTION:
  | ;www.openbsd.org.   IN  A
  | 
  | ;; Query time: 0 msec
  | ;; SERVER: 127.0.1.1#53(127.0.1.1)
  | ;; WHEN: Mon Jul 18 10:25:48 CEST 2016
  | ;; MSG SIZE  rcvd: 33
  | 
  | root@ornery:~# 

  While running 'dig @127.0.1.1 www.openbsd.org':

  | root@ornery:~# tcpdump -i lo port 53 -v -n
  | tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 
bytes
  | 10:26:04.728905 IP (tos 0x0, ttl 64, id 56577, offset 0, flags [none], 
proto UDP (17), length 72)
  | 127.0.0.1.54917 > 127.0.1.1.53: 32273+ [1au] A? www.openbsd.org. (44)
  | 10:26:04.729001 IP (tos 0x0, ttl 64, id 49204, offset 0, flags [DF], proto 
UDP (17), length 61)
  | 127.0.1.1.53 > 127.0.0.1.54917: 32273 Refused$ 0/0/0 (33)

  | root@ornery:~# netstat -anp | grep 127.0.[01].1:53
  | tcp0  0 127.0.1.1:530.0.0.0:*   LISTEN  
4035/dnsmasq
  | udp0  0 127.0.1.1:530.0.0.0:*   
4035/dnsmasq
  | root@ornery:~# 

  You can see below a) that dnsmasq thinks it is configured to use a DNS
  server provided by the VPN, and/but that b) it tries to answer a non
  local query like www.openbsd.org locally.

  | root@ornery:~# kill -USR1 4035; tail /var/log/syslog | grep dnsmasq
  | Jul 18 09:29:22 ornery dnsmasq[4035]: time 1468830562
  | Jul 18 09:29:22 ornery dnsmasq[4035]: cache size 0, 0/0 cache insertions 
re-used unexpired cache entries.
  | Jul 18 09:29:22 ornery dnsmasq[4035]: queries forwarded 1880976, queries 
answered locally 375041
  | Jul 18 09:29:22 ornery dnsmasq[4035]: queries for authoritative zones 0
  | Jul 18 09:29:22 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 
792, retried or failed 0
  | root@ornery:~# dig +short @127.0.1.1 www.openbsd.org
  | root@ornery:~# kill -USR1 4035; tail /var/log/syslog | grep dnsmasq
  | Jul 18 09:29:22 ornery dnsmasq[4035]: queries for authoritative zones 0
  | Jul 18 09:29:22 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 
792, retried or failed 0
  | Jul 18 09:29:37 ornery dnsmasq[4035]: time 1468830577
  | Jul 18 09:29:37 ornery dnsmasq[4035]: cache size 0, 0/0 cache insertions 
re-used unexpired cache entries.
  | Jul 18 09:29:37 ornery dnsmasq[4035]: queries forwarded 1880976, queries 
answered locally 375042
  | Jul 18 09:29:37 ornery dnsmasq[4035]: queries for authoritative zones 0
  | Jul 18 09:29:37 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 
792, retried or failed 0
  | root@ornery:~# 

  This is on Ubuntu 16.04, with the following packages:

  | james@ornery:~$ COLUMNS=200 dpkg -l dnsmasq-base network-manager 
network-manager-openvpn | grep ^ii
  | ii  dnsmasq-base 2.75-1ubuntu0.16.04.1  
 amd64   

[Touch-packages] [Bug 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt

[Aron Xu]

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

** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

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

Title:
  Network Manager + OpenVPN does not respond to DNS server change on
  second connection attempt

Status in dnsmasq:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Scenario:
  Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I 
only have the one computer to test with, the 16.10 is definitely relevant (I 
did not have this problem on 16.04)  but I can't tell if the upgrade is part of 
it,  (the upgrade may or may not be relevant).

  Have "full time"  wired or wireless connection  (does not matter which used)
  Part time OpenVPN connection set up via NetworkManager.

  Steps to reproduce
  1. Fresh boot
  2.  ping a device on the VPN network  (eg amachine.remotelan ) Result:  
"ping: amachine.remotelan: Name or service not known"
  3.  Connect to the VPN service via Network Manager.
  4. ping amachine.remotelan  -  result:
   PING amachine.remotelan (192.168.68.44) 56(84) bytes of data.
64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 
time=7.75 ms
  5.  Disconnect from the VPN service again.
ping result again "ping: amachine.remotelan: Name or service not known"

  6. Reconnect to the VPN again, and ping again

  Observed: 
 "ping: amachine.remotelan: Name or service not known"

However "ping 192.168.68.44"  responds successfully as expected

  Expected:
  PING ... 192.168 64 bytes from .. etc   to the ping by name

  ---
  Further info I'm going to add in a subsequent comment. (just annotating 
syslog right now!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dnsmasq/+bug/1644098/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

[Aron Xu]

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

** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1671964] Re: DNS fails after reconnecting to a VPN

[Aron Xu]

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

** This bug is no longer a duplicate of bug 1671606
   DNS server from vpn connection is not being used after network-manager 
upgrade to 1.2.6-0ubuntu0.16.04.1
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

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

Title:
  DNS fails after reconnecting to a VPN

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since update 1.2.2-0ubuntu0.16.04.3 of network-manager, when I
  reconnect (i.e. connect, disconnect, connect) to a VPN (OpenVPN), DNS
  resolution stops working.

  Workaround: systemctl restart NetworkManager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671964/+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 1672491] Re: New NetworkManager breaks VPN DNS.

[Aron Xu]

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

** This bug is no longer a duplicate of bug 1671606
   DNS server from vpn connection is not being used after network-manager 
upgrade to 1.2.6-0ubuntu0.16.04.1
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

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

Title:
  New NetworkManager breaks VPN DNS.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Alright, this is going to be a frustrating bug for everyone involved I
  expect, but here goes.

  On Ubuntu 16.04, using a non-released VPN client (making this _much_
  harder for anyone to reproduce), upgrading the network-manager
  packages from 1.2.2-0ubuntu0.16.04.3 to 1.2.6-0ubuntu0.16.04.1 quite
  handily broke DNS over the VPN.

  And it broke it really oddly.

  dnsmasq binds to socket 12 for the new interface, just fine.

  strace shows that it does the sendto for the DNS request, and that the
  poll calls are working, just fine.

  tcpdump shows the response messages, they are coming back from the
  correct host and port, going to my IP and the port that dnsmasq is
  sending from.

  There are no iptables rules involved, nothing is set to deny.

  dnsmasq is never getting the response packet.

  The request thus times out.

  Doing a host or dig directly to the DNS server works just fine.

  And this is completely reproducible, and goes away the moment I
  downgrade back to 1.2.2-0ubuntu0.16.04.3.

  Was there some change to how network-manager handles VPN
  interfaces/tap0 in the new version?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1672491/+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 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1675519/+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 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Aron Xu]

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

** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

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

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1675519/+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 1675820] Re: Network manager fails to set domain server in some circumstances

[Aron Xu]

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

** This bug is no longer a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

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

Title:
  Network manager fails to set domain server in some circumstances

Status in network-manager package in Ubuntu:
  New

Bug description:
  Occasionally, after a resume from an update, network manager starts
  behaving strangely, not setting the DomainServer for the network.

  This happens when resuming the laptop to a location where:
  - an additional ethernet card (which is the one to use) is attached via USB
  - configuring that ethernet card NM is set up to clone a given mac address 
and get addresses only from dhcp, while the dns server is set manually in the 
network manager configuration
  - there are also free wifi signals to which NM tends to connect

  In this setup, NM fails to set the dns name in dnsmasq

  The issue gets worked around by either

  1) Using qdbus to call the dnsmasq dbus method to set the domain
  server. In this case the solution is temporary. Namely when NM is
  asked to disconnect from the net and then to reconnect, the issue
  comes again; or

  2) Killing dnsmasq. In this case, dnsmasq ia automatically restarted
  and everything starts working fine; or

  3) Restarting NM itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 24 16:22:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1197 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 10.143.1.254 dev enx0050b61af5c1  proto static  metric 100 
   10.143.0.0/19 dev enx0050b61af5c1  proto kernel  scope link  src 
10.143.20.139  metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2017-01-10 (73 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675820/+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 1675353] Re: Network manager does not resolve dns names

[Aron Xu]

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

** This bug is no longer a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

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

Title:
  Network manager does not resolve dns names

Status in network-manager package in Ubuntu:
  New

Bug description:
  NM seems completely broken in 16.10.

  I use NM, wifi and several VPN connections.

  Expected behaviour:

  1. Connect NM to default wlan -> name resolution works without interuption 
and permanently
  2. Connection to Cisco Anyconnect (via openconnect) -> DNS servers sent via 
DHCP should be added to the resolver list, name resolution should work in 
destination network, routes adjusted accordingly
  3. Connect NM to foreign network (WPA2) -> DNS resolution sent via DHCP 
should be taken as default

  Current behaviour:

  NM starts dnsmasq by default (I commented the start line to fix
  issues). DNS resolution stops after some minutes.

  Removing dnsmasq fron NetworkManager.conf (as I did) allows for name
  resolution except for web browsers (neither Firefox nor Chromium use
  the systemd.resolver).

  5 minutes of inactivity on the network suffice for the name resolution
  to stop working. Have to reestablish network connection (sudo
  resolveconf -u does not work).

  This violates expectation 1

  NM connects via openconnect. In the settings I added additional DNS
  servers and domain searches. They are ignored by dnsmasq. Name
  resolution does not work.

  *Worksaround* -> enter IP-addresses in /etc/hosts.

  dig @server-ip returns the correct IP address for target services but
  Firefox and Chromium do not utilize these services. dnsmasq does not
  return the correct address.

  This violates expectation 2

  Entering a foreign but known network, DNS resolution stops after a
  while (5 minutes inactivity suffice).

  Summarizing:

  a. DNS resolution using VPN connections does not work (I use openvpn, 
openconnect and pptp).
  b. dnsmasq does not resolve dns names correctly in wlan situations
  c. dnsmasq conflicts with systemd.resolver
  d. Firefox and Chromium ignore systemd.resolver
  e. removing dnsmasq from NetworkManager.conf releaves the issue a little 
(resolution drop-outs do not occur so frequently)

  Comparison to plain Debian demonstrated that Debian does not start
  dnsmasq. This led to the elimination of my dns=dnsmaq line in
  NetworkManager.conf

  Comparison to Raspian demonstrated that Raspian uses wpa_supplicant to
  control dns name resolution. I have not tried this setup in Ubuntu
  yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar 23 11:28:21 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-27 (54 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 10.1.0.254 dev wlp4s0  proto static  metric 600 
   10.0.0.0/8 dev wlp4s0  proto kernel  scope link  src 10.1.0.168  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   172.16.199.0/24 dev vmnet8  proto kernel  scope link  src 172.16.199.1 
   192.168.31.0/24 dev vmnet1  proto kernel  scope link  src 192.168.31.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-03-23T11:24:00.888213
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
rsb_hs  7a8389dc-afd3-444b-a106-1974e9e74dff  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   vmnet1  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

   vmnet8  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ---- 

   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/3  --   
   ----
  

[Touch-packages] [Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

[Aron Xu]

Adding a network-manager task here to have it tracked because reports
flows in to the package a lot, but marking as invalid since the cause is
actually in dnsmasq.

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

-- 
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:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Committed
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  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 1679928] Re: Dns lookups fail after going out of sleep mode

[Aron Xu]

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

This is actually the same issue in Bug #1675519, even though the title
says different stuff, thus I'm marking it as duplicate.

** This bug has been marked a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing

** This bug is no longer a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

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

Title:
  Dns lookups fail after going out of sleep mode

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04, 64bits, Dell XPS 15.

  When I wake up from sleep mode, I can no longer reach any domain by
  name, but still ping any IP address.

  Other users reported this problem here:
  http://askubuntu.com/questions/837575/dns-resolution-fails-after-
  wakeup-from-standby-ubuntu-16-10

  One of the proposed workaround is to disable dns caching by commenting
  out "dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf.

  Since dnsmasq is espacially useful when you use VPN, I must add I have
  openvpn setup on my machine so it could be part of the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1679928/+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 1680226] Re: Broken SplitDNS resolution in networ-manager VPN after disconnect and reconnect

[Aron Xu]

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

** This bug has been marked a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing

** This bug is no longer a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

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

Title:
  Broken SplitDNS resolution in networ-manager VPN after disconnect and
  reconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 16.04.2 LTS
  network-manager package version: 1.2.6-0ubuntu0.16.04.1

  I'm using Ubuntu Desktop 16.04 x64 and I have some VPN (OpenVPN and
  Cisco vpnc) connections defined. In all these connections I use both
  split tunnel and split dns.

  When I connect to a remote VPN server, my Ubuntu client correctly resolves 
DNS names in zones pushed by the remode server using the remote DNS server.
  For example: the remote VPN server pushes to the client "DNS resolver is 
192.168.10.1 for domain "vpndom.net"", then "host srv1.vpndom.net" is correctly 
resolved bu 192.168.10.1 and I get 192.168.10.7.

  After disconnecting and reconnecting to the VPN server, my Ubuntu
  client is no longer able to resolve DNS names in zones pushed by the
  VPN servers: "host srv1.vpndom.net" returns host not found.

  As a temporary solution, I downgraded netowrk manager to
  1.2.2-0ubuntu0.16.04.4 and all is working fine. So I think the problem
  is in network-manager 1.2.6-0ubuntu0.16.04.1

  As a workaround, with the connected VPN tunnel, I just "sudo killall
  dnsmasq": NetworkManager will then restart dnsmasq passing it all
  correct DNSes. There is no need to disconnect from the vpn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1680226/+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 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Aron Xu]

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

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

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

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1675519/+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 1680668] [NEW] Unexpected shutdown of Chrome Browser

[Barry Parker]

Public bug reported:

Unexpected shutdown of Chrome browser after last visit here regarding
the same issue

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia wl
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Apr  6 19:21:47 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Apple Inc. G84M [GeForce 8600M GT] [106b:00a3]
InstallationDate: Installed on 2017-03-31 (6 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
MachineType: Apple Inc. MacBookPro4,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP41.88Z.00C1.B03.0802271651
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42C89C8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42C89C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B03.0802271651:bd02/27/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8:
dmi.product.name: MacBookPro4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Apr  6 19:08:31 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Unexpected shutdown of Chrome Browser

Status in xorg package in Ubuntu:
  New

Bug description:
  Unexpected shutdown of Chrome browser after last visit here regarding
  the same issue

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Apr  6 

[Touch-packages] [Bug 1680665] [NEW] Attem; pted reboot with timeouts

[Barry Parker]

Public bug reported:

I had attempted a reboot because system was malfunctioning, at which
system was not recovering from timeouts so I had to shut down manually.
Same error messages as I has sent the last two times today.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia wl
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Apr  6 19:12:07 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Apple Inc. G84M [GeForce 8600M GT] [106b:00a3]
InstallationDate: Installed on 2017-03-31 (6 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
MachineType: Apple Inc. MacBookPro4,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP41.88Z.00C1.B03.0802271651
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42C89C8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42C89C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B03.0802271651:bd02/27/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8:
dmi.product.name: MacBookPro4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Apr  6 19:08:31 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Attem;pted reboot with timeouts

Status in xorg package in Ubuntu:
  New

Bug description:
  I had attempted a reboot because system was malfunctioning, at which
  system was not recovering from timeouts so I had to shut down
  manually.  Same error messages as I has sent the last two times today.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, 

[Touch-packages] [Bug 1680659] [NEW] Problem shutting down

[Barry Parker]

Public bug reported:

Hello I had a problem shutting down kept timing out had to manually shut
down.  Still getting error messages RE:

main: daemon not run
main: ping failed.

Everything else is in the report sent.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia wl
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Apr  6 18:41:52 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Apple Inc. G84M [GeForce 8600M GT] [106b:00a3]
InstallationDate: Installed on 2017-03-31 (6 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
MachineType: Apple Inc. MacBookPro4,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP41.88Z.00C1.B03.0802271651
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42C89C8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42C89C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B03.0802271651:bd02/27/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8:
dmi.product.name: MacBookPro4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Apr  6 18:36:13 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Problem shutting down

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello I had a problem shutting down kept timing out had to manually
  shut down.  Still getting error messages RE:

  main: daemon not run
  main: ping failed.

  Everything else is in the report sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not 

[Touch-packages] [Bug 1680643] [NEW] package libfdisk1:amd64 2.28.2-1ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[alex]

Public bug reported:

update error

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libfdisk1:amd64 2.28.2-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Thu Apr  6 09:56:13 2017
DpkgTerminalLog:
 dpkg: error processing package libfdisk1:amd64 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-04-06 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: util-linux
Title: package libfdisk1:amd64 2.28.2-1ubuntu1.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package libfdisk1:amd64 2.28.2-1ubuntu1.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in util-linux package in Ubuntu:
  New

Bug description:
  update error

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libfdisk1:amd64 2.28.2-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Apr  6 09:56:13 2017
  DpkgTerminalLog:
   dpkg: error processing package libfdisk1:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-04-06 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: util-linux
  Title: package libfdisk1:amd64 2.28.2-1ubuntu1.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  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/1680643/+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 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild

[Ubuntu Foundations Team Bug Bot]

The attachment "Fix synced from debian" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  pygobject-2 FTBFS on most arches during zesty test rebuild

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
   pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on
  most (not amd64) arches during a test rebuild of zesty. The build log
  can be found here:

  https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386
  .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz

  The failure seems to be due to the following:

   debian/rules build-arch
  make: *** No rule to make target 'build-arch'.  Stop.
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1679835/+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 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild

[Robert Bruce Park]

oops, please ignore previous comment text, copy error on my part.
the attached patch resolves this issue.

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

Title:
  pygobject-2 FTBFS on most arches during zesty test rebuild

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
   pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on
  most (not amd64) arches during a test rebuild of zesty. The build log
  can be found here:

  https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386
  .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz

  The failure seems to be due to the following:

   debian/rules build-arch
  make: *** No rule to make target 'build-arch'.  Stop.
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1679835/+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 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild

[Robert Bruce Park]

I just did:

$ reverse-depends src:pygobject-2 | sed -ne 's/^* \(\S\+\).*$/\1/p' |
xargs -n 1 rmadison

And according to the output, only these packages even saw uploads during
the zesty cycle:

python-gtk2-doc, comitup, mate-tweak, python-gconf, python-gnome2,
python-gobject

** Patch added: "Fix synced from debian"
   
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1679835/+attachment/4856746/+files/pygobject.patch

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

Title:
  pygobject-2 FTBFS on most arches during zesty test rebuild

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
   pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on
  most (not amd64) arches during a test rebuild of zesty. The build log
  can be found here:

  https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386
  .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz

  The failure seems to be due to the following:

   debian/rules build-arch
  make: *** No rule to make target 'build-arch'.  Stop.
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1679835/+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 433897] Re: Console/VT font is (randomly) not set (sometimes) on some machines. Stuck with the default VGA BIOS font.

[Minimax]

Bug still persist. Font settings (size) doesn't save through reboots.
Ubuntu version: 16.04.2
console-setup version: 1.108ubuntu15.3

I was found the workaround to fix this problem in here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759657. You need to
add the following file:

/etc/udev/rules.d/90-setupcon.rules
ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*", RUN+="/bin/setupcon"

It worked in the my case.

** Bug watch added: Debian Bug tracker #759657
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759657

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

Title:
  Console/VT font is (randomly) not set (sometimes) on some machines.
  Stuck with the default VGA BIOS font.

Status in console-setup:
  New
Status in console-setup package in Ubuntu:
  Confirmed
Status in console-setup source package in Precise:
  Confirmed
Status in console-setup source package in Quantal:
  Won't Fix

Bug description:
  [Impact]

  [Fix]

  [Test Case]

  [Regression Potential]

  [Original Report]
  Since the Karmic transition away from init.d scripts to upstart services has 
started, the font is no longer set at bootup. This results in unreadable user 
prompts, whenever applications output non-ascii characters to screen and it 
also affects graphic box characters used by ncurses, such as for debconf 
dialogs.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Sep 21 12:51:40 2009
  DistroRelease: Ubuntu 9.10
  Package: console-setup 1.34ubuntu2
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fi_FI.UTF-8
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
  SourcePackage: console-setup
  Uname: Linux 2.6.31-10-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/console-setup/+bug/433897/+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 1660053] Re: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2

[Alberto Salvia Novella]

It was "a marker instead of cursor comes on my screen now and then".

** Description changed:

- A marker instead of cursor comes on my screen now and then.
- 
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportLog:
-  ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: called for pid 10831, 
signal 11, core limit 0
-  ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable: 
/usr/lib/firefox/plugin-container (command line 
"/usr/lib/firefox/plugin-container 
/usr/lib/flashplugin-installer/libflashplayer.so -greomni 
/usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir 
/usr/lib/firefox/browser 2196 true plugin")
-  ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable version is 
blacklisted, ignoring
+  ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: called for pid 10831, 
signal 11, core limit 0
+  ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable: 
/usr/lib/firefox/plugin-container (command line 
"/usr/lib/firefox/plugin-container 
/usr/lib/flashplugin-installer/libflashplayer.so -greomni 
/usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir 
/usr/lib/firefox/browser 2196 true plugin")
+  ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable version is 
blacklisted, ignoring
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashReports:
-  644:0:116:0:2017-01-26 21:26:16.589169125 +0530:2017-01-26 
21:26:16.589169125 +0530:/var/crash/bluefish-data.0.upload
-  640:0:116:204816:2017-01-26 21:26:15.569168806 +0530:2017-01-26 
21:26:16.569168806 +0530:/var/crash/bluefish-data.0.crash
-  600:0:116:159472:2017-01-28 22:32:36.371843338 +0530:2017-01-28 
22:32:37.371843338 +0530:/var/crash/apport.0.crash
-  600:109:116:0:2017-01-27 03:37:06.746315169 +0530:2017-01-27 
03:37:06.746315169 +0530:/var/crash/bluefish-data.0.uploaded
+  644:0:116:0:2017-01-26 21:26:16.589169125 +0530:2017-01-26 
21:26:16.589169125 +0530:/var/crash/bluefish-data.0.upload
+  640:0:116:204816:2017-01-26 21:26:15.569168806 +0530:2017-01-26 
21:26:16.569168806 +0530:/var/crash/bluefish-data.0.crash
+  600:0:116:159472:2017-01-28 22:32:36.371843338 +0530:2017-01-28 
22:32:37.371843338 +0530:/var/crash/apport.0.crash
+  600:109:116:0:2017-01-27 03:37:06.746315169 +0530:2017-01-27 
03:37:06.746315169 +0530:/var/crash/bluefish-data.0.uploaded
  Date: Sat Jan 28 22:32:37 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 2
  InstallationDate: Installed on 2016-12-04 (54 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1.1
-  apt  1.2.19
+  dpkg 1.18.4ubuntu1.1
+  apt  1.2.19
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 2

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportLog:
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: called for pid 10831, 
signal 11, core limit 0
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable: 
/usr/lib/firefox/plugin-container (command line 
"/usr/lib/firefox/plugin-container 
/usr/lib/flashplugin-installer/libflashplayer.so -greomni 
/usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir 
/usr/lib/firefox/browser 2196 true plugin")
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable version is 
blacklisted, ignoring
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashReports:
   644:0:116:0:2017-01-26 21:26:16.589169125 +0530:2017-01-26 
21:26:16.589169125 +0530:/var/crash/bluefish-data.0.upload
   640:0:116:204816:2017-01-26 21:26:15.569168806 +0530:2017-01-26 
21:26:16.569168806 +0530:/var/crash/bluefish-data.0.crash
   600:0:116:159472:2017-01-28 22:32:36.371843338 +0530:2017-01-28 
22:32:37.371843338 +0530:/var/crash/apport.0.crash
   600:109:116:0:2017-01-27 03:37:06.746315169 +0530:2017-01-27 
03:37:06.746315169 +0530:/var/crash/bluefish-data.0.uploaded
  Date: Sat Jan 28 22:32:37 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 2
  InstallationDate: Installed on 2016-12-04 (54 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - 

[Touch-packages] [Bug 1660053] Re: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2

[Alberto Salvia Novella]

Please open a new report about the bug you mentioned in the description

(https://help.ubuntu.com/community/ReportingBugs#Reporting_non-
crash_hardware_and_desktop_application_bugs)

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

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

Title:
  package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 2

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportLog:
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: called for pid 10831, 
signal 11, core limit 0
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable: 
/usr/lib/firefox/plugin-container (command line 
"/usr/lib/firefox/plugin-container 
/usr/lib/flashplugin-installer/libflashplayer.so -greomni 
/usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir 
/usr/lib/firefox/browser 2196 true plugin")
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable version is 
blacklisted, ignoring
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashReports:
   644:0:116:0:2017-01-26 21:26:16.589169125 +0530:2017-01-26 
21:26:16.589169125 +0530:/var/crash/bluefish-data.0.upload
   640:0:116:204816:2017-01-26 21:26:15.569168806 +0530:2017-01-26 
21:26:16.569168806 +0530:/var/crash/bluefish-data.0.crash
   600:0:116:159472:2017-01-28 22:32:36.371843338 +0530:2017-01-28 
22:32:37.371843338 +0530:/var/crash/apport.0.crash
   600:109:116:0:2017-01-27 03:37:06.746315169 +0530:2017-01-27 
03:37:06.746315169 +0530:/var/crash/bluefish-data.0.uploaded
  Date: Sat Jan 28 22:32:37 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 2
  InstallationDate: Installed on 2016-12-04 (54 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1660053/+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 1569719] Re: package python3 3.5.1-3 failed to install/upgrade: pre-dependency problem - not installing python3

[Barry Warsaw]

Setting up python3.5-minimal (3.5.1-10) ...
Traceback (most recent call last):
  File "/usr/lib/python3.5/py_compile.py", line 6, in 
import importlib._bootstrap_external
  File "/usr/lib/python3.5/importlib/__init__.py", line 93
raise ValueError('{}.__loader__ is not set'.format(name)) from None
 ^
SyntaxError: invalid syntax

That's super weird.  raise-from (i.e. PEP 3134 chained exceptions) go
waay back in Python 3.

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

Title:
  package python3 3.5.1-3 failed to install/upgrade: pre-dependency
  problem - not installing python3

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to Ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Tue Apr 12 12:33:05 2016
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-01-16 (453 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-3 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to xenial on 2016-04-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1569719/+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 1650827] Re: "Failed name lookup - disconnected path"

[Alberto Salvia Novella]

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

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

Title:
  "Failed name lookup - disconnected path"

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.10 series:
  Fix Committed
Status in AppArmor 2.9 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I'm currently trying to use dovecot in a test scenario, but run into
  the problem of a strange malfunction of apparmor.

  What I do:

  installed packages   dovecot-core   and   dovecot-lmtp
  (and of course apparmor)

  Then I do (as root)

  /usr/lib/dovecot/dovecot-lda -d hadmut 

[Touch-packages] [Bug 1590970] Re: package lightdm 1.18.1-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10

[Alberto Salvia Novella]

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

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

Title:
  package lightdm 1.18.1-0ubuntu1 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 10

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  removed and reinstalled due to graphical error with Radeon video card.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   ubuntu-desktop: Purge
   lightdm: Purge
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jun  8 20:50:25 2016
  DpkgTerminalLog:
   Removing ubuntu-desktop (1.361) ...
   Removing lightdm (1.18.1-0ubuntu1) ...
   dpkg: error processing package lightdm (--purge):
subprocess installed pre-removal script returned error exit status 10
  DuplicateSignature:
   package:lightdm:1.18.1-0ubuntu1
   Removing lightdm (1.18.1-0ubuntu1) ...
   dpkg: error processing package lightdm (--purge):
subprocess installed pre-removal script returned error exit status 10
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 10
  InstallationDate: Installed on 2016-05-31 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: lightdm
  Title: package lightdm 1.18.1-0ubuntu1 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1590970/+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 1569719] Re: package python3 3.5.1-3 failed to install/upgrade: pre-dependency problem - not installing python3

[Alberto Salvia Novella]

** Changed in: python3-defaults (Ubuntu)
   Importance: Undecided => High

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

Title:
  package python3 3.5.1-3 failed to install/upgrade: pre-dependency
  problem - not installing python3

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to Ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Tue Apr 12 12:33:05 2016
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-01-16 (453 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-3 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to xenial on 2016-04-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1569719/+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 1650827] Re: "Failed name lookup - disconnected path"

[Christian Boltz]

Thanks for the report!

I commited the updated profile to bzr trunk r3651, 2.10 branch r3391 and
2.9 branch r3056.

If you want to update your profile locally, the needed changes are:

-/usr/lib/dovecot/dovecot-lda {
+/usr/lib/dovecot/dovecot-lda flags=(attach_disconnected) {

+  /run/dovecot/auth-userdb rw,
+  /usr/share/dovecot/protocols.d/ r,


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

** Also affects: apparmor/2.9
   Importance: Undecided
   Status: New

** Also affects: apparmor/2.10
   Importance: Undecided
   Status: New

** Changed in: apparmor
   Status: New => Fix Committed

** Changed in: apparmor
Milestone: None => 2.11.1

** Changed in: apparmor/2.10
   Status: New => Fix Committed

** Changed in: apparmor/2.10
Milestone: None => 2.10.3

** Changed in: apparmor/2.9
   Status: New => Fix Committed

** Changed in: apparmor/2.9
Milestone: None => 2.9.5

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

Title:
  "Failed name lookup - disconnected path"

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.10 series:
  Fix Committed
Status in AppArmor 2.9 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I'm currently trying to use dovecot in a test scenario, but run into
  the problem of a strange malfunction of apparmor.

  What I do:

  installed packages   dovecot-core   and   dovecot-lmtp
  (and of course apparmor)

  Then I do (as root)

  /usr/lib/dovecot/dovecot-lda -d hadmut 

[Touch-packages] [Bug 1650827] Re: "Failed name lookup - disconnected path"

[Launchpad Bug Tracker]

** Branch linked: lp:apparmor

** Branch linked: lp:apparmor/2.10

** Branch linked: lp:apparmor/2.9

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

Title:
  "Failed name lookup - disconnected path"

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.10 series:
  Fix Committed
Status in AppArmor 2.9 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I'm currently trying to use dovecot in a test scenario, but run into
  the problem of a strange malfunction of apparmor.

  What I do:

  installed packages   dovecot-core   and   dovecot-lmtp
  (and of course apparmor)

  Then I do (as root)

  /usr/lib/dovecot/dovecot-lda -d hadmut 

[Touch-packages] [Bug 1602536] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives

[Sebastian Unger]

I believe this happens because unattended-upgrades gets and releases the
lock a couple times (such as between installing upgrades and then
removing now no longer required automatically installed packages) and
dies if it cannot re-aquire the lock (rather than gracefully handling
it).

The high frequency is easily explained since apt-daily runs both
unattended-upgrades and aptd (via dbus triggers both from Update-Post-
Invoke-Success (or whatever it was called) and directly from the apt-
daily script) and this sets up a race with a fairly high chance of
hitting unattended-upgrades somewhere where it hurts.

Even when it does not lead to a crash it often causes upgrades not to be
installed. This can be seen by setting APT::Periodic::Verbose to 3 and
monitoring the logs. Often one or another of the steps of apt-daily will
fail because it could not acquire the lock.

Hope this helps.

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

Title:
  /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin
  /unattended-
  upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unattended-upgrades.  This problem was most recently seen
  with version 0.90, the problem page at
  https://errors.ubuntu.com/problem/19f99745d7dce5aea118eb31bfffcbdcdf238c4f
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1602536/+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 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

[bugproxy]

--- Comment From ru...@us.ibm.com 2017-04-06 17:50 EDT---
Sorry about the long delay, but our bridge missed the last two LP status 
updates.  Validated with 4.4.0-72 and closing on our end.  Thanks.

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16042

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in bridge-utils source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in bridge-utils source package in Yakkety:
  Invalid

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058984]  [] 

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Alberto Salvia Novella]

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: avahi (Ubuntu)
   Importance: Undecided => 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/1586528

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1680599] [NEW] unattended-upgrades crashes without writing to the log on invalid config file entries

[Dan Valentine]

Public bug reported:

If Unattended-Upgrade::Allowed-Origins in 50unattended-upgrades contains
an invalid entry, such as "invalid", unattended-upgrades crashes without
writing to /var/log/unattended-upgrades/unattended-upgrades.log.

# unattended-upgrades --debug
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrades", line 1536, in 
main(options)
  File "/usr/bin/unattended-upgrades", line 1202, in main
allowed_origins = get_allowed_origins()
  File "/usr/bin/unattended-upgrades", line 343, in get_allowed_origins
allowed_origins = get_allowed_origins_legacy()
  File "/usr/bin/unattended-upgrades", line 328, in get_allowed_origins_legacy
(distro_id, distro_codename) = s.split()
ValueError: not enough values to unpack (expected 2, got 1)

0.92ubuntu1.2 on 16.10

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

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

Title:
  unattended-upgrades crashes without writing to the log on invalid
  config file entries

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  If Unattended-Upgrade::Allowed-Origins in 50unattended-upgrades
  contains an invalid entry, such as "invalid", unattended-upgrades
  crashes without writing to /var/log/unattended-upgrades/unattended-
  upgrades.log.

  # unattended-upgrades --debug
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrades", line 1536, in 
  main(options)
File "/usr/bin/unattended-upgrades", line 1202, in main
  allowed_origins = get_allowed_origins()
File "/usr/bin/unattended-upgrades", line 343, in get_allowed_origins
  allowed_origins = get_allowed_origins_legacy()
File "/usr/bin/unattended-upgrades", line 328, in get_allowed_origins_legacy
  (distro_id, distro_codename) = s.split()
  ValueError: not enough values to unpack (expected 2, got 1)

  0.92ubuntu1.2 on 16.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1680599/+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 1680597] [NEW] udev 60-block.rules does not watch bcache

[Scott Moser]

Public bug reported:

bcache devices do not have a watch on them from /lib/udev/rules.d/60-block.rules
The result is that this will fail:

  mkfs.ext4 /dev/bcache0 -L  foobar
  udevadm settle
  ls -l /dev/disk/by-label/foobar

where as it will work on
  mkfs.ext4 /dev/vdb -L foobar
  udevadm settle
  ls -l /dev/disk/by-label/foobar

We found this when chasing a curtin bug (bug 1680591).  The result of it was 
that
we were installing and an update-grub would choose to boot with 
root=/dev/bcache0 
rather than UUID=.


Related bugs:
 * bug 1680591:  installed system boots with root=/dev/bcache0 rather than 
root=UUID when root is bcache

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: udev 232-19
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Apr  6 16:28:59 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (623 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Intel Corporation

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


** Tags: amd64 apport-bug zesty

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

Title:
  udev 60-block.rules does not watch bcache

Status in systemd package in Ubuntu:
  New

Bug description:
  bcache devices do not have a watch on them from 
/lib/udev/rules.d/60-block.rules
  The result is that this will fail:

mkfs.ext4 /dev/bcache0 -L  foobar
udevadm settle
ls -l /dev/disk/by-label/foobar

  where as it will work on
mkfs.ext4 /dev/vdb -L foobar
udevadm settle
ls -l /dev/disk/by-label/foobar

  We found this when chasing a curtin bug (bug 1680591).  The result of it was 
that
  we were installing and an update-grub would choose to boot with 
root=/dev/bcache0 
  rather than UUID=.

  
  Related bugs:
   * bug 1680591:  installed system boots with root=/dev/bcache0 rather than 
root=UUID when root is bcache

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: udev 232-19
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Apr  6 16:28:59 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (623 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1680597/+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 1665602] Re: nautilus no thumbnails for .jpg and .png

[Jeremy Bicha]

Nick, that issue should be fixed now with this update:

https://launchpad.net/ubuntu/+source/librsvg/2.40.16-2~svn1

After updating, log out and log back in. If things work, there is no
need to file a bug for this issue now.

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

Title:
  nautilus no thumbnails for .jpg and .png

Status in gnome-desktop:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  thumbnail for .tif is ok
  corrado@corrado-z2:~$ inxi
  CPU~Dual core Intel Core i3-4130 (-HT-MCP-) speed/max~3366/3400 MHz 
Kernel~4.10.0-8-generic x86_64 Up~1:03 Mem~983.2/7861.2MB HDD~1000.2GB(16.0% 
used) Procs~231 Client~Shell inxi~2.3.8  
  corrado@corrado-z2:~$ uname -a
  Linux corrado-z2 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  corrado@corrado-z2:~$ 
  display was ok with kernel 4.9.0-15
  corrado@corrado-z2:~$ apt-cache policy nautilus
  nautilus:
Installed: 1:3.20.3-1ubuntu4
Candidate: 1:3.20.3-1ubuntu4
Version table:
   *** 1:3.20.3-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-z2:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.3-1ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Feb 17 11:22:50 2017
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'search-view' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'1329x774+49+24'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'larger'"
  InstallationDate: Installed on 2017-01-23 (24 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170123)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-desktop/+bug/1665602/+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 1674680] Re: Deprecated rfcomm.conf still mentioned

[Dave Chiluk]

Just so you know I'm waiting for zesty release before uploading this.  I
don't want to risk causing issues on the release media.  Additionally
policy is to only push high priority bug fixes for the few weeks leading
up to release.

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

Title:
  Deprecated rfcomm.conf still mentioned

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

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 1680585] Re: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()

[Apport retracing service]

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

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 #1556439, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1680585/+attachment/4856606/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1680585/+attachment/4856609/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1680585/+attachment/4856612/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1680585/+attachment/4856613/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1680585/+attachment/4856615/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680585/+attachment/4856616/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680585/+attachment/4856617/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1556439

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  A random pulseaudio crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  Uname: Linux 4.10.8-041008-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl  29575 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Apr  6 21:38:36 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so
   ?? () from /usr/lib/pulse-10.0/modules/module-switch-on-port-available.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: Upgraded to zesty on 2017-03-12 (25 days ago)
  UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1680585/+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 1640320] Re: FTBFS in zesty

[Balint Reczey]

** Changed in: location-service (Ubuntu)
 Assignee: Balint Reczey (rbalint) => (unassigned)

** Changed in: location-service (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  FTBFS in zesty

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  FTBFS in zesty during a no change rebuild against new boost

  Please see build logs at: https://launchpad.net/ubuntu/+source
  /location-service/3.0.0+16.10.20160912-0ubuntu2

  Please help fix this

  [ 10%] Building CXX object 
src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
  cd 
/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location
 && /usr/bin/g++   -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 
-DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS 
-Dubuntu_location_service_connectivity_EXPORTS 
-I/<>/location-service-3.0.0+16.10.20160912/3rd-party 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/json-c 
-I/<>/location-service-3.0.0+16.10.20160912/include/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/src/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service
 -I/usr/include/ubuntu  -g -O2 
-fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra 
-fPIC -Wno-error=unused-local-typedefs -fPIC   -o 
CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
 -c 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp
  In file included from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0,
   from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19:
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   std::vector xtra_hosts
^~
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10:
 warning: extra ‘;’ [-Wpedantic]
   };
^
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   virtual std::vector download_xtra_data(const Configuration& 
config) = 0;
^~
  make -f po/CMakeFiles/pofiles_70.dir/build.make 
po/CMakeFiles/pofiles_70.dir/depend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+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 1676996] Re: unity8-tests is installed as a depends of unity8-common, but unity8-tests does not seem like a package most users need

[Michał Sawicz]

** Changed in: canonical-devices-system-image
Milestone: u8c-z => u8c-2

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

Title:
  unity8-tests is installed as a depends of unity8-common, but
  unity8-tests does not seem like a package most users need

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

Bug description:
  unity8-common depends on unity8-tests, but it seems like unity8-tests
  and its dependencies are not necessary on most users' systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676996/+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 1677187] Re: Applications aren't given input when launched from the launcher or the app drawer

[Michał Sawicz]

** Changed in: canonical-devices-system-image
Milestone: u8c-z => u8c-2

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

Title:
  Applications aren't given input when launched from the launcher or the
  app drawer

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

Bug description:
  Steps to reproduce:

  1. Open the app drawer and type "terminal"

  2. Select the ubuntu-terminal-app

  3. The terminal will launch and the window style will make it look as
  though it has focus. It will display a password input prompt.

  4. Type "Hello"

  5. Open the app drawer again and see the input went to the search bar
  instead

  Expected result:

  The terminal password prompt should display "*"

  Actual result:

  The app drawer search bar will receive this input instead (despite not
  being visible)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677187/+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 1668700] Re: Blank default scope in unity8-deb

[Michał Sawicz]

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

** Changed in: unity-scope-mediascanner (Ubuntu)
   Status: New => Invalid

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

Title:
  Blank default scope in unity8-deb

Status in Canonical System Image:
  Fix Released
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Environment:
  unity8-deb on a fresh zesty installation in kvm

  Steps:

  1º Install zesty on kvm image
  2º Enter unity8-deb
  3º Check the default scope

  Expected result: some scopes should be marked by default as favorite,
  unity-scope-mediascanner2 wasn't installed along with zesty so some
  scopes are missing

  Current result: default scope is blank and only 3rd party scopes are
  available

  Add info: Bug #1668701

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668700/+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 1675448] Re: Unity 8 doesn't allow multiple Mir connections from an application instance

[Michał Sawicz]

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

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

Title:
  Unity 8 doesn't allow multiple Mir connections from an application
  instance

Status in Canonical System Image:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Some clients like to probe to see if a mir connection is available
  such as SDL2 and SDL1.2.

  This is an issue in U8 as it doesnt seem to allow multiple connections
  in one process.

  Example:
  http://paste.ubuntu.com/24235399/

  Output on U8:
  http://paste.ubuntu.com/24235406/

   Proposed solution 

  Related to bug #1589637

  We need to accept multiple connections from the same application
  instance, relying on ubuntu-app-launch to tell us about instances and
  their lifecycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675448/+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 1676878] Re: Not using Ubuntu font family and suru icons in Qt widget apps

[Michał Sawicz]

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

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

Title:
  Not using Ubuntu font family and suru icons in Qt widget apps

Status in Canonical System Image:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  Widget apps (as opposed to QML apps using UITK) don't correctly
  default to the Ubuntu font family or suru icon theme, resulting e.g.
  in lots of missing toolbar icons in Qt apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676878/+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] It's impossible to close some dialogs (missing 'X' window button)

[Michał Sawicz]

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

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

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

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

-- 
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] It's impossible to close some dialogs (missing 'X' window
  button)

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Invalid
Status in Ubuntu UX:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

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 1667570] Re: App drawer icon titles are difficult to read (truncated too much and have no tooltips)

[Michał Sawicz]

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

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

Title:
  App drawer icon titles are difficult to read (truncated too much and
  have no tooltips)

Status in Canonical System Image:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  App drawer icon titles are difficult to read (truncated too much
  ending in "..." and have no tooltips)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667570/+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 1672673] Re: Application menus should hide when triggering the spread

[Michał Sawicz]

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

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

Title:
  Application menus should hide when triggering the spread

Status in Canonical System Image:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Having the menu open makes using the spread hard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672673/+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 1675373] Re: Pressing Super hides launcher

[Michał Sawicz]

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

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

Title:
  Pressing Super hides launcher

Status in Canonical System Image:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps:
  * log in to unity8 (make sure launcher is set to always show)
  * press Super

  Expected:
  * app drawer is shown

  Current:
  * launcher hides

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675373/+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 1666363] Re: Windows behind are missing during un-maximize animation

[Michał Sawicz]

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

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

Title:
  Windows behind are missing during un-maximize animation

Status in Canonical System Image:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Windows behind are missing during an un-maximize animation. They don't
  appear until the animation completes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666363/+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 1676995] Re: [regression] App switcher does not respond to tab events

[Michał Sawicz]

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

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

Title:
  [regression] App switcher does not respond to tab events

Status in Canonical System Image:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  17.04 deb based unity8 session running in VM.
  unity8: 8.15+17.04.20170321-0ubuntu1

  To reproduce:
  1) Boot up unity8 deb based session.
  2) Load an application either from launcher or app drawer, e.g. System 
Settings
  3) Press Alt+Tab to display task switcher and then release Tab key to leave 
switcher showing.
  4) Press Tab again.

  Expected result:
  Pressing Tab should cycle through the available apps.

  Actual result:
  The selected app does not change using the Tab key.

  Note: Once the unity8 session has been locked and unlocked, the Tab
  key selection will work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676995/+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 1677259] Re: [regression] Search string not replaced in app drawer after Super+A

[Michał Sawicz]

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

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

Title:
  [regression] Search string not replaced in app drawer after Super+A

Status in Canonical System Image:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps:
  * open the app drawer
  * type "foo"
  * close the app drawer
  * press Super+A to open the app drawer
  * type "bar"

  Expected:
  * search term is "bar"

  Current:
  * search term is "foobar"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 29 16:00:37 2017
  InstallationDate: Installed on 2016-05-06 (326 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (127 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677259/+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 1666363] Re: Windows behind are missing during un-maximize animation

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170404.7-0ubuntu2

---
unity8 (8.15+17.04.20170404.7-0ubuntu2) zesty; urgency=medium

  [ Michael Zanetti ]
  * Make the default store uri point to gnome software center

 -- Timo Jyrinki   Thu, 06 Apr 2017 10:49:29
+0300

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Windows behind are missing during un-maximize animation

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

Bug description:
  Windows behind are missing during an un-maximize animation. They don't
  appear until the animation completes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666363/+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] It's impossible to close some dialogs (missing 'X' window button)

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170404.7-0ubuntu2

---
unity8 (8.15+17.04.20170404.7-0ubuntu2) zesty; urgency=medium

  [ Michael Zanetti ]
  * Make the default store uri point to gnome software center

 -- Timo Jyrinki   Thu, 06 Apr 2017 10:49:29
+0300

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

-- 
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] It's impossible to close some dialogs (missing 'X' window
  button)

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:
  Fix Released

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 1667570] Re: App drawer icon titles are difficult to read (truncated too much and have no tooltips)

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170404.7-0ubuntu2

---
unity8 (8.15+17.04.20170404.7-0ubuntu2) zesty; urgency=medium

  [ Michael Zanetti ]
  * Make the default store uri point to gnome software center

 -- Timo Jyrinki   Thu, 06 Apr 2017 10:49:29
+0300

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  App drawer icon titles are difficult to read (truncated too much and
  have no tooltips)

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

Bug description:
  App drawer icon titles are difficult to read (truncated too much
  ending in "..." and have no tooltips)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667570/+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 1673199] Re: Greeter shows "unknown" session if user has never logged in when it should show default.

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170404.7-0ubuntu2

---
unity8 (8.15+17.04.20170404.7-0ubuntu2) zesty; urgency=medium

  [ Michael Zanetti ]
  * Make the default store uri point to gnome software center

 -- Timo Jyrinki   Thu, 06 Apr 2017 10:49:29
+0300

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

-- 
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:
  Fix Released

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 1675373] Re: Pressing Super hides launcher

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170404.7-0ubuntu2

---
unity8 (8.15+17.04.20170404.7-0ubuntu2) zesty; urgency=medium

  [ Michael Zanetti ]
  * Make the default store uri point to gnome software center

 -- Timo Jyrinki   Thu, 06 Apr 2017 10:49:29
+0300

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Pressing Super hides launcher

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

Bug description:
  Steps:
  * log in to unity8 (make sure launcher is set to always show)
  * press Super

  Expected:
  * app drawer is shown

  Current:
  * launcher hides

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675373/+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 1676878] Re: Not using Ubuntu font family and suru icons in Qt widget apps

[Launchpad Bug Tracker]

This bug was fixed in the package qtubuntu -
0.64+17.04.20170404-0ubuntu1

---
qtubuntu (0.64+17.04.20170404-0ubuntu1) zesty; urgency=medium

  * Use the correct font (Ubuntu family) and icon theme (suru) (LP:
#1676878)

 -- Lukáš Tinkl   Tue, 04 Apr 2017 00:47:22
+

** Changed in: qtubuntu (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Not using Ubuntu font family and suru icons in Qt widget apps

Status in Canonical System Image:
  In Progress
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  Widget apps (as opposed to QML apps using UITK) don't correctly
  default to the Ubuntu font family or suru icon theme, resulting e.g.
  in lots of missing toolbar icons in Qt apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676878/+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 1676995] Re: [regression] App switcher does not respond to tab events

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170404.7-0ubuntu2

---
unity8 (8.15+17.04.20170404.7-0ubuntu2) zesty; urgency=medium

  [ Michael Zanetti ]
  * Make the default store uri point to gnome software center

 -- Timo Jyrinki   Thu, 06 Apr 2017 10:49:29
+0300

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [regression] App switcher does not respond to tab events

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

Bug description:
  17.04 deb based unity8 session running in VM.
  unity8: 8.15+17.04.20170321-0ubuntu1

  To reproduce:
  1) Boot up unity8 deb based session.
  2) Load an application either from launcher or app drawer, e.g. System 
Settings
  3) Press Alt+Tab to display task switcher and then release Tab key to leave 
switcher showing.
  4) Press Tab again.

  Expected result:
  Pressing Tab should cycle through the available apps.

  Actual result:
  The selected app does not change using the Tab key.

  Note: Once the unity8 session has been locked and unlocked, the Tab
  key selection will work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676995/+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 1677259] Re: [regression] Search string not replaced in app drawer after Super+A

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170404.7-0ubuntu2

---
unity8 (8.15+17.04.20170404.7-0ubuntu2) zesty; urgency=medium

  [ Michael Zanetti ]
  * Make the default store uri point to gnome software center

 -- Timo Jyrinki   Thu, 06 Apr 2017 10:49:29
+0300

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [regression] Search string not replaced in app drawer after Super+A

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

Bug description:
  Steps:
  * open the app drawer
  * type "foo"
  * close the app drawer
  * press Super+A to open the app drawer
  * type "bar"

  Expected:
  * search term is "bar"

  Current:
  * search term is "foobar"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 29 16:00:37 2017
  InstallationDate: Installed on 2016-05-06 (326 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (127 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677259/+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 1675448] Re: Unity 8 doesn't allow multiple Mir connections from an application instance

[Launchpad Bug Tracker]

This bug was fixed in the package qtmir - 0.5.1+17.04.20170404-0ubuntu1

---
qtmir (0.5.1+17.04.20170404-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * Remove m_tools member
  * EventInfo::store: Store an empty cookie for mir events without
cookie

  [ Daniel d'Andrada ]
  * Support multiple sessions per Application (LP: #1675448)

 -- Lukáš Tinkl   Tue, 04 Apr 2017 00:47:22
+

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

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

Title:
  Unity 8 doesn't allow multiple Mir connections from an application
  instance

Status in Canonical System Image:
  In Progress
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Some clients like to probe to see if a mir connection is available
  such as SDL2 and SDL1.2.

  This is an issue in U8 as it doesnt seem to allow multiple connections
  in one process.

  Example:
  http://paste.ubuntu.com/24235399/

  Output on U8:
  http://paste.ubuntu.com/24235406/

   Proposed solution 

  Related to bug #1589637

  We need to accept multiple connections from the same application
  instance, relying on ubuntu-app-launch to tell us about instances and
  their lifecycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675448/+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 1672053] Re: [unity8] opening app drawer breaks Alt-Tab in app switcher

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170404.7-0ubuntu2

---
unity8 (8.15+17.04.20170404.7-0ubuntu2) zesty; urgency=medium

  [ Michael Zanetti ]
  * Make the default store uri point to gnome software center

 -- Timo Jyrinki   Thu, 06 Apr 2017 10:49:29
+0300

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [unity8] opening app drawer breaks Alt-Tab in app switcher

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

Bug description:
  ubuntu 17.04 unity8

  first, open some random app 
  then open the app drawer with the mouse (smash the mouse into the left side 
of the screen) then click outside the app drawer to close it. now press ALT TAB 
multiple times to move through the apps in app switcher (doesn't seem to work 
here)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672053/+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 1672673] Re: Application menus should hide when triggering the spread

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170404.7-0ubuntu2

---
unity8 (8.15+17.04.20170404.7-0ubuntu2) zesty; urgency=medium

  [ Michael Zanetti ]
  * Make the default store uri point to gnome software center

 -- Timo Jyrinki   Thu, 06 Apr 2017 10:49:29
+0300

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Application menus should hide when triggering the spread

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

Bug description:
  Having the menu open makes using the spread hard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672673/+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 1680124] Re: desktop overrides not being used in Zesty VM

[Olivier Tilloy]

I can confirm that UA overrides are not being loaded in a virtualbox VM
running zesty+unity8. However they are loaded in the same VM in unity7.

** Summary changed:

- desktop overrides not being used in Zesty VM
+ UA overrides not being loaded in Zesty VM running unity8

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  UA overrides not being loaded in Zesty VM running unity8

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  running zesty release in virtualbox vm. When visting gmail.com, and
  others in override file it appears we are getting basic versions of
  the site and our overrides are not being presented.

  Here is browser log when launching:
  http://pastebin.ubuntu.com/24320670/

  Seems to work as expected on zesty natively, but not in vm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1680124/+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 1679776] Re: Package FTBFS because of missing qdoc command

[Launchpad Bug Tracker]

This bug was fixed in the package accounts-qml-module -
0.6+17.04.20170405-0ubuntu1

---
accounts-qml-module (0.6+17.04.20170405-0ubuntu1) zesty; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * Be sure to depend on qttools5-dev-tools to be able to use the qdoc
binary. (LP: #1679776)

 -- Łukasz Zemczak   Wed, 05 Apr 2017
08:58:21 +

** Changed in: accounts-qml-module (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Package FTBFS because of missing qdoc command

Status in accounts-qml-module package in Ubuntu:
  Fix Released

Bug description:
  During the zesty test-rebuild the accounts-qml-module package FTBFS on
  all archs due to the following reason:

  make[3]: Entering directory 
'/<>/accounts-qml-module-0.6+16.04.20151106/tests'
  install -m 755 -p tst_plugin 
/<>/accounts-qml-module-0.6+16.04.20151106/debian/tmp/usr/bin/tst_plugin
  make[3]: Leaving directory 
'/<>/accounts-qml-module-0.6+16.04.20151106/tests'
  make[2]: Leaving directory 
'/<>/accounts-qml-module-0.6+16.04.20151106/tests'
  /usr/lib/x86_64-linux-gnu/qt5/bin/qdoc 
/<>/accounts-qml-module-0.6+16.04.20151106/doc/accounts-qml-module-ubuntu.qdocconf
  make[1]: /usr/lib/x86_64-linux-gnu/qt5/bin/qdoc: Command not found
  Makefile:266: recipe for target 'docs-html' failed
  make[1]: *** [docs-html] Error 127
  make[1]: Leaving directory 
'/<>/accounts-qml-module-0.6+16.04.20151106'
  dh_auto_install: make -j1 install 
DESTDIR=/<>/accounts-qml-module-0.6+16.04.20151106/debian/tmp 
AM_UPDATE_INFO_DIR=no 
INSTALL_ROOT=/<>/accounts-qml-module-0.6+16.04.20151106/debian/tmp 
returned exit code 2
  debian/rules:21: recipe for target 'binary' failed
  make: *** [binary] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accounts-qml-module/+bug/1679776/+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 1672392] Re: Install an app from Ubuntu Terminal and it doesn't show up in the app drawer

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-app-launch -
0.12+17.04.20170404.2-0ubuntu1

---
ubuntu-app-launch (0.12+17.04.20170404.2-0ubuntu1) zesty; urgency=medium

  [ Michael Terry ]
  * Bump version for new AppID methods

  [ Ted Gould ]
  * Cleanup registry references to make them consistent (LP: #1676361)
  * Watch system folders for apps added and removed (LP: #1630997,
#1672392)
  * Wait with a timeout for the libertine service to start
  * Provide equality operators for Application and Application::Instance
objects. (LP: #1677345)
  * Force GTK and Qt backends when using XMir

 -- Ted Gould   Tue, 04 Apr 2017 21:48:48 +

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Install an app from Ubuntu Terminal and it doesn't show up in the app
  drawer

Status in Canonical System Image:
  In Progress
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  On a fresh Zesty Qemu VM, I installed dconf-editor from the archive
  using the terminal.

    sudo apt install dconf-editor

  and it didn't show up in the app drawer, either in the scrollable list
  or searching by name.

  After a reboot (can't logout due to bug #1670657) dconf-editor is
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672392/+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 1680548] [NEW] Problems with Ubuntu Nome persist

[Barry Parker]

Public bug reported:

I have Ubuntu Nome 16.04.2 64-bit and the same problems persist there is
a report that was sent to you regarding this problem.  I keep seeing
this error message in my boot information:

main: daemon not run
main: ping failed

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia wl
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Apr  6 10:47:21 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Apple Inc. G84M [GeForce 8600M GT] [106b:00a3]
InstallationDate: Installed on 2017-03-31 (5 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
MachineType: Apple Inc. MacBookPro4,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP41.88Z.00C1.B03.0802271651
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42C89C8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42C89C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B03.0802271651:bd02/27/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8:
dmi.product.name: MacBookPro4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Apr  6 09:06:13 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Problems with Ubuntu Nome persist

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Ubuntu Nome 16.04.2 64-bit and the same problems persist there
  is a report that was sent to you regarding this problem.  I keep
  seeing this error message in my boot information:

  main: daemon not run
  main: ping failed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use 

[Touch-packages] [Bug 1680546] [NEW] grub

[sean markham]

Public bug reported:

I moved "grub" out of the boot file by accident. I though it was put
back correct, but now at start up I see the computer booting up, instead
of my nice Lubuntu screen. This seen ok. But what did I do?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
BootLog: /dev/sda1: clean, 472643/9641984 files, 6975586/38550528 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Apr  6 12:37:29 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[1028:01fe]
   Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01fe]
InstallationDate: Installed on 2016-07-08 (272 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: Dell Inc. Latitude D830
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=48e542bb-c7f2-459f-b9a7-c0195cdd8a16 ro plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0HN341
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D830
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Apr  6 12:14:11 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   13144 
 vendor SEC
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: apport-bug i386 ubuntu xenial

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

Title:
  grub

Status in xorg package in Ubuntu:
  New

Bug description:
  I moved "grub" out of the boot file by accident. I though it was put
  back correct, but now at start up I see the computer booting up,
  instead of my nice Lubuntu screen. This seen ok. But what did I do?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  BootLog: /dev/sda1: clean, 472643/9641984 files, 6975586/38550528 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Apr  6 12:37:29 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [1028:01fe]
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01fe]
  InstallationDate: Installed on 2016-07-08 (272 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: Dell Inc. Latitude D830
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=48e542bb-c7f2-459f-b9a7-c0195cdd8a16 ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0HN341
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D830
  dmi.sys.vendor: Dell 

[Touch-packages] [Bug 1626469] Re: qdoc moved to qttools5-dev-tools, causes packages fail to build

[Launchpad Bug Tracker]

This bug was fixed in the package unity-action-api -
1.1.0+17.04.20170405-0ubuntu1

---
unity-action-api (1.1.0+17.04.20170405-0ubuntu1) zesty; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * Switch qtbase5-dev-tools built-dep to qttools5-dev-tools as qdoc has
moved. Stop using transitional dependencies. (LP: #1626469)

 -- Łukasz Zemczak   Wed, 05 Apr 2017
08:58:18 +

** Changed in: unity-action-api (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  qdoc moved to qttools5-dev-tools, causes packages fail to build

Status in unity-action-api package in Ubuntu:
  Fix Released

Bug description:
  $ qdoc
  qdoc: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qdoc': No such file 
or directory

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

[mir-ci-bot]

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.28.0

** Changed in: mir
   Status: In Progress => Fix Committed

-- 
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:
  In Progress
Status in Mir:
  Fix Committed
Status in MirAL:
  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 1680124] Re: desktop overrides not being used in Zesty VM

[Olivier Tilloy]

Just tested webbrowser-app natively on zesty in unity8, and overrides are being 
loaded correctly.
Having issues with virtualbox atm, but will try to confirm that the issue 
happens only in VMs.

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

Title:
  desktop overrides not being used in Zesty VM

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  running zesty release in virtualbox vm. When visting gmail.com, and
  others in override file it appears we are getting basic versions of
  the site and our overrides are not being presented.

  Here is browser log when launching:
  http://pastebin.ubuntu.com/24320670/

  Seems to work as expected on zesty natively, but not in vm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1680124/+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 1680541] [NEW] iputils-ping ping -I IPADDRESS not working in iputils-s20150815

[Christian]

Public bug reported:

command 
ping -I 10.10.10.254 10.10.10.1
ping: unknown iface 10.10.10.254

it works though when using -I Iface name (ex. eth2)


Seen on:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.10
DISTRIB_CODENAME=yakkety
DISTRIB_DESCRIPTION="Ubuntu 16.10"
NAME="Ubuntu"
VERSION="16.10 (Yakkety Yak)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.10"
VERSION_ID="16.10"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="http://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=yakkety
UBUNTU_CODENAME=yakkety
sqa@simubu16:~/devel/iputils$ uname -a
Linux simubu16 4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
sqa@simubu16:~/devel/iputils$ ping -V
ping utility, iputils-s20150815
sqa@simubu16:~/devel/iputils$

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

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

Title:
  iputils-ping ping -I IPADDRESS not working in iputils-s20150815

Status in iputils package in Ubuntu:
  New

Bug description:
  command 
  ping -I 10.10.10.254 10.10.10.1
  ping: unknown iface 10.10.10.254

  it works though when using -I Iface name (ex. eth2)

  
  Seen on:

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.10
  DISTRIB_CODENAME=yakkety
  DISTRIB_DESCRIPTION="Ubuntu 16.10"
  NAME="Ubuntu"
  VERSION="16.10 (Yakkety Yak)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.10"
  VERSION_ID="16.10"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="http://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=yakkety
  UBUNTU_CODENAME=yakkety
  sqa@simubu16:~/devel/iputils$ uname -a
  Linux simubu16 4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  sqa@simubu16:~/devel/iputils$ ping -V
  ping utility, iputils-s20150815
  sqa@simubu16:~/devel/iputils$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1680541/+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 1680496] Re: black screen when using 'GNOME Wayland' with lightdm on zesty

[Jamie Strandboge]

** Description changed:

  In an up to date Ubuntu 17.04 amd64 vm, if I:
  
  1. install ubuntu-gnome-desktop
  2. select lightdm as the default
  3. sudo service lightdm stop ; sudo service lightdm start
  4. login choosing 'GNOME Wayland'
  
  the screen goes black with a flashing cursor in the upper left. If I
- 'dpkg-reconfigure -plow lightdm' and choose 'gdm3', then stop light and
- start gdm3, then I can login to a wayland gnome3 desktop.
+ 'dpkg-reconfigure -plow lightdm' and choose 'gdm3', then stop lightdm
+ and start gdm3, then I can login to a wayland gnome3 desktop.

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

Title:
  black screen when using 'GNOME Wayland' with lightdm on zesty

Status in Ubuntu GNOME:
  New
Status in gnome-session package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  In an up to date Ubuntu 17.04 amd64 vm, if I:

  1. install ubuntu-gnome-desktop
  2. select lightdm as the default
  3. sudo service lightdm stop ; sudo service lightdm start
  4. login choosing 'GNOME Wayland'

  the screen goes black with a flashing cursor in the upper left. If I
  'dpkg-reconfigure -plow lightdm' and choose 'gdm3', then stop lightdm
  and start gdm3, then I can login to a wayland gnome3 desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1680496/+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 1679434] Re: Sync libarchive 3.2.2-1 (main) from Debian unstable (main)

[Jeremy Bicha]

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

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

Title:
  Sync libarchive 3.2.2-1 (main) from Debian unstable (main)

Status in libarchive package in Ubuntu:
  Fix Released

Bug description:
  Please sync libarchive 3.2.2-1 (main) from Debian unstable (main)

  Here's the diff. It's kinda big for the very small NEWS entry
  "Security release" :|

  
https://launchpadlibrarian.net/314278812/libarchive_3.2.1-6_3.2.2-1~ubuntu17.04.1.diff.gz

  Changelog entries since current zesty version 3.2.1-6:

  libarchive (3.2.2-1) unstable; urgency=medium

* Shorten long line in previous changelog entry to please lintian.
* debian/gbp.conf: add upstream-vcs-tag for import-orig
* New upstream release.
* Drop patches now part of upstream release.
* Stop shipping README for now

   -- Andreas Henriksson   Mon, 03 Apr 2017 17:17:02
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1679434/+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 1680428] Re: dbus-cpp FTBFS due to cmake gmock issues

[Łukasz Zemczak]

** Branch linked: lp:~sil2100/dbus-cpp/fix_ftbfs_gtest

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

Title:
  dbus-cpp FTBFS due to cmake gmock issues

Status in dbus-cpp package in Ubuntu:
  New

Bug description:
  During the test-rebuild, the package fails due to a known issue with
  gmock in CMake:

  CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
add_library cannot create target "gmock" because another target with the
same name already exists.  The existing target is a static library created
in source directory "/usr/src/googletest/googlemock".  See documentation
for policy CMP0002 for more details.
  Call Stack (most recent call first):
/usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
/usr/src/gmock/CMakeLists.txt:84 (cxx_library)

  
  CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
add_library cannot create target "gmock_main" because another target with
the same name already exists.  The existing target is a static library
created in source directory "/usr/src/googletest/googlemock".  See
documentation for policy CMP0002 for more details.
  Call Stack (most recent call first):
/usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
/usr/src/gmock/CMakeLists.txt:89 (cxx_library)

  
  CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
install TARGETS given target "gmock" which does not exist in this
directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1680428/+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 1670745] Re: ssh-keyscan : bad host signature when using port option

[Colin Watson]

Gautier, as well as Christian's comments:

(1) In your output, 6.7p1 is the version of the server you're connecting
to, not the client version.
(2) libssh is irrelevant here.
(3) 7.2p2-4 is not the fixed version.  See comment #9 on this bug.

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

Title:
  ssh-keyscan : bad host signature when using port option

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Yakkety:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]

   * using ssh-keyscan while using the port (-p) option of it will create 
 bad entries. They will contain the port and thereby be invalid for 
 latter use under the purpose of known_hosts.

   * Fix by backporting upstream fix.

  [Test Case]

   * Further evolving from the simplification Josh provided:
  Testcase:
  $ release=xenial
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-client
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-server
  $ lxc exec ${release}-test-ssh-port-scan-server -- sed -i 's/Port 22/Port 
/' /etc/ssh/sshd_config
  $ lxc exec ${release}-test-ssh-port-scan-server -- service ssh restart
  $ IP=$(lxc exec ${release}-test-ssh-port-scan-server -- hostname --ip-address)
  $ lxc exec ${release}-test-ssh-port-scan-client -- ssh-keyscan -H -p  
${IP}

  # See the port in the Hash still

  # Install the fixed version in *-client and see the port gone from the
  output

  [Regression Potential]

   * Change is limited to ssh-keyscan (not any touching other parts of openssh)
   * Fix is from upstream (no "Ubuntu special" change)
   * Fix is small and "only" changing string creation (11 lines touched)
   So overall the regression potential should be low.

  [Other Info]

   * n/a

  ---

  When I use the port option with ssh-keygen, the result is not
  compatible with ssh known_host file format.

  UBUNTU VERSION :
  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  BAD :
  
  :~/.ssh$ cat /etc/issue
  Ubuntu 16.04.1 LTS \n \l
  :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...]
  debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
  # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we see the port number because it is not hashed !

  GOOD :
  
  rm ~/.ssh/known_hosts
  :~/$ ssh -p [...port...] [...snip...]
  The authenticity of host '[[...snip...]]:[...port...] 
([[...snip...]]:[...port...])' can't be established.
  ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 
'[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list 
of known hosts.
  [...snip...]@[...snip...]'s password:

  :~/$ !cat
  cat ~/.ssh/known_hosts
  |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
  |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we cannot see the port number as it is well hashed !

  REMARKS :
  ==
  Same problem has already reported here (on macOS): 
https://github.com/ansible/ansible-modules-extras/issues/2651

  It seems that ssh-keyscan version and open-ssh version differs :
  dpkg -l | grep openssh :: ii  openssh-client  1:7.2p2-4ubuntu2.1  [...]
  ssh-keyscan -v [...] :: debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat 
OpenSSH* compat 0x0400

  It is very annoying because I am trying to manage hand installed VMs
  with Ansible. For that I want to automate SSH host keys storing in
  known_hosts database. And because of this bug I can't. (ansible 

[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

[Louis Bouchard]

Targetting Zesty as the fix will come after release so as a SRU.

** Also affects: unattended-upgrades (Ubuntu Zesty)
   Importance: High
 Assignee: Louis Bouchard (louis-bouchard)
   Status: In Progress

-- 
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 source package in Zesty:
  In Progress
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 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild

[Robert Bruce Park]

Yeah, which is tiny compared to the rdeps for python3-gi, which is what
replaces this package. Anything that depends on pygobject-2 is going to
be abandonware stuck on python2 and gtk2.

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

Title:
  pygobject-2 FTBFS on most arches during zesty test rebuild

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
   pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on
  most (not amd64) arches during a test rebuild of zesty. The build log
  can be found here:

  https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386
  .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz

  The failure seems to be due to the following:

   debian/rules build-arch
  make: *** No rule to make target 'build-arch'.  Stop.
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1679835/+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 1680504] [NEW] package libopencv-objdetect2.4v5 (not installed) failed to install/upgrade: no package named 'libopencv-objdetect2.4v5' is installed, cannot configure

[Seth]

Public bug reported:

Upon upgrade from 14.04 to 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libopencv-objdetect2.4v5 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu Apr  6 08:46:26 2017
ErrorMessage: no package named 'libopencv-objdetect2.4v5' is installed, cannot 
configure
InstallationDate: Installed on 2015-01-10 (817 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: opencv
Title: package libopencv-objdetect2.4v5 (not installed) failed to 
install/upgrade: no package named 'libopencv-objdetect2.4v5' is installed, 
cannot configure
UpgradeStatus: Upgraded to xenial on 2017-04-06 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libopencv-objdetect2.4v5 (not installed) failed to
  install/upgrade: no package named 'libopencv-objdetect2.4v5' is
  installed, cannot configure

Status in opencv package in Ubuntu:
  New

Bug description:
  Upon upgrade from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-objdetect2.4v5 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Apr  6 08:46:26 2017
  ErrorMessage: no package named 'libopencv-objdetect2.4v5' is installed, 
cannot configure
  InstallationDate: Installed on 2015-01-10 (817 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: opencv
  Title: package libopencv-objdetect2.4v5 (not installed) failed to 
install/upgrade: no package named 'libopencv-objdetect2.4v5' is installed, 
cannot configure
  UpgradeStatus: Upgraded to xenial on 2017-04-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1680504/+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 1680496] Re: black screen when using 'GNOME Wayland' with lightdm on zesty

[Jeremy Bicha]

gdm3 runs using Wayland by default. If it can't run Wayland, then it
hides the GNOME on Wayland session. That implies to me that it is
required for the login greeter to run Wayland?

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

Title:
  black screen when using 'GNOME Wayland' with lightdm on zesty

Status in Ubuntu GNOME:
  New
Status in gnome-session package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  In an up to date Ubuntu 17.04 amd64 vm, if I:

  1. install ubuntu-gnome-desktop
  2. select lightdm as the default
  3. sudo service lightdm stop ; sudo service lightdm start
  4. login choosing 'GNOME Wayland'

  the screen goes black with a flashing cursor in the upper left. If I
  'dpkg-reconfigure -plow lightdm' and choose 'gdm3', then stop light
  and start gdm3, then I can login to a wayland gnome3 desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1680496/+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 1660053] Re: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2

[Launchpad Bug Tracker]

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

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

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

Title:
  package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 2

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  A marker instead of cursor comes on my screen now and then.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportLog:
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: called for pid 10831, 
signal 11, core limit 0
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable: 
/usr/lib/firefox/plugin-container (command line 
"/usr/lib/firefox/plugin-container 
/usr/lib/flashplugin-installer/libflashplayer.so -greomni 
/usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir 
/usr/lib/firefox/browser 2196 true plugin")
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable version is 
blacklisted, ignoring
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashReports:
   644:0:116:0:2017-01-26 21:26:16.589169125 +0530:2017-01-26 
21:26:16.589169125 +0530:/var/crash/bluefish-data.0.upload
   640:0:116:204816:2017-01-26 21:26:15.569168806 +0530:2017-01-26 
21:26:16.569168806 +0530:/var/crash/bluefish-data.0.crash
   600:0:116:159472:2017-01-28 22:32:36.371843338 +0530:2017-01-28 
22:32:37.371843338 +0530:/var/crash/apport.0.crash
   600:109:116:0:2017-01-27 03:37:06.746315169 +0530:2017-01-27 
03:37:06.746315169 +0530:/var/crash/bluefish-data.0.uploaded
  Date: Sat Jan 28 22:32:37 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 2
  InstallationDate: Installed on 2016-12-04 (54 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1660053/+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 1680496] Re: black screen when using 'GNOME Wayland' with lightdm on zesty

[Jeremy Bicha]

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

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

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

Title:
  black screen when using 'GNOME Wayland' with lightdm on zesty

Status in Ubuntu GNOME:
  New
Status in gnome-session package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  In an up to date Ubuntu 17.04 amd64 vm, if I:

  1. install ubuntu-gnome-desktop
  2. select lightdm as the default
  3. sudo service lightdm stop ; sudo service lightdm start
  4. login choosing 'GNOME Wayland'

  the screen goes black with a flashing cursor in the upper left. If I
  'dpkg-reconfigure -plow lightdm' and choose 'gdm3', then stop light
  and start gdm3, then I can login to a wayland gnome3 desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1680496/+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 1670745] Re: ssh-keyscan : bad host signature when using port option

[ChristianEhrhardt]

Also after enabling proposed you can install "just the package and its
dependencies" by instead of running "apt upgrade" just running in this
case "apt install openssh-client".


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

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

Title:
  ssh-keyscan : bad host signature when using port option

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Yakkety:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]

   * using ssh-keyscan while using the port (-p) option of it will create 
 bad entries. They will contain the port and thereby be invalid for 
 latter use under the purpose of known_hosts.

   * Fix by backporting upstream fix.

  [Test Case]

   * Further evolving from the simplification Josh provided:
  Testcase:
  $ release=xenial
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-client
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-server
  $ lxc exec ${release}-test-ssh-port-scan-server -- sed -i 's/Port 22/Port 
/' /etc/ssh/sshd_config
  $ lxc exec ${release}-test-ssh-port-scan-server -- service ssh restart
  $ IP=$(lxc exec ${release}-test-ssh-port-scan-server -- hostname --ip-address)
  $ lxc exec ${release}-test-ssh-port-scan-client -- ssh-keyscan -H -p  
${IP}

  # See the port in the Hash still

  # Install the fixed version in *-client and see the port gone from the
  output

  [Regression Potential]

   * Change is limited to ssh-keyscan (not any touching other parts of openssh)
   * Fix is from upstream (no "Ubuntu special" change)
   * Fix is small and "only" changing string creation (11 lines touched)
   So overall the regression potential should be low.

  [Other Info]

   * n/a

  ---

  When I use the port option with ssh-keygen, the result is not
  compatible with ssh known_host file format.

  UBUNTU VERSION :
  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  BAD :
  
  :~/.ssh$ cat /etc/issue
  Ubuntu 16.04.1 LTS \n \l
  :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...]
  debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
  # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we see the port number because it is not hashed !

  GOOD :
  
  rm ~/.ssh/known_hosts
  :~/$ ssh -p [...port...] [...snip...]
  The authenticity of host '[[...snip...]]:[...port...] 
([[...snip...]]:[...port...])' can't be established.
  ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 
'[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list 
of known hosts.
  [...snip...]@[...snip...]'s password:

  :~/$ !cat
  cat ~/.ssh/known_hosts
  |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
  |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we cannot see the port number as it is well hashed !

  REMARKS :
  ==
  Same problem has already reported here (on macOS): 
https://github.com/ansible/ansible-modules-extras/issues/2651

  It seems that ssh-keyscan version and open-ssh version differs :
  dpkg -l | grep openssh :: ii  openssh-client  1:7.2p2-4ubuntu2.1  [...]
  ssh-keyscan -v [...] :: debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat 
OpenSSH* compat 0x0400

  It is very annoying because I am trying to manage hand installed VMs
  with Ansible. For that I want to automate SSH host keys storing in
  known_hosts database. And because of this bug I can't. 

[Touch-packages] [Bug 1668093] Re: ssh-keygen -H corrupts already hashed entries

[ChristianEhrhardt]

Prior to the update I had a diff when rehashing like:
$ ssh-keyscan 10.245.71.133 > ~/.ssh/known_hosts; for i in $(seq 1 20); do 
ssh-keygen -H; diff -Naur ~/.ssh/known_hosts.old ~/.ssh/known_hosts; done

Removing the known_hosts file and upgrading to proposed version.

After the update I see one diff when initially adding the entries, but
then now bad rehashing anymore.

Verified Xenial and Yakkety.

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

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

Title:
  ssh-keygen -H corrupts already hashed entries

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Yakkety:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]

   * re-execution of ssh-keygen -H can clobber known-hosts
   * Due to that users might get spurious re-warnings of known systems. For 
Automation it might be worse as it might stop to work when re-executed.

   * This is a regression from Trusty (working) to Xenial (fail) upgrade
  due to an upstream bug in the versions we merged.

   * This is a backport of the upstream fix

  [Test Case]

   * Pick a Host IP to scan keys from that you can reach and replies with SSH, 
then run the following trivial loop:
$ ssh-keyscan ${IP} > ~/.ssh/known_hosts; for i in $(seq 1 20); do 
ssh-keygen -H; diff -Naur ~/.ssh/known_hosts.old ~/.ssh/known_hosts; done

   * Expected: no diff reported, since already hashed entries should be left 
as-is
   * Without fix: - diff in the hashes

  [Regression Potential]

   * The fix is upstream and soon in Debian as well, so we are not
  custom diverting here.

   * The risk should be minimal as this only changes ssh-keygen so
  despite openssh being really critical this doesn't affect ssh itself
  at all.

  [Other Info]
   
   * n/a

  
  ---

  xenial @ 1:7.2p2-4ubuntu2.1 on amd64 has this bug. trusty @
  1:6.6p1-2ubuntu2.8 on amd64 does not have this bug. I have not tested
  any other ssh versions.

  The following should reproduce the issue:

  #ssh-keyscan  > ~/.ssh/known_hosts
  # ssh root@X
  Permission denied (publickey).
  # ssh-keygen -H
  /root/.ssh/known_hosts updated.
  Original contents retained as /root/.ssh/known_hosts.old
  WARNING: /root/.ssh/known_hosts.old contains unhashed entries
  Delete this file to ensure privacy of hostnames
  # ssh root@XX
  Permission denied (publickey).
  # ssh-keygen -H
  /root/.ssh/known_hosts updated.
  Original contents retained as /root/.ssh/known_hosts.old
  WARNING: /root/.ssh/known_hosts.old contains unhashed entries
  Delete this file to ensure privacy of hostnames
  # ssh root@X
  The authenticity of host 'XX' can't be established.
  RSA key fingerprint is XX.
  Are you sure you want to continue connecting (yes/no)?

  # diff known_hosts.old known_hosts
  1c1
  < |1|BoAbRpUE3F5AzyprJcbjdepeDh8=|x/1AcaLxh45FlShmVQnlgx2qjxY= X
  ---
  > |1|nTPsoLxCugQyZi3pqOa2pc/cX64=|bUH5qwZlZPp8msMGHdLtslf3Huk= X

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1668093/+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 1670745] Re: ssh-keyscan : bad host signature when using port option

[ChristianEhrhardt]

Prior to updating when scanning from a target I still have ports in the
output:

ssh-keyscan -H -p  10.0.4.153
# 10.0.4.153: SSH-2.0-OpenSSH_7.4p1 Ubuntu-10
[|1|nTWrNxylhhwkyicxuuS/5p2Tlts=|ziw5AkY9sg/oRSpkYIuxswDgIf8=]: ssh-ed25519 
C3NzaC1lZDI1NTE5ID4/W/XQvgco3vziMDLT5PyHwuqY9pupyB2NNvpF+9bR

Upgrading to proposed version.

Afterwards the entry looks good like:
# 10.0.4.153: SSH-2.0-OpenSSH_7.4p1 Ubuntu-10
|1|A5Uker2NsxV0OgNrMNT+aaUDrJM=|bsWW57Lhko5h+t6BtjU9u/wkAkw= ssh-ed25519 
C3NzaC1lZDI1NTE5ID4/W/XQvgco3vziMDLT5PyHwuqY9pupyB2NNvpF+9bR

Verified on Xenial and Yakkety.


@Gautier - please go on with your own verification and in the worst case if you 
can prove it not working change it back to verification-needed or even -failed. 
I'm away the next few days, but I'm sure cjwatson or powerj who are on this bug 
can help you in case it is needed.

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

Title:
  ssh-keyscan : bad host signature when using port option

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Yakkety:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]

   * using ssh-keyscan while using the port (-p) option of it will create 
 bad entries. They will contain the port and thereby be invalid for 
 latter use under the purpose of known_hosts.

   * Fix by backporting upstream fix.

  [Test Case]

   * Further evolving from the simplification Josh provided:
  Testcase:
  $ release=xenial
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-client
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-server
  $ lxc exec ${release}-test-ssh-port-scan-server -- sed -i 's/Port 22/Port 
/' /etc/ssh/sshd_config
  $ lxc exec ${release}-test-ssh-port-scan-server -- service ssh restart
  $ IP=$(lxc exec ${release}-test-ssh-port-scan-server -- hostname --ip-address)
  $ lxc exec ${release}-test-ssh-port-scan-client -- ssh-keyscan -H -p  
${IP}

  # See the port in the Hash still

  # Install the fixed version in *-client and see the port gone from the
  output

  [Regression Potential]

   * Change is limited to ssh-keyscan (not any touching other parts of openssh)
   * Fix is from upstream (no "Ubuntu special" change)
   * Fix is small and "only" changing string creation (11 lines touched)
   So overall the regression potential should be low.

  [Other Info]

   * n/a

  ---

  When I use the port option with ssh-keygen, the result is not
  compatible with ssh known_host file format.

  UBUNTU VERSION :
  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  BAD :
  
  :~/.ssh$ cat /etc/issue
  Ubuntu 16.04.1 LTS \n \l
  :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...]
  debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
  # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we see the port number because it is not hashed !

  GOOD :
  
  rm ~/.ssh/known_hosts
  :~/$ ssh -p [...port...] [...snip...]
  The authenticity of host '[[...snip...]]:[...port...] 
([[...snip...]]:[...port...])' can't be established.
  ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 
'[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list 
of known hosts.
  [...snip...]@[...snip...]'s password:

  :~/$ !cat
  cat ~/.ssh/known_hosts
  |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
  |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we cannot 

[Touch-packages] [Bug 1670745] Re: ssh-keyscan : bad host signature when using port option

[ChristianEhrhardt]

@Gautier - thanks for trying to verify - I'm currently doing the same.
The known_hosts file you have still has the broken content.
The fix cannot change your existing known_hosts file to be good.
You'd have to remove the broken lines and add them again with ssh-keyscan.
But the fix in keyscan is in a way that now it should create valid entries that 
work.

So when you rescan your target afterwards and appand that to your known
hosts it will be good then.

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

Title:
  ssh-keyscan : bad host signature when using port option

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Yakkety:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]

   * using ssh-keyscan while using the port (-p) option of it will create 
 bad entries. They will contain the port and thereby be invalid for 
 latter use under the purpose of known_hosts.

   * Fix by backporting upstream fix.

  [Test Case]

   * Further evolving from the simplification Josh provided:
  Testcase:
  $ release=xenial
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-client
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-server
  $ lxc exec ${release}-test-ssh-port-scan-server -- sed -i 's/Port 22/Port 
/' /etc/ssh/sshd_config
  $ lxc exec ${release}-test-ssh-port-scan-server -- service ssh restart
  $ IP=$(lxc exec ${release}-test-ssh-port-scan-server -- hostname --ip-address)
  $ lxc exec ${release}-test-ssh-port-scan-client -- ssh-keyscan -H -p  
${IP}

  # See the port in the Hash still

  # Install the fixed version in *-client and see the port gone from the
  output

  [Regression Potential]

   * Change is limited to ssh-keyscan (not any touching other parts of openssh)
   * Fix is from upstream (no "Ubuntu special" change)
   * Fix is small and "only" changing string creation (11 lines touched)
   So overall the regression potential should be low.

  [Other Info]

   * n/a

  ---

  When I use the port option with ssh-keygen, the result is not
  compatible with ssh known_host file format.

  UBUNTU VERSION :
  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  BAD :
  
  :~/.ssh$ cat /etc/issue
  Ubuntu 16.04.1 LTS \n \l
  :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...]
  debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
  # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we see the port number because it is not hashed !

  GOOD :
  
  rm ~/.ssh/known_hosts
  :~/$ ssh -p [...port...] [...snip...]
  The authenticity of host '[[...snip...]]:[...port...] 
([[...snip...]]:[...port...])' can't be established.
  ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 
'[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list 
of known hosts.
  [...snip...]@[...snip...]'s password:

  :~/$ !cat
  cat ~/.ssh/known_hosts
  |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
  |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we cannot see the port number as it is well hashed !

  REMARKS :
  ==
  Same problem has already reported here (on macOS): 
https://github.com/ansible/ansible-modules-extras/issues/2651

  It seems that ssh-keyscan version and open-ssh version differs :
  dpkg -l | grep openssh :: ii  openssh-client  1:7.2p2-4ubuntu2.1  [...]
  ssh-keyscan -v [...] :: debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat 
OpenSSH* compat 

[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist

[Michael Terry]

I agree with Brian that this might not be worth fixing, but at the same
time, there's 4 more years of 16.04 to go.

I've uploaded both the xenial and yakkety patches (I see that you had to
fix yakkety too so that the versions upgraded nicely) to proposed.
Let's see what the SRU team thinks.

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

Title:
  The tc man page references tc-index man page but tc-index man page
  does not exist

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  In Progress
Status in iproute2 source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * The man pages for tc make reference to a non-existent tc-index man
  page. Purely a typo that should have been tc-tcindex.

   *  Purely a documentation fix, but nice to fix for an LTS release
  that has many years left to it.

  
  [Test Case]

   * To see this issue, fire up a 16,04 image (I did so via lxd) and
  type:

 root@xi386# man tc | grep tc-index
   Filter packets based on traffic control index. See 
tc-index(8).

  , HOWEVER:

 root@xi386:~# man tc-index
 No manual entry for tc-index

  
  * on a fixed system you should only see refereces to tc-tcindex, not tc-index:

 root@x1:~# man tc | grep tc-index
 root@x1:~# man tc | grep tc-tcindex
   Filter packets based on traffic control index. See 
tc-tcindex(8).
red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8), 
tc-tcindex(8), tc-u32(8),


  
  [Regression Potential] 

   * This is only a change to man pages, so any regression would be non-
  functional, but this fix is trivial to fix and verify, and the fix is
  exactly from the upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+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 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild

[Barry Warsaw]

% reverse-depends src:pygobject-2
Reverse-Recommends
==
* python-gtk2-doc   (for python-gobject-2)
* winswitch (for python-gobject-2)

Reverse-Depends
===
* coccinelle(for python-gobject-2)
* comitup   (for python-gobject-2)
* hamster-applet(for python-gobject-2)
* mate-tweak(for python-gobject-2)
* python-gconf  (for python-gobject-2)
* python-gnome2 (for python-gobject-2)
* python-gnome2-dev (for python-gobject-2-dev)
* python-gobject(for python-gobject-2)
* python-gobject-dbg(for python-gobject-2-dbg)
* python-gobject-dev(for python-gobject-2-dev)
* python-gtk2   (for python-gobject-2)
* python-gtk2-dbg   (for python-gobject-2-dbg)
* python-gtk2-dev   (for python-gobject-2-dev)
* python-gtksourceview2 (for python-gobject-2)
* python-indicate   (for python-gobject-2)
* python-liblarch   (for python-gobject-2)
* python-zeitgeist  (for python-gobject-2)
* sat-xmpp-core (for python-gobject-2)
* zenmap(for python-gobject-2)


% reverse-depends -b src:pygobject-2
Reverse-Build-Depends
=
* gnome-python  (for python-gobject-2-dev)
* pygtk (for python-gobject-2-dbg)
* pygtk (for python-gobject-2-dev)
* pygtksourceview   (for python-gobject-2-dev)
* winswitch (for python-gobject-2)

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

Title:
  pygobject-2 FTBFS on most arches during zesty test rebuild

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
   pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on
  most (not amd64) arches during a test rebuild of zesty. The build log
  can be found here:

  https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386
  .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz

  The failure seems to be due to the following:

   debian/rules build-arch
  make: *** No rule to make target 'build-arch'.  Stop.
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1679835/+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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Bug Watch Updater]

** Changed in: dbus
   Status: Unknown => Fix Released

** Changed in: dbus
   Importance: Unknown => Medium

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Fix Released
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Fix Committed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

-- 
Mailing list: 

[Touch-packages] [Bug 1680453] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

[Apport retracing service]

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

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 #1629638, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1680453/+attachment/4856203/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1680453/+attachment/4856206/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1680453/+attachment/4856213/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1680453/+attachment/4856215/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1680453/+attachment/4856216/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680453/+attachment/4856217/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1680453/+attachment/4856218/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1629638

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  auto generated. Ubuntu is installed on sdd.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: udev 232-19
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Thu Apr  6 14:48:31 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305FA
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-15-generic.efi.signed 
root=UUID=5f7f9ccf-2282-415c-a8f0-c8ec13104b13 ro rootflags=subvol=@ noprompt
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305FA.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.207:bd02/05/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305FA
  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/systemd/+bug/1680453/+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

[David Ford]

use this in /etc/modprobe.d/alsa-base.conf
`options snd-hda-intel model=laptop-dmic,headset-mic`
and the internal mic and headset mic will work.

-- 
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 1626469] Re: qdoc moved to qttools5-dev-tools, causes packages fail to build

[Łukasz Zemczak]

Released as part of https://bileto.ubuntu.com/#/ticket/2696 - waiting to
get approved from UNAPPROVED.

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

Title:
  qdoc moved to qttools5-dev-tools, causes packages fail to build

Status in unity-action-api package in Ubuntu:
  In Progress

Bug description:
  $ qdoc
  qdoc: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qdoc': No such file 
or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-action-api/+bug/1626469/+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 1670745] Re: ssh-keyscan : bad host signature when using port option

[Gautier HUSSON]

First : thank you everybody for all your work !

At now I am not able to see the difference. But I think I may not doing the 
right thing in order to test :
wget "http://launchpadlibrarian.net/254059000/openssh-client_7.2p2-4_amd64.deb;
dpkg -i openssh-client_7.2p2-4_amd64.deb
ssh-keyscan -v -t dsa -H -p 22000 -T 5 test.[snip]
debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
# test.liberasys.com:22000 SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
debug1: Enabling compatibility mode for protocol 2.0
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha...@libssh.org
debug1: kex: host key algorithm: ssh-dss
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
[|1|xkG3IqIo2wV4LVdHUIdFxpV+cN0=|qPnIs826Ny8lK2r9MYnN94rt+3w=]:22000 ssh-dss 
B3NzaC1kc3MAAACBAOWWBwm[snip]

==> OpenSSH_6.7p1 is not the right version... although :

ssh -V
OpenSSH_7.2p2 Ubuntu-4, OpenSSL 1.0.2g  1 Mar 2016

root@ghu-thinkpad:~# dpkg -l | grep ssh
ii  libssh-4:amd64  0.6.3-4.3   
  amd64tiny C SSH library (OpenSSL flavor)
ii  libssh-gcrypt-4:amd64   0.6.3-4.3   
  amd64tiny C SSH library (gcrypt flavor)
ii  libssh2-1:amd64 1.5.0-2ubuntu0.1
  amd64SSH2 client-side library
ii  openssh-client  1:7.2p2-4   
  amd64secure shell (SSH) client, for secure access to 
remote machines
ii  python-paramiko 1.16.0-1
  all  Make ssh v2 connections with Python (Python 2)
ii  sshpass 1.05-1  
  amd64Non-interactive ssh password authentication

It may be due to the libssh that I have not updated ?
RQ : I preafer to install updated packages directly rather than playing with 
dpgk database (I may be wrong on this point).

Thank you for your help.
B.R.
Gautier.

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

Title:
  ssh-keyscan : bad host signature when using port option

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Yakkety:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]

   * using ssh-keyscan while using the port (-p) option of it will create 
 bad entries. They will contain the port and thereby be invalid for 
 latter use under the purpose of known_hosts.

   * Fix by backporting upstream fix.

  [Test Case]

   * Further evolving from the simplification Josh provided:
  Testcase:
  $ release=xenial
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-client
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-server
  $ lxc exec ${release}-test-ssh-port-scan-server -- sed -i 's/Port 22/Port 
/' /etc/ssh/sshd_config
  $ lxc exec ${release}-test-ssh-port-scan-server -- service ssh restart
  $ IP=$(lxc exec ${release}-test-ssh-port-scan-server -- hostname --ip-address)
  $ lxc exec ${release}-test-ssh-port-scan-client -- ssh-keyscan -H -p  
${IP}

  # See the port in the Hash still

  # Install the fixed version in *-client and see the port gone from the
  output

  [Regression Potential]

   * Change is limited to ssh-keyscan (not any touching other parts of openssh)
   * Fix is from upstream (no "Ubuntu special" change)
   * Fix is small and "only" changing string creation (11 lines touched)
   So overall the regression potential should be low.

  [Other Info]

   * n/a

  ---

  When I use the port option with ssh-keygen, the result is not
  compatible with ssh known_host file format.

  UBUNTU VERSION :
  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  BAD :
  
  :~/.ssh$ cat /etc/issue
  Ubuntu 16.04.1 LTS \n \l
  :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...]
  debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
  # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: 

[Touch-packages] [Bug 1679822] Re: zeromq3 FTBFS with zesty test rebuild

[Łukasz Zemczak]

As I remembered - I asked doko to re-run the failed build and now it
passed. The test suite would need some love to be made more reliable,
but that's a different issue. Marking as Invalid.

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

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

Title:
  zeromq3 FTBFS with zesty test rebuild

Status in zeromq3 package in Ubuntu:
  Invalid

Bug description:
  zeromq3 version 4.2.1-2ubuntu1 failed to build from source on armhf
  during a recent test rebuild for zesty. The build log can be found
  here:

  https://launchpadlibrarian.net/312257088/buildlog_ubuntu-zesty-
  armhf.zeromq3_4.2.1-2ubuntu1_BUILDING.txt.gz

  There seems to have been 1 test failure:

  FAIL: tests/test_use_fd_tcp
  ===

  lt-test_use_fd_tcp: tests/test_use_fd_tcp.cpp:59: void 
pre_allocate_sock(void*, const char*, const char*): Assertion `rc == 0' failed.
  FAIL tests/test_use_fd_tcp (exit status: 134)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1679822/+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 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule

[ChristianEhrhardt]

Also even when setting the profile to aa-complain I see:
[14406.210381] audit: type=1400 audit(1491482071.335:67): apparmor="ALLOWED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=7674 comm="libvirtd" 
rlimit=memlock value=2164260864

So far so good, but still the value is not raised.
As if the action never happened.

So on an ALLOWED setrlimit to pid 7674 the value afterwards is not the value 
set in the call.
Hrm - puzzled ...

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1679704/+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 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule

[ChristianEhrhardt]

Ok, by the recent insight this bug IS blocking the final resolution of bug 
1678322.
I'll work on the other bits of that bug and we will see how this one here turns 
out.

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1679704/+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 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule

[ChristianEhrhardt]

Very interesting disabling the profile completely via
 $ sudo aa-disable /usr/sbin/libvirtd

makes it working, so apparmor is involved in some way.
I'm still puzzled that the ALLOWED makes it a no-op still.

Anyway waiting for your reply - thanks a lot already jjohansen for the
IRC discussions!

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1679704/+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 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule

[ChristianEhrhardt]

For documentation purpose here an update.
I found that the last thing libvirt calls is "prlimit"

In glibc that is implemented as syscall prlimit64.
That in turn is on 64 bit:
#define __NR_prlimit64 302

According to the doc of prlimit it needs a capability:
To set or get the resources of a process other than itself, the caller must have
"the CAP_SYS_RESOURCE capability, or the real, effective, and saved set user 
IDs of the target  process  must  match the  real  user  ID of the caller and 
the real, effective, and saved set group IDs of the target process must match 
the real group ID of the caller."

But the profile already holds that with a suspicious comment above it matching 
my testcase:
  # Needed for vfio
  capability sys_resource,

Did something get more strict, maybe a mismatch on
prlimit/setrlimit/syscall mapping here?

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

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