[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

[Timo Jyrinki]

Now in zesty-proposed.

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in qtbase-opensource-src source package in Xenial:
  Confirmed
Status in qtbase-opensource-src source package in Yakkety:
  Confirmed

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

-- 
Mailing list: https://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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[rusbunker]

Дмитрий добрый день! Я правильно понимаю что если выполню инструкции
прописанные в этом сообщении, я получу желаемое? А именно устновлю принтер.


31.01.2017 13:33, Dimitri John Ledkov пишет:
> ** Changed in: cups (Ubuntu Zesty)
> Milestone: ubuntu-17.01 => ubuntu-17.02
>

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Triaged
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Triaged
Status in cups source package in Zesty:
  Triaged

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db 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: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1659002] Re: package python-apt 1.1.0~beta1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: python-apt (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python-apt 1.1.0~beta1build1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-apt 1.1.0~beta1build1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptOrdering:
   python-apt: Install
   python-sip: Configure
   python-qt4: Configure
   python-apt: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jan 24 16:45:23 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-23 (61 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: python-apt
  Title: package python-apt 1.1.0~beta1build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1659002/+subscriptions

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

[Touch-packages] [Bug 1660762] sosreport

[bugproxy]

--- Comment (attachment only) From vnarasim...@in.ibm.com 2017-02-01 00:47 
EDT---


** Attachment added: "sosreport"
   
https://bugs.launchpad.net/bugs/1660762/+attachment/4811613/+files/sosreport-NarasimhanV.LP1660762-20170131234159.tar.xz

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

Title:
  [Regression] Interface configuration not restored after driver
  unbind/bind (generic)

Status in ifupdown package in Ubuntu:
  Triaged

Bug description:
  ---Problem Description---
  Interface configuration not restored after driver unbind/bind
   

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4163  mtu 1500
  inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
  inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 13  bytes 1046 (1.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ltciofvtr-s824-lp8:~# cat /etc/network/interfaces
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto ibmveth2
  iface ibmveth2 inet static
address 9.47.68.120
netmask 255.255.240.0
network 9.47.64.0
broadcast 9.47.79.255
gateway 9.47.79.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 9.12.18.2
dns-search pok.stglabs.ibm.com

  auto enP28p96s0f0
  iface enP28p96s0f0 inet static
 address 10.10.10.11
 netmask 255.255.255.0

  root@ltciofvtr-s824-lp8:~# ethtool -i enP28p96s0f0
  driver: be2net
  version: 11.1.0.0
  firmware-version: 10.2.252.1913
  expansion-rom-version: 
  bus-info: 001c:60:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no
  supports-priv-flags: yes

  root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
  /sys/bus/pci/drivers/be2net/unbind

  root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 
  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  remove_id  
uevent  unbind

  root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
  /sys/bus/pci/drivers/be2net/bind

  root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net
  001c:60:00.0  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  
remove_id  uevent  unbind

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4098  mtu 1500
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0
  ifup: interface enP28p96s0f0 already configured

  root@ltciofvtr-s824-lp8:~# ifdown enP28p96s0f0
  RTNETLINK answers: Cannot assign requested address

  root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4163  mtu 1500
  inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
  inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 16  bytes 1344 (1.3 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

   
  ---uname output---
  Linux ltciofvtr-s824-lp8 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 12:52:39 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8286-42A LPAR 

  ---Steps to Reproduce---
   # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind

  # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind
   
  == Comment - Vaishnavi Bhat
  Hi,

  To bind a device to a driver, the device must first not be controlled by any 
other driver. Can you check for 'driver' in the below before you bind ?
   $ tree /sys//bus/pci/devices/001c:60:00.0 

  Thank you.

  == Comment - Murilo Fossa Vicentini
  Just adding some information, this is not a driver specific issue, this was 
also seen with tg3 and i40e adapters . This behavior is a regression when 
compared to Ubuntu 16.04 where the interfaces where properly reconfigured upon 
bind with the information set in /etc/network/interfaces

To manage notifications about this bug go to:

[Touch-packages] [Bug 1655584] Re: systemd-udevd busyloops when nvidia kernel module fails to load

[Ross Boylan]

I was able to stop the loop by blacklisting the nvidia modules and restarting 
the system.
I added /etc/modprobe.d/nvidia-kill.conf, deliberately chose to appear after 
the existing nvivida conf files in the same directory (not sure if that's 
essential):

blacklist nvidia_367
blacklist nvidia_367_uvm
blacklist nvidia_367_modeset
blacklist nvidia_367_drm

alias nvidia off
alias nvidia-uvm off
alias nvidia-modeset off
alias nvidia-drm off

This was all guesswork; I don't know how much is essential.

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

Title:
  systemd-udevd busyloops when nvidia kernel module fails to load

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a machine where nvidia-367 is installed, but the driver won't attach (due 
to
  the nvidia card being older and requiring legacy drivers), systemd-udevd
  repeatedly attempts to load it anyway, causing high CPU and memory usage. I
  observed the systemd-udevd process at 98% CPU usage and 2.5G RSS reported by
  top(1); restarting the service reduces resource usage momentarily, but it
  appears to be climbing back up (I suspect the number of events is growing).

  Workaround is of course installing the correct driver package, but udevd 
really
  ought not behave like this if something fails to load.

  Some journal entries for systemd-udevd.service:

  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' 
failed with exit code 9.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' 
failed with exit code 9.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.

  dmesg shows repeated failures for loading the nvidia module:

  [1675406.587926] NVRM: The NVIDIA GeForce 9300 GE GPU installed in this 
system is
 NVRM:  supported through the NVIDIA 340.xx Legacy drivers. 
Please
 NVRM:  visit http://www.nvidia.com/object/unix.html for 
more
 NVRM:  information.  The 367.57 NVIDIA driver will ignore
 NVRM:  this GPU.  Continuing probe...
  [1675406.587936] NVRM: No NVIDIA graphics adapter found!
  [1675406.588078] NVRM: NVIDIA init module failed!

  Release information:

  # lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  # apt policy systemd udev
  systemd:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu13
Version table:
   *** 229-4ubuntu13 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial/main amd64 Packages
  udev:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu13
Version table:
   *** 229-4ubuntu13 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial/main amd64 Packages

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

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

[Touch-packages] [Bug 1660232] Re: Inconsistent design: Six different font sizes used on Unity8 desktop

[Launchpad Bug Tracker]

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

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

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

Title:
  Inconsistent design: Six different font sizes used on Unity8 desktop

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

Bug description:
  Inconsistent design: There are six different font sizes used on Unity8
  desktop if you look at the attached screenshot.

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

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Dan Dascalescu]

"after resume, only a couple of wifi networks will be listed at most,
and never the one I use" - that's exactly the symptom I see after
resuming my DELL E7450. Also, the Wi-Fi icon is replaced with an "arrow
up arrow down" one. `sudo service network-manager restart` reconnects
most of the time, but sometimes that wrong icons stays on.

I've just modified `/lib/systemd/system-sleep/wpasupplicant` as
described in #64, and will be testing for the next several days. Is a
reboot necessary for that modification to take effect?

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

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

[Touch-packages] [Bug 1643413] Re: ubuntu-desktop shouldn't depend on checkbox-gui as it's a transitional package

[Mathew Hodson]

ubuntu-meta (1.377) zesty; urgency=medium

  * Refreshed dependencies
  * Added checkbox-converged to desktop
  * Removed checkbox-gui from desktop

 -- Robert Ancell   Wed, 01 Feb 2017
14:04:27 +1300

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  ubuntu-desktop shouldn't depend on checkbox-gui as it's a transitional
  package

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-desktop shouldn't depend on checkbox-gui. checkbox-gui is a
  transitional package that can be safely removed once no package
  depends on it.

  You should be able to run 'apt-get purge checkbox-gui' without
  removing ubuntu-desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-desktop 1.361
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 20 22:34:05 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-11-01 (1480 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to xenial on 2016-11-16 (5 days ago)

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

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

[Touch-packages] [Bug 1646925] Re: help me..am new

[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/1646925

Title:
  help me..am new

Status in xorg package in Ubuntu:
  Expired

Bug description:
  its even ok if some who can fix the bugs share the screen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Dec  3 00:01:36 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2166]
 Subsystem: Hewlett-Packard Company GK208M [GeForce GT 740M] [103c:2166]
  InstallationDate: Installed on 2016-12-01 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=698b7b05-7263-4dac-8ae1-7085313101ce ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.64
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2166
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.64:bd05/23/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr09921100410600080:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 09921100410600080
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Dec  2 23:04:41 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   18001 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1654365] Re: Session dbus lauched by /etc/X11/Xsession.d/75dbus_dbus-launch dies immediately

[Robert Ancell]

MIR_SOCKET is set by LightDM, so it will be present when the Xsession is
run.

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

Title:
  Session dbus lauched by /etc/X11/Xsession.d/75dbus_dbus-launch dies
  immediately

Status in dbus package in Ubuntu:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  We've been troubleshooting an issue with dbus on:

  $ system-image-cli -i
  current build number: 115
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-05 18:30:16
  version version: 115
  version ubuntu: 20170105.1
  version device: 20161014.0
  version custom: 20170105.1

  I've come to the conclusion as follows:

  The session dbus daemon is launched by lightdm through Xsession.d
  /75dbus_dbus-launch (pstree):

  systemd,1 fixrtc
    `-lightdm,2384
    `-lightdm,2439 --session-child 11 16
    `-dbus-launch,2692 --exit-with-session ubuntu-touch-session
    `-dbus-launch,2747 --exit-with-session ubuntu-touch-session
    `-dbus-daemon,2748 /usr/bin/dbus-daemon --fork --print-pid 
4 --print-address 6 --session

  Due to how the touch session is set up, dbus-launch subsequently kills
  the daemon because of the --exit-with-session option. Not sure exactly
  how/why this happens yet.

  The dbus-launch PID is replaced with upstart:

  phablet   2692 13.6  0.1  45948  3688 ?Ss   19:25   0:21
  upstart --user

  It was fine so far because the session upstart dbus job launched a
  session dbus regardless. With the change in
  https://launchpad.net/ubuntu/+source/dbus/1.10.6-1ubuntu3.2 however,
  it won't launch one if DBUS_SESSION_BUS_ADDRESS is set already. The
  environment is left with the address of the dead session dbus and so
  we're left with a bogus environment variable...

  
  === Workaround ===

  It's possible to disable the Xsessions-dbus script by editing
  /etc/X11/Xsession.options and commenting out the following entry:

  use-session-dbus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-touch-session 0.108+16.04.20161206-0ubuntu1
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Thu Jan  5 19:06:28 2017
  PackageArchitecture: all
  SourcePackage: ubuntu-touch-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ubuntu-touch-session.d.android.conf:
   GRID_UNIT_PX=13
   QTWEBKIT_DPR=1.0
   NATIVE_ORIENTATION=landscape
   FORM_FACTOR=tablet
  mtime.conffile..etc.ubuntu-touch-session.d.android.conf: 2016-10-14T08:44:51
  upstart.bluez-mpris-proxy.log:
   Can't get on session busCan't get on session busCan't get on session 
busCan't get on session busCan't get on session busCan't get on session 
busCan't get on session busCan't get on session busCan't get on session 
busCan't get on session busCan't get on session busCan't get on session 
busCan't get on session busCan't get on session busCan't get on session 
busCan't get on session busCan't get on session busCan't get on session 
busCan't get on session busCan't get on session busCan't get on session 
busCan't get on session busorg.bluez appeared
   Bluetooth Adapter /org/bluez/hci0 found
   player core.ubuntu.media.Service at :1.1746 found
  upstart.obexd.log:
   Failed to connect to socket /tmp/dbus-lf2wBKftE7: Connection refused
   Failed to connect to socket /tmp/dbus-ej3pH8DVYy: Connection refused
  upstart.plymouth-log.override: manual
  upstart.plymouth-shutdown.override: manual
  upstart.plymouth.override: manual

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

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

[Touch-packages] [Bug 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg

[Nathanaël Naeri]

Still affects xorg-lts-trusty (for Precise users)

** Changed in: xorg (Ubuntu)
   Status: Triaged => Invalid

** Changed in: xorg-lts-trusty (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Xorg fails to start after installing the Hardware Enablement Stack due
  to missing symlink after purging old xserver-xorg

Status in xorg package in Ubuntu:
  Invalid
Status in xorg-lts-trusty package in Ubuntu:
  Confirmed
Status in xorg-lts-utopic package in Ubuntu:
  Triaged
Status in xorg-lts-vivid package in Ubuntu:
  Fix Released

Bug description:
  Bug:

  The bug happens whenever the remaining configuration files of the
  original X stack is removed, ie purging. It does not happen for users
  who do not explicitly remove those.

  Workaround:

  For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack
  (=14.10/utopic):

  sudo dpkg-reconfigure xserver-xorg-lts-utopic

  This restores the symlink /etc/X11/X -> /usr/bin/Xorg

  ---

  After installing the hardware enablement stack on precise by running:
  sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal

  Xorg fail to start. There is no error message or anything, just a black 
screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink 
is missing:
  X: cannot stat /etc/X11/X (No such file or directory), aborting.

  I updates two computers running precise x86_64 and both had the
  problem.

  Just recreating the symlink fixes the problem and then precise runs
  perfectly fine with the new stack (in fact, it's more stable so far).

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

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

[Touch-packages] [Bug 1132736] [NEW] Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Bug:

The bug happens whenever the remaining configuration files of the
original X stack is removed, ie purging. It does not happen for users
who do not explicitly remove those.

Workaround:

For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack
(=14.10/utopic):

sudo dpkg-reconfigure xserver-xorg-lts-utopic

This restores the symlink /etc/X11/X -> /usr/bin/Xorg

---

After installing the hardware enablement stack on precise by running:
sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal

Xorg fail to start. There is no error message or anything, just a black screen. 
Switching to a vt i possible and lightdm/x-0.log shows that a symlink is 
missing:
X: cannot stat /etc/X11/X (No such file or directory), aborting.

I updates two computers running precise x86_64 and both had the problem.

Just recreating the symlink fixes the problem and then precise runs
perfectly fine with the new stack (in fact, it's more stable so far).

** Affects: xorg (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: xorg-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: xorg-lts-utopic (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: xorg-lts-vivid (Ubuntu)
 Importance: Undecided
 Status: Fix Released


** Tags: packaging precise regression-update trusty xorg-server
-- 
Xorg fails to start after installing the Hardware Enablement Stack due to 
missing symlink after purging old xserver-xorg
https://bugs.launchpad.net/bugs/1132736
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1655782] Re: Elfdalian layout + merge with Debian 2.19-1

[Gunnar Hjalmarsson]

** Summary changed:

- Elfdalian layout + merge with Debian 2.18-1
+ Elfdalian layout + merge with Debian 2.19-1

** Description changed:

  Please add the Elfdalian keyboard layout which has been added upstream
  (see the Freedesktop bug report).
  
  I also propose that we take this opportunity to merge with Debian
- xkeyboard-config 2.18-1.
+ xkeyboard-config 2.19-1.

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

Title:
  Elfdalian layout + merge with Debian 2.19-1

Status in xkeyboard-config:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  In Progress

Bug description:
  Please add the Elfdalian keyboard layout which has been added upstream
  (see the Freedesktop bug report).

  I also propose that we take this opportunity to merge with Debian
  xkeyboard-config 2.19-1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1655782/+subscriptions

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

[Touch-packages] [Bug 1539318] Re: Cannot import contacts from SIM card

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot import contacts from SIM card

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  Confirmed

Bug description:
  When i try to import contracts from the SIM card i receive a error
  message that says "Falha ao ler cartão SIM" - error reading the SIM
  card.

  I already reinstalled the OS and it give me the same error.

  I'm using a BQ Aquaris 4.5 Ubuntu Edition

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

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

[Touch-packages] [Bug 1568296] Re: Make JS dialogs app modal

[Chris Coulson]

** Changed in: oxide
   Status: In Progress => Fix Released

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

Title:
  Make JS dialogs app modal

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

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

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

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

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

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

[Touch-packages] [Bug 1655584] Re: systemd-udevd busyloops when nvidia kernel module fails to load

[Ross Boylan]

I tried 
systemctl stop nvidia-persistenced
nvidia-persistenced --no-persistence-mode
nvidia-smi --persistence-mode=Disabled
but none of them helped.  nvidia-smi failed because it couldn't communicate 
with the nvidia driver.

The system was created using a raw disk in a virtual machine
(VirtualBox).  I then booted off the disk so it was running for real,
and accepted the offered nvidia drivers.  Finally, I shutdown and
restarted in the VM.  That is the context for the loop.  The VM has no
nvidia hardware, and so obviously there is no reason for the driver to
load.

Ross

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

Title:
  systemd-udevd busyloops when nvidia kernel module fails to load

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a machine where nvidia-367 is installed, but the driver won't attach (due 
to
  the nvidia card being older and requiring legacy drivers), systemd-udevd
  repeatedly attempts to load it anyway, causing high CPU and memory usage. I
  observed the systemd-udevd process at 98% CPU usage and 2.5G RSS reported by
  top(1); restarting the service reduces resource usage momentarily, but it
  appears to be climbing back up (I suspect the number of events is growing).

  Workaround is of course installing the correct driver package, but udevd 
really
  ought not behave like this if something fails to load.

  Some journal entries for systemd-udevd.service:

  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' 
failed with exit code 9.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
  Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' 
failed with exit code 9.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' 
failed with exit code 1.
  Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' 
failed with exit code 1.

  dmesg shows repeated failures for loading the nvidia module:

  [1675406.587926] NVRM: The NVIDIA GeForce 9300 GE GPU installed in this 
system is
 NVRM:  supported through the NVIDIA 340.xx Legacy drivers. 
Please
 NVRM:  visit http://www.nvidia.com/object/unix.html for 
more
 NVRM:  information.  The 367.57 NVIDIA driver will ignore
 NVRM:  this GPU.  Continuing probe...
  [1675406.587936] NVRM: No NVIDIA graphics adapter found!
  [1675406.588078] NVRM: NVIDIA init module failed!

  Release information:

  # lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  # apt policy systemd udev
  systemd:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu13
Version table:
   *** 229-4ubuntu13 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial/main amd64 Packages
  udev:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu13
Version table:
   *** 229-4ubuntu13 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive 
xenial/main amd64 Packages

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

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

[Touch-packages] [Bug 1660573] Re: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04

[Paul Collins]

I forgot to mention that pam_nologin prints "System is booting up." and
fails non-root logins when /var/run/nologin exists, which is why that is
relevant. :)

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

Title:
  "system is booting up" while trying to log in after installing snapd
  on ubuntu 14.04

Status in snapd:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I've installed snapd on an up-to-date Ubuntu 14.04 server system
  running LTS enablement kernel.

  After toying with snapd and some simple snaps I logged out (so far everything 
was OK).
  I returned to the console after a while (I'm not sure if I logged out but I 
suspect I had to) and I saw the login prompt. After entering my username a line 
was printed "System is booting up" and I was kicked back ot the login prompt 
(It never asked for my password).

  After rebooting the problem went away.

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

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

[Touch-packages] [Bug 1660573] Re: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04

[Paul Collins]

With a freshly-booted up to date trusty VM (ubuntu-trusty-daily-
amd64-server-20170130-disk1.img, then dist-upgraded for libssl1.0.0
openssl), simply installing systemd seems to be sufficient to cause the
file to exist.

ubuntu@pjdc-test:~$ ls -l /var/run/nologin
ls: cannot access /var/run/nologin: No such file or directory
ubuntu@pjdc-test:~$ sudo apt-get install systemd
sudo: unable to resolve host pjdc-test
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
  libsystemd-journal0
Suggested packages:
  systemd-ui
The following NEW packages will be installed:
  libsystemd-journal0 systemd
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,476 kB of archives.
After this operation, 9,229 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://prodstack-zone-2.clouds.archive.ubuntu.com/ubuntu/ 
trusty-updates/main libsystemd-journal0 amd64 204-5ubuntu20.22 [51.0 kB]
Get:2 http://prodstack-zone-2.clouds.archive.ubuntu.com/ubuntu/ 
trusty-updates/main systemd amd64 204-5ubuntu20.22 [1,425 kB]
Fetched 1,476 kB in 0s (17.6 MB/s)
Selecting previously unselected package libsystemd-journal0:amd64.
(Reading database ... 51302 files and directories currently installed.)
Preparing to unpack .../libsystemd-journal0_204-5ubuntu20.22_amd64.deb ...
Unpacking libsystemd-journal0:amd64 (204-5ubuntu20.22) ...
Selecting previously unselected package systemd.
Preparing to unpack .../systemd_204-5ubuntu20.22_amd64.deb ...
Unpacking systemd (204-5ubuntu20.22) ...
Processing triggers for ureadahead (0.100.0-16) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up libsystemd-journal0:amd64 (204-5ubuntu20.22) ...
Setting up systemd (204-5ubuntu20.22) ...
Initializing machine ID from D-Bus machine ID.
systemd start/running, process 3110
Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
Processing triggers for ureadahead (0.100.0-16) ...
ubuntu@pjdc-test:~$ ls -l /var/run/nologin
-rw-r--r-- 1 root root 21 Feb  1 01:31 /var/run/nologin
ubuntu@pjdc-test:~$

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

Title:
  "system is booting up" while trying to log in after installing snapd
  on ubuntu 14.04

Status in snapd:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I've installed snapd on an up-to-date Ubuntu 14.04 server system
  running LTS enablement kernel.

  After toying with snapd and some simple snaps I logged out (so far everything 
was OK).
  I returned to the console after a while (I'm not sure if I logged out but I 
suspect I had to) and I saw the login prompt. After entering my username a line 
was printed "System is booting up" and I was kicked back ot the login prompt 
(It never asked for my password).

  After rebooting the problem went away.

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

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

[Touch-packages] [Bug 1660573] Re: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04

[Steve Langasek]

what version of the systemd package do you have installed?

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

Title:
  "system is booting up" while trying to log in after installing snapd
  on ubuntu 14.04

Status in snapd:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I've installed snapd on an up-to-date Ubuntu 14.04 server system
  running LTS enablement kernel.

  After toying with snapd and some simple snaps I logged out (so far everything 
was OK).
  I returned to the console after a while (I'm not sure if I logged out but I 
suspect I had to) and I saw the login prompt. After entering my username a line 
was printed "System is booting up" and I was kicked back ot the login prompt 
(It never asked for my password).

  After rebooting the problem went away.

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

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

[Touch-packages] [Bug 1657845] Re: Unity8 snap can't load the testability libraries

[Santiago Baldassin]

fyi, here's a great explanation about how this is supposed to work:
http://askubuntu.com/questions/841004/cannot-get-basic-content-
interface-example-working-with-snapcraft

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

Title:
  Unity8 snap can't load the testability libraries

Status in Unity8 Session Snap:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  In order to introspect unity8, the testability libraries should be
  available. Such libraries are provided by autopilot-qt snap through a
  content interface called testability

  unity8 snap should add a plug to such interface so that testability
  libraries get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-session-snap/+bug/1657845/+subscriptions

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

[Touch-packages] [Bug 1657845] Re: Unity8 snap can't load the testability libraries

[Santiago Baldassin]

Hi Michael, I gave it a try and it is not working. The problem is that
the path added to LD_LIBRARY_PATH does not seem to be ok.

./snappyenv:export
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$SNAP/testability/usr/lib:$SNAP/testability/usr/lib/$ARCH:$SNAP/testability/usr/lib/$ARCH/mesa

In the snap that I installed, that is the path added and the path to be
appended should be

$SNAP/testability/:$SNAP/testability/$ARCH:$SNAP/testability/$ARCH/mesa

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

Title:
  Unity8 snap can't load the testability libraries

Status in Unity8 Session Snap:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  In order to introspect unity8, the testability libraries should be
  available. Such libraries are provided by autopilot-qt snap through a
  content interface called testability

  unity8 snap should add a plug to such interface so that testability
  libraries get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-session-snap/+bug/1657845/+subscriptions

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

[Touch-packages] [Bug 1660464] Re: No ability to print on ubuntu touch device.

[Till Kamppeter]

This is already a project at Canonical, see

https://wiki.ubuntu.com/Printing

see also

https://blueprints.launchpad.net/ubuntu/+spec/client-1305-printing-
stack-with-mobile-in-mind


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

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

Title:
  No ability to print on ubuntu touch device.

Status in cups package in Ubuntu:
  In Progress

Bug description:
  Hi.

  I bought a bq aquaris m10 tablet with ubuntu onboard.

  And suddenly I've found that there are no printing ability. At all! I
  cannot add/setup printer, I cannot print.

  I really need it. I need to print from web browser, from pdf viewer as
  I can do it from android, ios or winmobile devices. Moreover, it's
  really more than funny to release an OS without printing support. How
  is it possible to miss BASIC functionality? Fix it URGENTLY please.

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

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

[Touch-packages] [Bug 1186331] Re: [PATCH] e2fsck hangs up boot process because "Device or resource busy while checking ext3 journal for foobar"

[Theodore Ts'o]

Was released a ***long*** time ago.   Guess Canonical doesn't do this
automatically.

** Changed in: e2fsprogs (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [PATCH] e2fsck hangs up boot process because "Device or resource busy
  while checking ext3 journal for foobar"

Status in e2fsprogs package in Ubuntu:
  Fix Released

Bug description:
  I installed Kubuntu 13.04 x64 on a new SSD, but pointed its ext4
  journal to another partition on a spinning disk (same block size, of
  course).

  At every boot, e2fsck prompts me to check / for errors but it dies
  because:

  fsck.ext4: Device or resource busy while checking ext3 journal for
  foobar

   foobar: ** WARNING: Filesystem still has errors **

  [Please, also note: If I press I to ignore and continue the boot
  process, it complains about /tmp not being ready yet (I used bind in
  fstab because it's on another partition). So I press S to skip the
  mount and access lightdm which can't login yet because /tmp is
  unmounted (it would just restart itself). Accessing the tty with
  CTRL+ALT+F1 works and I can "sudo mountall" to correctly mount /tmp,
  then login and use the system as usual.]

  Using a LiveCD to fsck the / partition shows that the filesystem is
  clean.

  I built e2fsck from source and applied this patch
  http://www.spinics.net/lists/linux-ext4/msg38096.html before compiling
  and it solved the problem.

  Now the boot-up process is smooth and it also carried away the /tmp
  not ready issue.

  Please, apply this patch to e2fsprogs.

  If you need more info, please just tell me.

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

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

[Touch-packages] [Bug 1645232] Re: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL)

[Theodore Ts'o]

Fix is in e2fsprogs 1.43.4


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

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

Title:
  e2fsprogs - could not preserve ACL permissions  : The getxattr()
  returns with (EINVAL)

Status in e2fsprogs package in Ubuntu:
  Fix Released

Bug description:
  The original installed e2fsprogs did not support mke2fs -d /directory
  " option . So ,  git cloned from e2fsprogs packages from repository
  and installed it and followed below steps to reproduce this :

  1. set the ACL rules as below to one of the binary :

  $ setfacl -m u:vipatil:r-- rootfs/usr/bin/helloworld
  $ getfacl rootfs/usr/bin/helloworld
  # file: rootfs/usr/bin/helloworld
  # owner: shkumar
  # group: hardev
  user::rwx
  user:vipatil:r--
  group::---
  mask::r--
  other::---

  2. $ dd if=/dev/zero of=test.ext4 bs=1M count=60

  3. $ mke2fs -t ext4 test.ext4 -d rootfs/
  mke2fs 1.43.3 (04-Sep-2016)
  Discarding device blocks: done
  Creating filesystem with 61440 1k blocks and 15360 inodes
  Filesystem UUID: 495713b3-5f1f-427a-8359-a736dfb2ece9
  Superblock backups stored on blocks:
  8193, 24577, 40961, 57345

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (4096 blocks): done
  Copying files into the device: done
  Writing superblocks and filesystem accounting information: done

  4. sudo mount -o loop,acl,user_xattr,rw,sync test.ext4 mountpoint

  5.@/mountpoint$ getfacl usr/bin/helloworld
  getfacl: usr/bin/helloworld: Invalid argument

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

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

[Touch-packages] [Bug 1654624] Re: dhcp apparmor profile complains about lxd client

[Seth Arnold]

Hadmut, AppArmor's stacking support was intended to allow supporting
unmodified Ubuntu inside LXD containers. If you're feeling up for some
experimentation, you could try to disable this feature by setting the
kernel.unprivileged_userns_apparmor_policy sysctl to 0 early in a system
boot, preferably before LXD starts. This should cause the attempts to
set policy within LXDs to fail, and either the services will then refuse
to start or they'll fall back to their old behaviour. (This reflects my
lack of familiarity with LXD.)

I'll note that this is a wild guess; I'd feel more comfortable giving
this advice on IRC than in a public bug tracker where it might do more
harm than good. But I'm cautiously optimistic that this might give you a
system you'd be happier using.

Thanks

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

Title:
  dhcp apparmor profile complains about lxd client

Status in apparmor package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  strange problem recently occured:

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

  But now the host generates messages like


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

  
  in /var/log/kern.log. 

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

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

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

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

[Touch-packages] [Bug 1657845] Re: Unity8 snap can't load the testability libraries

[Michael Terry]

The current edge store snap should be setting LD_LIBRARY_PATH
(correctly, I hope).  I had a hard time telling if the content interface
mount was working as expected, so please let me know if it works as
expected.

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

Title:
  Unity8 snap can't load the testability libraries

Status in Unity8 Session Snap:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  In order to introspect unity8, the testability libraries should be
  available. Such libraries are provided by autopilot-qt snap through a
  content interface called testability

  unity8 snap should add a plug to such interface so that testability
  libraries get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-session-snap/+bug/1657845/+subscriptions

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

[Touch-packages] [Bug 1598759] Re: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved

[Tyler Hicks]

This isn't fixed in AppArmor upstream. As an upstream, we decided
against taking in this policy update until the patches to perform D-Bus
mediation have landed in the upstream kernel. Without those patches,
we'd be granting full access to the D-Bus system bus socket from the
very commonly used namespace abstraction.

** Changed in: apparmor
   Status: Fix Released => Triaged

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

Title:
  AppArmor nameservice abstraction doesn't allow communication with
  systemd-resolved

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Invalid
Status in apparmor source package in Yakkety:
  Fix Released
Status in ntp source package in Yakkety:
  Invalid

Bug description:
  [ Impact ]

  Processes confined by AppArmor profiles making use of the nameservice
  AppArmor abstraction are unable to access the systemd-resolved network
  name resolution service. The nsswitch.conf file shipped in Yakkety
  puts the nss-resolve plugin to use which talks to systemd-resolved
  over D-Bus. The D-Bus communication is blocked for the confined
  processes described above and those processes will fallback to the
  traditional means of name resolution.

  [ Test Case ]

  * Use ntpd to test:
$ sudo apt-get install -y ntp
...
$ sudo systemctl stop ntp

# in another terminal, watch for AppArmor denials
$ dmesg -w

# in the original terminal, start ntp
$ sudo systemctl start ntp

# You'll see a number of denials on the system_bus_socket file:
audit: type=1400 audit(1476240762.854:35): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=3867 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=126 ouid=0

   * Use tcpdump to test:

 # Capture traffic on whichever network interface you're currently using
 $ sudo tcpdump -i eth0

 # Look in /var/log/syslog for denials on the system_bus_socket file:
 audit: type=1400 audit(1476240896.021:40): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/tcpdump" 
name="/run/dbus/system_bus_socket" pid=4106 comm="tcpdump" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

  In both situations, ntpd and tcpdump will seemingly work as expected
  due to the name resolution fallback configured in nsswitch.conf.
  However, neither confined process will be using systemd-resolved for
  name resolution.

  [ Regression Potential ]

  This fix will allow ntp, tcpdump, cupsd, dhclient, and other confined-
  by-default programs to start using systemd-resolved. There is some
  potential for regression since those applications have not been
  previously using systemd-resolved.

  [ Original bug description ]

  On this plain install of Xenial apparmor complains about ntpd:

  [   19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0

  Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the
  problem:

  #include 

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

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

[Touch-packages] [Bug 1660844] [NEW] SRU of LXC 2.0.7 (upstream bugfix release)

[Stéphane Graber]

Public bug reported:

LXC upstream released LXC 2.0.7 as a bugfix release with following changelog:
 - attach: Close lsm label file descriptor
 - attach: Non-functional changes
 - attach: Simplify lsm_openat()
 - caps: Add lxc_cap_is_set()
 - conf: attach: Save errno across call to close
 - conf: Clearly report to either use drop or keep
 - conf: criu: Add make_anonymous_mount_file()
 - conf: Fix suggest_default_idmap()
 - configure: Add --enable-gnutls option
 - configure: Check for memfd_create()
 - configure: Check whether gettid() is declared
 - configure: Do not allow variable length arrays
 - configure: Remove -Werror=vla
 - configure: Use AC_HEADER_MAJOR to detect major()/minor()/makedev()
 - conf: Non-functional changes
 - conf: Remove thread-unsafe strsignal + improve log
 - init: Add cgroupfs-mount to Should-Start/Stop sysvinit LSB headers
 - log: Add lxc_unix_epoch_to_utc()
 - log: Annotate lxc_unix_epoch_to_utc()
 - log: Drop all timezone conversion functions
 - log: Make sure that date is correctly formatted
 - log: Use lxc_unix_epoch_to_utc()
 - log: Use N/A if getpid() != gettid() when threaded
 - log: Use thread-safe localtime_r()
 - lvm: Suppress warnings about leaked files
 - lxccontainer: Log failure to send sig to init pid
 - monitor: Add more logging
 - monitor: Close mainloop on exit if we opened it
 - monitor: Improve log + set log level to DEBUG
 - monitor: Log which pipe fd is currently used
 - monitor: Make lxc-monitord async signal safe
 - monitor: Non-functional changes
 - python3-lxc: Fix api_test.py on s390x
 - start: Check for CAP_SETGID before setgroups()
 - start: Fix execute and improve setgroups() calls
 - state: Use async signal safe fun in lxc_wait()
 - templates: lxc-debian: Don't try to get stuff from /usr/lib/systemd on the 
host
 - templates: lxc-debian: Fix getty service startup
 - templates: lxc-debian: Fix typo in calling dpkg with 
--print-foreign-architectures option
 - templates: lxc-debian: Handle ppc hostarch -> powerpc
 - templates: lxc-opensuse: Change openSUSE default release to Leap 42.2
 - templates: lxc-opensuse: Remove libgcc_s1
 - templates: lxc-opensuse: Remove poweroff.target -> sigpwr.target copy
 - templates: lxc-opensuse: Set to be unconfined by AppArmor
 - templates: lxc-opensuse: Update for Leap 42.2
 - tests; Don't cause test failures on cleanup errors
 - tests: Skip unpriv tests on broken overlay module
 - tools: Improve logging
 - tools: lxc-start: Remove c->is_defined(c) check
 - tools: lxc-start: Set configfile after load_config
 - tools: Only check for O_RDONLY
 - tree-wide: Random macro cleanups
 - tree-wide: Remove any variable length arrays
 - tree-wide: Sic semper assertis!
 - utils: Add macro __LXC_NUMSTRLEN
 - utils: Add uid, gid, group convenience wrappers

Just like Ubuntu itself, upstream releases long term support releases,
as is 2.0 and then periodic point releases including all the accumulated
bugfixes.

Only the latest upstream release gets full support from the upstream
developers, everyone else is expected to first update to it before
receiving any kind of support.

This bugfix release has already been uploaded to Zesty and automatically
backported in the upstream PPAs for all Ubuntu releases. So far without
any reported regression.

This should qualify under the minor upstream bugfix release allowance of
the SRU policy, letting us SRU this without paperwork for every single
change included in this upstream release.

Once the SRU hits -updates, we will be backporting this to trusty-
backports as well, making sure we have the same version everywhere.

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: lxc (Ubuntu Trusty)
 Importance: Medium
 Assignee: Stéphane Graber (stgraber)
 Status: Triaged

** Affects: lxc (Ubuntu Xenial)
 Importance: Medium
 Assignee: Stéphane Graber (stgraber)
 Status: In Progress

** Affects: lxc (Ubuntu Yakkety)
 Importance: Medium
 Assignee: Stéphane Graber (stgraber)
 Status: In Progress

** Also affects: lxc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: lxc (Ubuntu Trusty)
   Status: In Progress => Triaged

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

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

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

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

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

** Changed in: lxc (Ubuntu Trusty)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxc (Ubuntu 

[Touch-packages] [Bug 1656450] Re: Desktop notifications stop working

[lediableboiteux]

No, there isn’t. There are others, but nothing about notification-deamon
or anything related.

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

Title:
  Desktop notifications stop working

Status in libnotify package in Ubuntu:
  Incomplete

Bug description:
  I don’t know how and why, but sometimes desktop notifications
  (libnotify) just stop working and are not shown – either applications’
  notifications (like telling you not to unplug your external HDD while
  unmounting), or these called directly by notify-send. Killing notify-
  osd doesn’t help.

  I have Ubuntu 16.10 x64, but I remember this issue back from 15.10 or
  even before, but I’m not sure.

  libnotify4: 0.7.6-2svn1
  libnotify-bin: 0.7.6-2svn1

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

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

[Touch-packages] [Bug 1598759] Re: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved

[John Johansen]

** Changed in: apparmor
   Status: Triaged => Fix Released

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

Title:
  AppArmor nameservice abstraction doesn't allow communication with
  systemd-resolved

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Invalid
Status in apparmor source package in Yakkety:
  Fix Released
Status in ntp source package in Yakkety:
  Invalid

Bug description:
  [ Impact ]

  Processes confined by AppArmor profiles making use of the nameservice
  AppArmor abstraction are unable to access the systemd-resolved network
  name resolution service. The nsswitch.conf file shipped in Yakkety
  puts the nss-resolve plugin to use which talks to systemd-resolved
  over D-Bus. The D-Bus communication is blocked for the confined
  processes described above and those processes will fallback to the
  traditional means of name resolution.

  [ Test Case ]

  * Use ntpd to test:
$ sudo apt-get install -y ntp
...
$ sudo systemctl stop ntp

# in another terminal, watch for AppArmor denials
$ dmesg -w

# in the original terminal, start ntp
$ sudo systemctl start ntp

# You'll see a number of denials on the system_bus_socket file:
audit: type=1400 audit(1476240762.854:35): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=3867 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=126 ouid=0

   * Use tcpdump to test:

 # Capture traffic on whichever network interface you're currently using
 $ sudo tcpdump -i eth0

 # Look in /var/log/syslog for denials on the system_bus_socket file:
 audit: type=1400 audit(1476240896.021:40): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/tcpdump" 
name="/run/dbus/system_bus_socket" pid=4106 comm="tcpdump" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

  In both situations, ntpd and tcpdump will seemingly work as expected
  due to the name resolution fallback configured in nsswitch.conf.
  However, neither confined process will be using systemd-resolved for
  name resolution.

  [ Regression Potential ]

  This fix will allow ntp, tcpdump, cupsd, dhclient, and other confined-
  by-default programs to start using systemd-resolved. There is some
  potential for regression since those applications have not been
  previously using systemd-resolved.

  [ Original bug description ]

  On this plain install of Xenial apparmor complains about ntpd:

  [   19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0

  Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the
  problem:

  #include 

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

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

[Touch-packages] [Bug 1660832] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1660832

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

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

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

Title:
  unix domain socket cross permission check failing with nested
  namespaces

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Incomplete
Status in apparmor source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Incomplete
Status in apparmor source package in Zesty:
  New
Status in linux source package in Zesty:
  Incomplete

Bug description:
  When using nested namespaces policy within the nested namespace is trying 
  
  to cross validate with policy outside of the namespace that is not
  
  visible to it. This results the access being denied and with no way to
  
  add a rule to policy that would allow it.

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

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

[Touch-packages] [Bug 1660832] [NEW] unix domain socket cross permission check failing with nested namespaces

[John Johansen]

Public bug reported:

When using nested namespaces policy within the nested namespace is trying   
to cross validate with policy outside of the namespace that is not  
visible to it. This results the access being denied and with no way to  
add a rule to policy that would allow it.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: apparmor (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: apparmor (Ubuntu Yakkety)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Yakkety)
 Importance: Undecided
 Status: New

** Affects: apparmor (Ubuntu Zesty)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Zesty)
 Importance: Undecided
 Status: Incomplete

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

** Also affects: apparmor (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: apparmor (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: apparmor (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

Title:
  unix domain socket cross permission check failing with nested
  namespaces

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  New
Status in linux source package in Yakkety:
  New
Status in apparmor source package in Zesty:
  New
Status in linux source package in Zesty:
  Incomplete

Bug description:
  When using nested namespaces policy within the nested namespace is trying 
  
  to cross validate with policy outside of the namespace that is not
  
  visible to it. This results the access being denied and with no way to
  
  add a rule to policy that would allow it.

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

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

[Touch-packages] [Bug 1428490] Re: AppArmor vs unix socket inside LXC containers

[John Johansen]

Unless we can get more debug info I am marking this won't fix


** Changed in: lxc (Ubuntu)
   Status: New => Won't Fix

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

Title:
  AppArmor vs unix socket inside LXC containers

Status in lxc package in Ubuntu:
  Won't Fix

Bug description:
  I know this seems like an odd bug, but I've spent all day chasing it
  down.

  I was seeing problems with LDAP lookups inside an LXC container, and
  strace on getent lookups was showing that attempts to read from
  /var/run/nslcd/socket were being closed as -1 (EACCESS).

  That file/UNIX socket is owned by nslcd, also running inside the LXC.

  Back on the host machine, setting the LXC config to set lxc.aa_profile
  = unconfined (and restarting the container) then allowed that socket
  to start working freely.

  This seems weird, as there's all sorts of other things using UNIX
  sockets inside containers that still function normally, but I thought
  I'd mention it, especially in case anyone hits this issue.

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

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

[Touch-packages] [Bug 1582414] Re: No HDMI audio on Lenovo pro dock with T440s

[Martin D. Weinberg]

The symptoms and behavior are nearly the same, so the issue seems
closely related, if not the same.  However, the report is for different
hardware and dock (UltraDock rather than OneLink dock although both
Haswell).  But, without doing the back port of Dave Airlie's patches to
4.9.x, 4.10.x or 4.4.0, it's hard to know for certain. I'd suggest
keeping the bug open if only to document the breadth of the problem.

If I get a chance, I may try the backport myself, but I don't have time
right now.

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

Title:
  No HDMI audio on Lenovo pro dock with T440s

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  pavucontrol shows Display Port/HDMI output as "(unplugged)" and cannot
  be chosen as a sink.  This is only a problem with the dock; audio
  works when plugging HDMI through the laptop's DP input.

  The audio did work with the dock in Ubuntu 14.04.  Did something in
  jack detection change?  Anyway, my work around is to plug a 3.4mm
  audio cable into the dock and power the speakers that way, but it
  would be nice to use the HDMI audio again.

  I would love to have a work around.  I've attached the output from
  alsa-info.sh, just in case this is useful.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  weinberg   2221 F pulseaudio
   /dev/snd/controlC2:  weinberg   2221 F pulseaudio
   /dev/snd/controlC0:  weinberg   2221 F pulseaudio
   /dev/snd/controlC1:  weinberg   2221 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May 16 17:18:06 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-06 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ARA0S100
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

[Halvor Lyche Strandvoll]

This is a critical issue as it makes the interface unusable until
systemd-networkd is manually restarted.

This bug is already fixed in upstream:
https://github.com/systemd/systemd/commit/e3a7b04848a438f7b5a9a2bf5d7e0e59c5c49a00

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

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1660496] Re: Libva upstream project has moved to Github from Freedesktop.org

[Bug Watch Updater]

** Changed in: libva (Debian)
   Status: Unknown => New

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

Title:
  Libva upstream project has moved to Github from Freedesktop.org

Status in libva package in Ubuntu:
  New
Status in libva package in Debian:
  New

Bug description:
  Package: libva
  Version: 1.7.3-2

  I'm a maintainer of upstream Libva.  I have moved our project from
  freedesktop.org to github.com.

  Wiki location has moved to: https://01.org/linuxmedia/vaapi

  Libva project has moved to https://github.com/01org/libva

  Use https://github.com/01org/libva/issues/new to file bugs on the
  libva github site

  Packages will need to be updated to pull source from the new github
  repos mentioned above.

  I have submitted this bug upstream to debian packagers of libva
  Bug#853270
  853...@bugs.debian.org

  Thanks,

  Sean

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

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

[Touch-packages] [Bug 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

[Launchpad Bug Tracker]

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

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

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

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1654624] Re: dhcp apparmor profile complains about lxd client

[Brian Murray]

** Tags added: regression-update

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

Title:
  dhcp apparmor profile complains about lxd client

Status in apparmor package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  strange problem recently occured:

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

  But now the host generates messages like


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

  
  in /var/log/kern.log. 

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

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

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

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

[Touch-packages] [Bug 1660464] Re: No ability to print on ubuntu touch device.

[Sergei Pikalev]

** Package changed: ubuntu => cups (Ubuntu)

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

Title:
  No ability to print on ubuntu touch device.

Status in cups package in Ubuntu:
  New

Bug description:
  Hi.

  I bought a bq aquaris m10 tablet with ubuntu onboard.

  And suddenly I've found that there are no printing ability. At all! I
  cannot add/setup printer, I cannot print.

  I really need it. I need to print from web browser, from pdf viewer as
  I can do it from android, ios or winmobile devices. Moreover, it's
  really more than funny to release an OS without printing support. How
  is it possible to miss BASIC functionality? Fix it URGENTLY please.

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

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

[Touch-packages] [Bug 1660633] Re: /usr/bin/ucfr: line ... : [: : integer expression expected

[Steve Langasek]

> I've had a reoccurring issue:
https://ubuntuforums.org/showthread.php?t=2350682

Please include full error messages in your bug report when filing,
rather than referring to other websites.

In this case, the error is that "count" is undefined in the script.  Is
/var/lib/ucf/registry missing from your system?

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

Title:
  /usr/bin/ucfr: line ... : [: : integer expression expected

Status in ucf package in Ubuntu:
  New

Bug description:
  I've had a reoccurring issue: 
https://ubuntuforums.org/showthread.php?t=2350682
  Running: ucf_3.0036_all.deb

  
http://askubuntu.com/questions/875415/usr-bin-ucfr-errors-integer-expression-expected
  
http://serverfault.com/questions/827873/grub-pc-update-fail-dev-sda-ext2-doesnt-support-embedding

  I don't know why ucfr is erroring out but the accumulated errors are
  now enough to stall priority packages which I feel hamstrung about.
  I've reinstalled the ucf package and danced around the issue enough.

  Any maintainers have a shot in the dark for why this would be
  happening?

  Discussion:
  https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737

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

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

[Touch-packages] [Bug 1660464] [NEW] No ability to print on ubuntu touch device.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi.

I bought a bq aquaris m10 tablet with ubuntu onboard.

And suddenly I've found that there are no printing ability. At all! I
cannot add/setup printer, I cannot print.

I really need it. I need to print from web browser, from pdf viewer as I
can do it from android, ios or winmobile devices. Moreover, it's really
more than funny to release an OS without printing support. How is it
possible to miss BASIC functionality? Fix it URGENTLY please.

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


** Tags: bot-comment
-- 
No ability to print on ubuntu touch device.
https://bugs.launchpad.net/bugs/1660464
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

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

[Touch-packages] [Bug 1660822] [NEW] I need install samsung ML-2010 on ubuntu mate

[Jorge Omar Cevallos Calle]

Public bug reported:

Hi friends .. I have a joybook lite u101c with ubuntu mate as operating
system. The problem is that I need to install and configure my samsung
ML-2010 printer and there are no suitable drivers .. try the system \
admin \ printers option but at the time of sending the print test comes
the following ML-2010 printer message << PAUSED >> ..

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: MATE
Date: Tue Jan 31 16:23:18 2017
InstallationDate: Installed on 2016-09-05 (148 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
Lpstat:
 device for ML-2010: usb://Samsung/ML-2010?serial=4461BKAQ137842T.
 device for MP250-series: usb://Canon/MP250%20series?serial=B03193=1
MachineType: BenQ Joybook Lite U101 Series
Papersize: a4
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MP250-series.ppd', 
'/etc/cups/ppd/ML-2010.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/MP250-series.ppd: Permission denied
 grep: /etc/cups/ppd/ML-2010.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=4aa8affa-55eb-4e39-817b-0d22285a84ec ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 2.07
dmi.board.name: Joybook Lite U101 Series
dmi.board.vendor: BenQ
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr2.07:bd04/23/2009:svnBenQ:pnJoybookLiteU101Series:pvr:rvnBenQ:rnJoybookLiteU101Series:rvr:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: Joybook Lite U101 Series
dmi.sys.vendor: BenQ

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


** Tags: apport-bug i386 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/1660822

Title:
  I need install samsung ML-2010 on ubuntu mate

Status in cups package in Ubuntu:
  New

Bug description:
  Hi friends .. I have a joybook lite u101c with ubuntu mate as
  operating system. The problem is that I need to install and configure
  my samsung ML-2010 printer and there are no suitable drivers .. try
  the system \ admin \ printers option but at the time of sending the
  print test comes the following ML-2010 printer message << PAUSED >> ..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: MATE
  Date: Tue Jan 31 16:23:18 2017
  InstallationDate: Installed on 2016-09-05 (148 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  Lpstat:
   device for ML-2010: usb://Samsung/ML-2010?serial=4461BKAQ137842T.
   device for MP250-series: usb://Canon/MP250%20series?serial=B03193=1
  MachineType: BenQ Joybook Lite U101 Series
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/MP250-series.ppd', '/etc/cups/ppd/ML-2010.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/MP250-series.ppd: Permission denied
   grep: /etc/cups/ppd/ML-2010.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=4aa8affa-55eb-4e39-817b-0d22285a84ec ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 2.07
  dmi.board.name: Joybook Lite U101 Series
  dmi.board.vendor: BenQ
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr2.07:bd04/23/2009:svnBenQ:pnJoybookLiteU101Series:pvr:rvnBenQ:rnJoybookLiteU101Series:rvr:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Joybook Lite U101 Series
  dmi.sys.vendor: BenQ

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

[Dan Streetman]

Has this been committed into trusty yet?  I rebased my trusty pull
request from comment 24; those patches will apply cleaning into the
trusty systemd repository.  I'm not sure if there is any other bug
holding up trusty.

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

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

Status in maas-images:
  Fix Released
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

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

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

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

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

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

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

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

  [Regression Potential]

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

  [Other Info]

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

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

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

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1647485/+subscriptions

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

[Touch-packages] [Bug 1355813] Re: Interface MTU management across MAAS/juju

[Andres Rodriguez]

** Changed in: maas
   Status: Triaged => Fix Released

** Changed in: maas
Milestone: next => None

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

Title:
  Interface MTU management across MAAS/juju

Status in juju-core:
  Fix Released
Status in MAAS:
  Fix Released
Status in juju-core package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Context:

  juju + MAAS deployed OpenStack environment, misc services deployed
  under LXC on the bootstrap node, interfaces configured for jumbo
  frames - note that I had to manually set the LXC container interfaces
  to mtu 9000 before the bridge would do the same.

  Action:

  Reboot one of the containers; MTU on br0 resets from 9000 -> 1500.

  This feels like more of a 'we need a better way to orchestrate MTU
  configuration across different services' so raising tasks for MAAS and
  Juju as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.5-0ubuntu0.1
  ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Tue Aug 12 13:26:00 2014
  KernLog:

  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxcsyslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions

-- 
Mailing list: https://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 1641236] Re: Confined processes inside container cannot fully access host pty device passed in by lxc exec

[Christian Brauner]

On Tue, Jan 31, 2017 at 11:34:43AM +0100, Christian Brauner wrote:
> I've reproduced this on a fresh standard xenial instance with LXD
> 2.0.8 and also on a xenial instance with a patched glibc that reports
> ENODEV on ttyname{_r}() on a pty fd that does not exist:
> 
> root@x:~# ./enodev_on_pty_in_different_namespace
> ttyname(): The pty device might exist in a different namespace: No such device
> ttyname_r(): The pty device might exist in a different namespace: No such 
> device

So to make this a little more elaborate:
- I managed to reproduce this with an unpatched glibc inside and outside the
  container just like @Tyler outlined.
- I managed to reproduce this with a patched glibc inside the container and an
  unpatched glibc outside the container.
- I managed to reproduce this with a patched glibc inside and outside the
  container.

So a patched glibc which returns ENODEV in case a symlink like /proc/self/fd/0
points to a pts device that lives in another namespace does not improve the
situation. The problem that @Tyler outlined still exists.

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

Title:
  Confined processes inside container cannot fully access host pty
  device passed in by lxc exec

Status in apparmor package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  Now that AppArmor policy namespaces and profile stacking is in place,
  I noticed odd stdout buffering behavior when running confined
  processes via lxc exec. Much more data stdout data is buffered before
  getting flushed when the program is confined by an AppArmor profile
  inside of the container.

  I see that lxd is calling openpty(3) in the host environment, using
  the returned fd as stdout, and then executing the command inside of
  the container. This results in an AppArmor denial because the file
  descriptor returned by openpty(3) originates outside of the namespace
  used by the container.

  The denial is likely from glibc calling fstat(), from inside the
  container, on the file descriptor associated with stdout to make a
  decision on how much buffering to use. The fstat() is denied by
  AppArmor and glibc ends up handling the buffering differently than it
  would if the fstat() would have been successful.

  Steps to reproduce (using an up-to-date 16.04 amd64 VM):

  Create a 16.04 container
  $ lxc launch ubuntu-daily:16.04 x

  Run tcpdump in one terminal and generate traffic in another terminal (wget 
google.com)
  $ lxc exec x -- tcpdump -i eth0
  tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
  listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
  
  47 packets captured
  48 packets received by filter
  1 packet dropped by kernel
  

  Note that everything above  was printed immediately
  because it was printed to stderr. , which is printed to
  stdout, was not printed until you pressed ctrl-c and the buffers were
  flushed thanks to the program terminating. Also, this AppArmor denial
  shows up in the logs:

  audit: type=1400 audit(1478902710.025:440): apparmor="DENIED"
  operation="getattr" info="Failed name lookup - disconnected path"
  error=-13 namespace="root//lxd-x_"
  profile="/usr/sbin/tcpdump" name="dev/pts/12" pid=15530 comm="tcpdump"
  requested_mask="r" denied_mask="r" fsuid=165536 ouid=165536

  Now run tcpdump unconfined and take note that  is printed 
immediately, before you terminate tcpdump. Also, there are no AppArmor denials.
  $ lxc exec x -- aa-exec -p unconfined -- tcpdump -i eth0
  ...

  Now run tcpdump confined but in lxc exec's non-interactive mode and note that 
 is printed immediately and no AppArmor denials are present. 
(Looking at the lxd code in lxd/container_exec.go, openpty(3) is only called in 
interactive mode)
  $ lxc exec x --mode=non-interactive -- tcpdump -i eth0
  ...

  Applications that manually call fflush(stdout) are not affected by
  this as manually flushing stdout works fine. The problem seems to be
  caused by glibc not being able to fstat() the /dev/pts/12 fd from the
  host's namespace.

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

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

[Touch-packages] [Bug 1587196] Re: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: Versuch, »/lib/systemd/system/console-setup.service« zu überschreiben, welches auch in Paket key

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15 failed to install/upgrade:
  Versuch, »/lib/systemd/system/console-setup.service« zu überschreiben,
  welches auch in Paket keyboard-configuration 1.108ubuntu15 ist

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  i installed katoolin aircrack-ng and then when it updated appeared an
  error and i followed the steps till here.

  ProblemType: Package
  DistroRelease: Kali 2016.1
  Package: console-setup-linux 1.108ubuntu15
  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
  Architecture: amd64
  Date: Tue May 31 02:02:23 2016
  ErrorMessage: Versuch, »/lib/systemd/system/console-setup.service« zu 
überschreiben, welches auch in Paket keyboard-configuration 1.108ubuntu15 ist
  InstallationDate: Installed on 2016-05-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.7
   apt  1.2.10ubuntu1
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: 
Versuch, »/lib/systemd/system/console-setup.service« zu überschreiben, welches 
auch in Paket keyboard-configuration 1.108ubuntu15 ist
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1587196/+subscriptions

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

[Touch-packages] [Bug 1604236] Re: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboa

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15

Status in console-setup package in Ubuntu:
  New

Bug description:
  While updating packages console-setup-linux 1.108ubuntu15 failed to
  install/upgrade: trying to overwrite '/lib/systemd/system/console-
  setup.service', which is also in package keyboard-configuration
  1.108ubuntu15

  ProblemType: Package
  DistroRelease: Kali 2016.1
  Package: console-setup-linux 1.108ubuntu15
  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
  Architecture: amd64
  Date: Tue Jul 19 08:11:23 2016
  DuplicateSignature:
   package:console-setup-linux:1.108ubuntu15
   Unpacking console-setup-linux (1.146) over (1.108ubuntu15) ...
   dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.146_all.deb (--unpack):
trying to overwrite '/lib/systemd/system/console-setup.service', which is 
also in package keyboard-configuration 1.108ubuntu15
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15
  InstallationDate: Installed on 2015-10-13 (279 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.7
   apt  1.2.10ubuntu1
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15
  UpgradeStatus: Upgraded to kali-rolling on 2016-04-30 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1604236/+subscriptions

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

[Touch-packages] [Bug 1608318] Re: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyb

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15.2

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  terminal screen is black, all authentication screens are black, etc.

  ProblemType: Package
  DistroRelease: Kali 2016.1
  Package: console-setup-linux 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 31 19:39:10 2016
  DuplicateSignature:
   package:console-setup-linux:1.108ubuntu15.2
   Unpacking console-setup-linux (1.147) over (1.108ubuntu15.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.147_all.deb (--unpack):
trying to overwrite '/lib/systemd/system/console-setup.service', which is 
also in package keyboard-configuration 1.108ubuntu15.2
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.2
  InstallationDate: Installed on 2016-07-08 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.9
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1608318/+subscriptions

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

[Touch-packages] [Bug 1612104] Re: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboa

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15

Status in console-setup package in Ubuntu:
  New

Bug description:
  bcm43142 wlan wifi disconnects after few minutes.no driver for
  it.ubuntu shows alternative driver usingwant to get the
  actual driver for it

  ProblemType: Package
  DistroRelease: Kali 2016.1
  Package: console-setup-linux 1.108ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 11 17:33:14 2016
  DuplicateSignature:
   Unpacking console-setup-linux (1.147) over (1.108ubuntu15) ...
   dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.147_all.deb (--unpack):
trying to overwrite '/lib/systemd/system/console-setup.service', which is 
also in package keyboard-configuration 1.108ubuntu15
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15
  InstallationDate: Installed on 2016-07-02 (40 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10
   apt  1.2.10ubuntu1
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612104/+subscriptions

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

[Touch-packages] [Bug 1592021] Re: package console-setup-linux 1.146 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-confi

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.146 failed to install/upgrade: trying to
  overwrite '/lib/systemd/system/console-setup.service', which is also
  in package keyboard-configuration 1.108ubuntu15.1

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  i try updating my ubuntu16.04 and its wasn't working so i tried to
  upgrade and after upgrading it only perform partial upgrade. And
  restarting gave me this bug.

  ProblemType: Package
  DistroRelease: Kali 2016.1
  Package: console-setup-linux 1.146
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Mon Jun 13 13:40:50 2016
  DuplicateSignature:
   package:console-setup-linux:1.146
   Unpacking console-setup-linux (1.146) over (1.108ubuntu15.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.146_all.deb (--unpack):
trying to overwrite '/lib/systemd/system/console-setup.service', which is 
also in package keyboard-configuration 1.108ubuntu15.1
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.1
  InstallationDate: Installed on 2015-03-16 (454 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.7
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: console-setup
  Title: package console-setup-linux 1.146 failed to install/upgrade: trying to 
overwrite '/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1592021/+subscriptions

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

[Touch-packages] [Bug 1622764] Re: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade:
  попытка перезаписать «/lib/systemd/system/console-setup.service»,
  который уже имеется в пакете keyboard-configuration 1.108ubuntu15.2

Status in console-setup package in Ubuntu:
  New

Bug description:
  Problem whith Kali Linux

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: console-setup-linux 1.108ubuntu15.2
  Uname: Linux 4.6.7-rt11 x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Sep 13 00:57:58 2016
  ErrorMessage: попытка перезаписать 
«/lib/systemd/system/console-setup.service», который уже имеется в пакете 
keyboard-configuration 1.108ubuntu15.2
  InstallationDate: Installed on 2016-09-12 (0 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10kali1
   apt  1.2.14
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
попытка перезаписать «/lib/systemd/system/console-setup.service», который уже 
имеется в пакете keyboard-configuration 1.108ubuntu15.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1622764/+subscriptions

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

[Touch-packages] [Bug 1659927] Re: console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-con

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: trying
  to overwrite '/lib/systemd/system/console-setup.service', which is
  also in package keyboard-configuration 1.108ubuntu15.2

Status in console-setup package in Ubuntu:
  New

Bug description:
  upgrade failure!

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: console-setup-linux 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Fri Jan 27 19:53:01 2017
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.2
  InstallationDate: Installed on 2016-10-16 (102 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.15kali1
   apt  1.2.18
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.2
  UpgradeStatus: Upgraded to kali-rolling on 2016-10-17 (102 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1659927/+subscriptions

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

[Touch-packages] [Bug 1635817] Re: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyb

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15.2

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15.2

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: console-setup-linux 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Oct 22 06:04:53 2016
  DuplicateSignature:
   package:console-setup-linux:1.108ubuntu15.2
   Unpacking console-setup-linux (1.152) over (1.108ubuntu15.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.152_all.deb (--unpack):
trying to overwrite '/lib/systemd/system/console-setup.service', which is 
also in package keyboard-configuration 1.108ubuntu15.2
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.2
  InstallationDate: Installed on 2016-10-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10kali1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1635817/+subscriptions

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

[Touch-packages] [Bug 1644808] Re: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: mencoba menimpa '/lib/systemd/system/console-setup.service', yang juga ada dalam paket keyboar

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade:
  mencoba menimpa '/lib/systemd/system/console-setup.service', yang juga
  ada dalam paket keyboard-configuration 1.108ubuntu15.2

Status in console-setup package in Ubuntu:
  New

Bug description:
  closed

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: console-setup-linux 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Fri Nov 25 18:30:12 2016
  ErrorMessage: mencoba menimpa '/lib/systemd/system/console-setup.service', 
yang juga ada dalam paket keyboard-configuration 1.108ubuntu15.2
  InstallationDate: Installed on 2016-11-24 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.15kali1
   apt  1.2.15
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
mencoba menimpa '/lib/systemd/system/console-setup.service', yang juga ada 
dalam paket keyboard-configuration 1.108ubuntu15.2
  UpgradeStatus: Upgraded to kali-rolling on 2016-11-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1644808/+subscriptions

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

[Touch-packages] [Bug 1650157] Re: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: a tentar sobre-escrever '/lib/systemd/system/console-setup.service', que também está no pacote

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade:
  a tentar sobre-escrever '/lib/systemd/system/console-setup.service',
  que também está no pacote keyboard-configuration 1.108ubuntu15.2

Status in console-setup package in Ubuntu:
  New

Bug description:
  erro

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: console-setup-linux 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Thu Dec 15 04:56:42 2016
  ErrorMessage: a tentar sobre-escrever 
'/lib/systemd/system/console-setup.service', que também está no pacote 
keyboard-configuration 1.108ubuntu15.2
  InstallationDate: Installed on 2016-08-24 (112 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.15kali1
   apt  1.2.15
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
a tentar sobre-escrever '/lib/systemd/system/console-setup.service', que também 
está no pacote keyboard-configuration 1.108ubuntu15.2
  UpgradeStatus: Upgraded to kali-rolling on 2016-09-15 (90 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1650157/+subscriptions

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

[Touch-packages] [Bug 1660118] Re: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: se încearcă suprascrierea „/lib/systemd/system/console-setup.service”, care este și în pachetu

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade:
  se încearcă suprascrierea „/lib/systemd/system/console-setup.service”,
  care este și în pachetul keyboard-configuration 1.108ubuntu15.2

Status in console-setup package in Ubuntu:
  New

Bug description:
  Actiunea pachetelor la instalare a esuat

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: console-setup-linux 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Jan 29 12:24:38 2017
  ErrorMessage: se încearcă suprascrierea 
„/lib/systemd/system/console-setup.service”, care este și în pachetul 
keyboard-configuration 1.108ubuntu15.2
  InstallationDate: Installed on 2017-01-22 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.15kali1
   apt  1.2.19
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
se încearcă suprascrierea „/lib/systemd/system/console-setup.service”, care 
este și în pachetul keyboard-configuration 1.108ubuntu15.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1660118/+subscriptions

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

[Touch-packages] [Bug 1585894] Re: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: intentando sobreescribir `/lib/systemd/system/console-setup.service', que está también en el paq

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15 failed to install/upgrade:
  intentando sobreescribir `/lib/systemd/system/console-setup.service',
  que está también en el paquete keyboard-configuration 1.108ubuntu15

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Kali 2016.1
  Package: console-setup-linux 1.108ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu May 26 08:31:12 2016
  ErrorMessage: intentando sobreescribir 
`/lib/systemd/system/console-setup.service', que está también en el paquete 
keyboard-configuration 1.108ubuntu15
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.7
   apt  1.2.12
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: 
intentando sobreescribir `/lib/systemd/system/console-setup.service', que está 
también en el paquete keyboard-configuration 1.108ubuntu15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1585894/+subscriptions

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

[Touch-packages] [Bug 1588998] Re: [master] package console-setup-linux 1.108ubuntu15 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in packa

[Hans Joachim Desserud]

** Summary changed:

- package console-setup-linux 1.108ubuntu15 failed to install/upgrade: trying 
to overwrite '/lib/systemd/system/console-setup.service', which is also in 
package keyboard-configuration 1.108ubuntu15
+ [master] package console-setup-linux 1.108ubuntu15 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15

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

Title:
  [master] package console-setup-linux 1.108ubuntu15 failed to
  install/upgrade: trying to overwrite '/lib/systemd/system/console-
  setup.service', which is also in package keyboard-configuration
  1.108ubuntu15

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Preparing to unpack .../console-setup-linux_1.143_all.deb ...
  Unpacking console-setup-linux (1.143) over (1.108ubuntu15) ...
  dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.143_all.deb (--unpack):
   trying to overwrite '/lib/systemd/system/console-setup.service', which is 
also in package keyboard-configuration 1.108ubuntu15
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Preparing to unpack .../console-setup_1.143_all.deb ...
  Unpacking console-setup (1.143) over (1.108ubuntu15) ...
  Preparing to unpack .../keyboard-configuration_1.143_all.deb ...
  Unpacking keyboard-configuration (1.143) over (1.108ubuntu15) ...
  Preparing to unpack .../xkb-data_2.17-1_all.deb ...
  Unpacking xkb-data (2.17-1) over (2.16-1ubuntu1) ...
  Preparing to unpack .../gcc-6-base_6.1.1-4_amd64.deb ...
  Unpacking gcc-6-base:amd64 (6.1.1-4) over (6.0.1-0ubuntu1) ...
  Processing triggers for systemd (229-4ubuntu6) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for doc-base (0.10.7) ...
  Processing 1 changed doc-base file...
  Errors were encountered while processing:

  ProblemType: Package
  DistroRelease: Kali 2016.1
  Package: console-setup-linux 1.108ubuntu15
  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
  Architecture: amd64
  Date: Fri Jun  3 18:24:08 2016
  DuplicateSignature:
   package:console-setup-linux:1.108ubuntu15
   Unpacking console-setup-linux (1.143) over (1.108ubuntu15) ...
   dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.143_all.deb (--unpack):
trying to overwrite '/lib/systemd/system/console-setup.service', which is 
also in package keyboard-configuration 1.108ubuntu15
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15
  InstallationDate: Installed on 2016-06-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.7
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1588998/+subscriptions

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

[Touch-packages] [Bug 1660762] Re: [Regression] Interface configuration not restored after driver unbind/bind (generic)

[Leann Ogasawara]

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

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

** Changed in: ifupdown (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  [Regression] Interface configuration not restored after driver
  unbind/bind (generic)

Status in ifupdown package in Ubuntu:
  Triaged

Bug description:
  ---Problem Description---
  Interface configuration not restored after driver unbind/bind
   

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4163  mtu 1500
  inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
  inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 13  bytes 1046 (1.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ltciofvtr-s824-lp8:~# cat /etc/network/interfaces
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto ibmveth2
  iface ibmveth2 inet static
address 9.47.68.120
netmask 255.255.240.0
network 9.47.64.0
broadcast 9.47.79.255
gateway 9.47.79.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 9.12.18.2
dns-search pok.stglabs.ibm.com

  auto enP28p96s0f0
  iface enP28p96s0f0 inet static
 address 10.10.10.11
 netmask 255.255.255.0

  root@ltciofvtr-s824-lp8:~# ethtool -i enP28p96s0f0
  driver: be2net
  version: 11.1.0.0
  firmware-version: 10.2.252.1913
  expansion-rom-version: 
  bus-info: 001c:60:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no
  supports-priv-flags: yes

  root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
  /sys/bus/pci/drivers/be2net/unbind

  root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 
  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  remove_id  
uevent  unbind

  root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
  /sys/bus/pci/drivers/be2net/bind

  root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net
  001c:60:00.0  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  
remove_id  uevent  unbind

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4098  mtu 1500
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0
  ifup: interface enP28p96s0f0 already configured

  root@ltciofvtr-s824-lp8:~# ifdown enP28p96s0f0
  RTNETLINK answers: Cannot assign requested address

  root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4163  mtu 1500
  inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
  inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 16  bytes 1344 (1.3 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

   
  ---uname output---
  Linux ltciofvtr-s824-lp8 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 12:52:39 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8286-42A LPAR 

  ---Steps to Reproduce---
   # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind

  # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind
   
  == Comment - Vaishnavi Bhat
  Hi,

  To bind a device to a driver, the device must first not be controlled by any 
other driver. Can you check for 'driver' in the below before you bind ?
   $ tree /sys//bus/pci/devices/001c:60:00.0 

  Thank you.

  == Comment - Murilo Fossa Vicentini
  Just adding some information, this is not a driver specific issue, this was 
also seen with tg3 and i40e adapters . This behavior is a regression when 
compared to Ubuntu 16.04 where the interfaces where properly reconfigured upon 
bind with the information set in /etc/network/interfaces

To manage notifications about this bug go to:

[Touch-packages] Fwd: [Bug 1660762] [NEW] [Regression] Interface configuration not restored after driver unbind/bind (generic)

[Michael Hohnbaum]

Leann,

Could you please have someone from the Kernel team look at this reported
regression.

Thanks.

  Michael


 Forwarded Message 
Subject:[Bug 1660762] [NEW] [Regression] Interface configuration not
restored after driver unbind/bind (generic)
Date:   Tue, 31 Jan 2017 19:49:16 -
From:   Launchpad Bug Tracker <1660...@bugs.launchpad.net>
Reply-To:   Bug 1660762 <1660...@bugs.launchpad.net>
To: michael.hohnb...@canonical.com


bugproxy (bugproxy) has assigned this bug to you for Ubuntu:

---Problem Description---
Interface configuration not restored after driver unbind/bind
 

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4163  mtu 1500
inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 13  bytes 1046 (1.0 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@ltciofvtr-s824-lp8:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ibmveth2
iface ibmveth2 inet static
address 9.47.68.120
netmask 255.255.240.0
network 9.47.64.0
broadcast 9.47.79.255
gateway 9.47.79.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 9.12.18.2
dns-search pok.stglabs.ibm.com

auto enP28p96s0f0
iface enP28p96s0f0 inet static
   address 10.10.10.11
   netmask 255.255.255.0

root@ltciofvtr-s824-lp8:~# ethtool -i enP28p96s0f0
driver: be2net
version: 11.1.0.0
firmware-version: 10.2.252.1913
expansion-rom-version: 
bus-info: 001c:60:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: no
supports-priv-flags: yes

root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
/sys/bus/pci/drivers/be2net/unbind

root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 
001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  remove_id  
uevent  unbind

root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
/sys/bus/pci/drivers/be2net/bind

root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net
001c:60:00.0  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  
remove_id  uevent  unbind

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4098  mtu 1500
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0
ifup: interface enP28p96s0f0 already configured

root@ltciofvtr-s824-lp8:~# ifdown enP28p96s0f0
RTNETLINK answers: Cannot assign requested address

root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4163  mtu 1500
inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 16  bytes 1344 (1.3 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 
---uname output---
Linux ltciofvtr-s824-lp8 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 12:52:39 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = IBM,8286-42A LPAR 
  
---Steps to Reproduce---
 # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind

# echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind
 
== Comment - Vaishnavi Bhat
Hi,

To bind a device to a driver, the device must first not be controlled by any 
other driver. Can you check for 'driver' in the below before you bind ?
 $ tree /sys//bus/pci/devices/001c:60:00.0 

Thank you.

== Comment - Murilo Fossa Vicentini
Just adding some information, this is not a driver specific issue, this was 
also seen with tg3 and i40e adapters . This behavior is a regression when 
compared to Ubuntu 16.04 where the interfaces where properly reconfigured upon 
bind with the information set in /etc/network/interfaces

** Affects: ubuntu
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-151103 severity-high 
targetmilestone-inin1704
-- 
[Regression] Interface configuration not restored after driver 

[Touch-packages] [Bug 1660762] [NEW] [Regression] Interface configuration not restored after driver unbind/bind (generic)

[bugproxy]

Public bug reported:

---Problem Description---
Interface configuration not restored after driver unbind/bind
 

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4163  mtu 1500
inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 13  bytes 1046 (1.0 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@ltciofvtr-s824-lp8:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ibmveth2
iface ibmveth2 inet static
address 9.47.68.120
netmask 255.255.240.0
network 9.47.64.0
broadcast 9.47.79.255
gateway 9.47.79.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 9.12.18.2
dns-search pok.stglabs.ibm.com

auto enP28p96s0f0
iface enP28p96s0f0 inet static
   address 10.10.10.11
   netmask 255.255.255.0

root@ltciofvtr-s824-lp8:~# ethtool -i enP28p96s0f0
driver: be2net
version: 11.1.0.0
firmware-version: 10.2.252.1913
expansion-rom-version: 
bus-info: 001c:60:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: no
supports-priv-flags: yes

root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
/sys/bus/pci/drivers/be2net/unbind

root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 
001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  remove_id  
uevent  unbind

root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
/sys/bus/pci/drivers/be2net/bind

root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net
001c:60:00.0  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  
remove_id  uevent  unbind

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4098  mtu 1500
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0
ifup: interface enP28p96s0f0 already configured

root@ltciofvtr-s824-lp8:~# ifdown enP28p96s0f0
RTNETLINK answers: Cannot assign requested address

root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4163  mtu 1500
inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 16  bytes 1344 (1.3 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 
---uname output---
Linux ltciofvtr-s824-lp8 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 12:52:39 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = IBM,8286-42A LPAR 
  
---Steps to Reproduce---
 # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind

# echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind
 
== Comment - Vaishnavi Bhat
Hi,

To bind a device to a driver, the device must first not be controlled by any 
other driver. Can you check for 'driver' in the below before you bind ?
 $ tree /sys//bus/pci/devices/001c:60:00.0 

Thank you.

== Comment - Murilo Fossa Vicentini
Just adding some information, this is not a driver specific issue, this was 
also seen with tg3 and i40e adapters . This behavior is a regression when 
compared to Ubuntu 16.04 where the interfaces where properly reconfigured upon 
bind with the information set in /etc/network/interfaces

** Affects: ifupdown (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-151103 severity-high 
targetmilestone-inin1704

** Tags added: architecture-ppc64le bugnameltc-151103 severity-high
targetmilestone-inin1704

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

** Package changed: ubuntu => ifupdown (Ubuntu)

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

Title:
  [Regression] Interface configuration not restored after driver
  unbind/bind (generic)

Status in ifupdown package in Ubuntu:
  New

Bug description:
  ---Problem 

[Touch-packages] [Bug 1660762] [NEW] [Regression] Interface configuration not restored after driver unbind/bind (generic)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

---Problem Description---
Interface configuration not restored after driver unbind/bind
 

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4163  mtu 1500
inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 13  bytes 1046 (1.0 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@ltciofvtr-s824-lp8:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ibmveth2
iface ibmveth2 inet static
address 9.47.68.120
netmask 255.255.240.0
network 9.47.64.0
broadcast 9.47.79.255
gateway 9.47.79.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 9.12.18.2
dns-search pok.stglabs.ibm.com

auto enP28p96s0f0
iface enP28p96s0f0 inet static
   address 10.10.10.11
   netmask 255.255.255.0

root@ltciofvtr-s824-lp8:~# ethtool -i enP28p96s0f0
driver: be2net
version: 11.1.0.0
firmware-version: 10.2.252.1913
expansion-rom-version: 
bus-info: 001c:60:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: no
supports-priv-flags: yes

root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
/sys/bus/pci/drivers/be2net/unbind

root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 
001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  remove_id  
uevent  unbind

root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
/sys/bus/pci/drivers/be2net/bind

root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net
001c:60:00.0  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  
remove_id  uevent  unbind

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4098  mtu 1500
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0
ifup: interface enP28p96s0f0 already configured

root@ltciofvtr-s824-lp8:~# ifdown enP28p96s0f0
RTNETLINK answers: Cannot assign requested address

root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4163  mtu 1500
inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 16  bytes 1344 (1.3 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 
---uname output---
Linux ltciofvtr-s824-lp8 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 12:52:39 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = IBM,8286-42A LPAR 
  
---Steps to Reproduce---
 # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind

# echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind
 
== Comment - Vaishnavi Bhat
Hi,

To bind a device to a driver, the device must first not be controlled by any 
other driver. Can you check for 'driver' in the below before you bind ?
 $ tree /sys//bus/pci/devices/001c:60:00.0 

Thank you.

== Comment - Murilo Fossa Vicentini
Just adding some information, this is not a driver specific issue, this was 
also seen with tg3 and i40e adapters . This behavior is a regression when 
compared to Ubuntu 16.04 where the interfaces where properly reconfigured upon 
bind with the information set in /etc/network/interfaces

** Affects: ifupdown (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-151103 severity-high 
targetmilestone-inin1704
-- 
[Regression] Interface configuration not restored after driver unbind/bind 
(generic)
https://bugs.launchpad.net/bugs/1660762
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ifupdown in Ubuntu.

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

[Touch-packages] [Bug 1582414] Re: No HDMI audio on Lenovo pro dock with T440s

[Ray-Ven]

check if this is a dupe of:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1467190/

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

Title:
  No HDMI audio on Lenovo pro dock with T440s

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  pavucontrol shows Display Port/HDMI output as "(unplugged)" and cannot
  be chosen as a sink.  This is only a problem with the dock; audio
  works when plugging HDMI through the laptop's DP input.

  The audio did work with the dock in Ubuntu 14.04.  Did something in
  jack detection change?  Anyway, my work around is to plug a 3.4mm
  audio cable into the dock and power the speakers that way, but it
  would be nice to use the HDMI audio again.

  I would love to have a work around.  I've attached the output from
  alsa-info.sh, just in case this is useful.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  weinberg   2221 F pulseaudio
   /dev/snd/controlC2:  weinberg   2221 F pulseaudio
   /dev/snd/controlC0:  weinberg   2221 F pulseaudio
   /dev/snd/controlC1:  weinberg   2221 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May 16 17:18:06 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-06 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ARA0S100
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1660748] [NEW] when closing libreoffice th whole systems hangs

[martin splinter]

Public bug reported:

Libreoffice closing leads to system freeze, no mouse not keyboard respons
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
BootLog:

CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Jan 31 19:48:49 2017
DistUpgraded: 2016-10-20 11:48:47,660 DEBUG icon theme changed, re-reading
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.6, 4.8.0-32-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-34-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f840]
InstallationDate: Installed on 2016-02-27 (339 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
Lsusb:
 Bus 001 Device 002: ID 8087:8001 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 002: ID 04f2:b446 Chicony Electronics Co., Ltd
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA SATELLITE L50-C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=878f0112-f90e-4fa6-a048-dbb3ecdf5159 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2016-10-20 (103 days ago)
dmi.bios.date: 09/11/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 5.10
dmi.board.name: 06F2
dmi.board.vendor: FF50
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr5.10:bd09/11/2015:svnTOSHIBA:pnSATELLITEL50-C:pvrPSKWNE-05F03CCE:rvnFF50:rn06F2:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE L50-C
dmi.product.version: PSKWNE-05F03CCE
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Tue Jan 31 19:42:25 2017
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: modeset

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


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

** Description changed:

- no
- 
+ Libreoffice closing leads to system freeze, no mouse not keyboard respons
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  BootLog:
-  
+ 
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jan 31 19:48:49 2017
  DistUpgraded: 2016-10-20 11:48:47,660 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox, 5.1.6, 4.8.0-32-generic, x86_64: installed
-  virtualbox, 5.1.6, 4.8.0-34-generic, x86_64: installed
+  virtualbox, 5.1.6, 4.8.0-32-generic, x86_64: installed
+  virtualbox, 5.1.6, 4.8.0-34-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f840]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f840]
  InstallationDate: Installed on 2016-02-27 (339 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
-  Bus 001 Device 002: ID 

[Touch-packages] [Bug 1660573] Re: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04

[Leo Arias]

** Tags added: trusty

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

Title:
  "system is booting up" while trying to log in after installing snapd
  on ubuntu 14.04

Status in snapd:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I've installed snapd on an up-to-date Ubuntu 14.04 server system
  running LTS enablement kernel.

  After toying with snapd and some simple snaps I logged out (so far everything 
was OK).
  I returned to the console after a while (I'm not sure if I logged out but I 
suspect I had to) and I saw the login prompt. After entering my username a line 
was printed "System is booting up" and I was kicked back ot the login prompt 
(It never asked for my password).

  After rebooting the problem went away.

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

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

[Touch-packages] [Bug 1657845] Re: Unity8 snap can't load the testability libraries

[Santiago Baldassin]

Hi Michael, $SNAP/testability/ should be added to LD_LIBRARY_PATH. QT loads the 
testability libraries if either the -testability command line argument is 
passed to QCoreApplication, or if the
QT_LOAD_TESTABILITY environment variable is set

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

Title:
  Unity8 snap can't load the testability libraries

Status in Unity8 Session Snap:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  In order to introspect unity8, the testability libraries should be
  available. Such libraries are provided by autopilot-qt snap through a
  content interface called testability

  unity8 snap should add a plug to such interface so that testability
  libraries get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-session-snap/+bug/1657845/+subscriptions

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

[Touch-packages] [Bug 1657845] Re: Unity8 snap can't load the testability libraries

[Michael Terry]

OK, I've kicked off a snap build/upload for unity8 that adds a plug for
this.  But I'm not sure what the expectation is for actually using the
content interface.

So I plug into the testability slot provided by autopilot-qt.  Which
gets mounted into $SNAP/testability/ -- so far so good.

But what's the expectation for using that?  Add it to LD_LIBRARY_PATH in
the snap's wrapper and load the testability library if that path has
content?

I looked at ubuntu-calculator-app which also plugs into testability, but
it doesn't seem to do anything special once plugged.

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

Title:
  Unity8 snap can't load the testability libraries

Status in Unity8 Session Snap:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  In order to introspect unity8, the testability libraries should be
  available. Such libraries are provided by autopilot-qt snap through a
  content interface called testability

  unity8 snap should add a plug to such interface so that testability
  libraries get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-session-snap/+bug/1657845/+subscriptions

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

[Touch-packages] [Bug 1639896] Re: Backport support for AMD Polaris

[Timo Aaltonen]

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Backport support for AMD Polaris

Status in mesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs.

  Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6
  backported instead

  [Test case]
  Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration

  [Regression potential]
  This is a stable upstream release, and 16.10 ships the same versions so 
regression potential should be minimal.

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

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

[Touch-packages] [Bug 1639896] Re: Backport support for AMD Polaris

[Timo Aaltonen]

mesa 12.0.6 backported instead

** Changed in: mesa (Ubuntu Xenial)
   Status: New => Fix Committed

** Description changed:

- Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes
- bugs.
+ [Impact]
+ Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs.
  
- Mesa needs a bunch of commits backported from 12.0.x.
+ Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6
+ backported instead
+ 
+ [Test case]
+ Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration
+ 
+ [Regression potential]
+ This is a stable upstream release, and 16.10 ships the same versions so 
regression potential should be minimal.

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

Title:
  Backport support for AMD Polaris

Status in mesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New

Bug description:
  [Impact]
  Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs.

  Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6
  backported instead

  [Test case]
  Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration

  [Regression potential]
  This is a stable upstream release, and 16.10 ships the same versions so 
regression potential should be minimal.

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

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

[Touch-packages] [Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial

[Akshay Moghe]

Facing a similar problem on a debootstrap rootfs.

Even after ensuring that the lvm2 package is installed (and hence the
initramfs scripts are present) I still get dropped to a shell in the
initramfs. Running `lvchange -ay` causes the volume to show up and
subsequently the bootup will succeed. I presume "fixing" the script (as
described in comment-8) will fix the problem but I'd like to see a fix
where I'm not forced to re-roll my own initrd.

Any pointers as to why this might be happening?

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

Title:
  LVM boot problem - volumes not activated after upgrade to Xenial

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Soon after upgrade to Xenial (from 15.10) the boot process got broken.
  I'm using LVM for /root swap and other partitions.

  ===
  The current behaviour is:

  When I boot short after the Grub login screen I'm getting log messages
  like:

  ---
  Scanning for Btrfs filesystems
  resume: Could not state the resume device file: '/dev/mapper/VolGroup'
  Please type in the full path...
  ---

  Then I press ENTER, for a few minutes some errors about floppy device
  access are raised (for some reason it tries to scan fd0 when floppy
  drive is empty). And then:

  ---
  Gave up waiting for root device. Common problems: ...
  ...
  ALERT! UUID=xxx-xxx does not exist.
  Dropping to a shell.
  ---

  From the BusyBox shell I managed to recover the boot by issuing "lvm
  vgchange -ay", then exit and then boot continues fine (all LVM file
  systems are successfully mounted).

  ===
  One workaround so far is creating 
/etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange 
-ay". But I'm looking for cleaner solution.

  Boot used to work fine with 15.10. Actually the first boot after
  upgrading to Xenial actually worked OK too, I'm not sure what might
  changed meanwhile (I've been fixing some packages installation since
  mysql server upgrade has failed).

  ===
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

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

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

[Touch-packages] [Bug 1660718] [NEW] /usr/sbin/avahi-daemon:11:avahi_normalize_name:avahi_normalize_name_strdup:avahi_key_new:lookup_handle_cname:lookup_multicast_callback

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: precise trusty wily xenial yakkety

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

Title:
  /usr/sbin/avahi-
  
daemon:11:avahi_normalize_name:avahi_normalize_name_strdup:avahi_key_new:lookup_handle_cname:lookup_multicast_callback

Status in avahi package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1660723] [NEW] /usr/bin/webbrowser-app:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_out_of_range

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: vivid yakkety zesty

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

Title:
  /usr/bin/webbrowser-
  
app:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_out_of_range

Status in webbrowser-app package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1442169] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

[Alex Kindred]

For those who are affected by this and may have found this page by
searching, please login (create an account, if necessary), then click on
the green line of text: "This bug affects xx persons. Does this bug
affect you?".  This is two lines below the title of the bug, at the top
of the page.

Perhaps if more people reported it as affecting them, it will receive
some attention.

As to the bug, get several notifications at startup that cupsd has
crashed, then I receive no more notifications throughout the day &
printing works fine.

It is more that a little disconcerting that this is marked as a security
bug and has been open for 10 months, now.

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-daemon 2.0.2-1ubuntu3
  ProcVersionSignature: Error: [Errno 2] File o directory non esistente: 
'/proc/version_signature'
  Uname: Linux 3.19.0-031900-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CupsErrorLog: W [09/Apr/2015:15:58:06 +0200] CreateProfile failed: 
org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
  Date: Sat Apr  4 11:48:06 2015
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2014-10-23 (167 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lpstat:
   device for Canon-LBP-5975: socket://192.168.1.130
   device for EPSON-Epson-Stylus-Photo-P50: 
usb://EPSON/Stylus%20Photo%20P50?serial=4C43514B3031353929
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   EPSON-Epson-Stylus-Photo-P50: Epson Stylus Photo P50 - CUPS+Gutenprint 
v5.2.10
   Canon-LBP-5975: Canon LBP-3460 Foomatic/pxlmono (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fca89173984 : cmpq   
$0x0,(%rdi)
   PC (0x7fca89173984) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to vivid on 2015-03-31 (8 days ago)
  UserGroups:
   
  dmi.bios.date: 05/15/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0307
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0307:bd05/15/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1660496] Re: Libva upstream project has moved to Github from Freedesktop.org

[Hans Joachim Desserud]

Thanks for reporting.

I've attached a bug watch for the Debian bug report ("Also affects
distribution/package"). Most likely Ubuntu will automatically sync the
package once the url has been updated there. :)

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

** Also affects: libva (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853270
   Importance: Unknown
   Status: Unknown

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

Title:
  Libva upstream project has moved to Github from Freedesktop.org

Status in libva package in Ubuntu:
  New
Status in libva package in Debian:
  Unknown

Bug description:
  Package: libva
  Version: 1.7.3-2

  I'm a maintainer of upstream Libva.  I have moved our project from
  freedesktop.org to github.com.

  Wiki location has moved to: https://01.org/linuxmedia/vaapi

  Libva project has moved to https://github.com/01org/libva

  Use https://github.com/01org/libva/issues/new to file bugs on the
  libva github site

  Packages will need to be updated to pull source from the new github
  repos mentioned above.

  I have submitted this bug upstream to debian packagers of libva
  Bug#853270
  853...@bugs.debian.org

  Thanks,

  Sean

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

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

[Touch-packages] [Bug 1564695] Re: The command "who -m" doesn't work

[Egmont Koblinger]

See https://bugzilla.gnome.org/show_bug.cgi?id=747046.

** Bug watch added: GNOME Bug Tracker #747046
   https://bugzilla.gnome.org/show_bug.cgi?id=747046

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

Title:
  The command "who -m" doesn't work

Status in Ubuntu Kylin:
  New
Status in coreutils package in Ubuntu:
  Incomplete
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  The command "who -m" doesn't work.

  ps: This bug also exists in ubuntu 16.04 x64 Daily build 20160329

  who -m只能没有作用，执行没有任何输出

  
  Steps:
  1. Install the Ubuntu Kylin 16.04 x64 Daily build 20160329
  2. Boot the system
  3. Open terminal, run the command "who -m"
  --Failed. It doesn't work after run the command. It should show the hostname 
and user asociated with stdin.

  Configuration:
  PC: Dell Vostor
  OS: Ubuntu Kylin 16.04 x64 Daily build 20160329

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

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

[Touch-packages] [Bug 1564695] Re: The command "who -m" doesn't work

[Brian Murray]

** Tags added: xenial

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

Title:
  The command "who -m" doesn't work

Status in Ubuntu Kylin:
  New
Status in coreutils package in Ubuntu:
  Incomplete
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  The command "who -m" doesn't work.

  ps: This bug also exists in ubuntu 16.04 x64 Daily build 20160329

  who -m只能没有作用，执行没有任何输出

  
  Steps:
  1. Install the Ubuntu Kylin 16.04 x64 Daily build 20160329
  2. Boot the system
  3. Open terminal, run the command "who -m"
  --Failed. It doesn't work after run the command. It should show the hostname 
and user asociated with stdin.

  Configuration:
  PC: Dell Vostor
  OS: Ubuntu Kylin 16.04 x64 Daily build 20160329

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

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

[Touch-packages] [Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

[Joshua Powers]

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

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

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

Title:
  rsync -u --inplace --partial -a can't resume transfer

Status in rsync package in Ubuntu:
  Triaged

Bug description:
  Suppose you have a file in hostA:

hostA$ ls -l /tmp/files
 -rw-rw-r-- 2 root root 563016 Jan 10 15:01 test.txt

  You download it from the hostB using:

hostB$ rsync -u --inplace --partial -a hostA::files/* .

  If the transfer is aborted, hostB will get only a partial file:

hostB$ ls -l /tmp/files
 -rw-rw-r-- 2 root root   2024 Jan 11 18:00 test.txt

  BUT the ctime/mtime of hostB/test.txt now is NEWER than hostA/test.txt(and 
mtime == ctime). So, if you run the same rsync -u command again:

hostB$ rsync -u --inplace --partial -a hostA::files/* .

  Rsync will SKIP THE FILE, because hostB/test.txt is "newer" than
  hostA/test.txt. So you CAN'T resume using rsync -u command, and you
  will think there are no differences.

  To avoid this bug, rsync must create the file with ctime=mtime=0. And
  if the file already exists before transfer, rsync -u must not change
  his current ctime/mtime. Ctime/mtime must be updated ONLY after the
  transfer was successfully completed.

  Note this is really need because there are scenarios where checksum
  comparison can't be used, only comparison by time. For example, to
  avoid deleting changes made in hostB to test.txt. Also I need to use
  --inplace.

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

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

[Touch-packages] [Bug 1630297] Re: open window titles not shown in launcher menu

[Andrea Azzarone]

** Branch linked: lp:~azzar1/unity8/ql-list-windows

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

Title:
  open window titles not shown in launcher menu

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

Bug description:
  webbrowser-app with multi-window support just landed and works in unity8
  the launcher icon shows dots representing the windows, but when right 
clicking on the launcher icon I expected to see the window titles in the menu 
(like unity7) but these are not shown

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

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

[Touch-packages] [Bug 1622686] Re: double header in 16.10

[Launchpad Bug Tracker]

This bug was fixed in the package humanity-icon-theme - 0.6.11.1

---
humanity-icon-theme (0.6.11.1) yakkety; urgency=medium

  [ David Jordan ]
  * Add hidpi @2 support (LP: #1657863, #1622686)

  [ Iain Lane ]
  * Update Vcs-Bzr for yakkety

 -- David Jordan   Wed, 25 Jan 2017 11:29:32 +

** Changed in: humanity-icon-theme (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  Fix Released
Status in ubiquity source package in Yakkety:
  New

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions

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

[Touch-packages] [Bug 1622686] Update Released

[Adam Conrad]

The verification of the Stable Release Update for humanity-icon-theme
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  Fix Released
Status in ubiquity source package in Yakkety:
  New

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions

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

[Touch-packages] [Bug 1622686] Re: double header in 16.10

[Launchpad Bug Tracker]

This bug was fixed in the package humanity-icon-theme - 0.6.10.1

---
humanity-icon-theme (0.6.10.1) xenial; urgency=medium

  [ David Jordan ]
  * Add hidpi @2 support (LP: #1657863, #1622686)

  [ Iain Lane ]
  * Set Vcs-Bzr for xenial.

 -- David Jordan   Wed, 25 Jan 2017 10:58:57 +

** Changed in: humanity-icon-theme (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  Fix Released
Status in ubiquity source package in Yakkety:
  New

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions

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

[Touch-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens

[Launchpad Bug Tracker]

This bug was fixed in the package humanity-icon-theme - 0.6.11.1

---
humanity-icon-theme (0.6.11.1) yakkety; urgency=medium

  [ David Jordan ]
  * Add hidpi @2 support (LP: #1657863, #1622686)

  [ Iain Lane ]
  * Update Vcs-Bzr for yakkety

 -- David Jordan   Wed, 25 Jan 2017 11:29:32 +

** Changed in: humanity-icon-theme (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  Icons are too big or the wrong icon is shown on hidpi screens

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in humanity-icon-theme source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Humanity icons are sometimes displayed too big on hidpi screens in
  16.04.  On both 16.04 and 16.10, different icons are used on hidpi
  screens than non-hidpi screens.  Sometimes the icons look similar but
  with much thinner strokes, while other times an icon with a different
  metaphor is used.  Users on hidpi screens will notice that icons in
  applications like Nautilus, Transmission, etc. look different (not
  just clearer) on hidpi screens.

  The fix here is to add support for @2 icons to the Humanity theme by
  adding symbolic links for @2 icons and updating the index.theme files
  accordingly.

  We should backport the fix to 16.04 and 16.10, so Humanity icons look
  the same on hidpi screens as non-hidpi screens.

  
  [Test Case]

  Here are a few test cases: 
  1) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi 
screen are much larger.  (This applies to icons on the desktop as well.)
  -The fix should result in icons being the same size on both hidpi and 
lowdpi.
  
  2) Using a computer with a hidpi screen and one with a lowdpi screen running 
Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the 
toolbar uses an icon with a different metaphor on hidpi screens (an up arrow 
emerging from a folder) than on lowdpi screens (a sheet of paper emerging from 
a folder).
  - The fix should result in the "sheet of paper emerging from a folder" 
icon being used here on both hidpi and lowdpi screens.

  3) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons 
look sutbly different.  The strokes in icons on the hidpi screen will be 
visibly thinner on the hidpi screen because icons for bigger scale are used 
(say 48 on hidpi instead of 24) rather than rendering the original size icon at 
a larger resolution.
  - The fix should result in icons that have the same stroke width on hidpi 
and lowdpi screens.  The icons will still be sharper on the hidpi screen, but 
the lines won't be thinner.
  

  [Regression Potential]

  The patch is designed for compatibility where @2 support is not
  available by listing the @2 directories under "ScaledDirectories="
  rather than "Directories=".  However it's possible there could be
  other kinds of issues not found in testing.  If there are any
  omissions or errors in the index.theme, this could cause rendering
  issues for some categories of icons.  Comparing icons on a broad range
  of applications and systems should catch this class of issues.

  Hidpi users may find that their machine looks different after the
  update than it did before.  This is not a regression, but a fix to a
  bug that's been present all along.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions

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

[Touch-packages] [Bug 1657863] Update Released

[Adam Conrad]

The verification of the Stable Release Update for humanity-icon-theme
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Icons are too big or the wrong icon is shown on hidpi screens

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in humanity-icon-theme source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Humanity icons are sometimes displayed too big on hidpi screens in
  16.04.  On both 16.04 and 16.10, different icons are used on hidpi
  screens than non-hidpi screens.  Sometimes the icons look similar but
  with much thinner strokes, while other times an icon with a different
  metaphor is used.  Users on hidpi screens will notice that icons in
  applications like Nautilus, Transmission, etc. look different (not
  just clearer) on hidpi screens.

  The fix here is to add support for @2 icons to the Humanity theme by
  adding symbolic links for @2 icons and updating the index.theme files
  accordingly.

  We should backport the fix to 16.04 and 16.10, so Humanity icons look
  the same on hidpi screens as non-hidpi screens.

  
  [Test Case]

  Here are a few test cases: 
  1) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi 
screen are much larger.  (This applies to icons on the desktop as well.)
  -The fix should result in icons being the same size on both hidpi and 
lowdpi.
  
  2) Using a computer with a hidpi screen and one with a lowdpi screen running 
Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the 
toolbar uses an icon with a different metaphor on hidpi screens (an up arrow 
emerging from a folder) than on lowdpi screens (a sheet of paper emerging from 
a folder).
  - The fix should result in the "sheet of paper emerging from a folder" 
icon being used here on both hidpi and lowdpi screens.

  3) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons 
look sutbly different.  The strokes in icons on the hidpi screen will be 
visibly thinner on the hidpi screen because icons for bigger scale are used 
(say 48 on hidpi instead of 24) rather than rendering the original size icon at 
a larger resolution.
  - The fix should result in icons that have the same stroke width on hidpi 
and lowdpi screens.  The icons will still be sharper on the hidpi screen, but 
the lines won't be thinner.
  

  [Regression Potential]

  The patch is designed for compatibility where @2 support is not
  available by listing the @2 directories under "ScaledDirectories="
  rather than "Directories=".  However it's possible there could be
  other kinds of issues not found in testing.  If there are any
  omissions or errors in the index.theme, this could cause rendering
  issues for some categories of icons.  Comparing icons on a broad range
  of applications and systems should catch this class of issues.

  Hidpi users may find that their machine looks different after the
  update than it did before.  This is not a regression, but a fix to a
  bug that's been present all along.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions

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

[Touch-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens

[Launchpad Bug Tracker]

This bug was fixed in the package humanity-icon-theme - 0.6.10.1

---
humanity-icon-theme (0.6.10.1) xenial; urgency=medium

  [ David Jordan ]
  * Add hidpi @2 support (LP: #1657863, #1622686)

  [ Iain Lane ]
  * Set Vcs-Bzr for xenial.

 -- David Jordan   Wed, 25 Jan 2017 10:58:57 +

** Changed in: humanity-icon-theme (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Icons are too big or the wrong icon is shown on hidpi screens

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in humanity-icon-theme source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Humanity icons are sometimes displayed too big on hidpi screens in
  16.04.  On both 16.04 and 16.10, different icons are used on hidpi
  screens than non-hidpi screens.  Sometimes the icons look similar but
  with much thinner strokes, while other times an icon with a different
  metaphor is used.  Users on hidpi screens will notice that icons in
  applications like Nautilus, Transmission, etc. look different (not
  just clearer) on hidpi screens.

  The fix here is to add support for @2 icons to the Humanity theme by
  adding symbolic links for @2 icons and updating the index.theme files
  accordingly.

  We should backport the fix to 16.04 and 16.10, so Humanity icons look
  the same on hidpi screens as non-hidpi screens.

  
  [Test Case]

  Here are a few test cases: 
  1) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi 
screen are much larger.  (This applies to icons on the desktop as well.)
  -The fix should result in icons being the same size on both hidpi and 
lowdpi.
  
  2) Using a computer with a hidpi screen and one with a lowdpi screen running 
Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the 
toolbar uses an icon with a different metaphor on hidpi screens (an up arrow 
emerging from a folder) than on lowdpi screens (a sheet of paper emerging from 
a folder).
  - The fix should result in the "sheet of paper emerging from a folder" 
icon being used here on both hidpi and lowdpi screens.

  3) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons 
look sutbly different.  The strokes in icons on the hidpi screen will be 
visibly thinner on the hidpi screen because icons for bigger scale are used 
(say 48 on hidpi instead of 24) rather than rendering the original size icon at 
a larger resolution.
  - The fix should result in icons that have the same stroke width on hidpi 
and lowdpi screens.  The icons will still be sharper on the hidpi screen, but 
the lines won't be thinner.
  

  [Regression Potential]

  The patch is designed for compatibility where @2 support is not
  available by listing the @2 directories under "ScaledDirectories="
  rather than "Directories=".  However it's possible there could be
  other kinds of issues not found in testing.  If there are any
  omissions or errors in the index.theme, this could cause rendering
  issues for some categories of icons.  Comparing icons on a broad range
  of applications and systems should catch this class of issues.

  Hidpi users may find that their machine looks different after the
  update than it did before.  This is not a regression, but a fix to a
  bug that's been present all along.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions

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

[Touch-packages] [Bug 1660645] Re: Connecting to unplugged ethernet network after suspend

[Vaclav Petras]

Forgot to include similar bug reports #59981 and #165004.

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

Title:
  Connecting to unplugged ethernet network after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  1. Plug in an Ethernet cable to get Internet connection. (Wireless 
connections also present.)
  2. Suspend the laptop.
  3. Unplug the Ethernet cable. (And move to different location with Wi-Fi 
only.)
  4. Wake up from suspend.
  5. Wait few moments to connect to a known Wi-Fi network.
  6. Try using the Internet.

  The Internet doesn't work, pages load indefinitely. The tray icon
  shows the wireless sign in the "connecting" state (animation). The
  tray menu shows one Ethernet connection. When I disconnect that one
  the Internet connection starts working immediately.

  The was not happening with 15.10 but happens to me regularly after
  upgrade to 16.04. I have Docker daemon running.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 31 09:46:54 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.139.120.1 dev wlp2s0  proto static  metric 600 
   10.139.120.0/21 dev wlp2s0  proto kernel  scope link  src 10.139.125.237  
metric 600 
   152.1.14.69 via 10.139.120.1 dev wlp2s0  proto dhcp  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-12-23 (38 days ago)
  nmcli-dev:
   DEVICETYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   docker0   bridgeconnected /org/freedesktop/NetworkManager/Devices/2  
docker0 d4fab1b4-08e4-45f6-a74b-0e4e4aa8898f  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp2s0wifi  connected /org/freedesktop/NetworkManager/Devices/3  
ncsu187812f8-932b-4c5a-9bf8-ec5ee97a95e9  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp1s0f1  ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/0  
--  ----
 
   loloopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1551274] Re: creating SRP file crashes openssl

[Launchpad Bug Tracker]

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

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

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

Title:
  creating SRP file crashes openssl

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  the following, with "test", "test" as passwords, make openssl crash:

  touch passwd.srpv ;  openssl srp -srpvfile passwd.srpv -add user

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2f-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb 29 16:15:20 2016
  InstallationDate: Installed on 2015-12-02 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151027)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1607169] Re: Youtube Videos in Video Scope are not working

[Olivier Tilloy]

Good. So that looks like maybe the authentication token had expired, and
for some reason wasn’t being renewed automatically. Someone more
familiar with the inners of the scope needs to look into it and comment.

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

Title:
  Youtube Videos in Video Scope are not working

Status in YouTube Scope:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  I have a Meizu MX4 running the OTA-12 update as of this morning and
  since OTA-9 I think clicking on a youtube in the video, music or
  youtube scope doesn't do anything. Normally one would get a preview of
  the youtube video along with a discription below and then you could
  click the video again and the web browser would start up and play the
  video. This still works for videos on Vimeo but not on Youtube. This
  has been broken for months now. It also happens as mention in the
  Music scope and Youtube scope. I was hopng that this would have been
  fixed with the OTA-12 update since this update focused on bugs and
  that you now could play videos directly from the Video scope. But
  sadly no... Has there been an API change with Youtube that caused this
  breakage maybe?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scope-youtube/+bug/1607169/+subscriptions

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

[Touch-packages] [Bug 1660642] [NEW] how to send data over BT SCO connection handle

[raviraj]

Public bug reported:

I have created bluetooth ACL and SCO connection using BT HCI commands.
My ACL connection handle is 0x0001 and SCO connection handle is 0x0008.
I want to send data over SCO connection using bluez API's. Please Help
me with the same.

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

** Description changed:

- I have created ACL and SCO connection using HCI commands. My ACL handle
- is 0x0001 and SCO handle is 0x0008. I want to send data over SCO
- connection using bluez API's. Please Help me with the same.
+ I have created bluetooth ACL and SCO connection using BT HCI commands.
+ My ACL connection handle is 0x0001 and SCO connection handle is 0x0008.
+ I want to send data over SCO connection using bluez API's. Please Help
+ me with the same.

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

Title:
  how to send data over BT SCO connection handle

Status in bluez package in Ubuntu:
  New

Bug description:
  I have created bluetooth ACL and SCO connection using BT HCI commands.
  My ACL connection handle is 0x0001 and SCO connection handle is
  0x0008. I want to send data over SCO connection using bluez API's.
  Please Help me with the same.

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

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

[Touch-packages] [Bug 1660645] [NEW] Connecting to unplugged ethernet network after suspend

[Vaclav Petras]

Public bug reported:

1. Plug in an Ethernet cable to get Internet connection. (Wireless connections 
also present.)
2. Suspend the laptop.
3. Unplug the Ethernet cable. (And move to different location with Wi-Fi only.)
4. Wake up from suspend.
5. Wait few moments to connect to a known Wi-Fi network.
6. Try using the Internet.

The Internet doesn't work, pages load indefinitely. The tray icon shows
the wireless sign in the "connecting" state (animation). The tray menu
shows one Ethernet connection. When I disconnect that one the Internet
connection starts working immediately.

The was not happening with 15.10 but happens to me regularly after
upgrade to 16.04. I have Docker daemon running.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 31 09:46:54 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 10.139.120.1 dev wlp2s0  proto static  metric 600 
 10.139.120.0/21 dev wlp2s0  proto kernel  scope link  src 10.139.125.237  
metric 600 
 152.1.14.69 via 10.139.120.1 dev wlp2s0  proto dhcp  metric 600 
 169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2016-12-23 (38 days ago)
nmcli-dev:
 DEVICETYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 docker0   bridgeconnected /org/freedesktop/NetworkManager/Devices/2  
docker0 d4fab1b4-08e4-45f6-a74b-0e4e4aa8898f  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 wlp2s0wifi  connected /org/freedesktop/NetworkManager/Devices/3  
ncsu187812f8-932b-4c5a-9bf8-ec5ee97a95e9  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 enp1s0f1  ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/0  
--  ----
 
 loloopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

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

Title:
  Connecting to unplugged ethernet network after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  1. Plug in an Ethernet cable to get Internet connection. (Wireless 
connections also present.)
  2. Suspend the laptop.
  3. Unplug the Ethernet cable. (And move to different location with Wi-Fi 
only.)
  4. Wake up from suspend.
  5. Wait few moments to connect to a known Wi-Fi network.
  6. Try using the Internet.

  The Internet doesn't work, pages load indefinitely. The tray icon
  shows the wireless sign in the "connecting" state (animation). The
  tray menu shows one Ethernet connection. When I disconnect that one
  the Internet connection starts working immediately.

  The was not happening with 15.10 but happens to me regularly after
  upgrade to 16.04. I have Docker daemon running.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 31 09:46:54 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.139.120.1 dev wlp2s0  proto static  metric 600 
   10.139.120.0/21 dev wlp2s0  proto kernel  scope link  src 10.139.125.237  
metric 600 
   152.1.14.69 via 10.139.120.1 dev wlp2s0  proto dhcp  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-12-23 (38 days ago)
  nmcli-dev:
   DEVICETYPE  STATE 

Re: [Touch-packages] [Bug 1607169] Re: Youtube Videos in Video Scope are not working

[André Fettouhi]

Yes, if you log out of youtube and try again then the preview shows up
and can tap it and the browser opens up.


Den 31-01-2017 kl. 13:11 skrev Olivier Tilloy:
> Looks like an HTTP request issued to youtube to get the subscribe id for a 
> video times out.
> I’m not familiar with that code, just had a quick look at it. This is the 
> authenticated code path. When not logged in to youtube, a different code path 
> is used. Can you try logging out from the scope, and see if that improves 
> things?
>

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

Title:
  Youtube Videos in Video Scope are not working

Status in YouTube Scope:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  I have a Meizu MX4 running the OTA-12 update as of this morning and
  since OTA-9 I think clicking on a youtube in the video, music or
  youtube scope doesn't do anything. Normally one would get a preview of
  the youtube video along with a discription below and then you could
  click the video again and the web browser would start up and play the
  video. This still works for videos on Vimeo but not on Youtube. This
  has been broken for months now. It also happens as mention in the
  Music scope and Youtube scope. I was hopng that this would have been
  fixed with the OTA-12 update since this update focused on bugs and
  that you now could play videos directly from the Video scope. But
  sadly no... Has there been an API change with Youtube that caused this
  breakage maybe?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scope-youtube/+bug/1607169/+subscriptions

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

[Touch-packages] [Bug 1660604] Re: Wrong import statement for Menu/MenuGroup

[Adnane Belmadiaf]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Adnane Belmadiaf (daker)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

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

Title:
  Wrong import statement for Menu/MenuGroup

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The docs says that the import statement for Menu/MenuGroup is "import
  Ubuntu.Components 1.3", the correct import is "import
  Ubuntu.Components.Labs 1.0"

  https://developer.ubuntu.com/api/apps/qml/sdk-15.04.6/Ubuntu.Components.Menu/
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.6/Ubuntu.Components.MenuGroup/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1660604/+subscriptions

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

[Touch-packages] [Bug 1660633] [NEW] /usr/bin/ucfr: line ... : [: : integer expression expected

[Andy]

Public bug reported:

I've had a reoccurring issue: https://ubuntuforums.org/showthread.php?t=2350682
Running: ucf_3.0036_all.deb

http://askubuntu.com/questions/875415/usr-bin-ucfr-errors-integer-expression-expected
http://serverfault.com/questions/827873/grub-pc-update-fail-dev-sda-ext2-doesnt-support-embedding

I don't know why ucfr is erroring out but the accumulated errors are now
enough to stall priority packages which I feel hamstrung about. I've
reinstalled the ucf package and danced around the issue enough.

Any maintainers have a shot in the dark for why this would be happening?

Discussion:
https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737

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

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

Title:
  /usr/bin/ucfr: line ... : [: : integer expression expected

Status in ucf package in Ubuntu:
  New

Bug description:
  I've had a reoccurring issue: 
https://ubuntuforums.org/showthread.php?t=2350682
  Running: ucf_3.0036_all.deb

  
http://askubuntu.com/questions/875415/usr-bin-ucfr-errors-integer-expression-expected
  
http://serverfault.com/questions/827873/grub-pc-update-fail-dev-sda-ext2-doesnt-support-embedding

  I don't know why ucfr is erroring out but the accumulated errors are
  now enough to stall priority packages which I feel hamstrung about.
  I've reinstalled the ucf package and danced around the issue enough.

  Any maintainers have a shot in the dark for why this would be
  happening?

  Discussion:
  https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737

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

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

[Touch-packages] [Bug 1633781] Re: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of

[Launchpad Bug Tracker]

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

** Changed in: qt4-x11 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/etc/xdg/Trolltech.conf', which is
  different from other instances of package libqtcore4:i386

Status in qt4-x11 package in Ubuntu:
  Confirmed

Bug description:
  I dowloaded the abckage skype-ubuntu-precise_4.3.0.37-1_i386.deb from
  skype webpage and installed. during the installation my ubuntu sent me
  the popup of error report although the installation claimed to be
  successfull

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Oct 16 09:26:43 2016
  DuplicateSignature:
   package:libqtcore4:4:4.8.7+dfsg-5ubuntu2
   Unpacking libqtcore4:i386 (4:4.8.7+dfsg-5ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-5ubuntu2_i386.deb (--unpack):
trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different 
from other instances of package libqtcore4:i386
  ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:i386
  InstallationDate: Installed on 2016-03-14 (215 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from 
other instances of package libqtcore4:i386
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (174 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1633781/+subscriptions

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

[Touch-packages] [Bug 1649077] Re: [regression] OSK appears blank and/or flickers in the lock screen

[Gerry Boland]

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

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

Title:
  [regression] OSK appears blank and/or flickers in the lock screen

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in QtMir:
  Fix Released
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  After using OTA-14 a while, the OSK starts to exhibit a strange
  behaviour.

  1. It appears blank after a while in the lock screen. You can still
  press randomly which then makes the OSK to appear fully. When you
  press a character again it starts to flicker.

  2. OSK starts to flicker similar to bug #1590765 which was fixed in
  OTA-12. It seems to have resurfaced in OTA-14.

  Systems Info:
  OTA-14 Stable Channel
  Devices: E4.5, E5

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

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

[Touch-packages] [Bug 1660576] Re: CI builds sometimes fail with cp error

[Albert Astals Cid]

** Branch linked: lp:~aacid/unity8/fix-1660576

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

Title:
  CI builds sometimes fail with cp error

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Example 
  
https://unity8-jenkins.ubuntu.com/job/build-2-binpkg/arch=armhf,release=zesty/3888/console

  Failed with 
  cp: cannot create regular file 
'/<>/unity8-8.15+17.04.20170124+fetch4044bzr2786/obj-arm-linux-gnueabihf/tests/mocks/Unity/qmldir':
 File exists

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

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

[Touch-packages] [Bug 1564695] Re: The command "who -m" doesn't work

[Launchpad Bug Tracker]

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

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Confirmed

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

Title:
  The command "who -m" doesn't work

Status in Ubuntu Kylin:
  New
Status in coreutils package in Ubuntu:
  Incomplete
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  The command "who -m" doesn't work.

  ps: This bug also exists in ubuntu 16.04 x64 Daily build 20160329

  who -m只能没有作用，执行没有任何输出

  
  Steps:
  1. Install the Ubuntu Kylin 16.04 x64 Daily build 20160329
  2. Boot the system
  3. Open terminal, run the command "who -m"
  --Failed. It doesn't work after run the command. It should show the hostname 
and user asociated with stdin.

  Configuration:
  PC: Dell Vostor
  OS: Ubuntu Kylin 16.04 x64 Daily build 20160329

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

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

[Touch-packages] [Bug 1564695] Re: The command "who -m" doesn't work

[Launchpad Bug Tracker]

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

** Changed in: vte2.91 (Ubuntu)
   Status: New => Confirmed

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

Title:
  The command "who -m" doesn't work

Status in Ubuntu Kylin:
  New
Status in coreutils package in Ubuntu:
  Incomplete
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  The command "who -m" doesn't work.

  ps: This bug also exists in ubuntu 16.04 x64 Daily build 20160329

  who -m只能没有作用，执行没有任何输出

  
  Steps:
  1. Install the Ubuntu Kylin 16.04 x64 Daily build 20160329
  2. Boot the system
  3. Open terminal, run the command "who -m"
  --Failed. It doesn't work after run the command. It should show the hostname 
and user asociated with stdin.

  Configuration:
  PC: Dell Vostor
  OS: Ubuntu Kylin 16.04 x64 Daily build 20160329

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

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

[Touch-packages] [Bug 1564695] Re: The command "who -m" doesn't work

[Mikma]

The source of the problem is gnome-terminal in 16.04 which doesn't
update wtmp. It broke a script of mine.

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

** Also affects: vte2.91 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  The command "who -m" doesn't work

Status in Ubuntu Kylin:
  New
Status in coreutils package in Ubuntu:
  Incomplete
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  The command "who -m" doesn't work.

  ps: This bug also exists in ubuntu 16.04 x64 Daily build 20160329

  who -m只能没有作用，执行没有任何输出

  
  Steps:
  1. Install the Ubuntu Kylin 16.04 x64 Daily build 20160329
  2. Boot the system
  3. Open terminal, run the command "who -m"
  --Failed. It doesn't work after run the command. It should show the hostname 
and user asociated with stdin.

  Configuration:
  PC: Dell Vostor
  OS: Ubuntu Kylin 16.04 x64 Daily build 20160329

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Girasola]

Thanks #8, problem solved :-)

-- 
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 1660573] Re: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04

[Thomas Voß]

** Changed in: snapd
   Status: New => Confirmed

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

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

Title:
  "system is booting up" while trying to log in after installing snapd
  on ubuntu 14.04

Status in snapd:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I've installed snapd on an up-to-date Ubuntu 14.04 server system
  running LTS enablement kernel.

  After toying with snapd and some simple snaps I logged out (so far everything 
was OK).
  I returned to the console after a while (I'm not sure if I logged out but I 
suspect I had to) and I saw the login prompt. After entering my username a line 
was printed "System is booting up" and I was kicked back ot the login prompt 
(It never asked for my password).

  After rebooting the problem went away.

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

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