[Touch-packages] [Bug 1722427] Re: [error-report]error occurs when reading /etc/profile

2017-10-13 Thread handsome_feng
Hi, Gunnar, I have modified the 22_fcitx.rc in ubuntu kylin as you
mentioned, and It worked, Thank you!

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

Title:
  [error-report]error occurs when reading /etc/profile

Status in Ubuntu Kylin:
  Confirmed
Status in fcitx package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  system:artful-1008-64bit

  process:
  1.start the system
  2.put in password
  3.after the log in screen, an error message shows up, check the attached file

  expectation:
  no error message shows up after log in

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

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


[Touch-packages] [Bug 1701289] Re: gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat()

2017-10-13 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Confirmed

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  gnome-shell crashed with signal 5 in XIGetClientPointer() from
  gdk_x11_display_get_default_seat()

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/fb179bc620e408d216f4b8700f714e6ebb2ebf09

  ---

  cant login to gnome desktop

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 29 16:14:29 2017
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-03-25 (96 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XIGetClientPointer () at /usr/lib/x86_64-linux-gnu/libXi.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1355137] Re: gtk2 theme version improvements for high-dpi screens

2017-10-13 Thread Launchpad Bug Tracker
[Expired for ubuntu-themes (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gtk2 theme version improvements for high-dpi screens

Status in ubuntu-themes package in Ubuntu:
  Expired

Bug description:
  GTK2 applications are still widespread and the lack of resolution
  independence poses significant usability problems, for example for
  clicking radio buttons or checkboxes.

  By editing the gtkrc file one can at least mitigate a majority of
  issues. By doubling dimensions (like widths, heights, not border-
  widths),  the following controls can be made usable: radio buttons,
  checkboxes, scrollbars, expand/collapse triangles in trees. While this
  is nothing like complete high-dpi support, still a significant partial
  improvement can be achieved.

  Users of high-dpi screens should not have to suffer under the current
  default, or have to patch the theme manually. It would be good to
  implement a way that when the scaling factor is >= 2.0, as many GTK 2
  widgets as possible are rendered with larger dimensions, be it by
  theme engine or by switching the theme.

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

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


[Touch-packages] [Bug 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain

2017-10-13 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.125ubuntu12

---
initramfs-tools (0.125ubuntu12) artful; urgency=medium

  * hook-functions: include vmd driver. (LP: #1703339)

 -- Seth Forshee   Fri, 13 Oct 2017 14:09:26
-0500

** Changed in: initramfs-tools (Ubuntu Artful)
   Status: New => Fix Released

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

Title:
  Unable to install Ubuntu on the NVMe disk under VMD PCI domain

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Artful:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  It is not possible to install Ubuntu on the NVMe disk under VMD
  (Volume Management Device) PCI domain. The disk is not visible in the
  installer because VMD module is not available at this stage.

  I'm raising it against kernel package as I have impression VMD module
  must be included in linux-image dpkg package, not linux-image-extra.

  Please also assure VMD module gets included in initramfs by installer
  (if necessary).

  For more information about VMD please see bug 1591806.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.10.0.26.28
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   tomasz 1659 F...m pulseaudio
   /dev/snd/controlC0:  tomasz 1659 F pulseaudio
   /dev/snd/timer:  tomasz 1659 f pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jul 10 10:40:20 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-07-06 (3 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170702)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Touch-packages] [Bug 1723562] Re: Kernels get stuck in "manual" state and fail to autoremove after disk full condition

2017-10-13 Thread Steve Langasek
I don't believe this occurs with xenial and later.

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

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

Title:
  Kernels get stuck in "manual" state and fail to autoremove after disk
  full condition

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  I use unattended-upgrades to install new kernels (I think probably
  from the security pocket). I believe this is the default. I also don't
  run autoremove automatically, which I believe is also the default.

  I just recovered a system that had been stuck in a disk full state for
  a while without me noticing because, without an automated autoremove,
  unattended-upgrades had filled my system full of kernels.

  Expected: "apt-get --purge autoremove" will remove all unused kernels,
  perhaps with a bit of coaxing from me to provide enough free space for
  dpkg and apt to function.

  Actual: "apt-get --purge autoremove" left many extra kernels
  installed.

  It seems that the reason is that apt considered most of the
  automatically installed kernels as being marked for manual install. I
  suspect that this is because apt wasn't able to mark kernels as
  automatically installed because it didn't have enough space to do so
  at the time, and without such a mark, it assumes manual.

  Workaround: use "apt-mark" to mark all kernels as automatic once
  enough space is available. Then run "/etc/kernel/postinst.d/apt-auto-
  removal" manually. Then "apt-get --purge autoremove" works.

  I'm not sure how we might approach fixing this. But I think it's a
  poor UX that Ubuntu currently relies on autoremove to remove old
  kernels to prevent the disk filling up, but this fails to work in some
  cases when the disk does fill up.

  I'm tagging such bugs "kernel-autoremove" to help us identify what
  needs fixing to make kernel autoremovals work completely to fix this
  UX issue.

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

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


[Touch-packages] [Bug 1723562] [NEW] Kernels get stuck in "manual" state and fail to autoremove after disk full condition

2017-10-13 Thread Robie Basak
Public bug reported:

I use unattended-upgrades to install new kernels (I think probably from
the security pocket). I believe this is the default. I also don't run
autoremove automatically, which I believe is also the default.

I just recovered a system that had been stuck in a disk full state for a
while without me noticing because, without an automated autoremove,
unattended-upgrades had filled my system full of kernels.

Expected: "apt-get --purge autoremove" will remove all unused kernels,
perhaps with a bit of coaxing from me to provide enough free space for
dpkg and apt to function.

Actual: "apt-get --purge autoremove" left many extra kernels installed.

It seems that the reason is that apt considered most of the
automatically installed kernels as being marked for manual install. I
suspect that this is because apt wasn't able to mark kernels as
automatically installed because it didn't have enough space to do so at
the time, and without such a mark, it assumes manual.

Workaround: use "apt-mark" to mark all kernels as automatic once enough
space is available. Then run "/etc/kernel/postinst.d/apt-auto-removal"
manually. Then "apt-get --purge autoremove" works.

I'm not sure how we might approach fixing this. But I think it's a poor
UX that Ubuntu currently relies on autoremove to remove old kernels to
prevent the disk filling up, but this fails to work in some cases when
the disk does fill up.

I'm tagging such bugs "kernel-autoremove" to help us identify what needs
fixing to make kernel autoremovals work completely to fix this UX issue.

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


** Tags: kernel-autoremove

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

Title:
  Kernels get stuck in "manual" state and fail to autoremove after disk
  full condition

Status in apt package in Ubuntu:
  New

Bug description:
  I use unattended-upgrades to install new kernels (I think probably
  from the security pocket). I believe this is the default. I also don't
  run autoremove automatically, which I believe is also the default.

  I just recovered a system that had been stuck in a disk full state for
  a while without me noticing because, without an automated autoremove,
  unattended-upgrades had filled my system full of kernels.

  Expected: "apt-get --purge autoremove" will remove all unused kernels,
  perhaps with a bit of coaxing from me to provide enough free space for
  dpkg and apt to function.

  Actual: "apt-get --purge autoremove" left many extra kernels
  installed.

  It seems that the reason is that apt considered most of the
  automatically installed kernels as being marked for manual install. I
  suspect that this is because apt wasn't able to mark kernels as
  automatically installed because it didn't have enough space to do so
  at the time, and without such a mark, it assumes manual.

  Workaround: use "apt-mark" to mark all kernels as automatic once
  enough space is available. Then run "/etc/kernel/postinst.d/apt-auto-
  removal" manually. Then "apt-get --purge autoremove" works.

  I'm not sure how we might approach fixing this. But I think it's a
  poor UX that Ubuntu currently relies on autoremove to remove old
  kernels to prevent the disk filling up, but this fails to work in some
  cases when the disk does fill up.

  I'm tagging such bugs "kernel-autoremove" to help us identify what
  needs fixing to make kernel autoremovals work completely to fix this
  UX issue.

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

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


[Touch-packages] [Bug 1723562] Re: Kernels get stuck in "manual" state and fail to autoremove after disk full condition

2017-10-13 Thread Robie Basak
Incidentally I noticed this on an EOL installation in a VM, but I have
no reason to think that anything has changed.

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

Title:
  Kernels get stuck in "manual" state and fail to autoremove after disk
  full condition

Status in apt package in Ubuntu:
  New

Bug description:
  I use unattended-upgrades to install new kernels (I think probably
  from the security pocket). I believe this is the default. I also don't
  run autoremove automatically, which I believe is also the default.

  I just recovered a system that had been stuck in a disk full state for
  a while without me noticing because, without an automated autoremove,
  unattended-upgrades had filled my system full of kernels.

  Expected: "apt-get --purge autoremove" will remove all unused kernels,
  perhaps with a bit of coaxing from me to provide enough free space for
  dpkg and apt to function.

  Actual: "apt-get --purge autoremove" left many extra kernels
  installed.

  It seems that the reason is that apt considered most of the
  automatically installed kernels as being marked for manual install. I
  suspect that this is because apt wasn't able to mark kernels as
  automatically installed because it didn't have enough space to do so
  at the time, and without such a mark, it assumes manual.

  Workaround: use "apt-mark" to mark all kernels as automatic once
  enough space is available. Then run "/etc/kernel/postinst.d/apt-auto-
  removal" manually. Then "apt-get --purge autoremove" works.

  I'm not sure how we might approach fixing this. But I think it's a
  poor UX that Ubuntu currently relies on autoremove to remove old
  kernels to prevent the disk filling up, but this fails to work in some
  cases when the disk does fill up.

  I'm tagging such bugs "kernel-autoremove" to help us identify what
  needs fixing to make kernel autoremovals work completely to fix this
  UX issue.

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

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


[Touch-packages] [Bug 1723562] Re: Kernels get stuck in "manual" state and fail to autoremove after disk full condition

2017-10-13 Thread Robie Basak
Actually let's let someone else confirm this.

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

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

Title:
  Kernels get stuck in "manual" state and fail to autoremove after disk
  full condition

Status in apt package in Ubuntu:
  New

Bug description:
  I use unattended-upgrades to install new kernels (I think probably
  from the security pocket). I believe this is the default. I also don't
  run autoremove automatically, which I believe is also the default.

  I just recovered a system that had been stuck in a disk full state for
  a while without me noticing because, without an automated autoremove,
  unattended-upgrades had filled my system full of kernels.

  Expected: "apt-get --purge autoremove" will remove all unused kernels,
  perhaps with a bit of coaxing from me to provide enough free space for
  dpkg and apt to function.

  Actual: "apt-get --purge autoremove" left many extra kernels
  installed.

  It seems that the reason is that apt considered most of the
  automatically installed kernels as being marked for manual install. I
  suspect that this is because apt wasn't able to mark kernels as
  automatically installed because it didn't have enough space to do so
  at the time, and without such a mark, it assumes manual.

  Workaround: use "apt-mark" to mark all kernels as automatic once
  enough space is available. Then run "/etc/kernel/postinst.d/apt-auto-
  removal" manually. Then "apt-get --purge autoremove" works.

  I'm not sure how we might approach fixing this. But I think it's a
  poor UX that Ubuntu currently relies on autoremove to remove old
  kernels to prevent the disk filling up, but this fails to work in some
  cases when the disk does fill up.

  I'm tagging such bugs "kernel-autoremove" to help us identify what
  needs fixing to make kernel autoremovals work completely to fix this
  UX issue.

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

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


[Touch-packages] [Bug 1597377] Re: Malformed 01autoremove-kernels apt file

2017-10-13 Thread Robie Basak
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

I was just looking for kernel-related apt bugs and came across this
report.

It seems likely to me, given that it's had only one affected user in
this time, that this was caused by filesystem corruption or a hardware
problem on the reporter's computer and not by a bug in Ubuntu. So I'm
marking this bug as Incomplete to make it clear that no progress can be
made on this bug by Ubuntu developers.

If you believe this really is a bug in Ubuntu rather than a problem on
your system, please explain and set the bug status back to New. Thanks!

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

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

Title:
  Malformed 01autoremove-kernels apt file

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After updating my system earlier today, I wanted to perform an apt
  search and it failed with this error:

  E: Syntax error /etc/apt/apt.conf.d/01autoremove-kernels:20: Malformed
  tag

  Upon inspecting the file I saw this malformed line (2nd line):

 "^.*-modules-4\.4\.0-24-generic$";
   ^@h½N^H<88>ÿÿodules-4\.4\.0-28-generic$";
 "^.*-kernel-4\.4\.0-24-generic$";

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

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


[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

2017-10-13 Thread Robie Basak
** Tags added: kernel-autoremove

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  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
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

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


[Touch-packages] [Bug 1637797] Re: kernel referred to by /*.old autoremoved

2017-10-13 Thread Robie Basak
** Tags added: kernel-autoremove

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

Title:
  kernel referred to by /*.old autoremoved

Status in apt package in Ubuntu:
  New

Bug description:
  apt-get suggests to remove and, with autoremove command, actually
  removes previous kernel referenced by /*.old links and breaks the
  ability to boot with a previous kernel. Kernel referenced by /*.old
  may not be autoremoved.

  # apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-3.13.0-88 linux-headers-3.13.0-88-generic
linux-image-3.13.0-88-generic linux-image-extra-3.13.0-88-generic
  Use 'apt-get autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Press any key to continue...

  # ls -l /*.old
  lrwxrwxrwx 1 root root 33 Jun 10 11:57 /initrd.img.old -> 
boot/initrd.img-3.13.0-88-generic
  lrwxrwxrwx 1 root root 30 Jun 10 11:57 /vmlinuz.old -> 
boot/vmlinuz-3.13.0-88-generic

  # uname -a
  Linux server 3.13.0-100-generic #147-Ubuntu SMP Tue Oct 18 16:49:53 UTC 2016 
i686 athlon i686 GNU/Linux
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2011-08-18 (1899 days ago)
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  NonfreeKernelModules: nvidia
  Package: apt 1.0.1ubuntu2.15
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  Tags:  trusty
  Uname: Linux 3.13.0-100-generic i686
  UpgradeStatus: Upgraded to trusty on 2014-10-18 (743 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1723558] [NEW] apport hangs after

2017-10-13 Thread Humphrey van Polanen Petel
Public bug reported:

I wanted to report a bug using "ubuntu-bug -w", but clicked on the wrong panel 
so when apport displayed the panel saying "collecting problem information" I 
clicked .
The panel wen dark and has stayed dark for a long time.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport-gtk 2.20.1-0ubuntu2.10
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CrashReports:
 640:1000:116:67220138:2017-10-14 07:52:54.047099828 +1100:2017-10-14 
07:52:55.047099828 
+1100:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
 664:1000:116:0:2017-10-14 07:52:55.059100284 +1100:2017-10-14 
07:52:55.059100284 
+1100:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.upload
 600:109:116:0:2017-10-14 07:53:00.243340011 +1100:2017-10-14 
07:53:00.243340011 
+1100:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.uploaded
CurrentDesktop: Unity
Date: Sat Oct 14 11:44:22 2017
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2017-07-27 (78 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  apport hangs after 

Status in apport package in Ubuntu:
  New

Bug description:
  I wanted to report a bug using "ubuntu-bug -w", but clicked on the wrong 
panel so when apport displayed the panel saying "collecting problem 
information" I clicked .
  The panel wen dark and has stayed dark for a long time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports:
   640:1000:116:67220138:2017-10-14 07:52:54.047099828 +1100:2017-10-14 
07:52:55.047099828 
+1100:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
   664:1000:116:0:2017-10-14 07:52:55.059100284 +1100:2017-10-14 
07:52:55.059100284 
+1100:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.upload
   600:109:116:0:2017-10-14 07:53:00.243340011 +1100:2017-10-14 
07:53:00.243340011 
+1100:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.uploaded
  CurrentDesktop: Unity
  Date: Sat Oct 14 11:44:22 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-07-27 (78 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 775803] Re: something new and cool

2017-10-13 Thread John Butterworth
Hello!


Perhaps you have already seen that new stuff? You need to take a peek, it rocks 
!,  check it out 
http://www.littlebluelight.com/aggression.php?UE83NzU4MDNAYnVncy5sYXVuY2hwYWQubmV0

Margaret Aiken


From: Bug 775803 [mailto:775...@bugs.launchpad.net]
Sent: Friday, October 13, 2017 7:40 PM
To: john.butterwo...@talktalk.net
Subject: Highlight reel

So..  what's your idea? A lumi weapon camo or just a straight up weapon
with lumifiber stripes? Im fine with either but I'd kinda like all
possible combinations  to be made then.


(3 auraxium camos: 1 for vehicles, 1 for infantry, 1 for weapons, 3 lumi camos: 
 1  vehicles, 1 for infantry and 1 for weapons)


Sent from Mail for Windows 10

** Attachment added: "4301039AFF589D67.jpg"
   
https://bugs.launchpad.net/bugs/775803/+attachment/4970564/+files/4301039AFF589D67.jpg

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

Title:
  /usr/bin/python: error while loading shared libraries: /lib/i386
  -linux-gnu/libz.so.1: invalid ELF header

Status in zlib package in Ubuntu:
  New

Bug description:
  Binary package hint: nvidia-common

  Upgrade failed to install correctly

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-9-generic 2.6.38-9.43
  ProcVersionSignature: Ubuntu 2.6.35-29.51-generic 2.6.35.12
  Uname: Linux 2.6.35-29-generic i686
  Architecture: i386
  Date: Mon May  2 19:42:26 2011
  ErrorMessage: run-parts: /etc/kernel/postinst.d/nvidia-common exited with 
return code 127
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  SourcePackage: nvidia-common
  Title: package linux-image-2.6.38-9-generic 2.6.38-9.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/nvidia-common exited with 
return code 127
  UpgradeStatus: Upgraded to natty on 2011-05-02 (0 days ago)

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

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


[Touch-packages] [Bug 1723552] Re: package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-10-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in eglibc package in Ubuntu:
  New

Bug description:
  After logging in to Ubuntu this error appear on the screen. System
  program error.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc-bin 2.19-0ubuntu6.13
  ProcVersionSignature: Ubuntu 4.4.0-97.120~14.04.1-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Fri Oct 13 21:03:54 2017
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.13
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.13
  DuplicateSignature: package:libc-bin:2.19-0ubuntu6.13:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: eglibc
  Title: package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1723552] [NEW] package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-10-13 Thread Eduardo D. Dequilla
Public bug reported:

After logging in to Ubuntu this error appear on the screen. System
program error.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libc-bin 2.19-0ubuntu6.13
ProcVersionSignature: Ubuntu 4.4.0-97.120~14.04.1-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
Date: Fri Oct 13 21:03:54 2017
Dependencies:
 gcc-4.9-base 4.9.3-0ubuntu4
 libc6 2.19-0ubuntu6.13
 libgcc1 1:4.9.3-0ubuntu4
 multiarch-support 2.19-0ubuntu6.13
DuplicateSignature: package:libc-bin:2.19-0ubuntu6.13:subprocess installed 
post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2017-10-13 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: eglibc
Title: package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in eglibc package in Ubuntu:
  New

Bug description:
  After logging in to Ubuntu this error appear on the screen. System
  program error.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc-bin 2.19-0ubuntu6.13
  ProcVersionSignature: Ubuntu 4.4.0-97.120~14.04.1-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Fri Oct 13 21:03:54 2017
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.13
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.13
  DuplicateSignature: package:libc-bin:2.19-0ubuntu6.13:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: eglibc
  Title: package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1723272] Re: apport-bug unable to init server, dumps core

2017-10-13 Thread Paul
Interesting. According to that ticket, applications require changes to
PolicyKit and ultimately maybe their architecture (separation into non-
graphical and graphical components) in order to run as root on Wayland.
So it looks like you have two options:

1. Put your foot down and refuse to make those changes in apport-bug
2. Decide to re-architect apport-bug to work under Wayland

Keep this ticket open in the latter case.

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

Title:
  apport-bug unable to init server, dumps core

Status in apport package in Ubuntu:
  New

Bug description:
  After upgrading to 17.10, apport-bug fails with the follow error:

  # apport-bug
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  Segmentation fault (core dumped)

  Calling apport-cli directly works just fine. The problem seems to be a
  general Xwayland permission issue, since nothing can connect to the
  display server if sudo/su is used:

  $ sudo xclock
  No protocol specified
  Error: Can't open display: :0
  $ xauth list
  xauth:  file /home/user/.Xauthority does not exist

  If that's the way things are going to be in Ubuntu from now on, we
  need to make apport-bug a bit smarter in the way it decides whether to
  use the GUI version or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports: 640:0:119:7137742:2017-10-13 09:46:22.546417474 
+1100:2017-10-13 09:46:23.546417474 
+1100:/var/crash/_usr_share_apport_apport-gtk.0.crash
  Date: Fri Oct 13 09:49:17 2017
  InstallationDate: Installed on 2016-12-02 (313 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago)

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

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


[Touch-packages] [Bug 1723272] Re: apport-bug unable to init server, dumps core

2017-10-13 Thread Brian Murray
This looks like a duplicate of bug 1713313 but LP keeps timing out when
I try to mark it as one.

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

Title:
  apport-bug unable to init server, dumps core

Status in apport package in Ubuntu:
  New

Bug description:
  After upgrading to 17.10, apport-bug fails with the follow error:

  # apport-bug
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  Segmentation fault (core dumped)

  Calling apport-cli directly works just fine. The problem seems to be a
  general Xwayland permission issue, since nothing can connect to the
  display server if sudo/su is used:

  $ sudo xclock
  No protocol specified
  Error: Can't open display: :0
  $ xauth list
  xauth:  file /home/user/.Xauthority does not exist

  If that's the way things are going to be in Ubuntu from now on, we
  need to make apport-bug a bit smarter in the way it decides whether to
  use the GUI version or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports: 640:0:119:7137742:2017-10-13 09:46:22.546417474 
+1100:2017-10-13 09:46:23.546417474 
+1100:/var/crash/_usr_share_apport_apport-gtk.0.crash
  Date: Fri Oct 13 09:49:17 2017
  InstallationDate: Installed on 2016-12-02 (313 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago)

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

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


[Touch-packages] [Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown

2017-10-13 Thread Lorenzo
Hi again,
I've got an interesting piece of news: I've recently discovered that the 
problem only appears when I'm connected to the optical fiber network in the 
flat where I live during the week; when I use ubuntu with the wi-fi at my home 
(much slower, at 7 Mbps) everything is working just fine.
I don't know  if there is a problem with the management of the fiber network in 
Ubuntu or if the issue is caused by a wrong configuration of the router.

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

Title:
  can't disable wi-fi and system hangs on shutdown

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If I try to turn off wi-fi the system freezes for few seconds and after that 
internet is not working and I can't open settings anymore, even if the wi-fi 
tray icon still shows a connection.
  When I shutdown the system it says that "A stop job for network-manager and 
wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension 
doesn't work neither.
  Everything was working just fine on 17.10 daily builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 23:18:01 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-22 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  IpRoute:
   default via 192.168.1.254 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread Brian Murray
** Also affects: freetype (Ubuntu Artful)
   Importance: High
   Status: Confirmed

** Changed in: freetype (Ubuntu Artful)
Milestone: None => artful-updates

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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


[Touch-packages] [Bug 1681077] Re: ideviceinfo (libimobiledevice): GnuTLS error: Error in the pull function

2017-10-13 Thread Launchpad Bug Tracker
This bug was fixed in the package libimobiledevice -
1.2.0+dfsg-3.1ubuntu3

---
libimobiledevice (1.2.0+dfsg-3.1ubuntu3) artful; urgency=medium

  * debian/patches/git_ios11_devices.patch:
- backport upstream commit required to work with iOS11 devices
  (lp: #1681077)

 -- Sebastien Bacher   Fri, 13 Oct 2017 12:27:18
+0200

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

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

Title:
  ideviceinfo (libimobiledevice): GnuTLS error: Error in the pull
  function

Status in Libimobiledevice:
  New
Status in libimobiledevice package in Ubuntu:
  Fix Released

Bug description:
  Cannot connect to IPhone 5S with ifuse or ideviceinfo due to GnuTLS
  error.

  Reproducable on Ubuntu 16.04.2 LTS and Ubuntu 15.04.

  ideviceinfo 
  GnuTLS error: Error in the pull function.
  ERROR: Could not connect to lockdownd, error code -5

  As far as I know from google, the current IOS 10 release uses TLS instead of 
the insecure SSLv3.
  libimobiledevice (used by ideviceinfo) must be configured to use GnuTLS with 
TLS to successfully connect to IOS 10.
  For IOS 9 there are some (not recommended because insecure) hacks to 
re-enable SSLv3 to get it working.
  But I couldn't find any instructions how to get this working without 
compromising security.

  Other idevice tools like idevicebackup also don't work.

  Successfully using ifuse and idevicebackup for backup purposes is
  quite urgent for me to have a recent backup in case attackers could
  manage to remotely compromise or erase iphones as mentioned in the
  latest news.

  lsb_release -rd
  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  
  Paket: libimobiledevice6
  Zustand: Installiert
  Automatisch installiert: ja
  Multi-Arch: same
  Version: 1.2.0+dfsg-3~ubuntu0.2
  Priorität: optional
  Bereich: libs
  Verwalter: Ubuntu Developers 
  Architektur: amd64
  Unkomprimierte Größe: 181 k
  Hängt ab von: libc6 (>= 2.15), libgcrypt20 (>= 1.6.1), libgnutls30 (>= 3.4.2),
libplist3 (>= 1.11), libtasn1-6 (>= 4.5), libusbmuxd4 (>= 
1.0.10)
  Empfiehlt: usbmuxd
  Schlägt vor: libusbmuxd-tools
  Kollidiert mit: libiphone0
  Beschädigt: libimobiledevice6:i386 (!= 1.2.0+dfsg-3~ubuntu0.2)
  Ersetzt: libimobiledevice0, libimobiledevice1, libiphone0,
   libimobiledevice6:i386 (< 1.2.0+dfsg-3~ubuntu0.2)
  Beschreibung: Bibliothek zur Kommunikation mit dem iPhone und iPod Touch.
   Die Bibliothek libimobiledevice beherrscht die nativen USB-Protokolle von
   Apple, welche von iPhone und iPod Touch verwendet werden. Im Gegensatz zu
   anderen Projekten hängt libimobiledevice nicht von der Verwendung 
irgendwelcher
   vorhandener Apple-Bibliotheken ab.
  Homepage: http://libimobiledevice.org/

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

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


[Touch-packages] [Bug 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain

2017-10-13 Thread Seth Forshee
** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unable to install Ubuntu on the NVMe disk under VMD PCI domain

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Artful:
  New
Status in linux source package in Artful:
  Fix Released

Bug description:
  It is not possible to install Ubuntu on the NVMe disk under VMD
  (Volume Management Device) PCI domain. The disk is not visible in the
  installer because VMD module is not available at this stage.

  I'm raising it against kernel package as I have impression VMD module
  must be included in linux-image dpkg package, not linux-image-extra.

  Please also assure VMD module gets included in initramfs by installer
  (if necessary).

  For more information about VMD please see bug 1591806.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.10.0.26.28
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   tomasz 1659 F...m pulseaudio
   /dev/snd/controlC0:  tomasz 1659 F pulseaudio
   /dev/snd/timer:  tomasz 1659 f pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jul 10 10:40:20 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-07-06 (3 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170702)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later

2017-10-13 Thread John Johansen
err make that 4.14 not 4.13 in my above explanation

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

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
  w/ 4.14-rc2 and later

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed
Status in apparmor source package in Zesty:
  Confirmed
Status in apparmor source package in Artful:
  Confirmed

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor
  2.10.95-0ubuntu2.7, in the system log each second the error message
  below is printed to.

  ```
  […]
  [Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  […]
  ```

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

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


[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread Denis Kalinin
Oh, totally missed your comment. That confirms it.

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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


[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later

2017-10-13 Thread John Johansen
@Doug,

not a kernel regression and not an incompatible kernel change either.
The kernel does support the older abi, however the compiled policy being
sent to the kernel is for the new abi that the kernel is now advertising
as being supported.

The kernel advertises its supported feature set and abis through the
/sys/kernel/security/apparmor/features directory.

The userspace side of things can choose to take advantage of the current
kernel feature set/abi or to pin its supported feature set by setting
the features file. This is not being done on ubuntu so the newest
version of kernel features is always being supported, generally the
userspace has been ahead of kernel features so it is more than willing
to compile for them.

What is odd, is that Ubuntu carries profiles with fine grained unix
socket rules and these should be downgraded to basic the basic socket
rules that the 4.13 kernel supports.

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

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
  w/ 4.14-rc2 and later

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed
Status in apparmor source package in Zesty:
  Confirmed
Status in apparmor source package in Artful:
  Confirmed

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor
  2.10.95-0ubuntu2.7, in the system log each second the error message
  below is printed to.

  ```
  […]
  [Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  […]
  ```

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

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


[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread Denis Kalinin
The title of Konsole definitely doesn't look right, but I'm not sure I
would blame FreeType for that. It could be some KDE or Qt problem.

On my installation, Ubuntu Tweak Tool doesn't allow me to set Window
Font to "Ubuntu Bold 9". It simply switches to "Ubuntu Medium 9" and
makes window titles look regular, not bold. However, when I increase the
font size, it does make the title appear bold and it looks perfectly
fine to me (attaching the screenshot).

I also updated to Michael's PPA and tried installing Konsole - the fonts
still look OK.

** Attachment added: "Bold titles"
   
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+attachment/4970305/+files/comparison-bold.png

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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


[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread mrvanes
I meant to write "fine after upgrade to plasma 5.11".

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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


[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later

2017-10-13 Thread John Johansen
As of 4.13 the upstream kernel does support basic socket mediation which
does include unix sockets. This denial is not due to fine grained unix
socket mediation.

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

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
  w/ 4.14-rc2 and later

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed
Status in apparmor source package in Zesty:
  Confirmed
Status in apparmor source package in Artful:
  Confirmed

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor
  2.10.95-0ubuntu2.7, in the system log each second the error message
  below is printed to.

  ```
  […]
  [Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  […]
  ```

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

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


[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later

2017-10-13 Thread Mario Limonciello
>This isn't really an *Ubuntu* issue per se as we've never claimed to
support apparmor profiles with non-Ubuntu kernels.

So I think the problem is that kernel team maintains a PPA of mainline
kernels and often will ask users to check stuff with mainline kernel
when there are bugs that come up.  This will make that more difficult if
it's not fixed.

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

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
  w/ 4.14-rc2 and later

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed
Status in apparmor source package in Zesty:
  Confirmed
Status in apparmor source package in Artful:
  Confirmed

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor
  2.10.95-0ubuntu2.7, in the system log each second the error message
  below is printed to.

  ```
  […]
  [Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  […]
  ```

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

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


[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later

2017-10-13 Thread Mario Limonciello
And FWIW the /sbin/dhclient and /usr/lib/NetworkManager/nm-dhcp-helper
errors are also family="unix" denying create operations.

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

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
  w/ 4.14-rc2 and later

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed
Status in apparmor source package in Zesty:
  Confirmed
Status in apparmor source package in Artful:
  Confirmed

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor
  2.10.95-0ubuntu2.7, in the system log each second the error message
  below is printed to.

  ```
  […]
  [Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  […]
  ```

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

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


[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread mrvanes
It seems a plasma desktop bug, window title renders fine now, but bold
fonts in panel and kmail still render the ugly way.

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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


[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later

2017-10-13 Thread Jamie Strandboge
This isn't really an *Ubuntu* issue per se as we've never claimed to
support apparmor profiles with non-Ubuntu kernels. I do think it is
interesting that there are 'unix' denials on a kernel that isn't
supposed to support unix rules.

John, can you comment on this?

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

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
  w/ 4.14-rc2 and later

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed
Status in apparmor source package in Zesty:
  Confirmed
Status in apparmor source package in Artful:
  Confirmed

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor
  2.10.95-0ubuntu2.7, in the system log each second the error message
  below is printed to.

  ```
  […]
  [Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  […]
  ```

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

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


[Touch-packages] [Bug 1722053] Re: few minutes after new start of pc every function slows down, online as well as offline / package linux-image-extra-4.4.0-64-generic 4.4.0-64.85 failed to install/upg

2017-10-13 Thread Tyler Hicks
** Information type changed from Private Security to Public

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

Title:
  few minutes after new start of pc every function slows down, online as
  well as offline   /  package linux-image-extra-4.4.0-64-generic
  4.4.0-64.85 failed to install/upgrade: run-parts:
  /etc/kernel/postinst.d/initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  1) Release:  UBUNTU 16.04.3 LTS , release: 16.04

  2) Version of the package:  
  N: Datei "mono" in Verzeichnis "etc/apt/sources.list.d" wird ignoriert, da 
sie keine Dateinamen-Erweiterung hat. 
  N: Paket pkgname kann nicht gefunden werden.

  3) My expectation: Normal speed of all Ubuntu functions.

  4) Instead: Few minutes after every new start of pc every function
  slows down, online as  well as offline.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  swami  1424 F pulseaudio
  Date: Sat Oct  7 23:21:36 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=50f940a4-4706-4749-ac2f-82774f6126fc
  InstallationDate: Installed on 2017-01-24 (256 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E6500
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=3f09c27e-7004-45ce-b32b-474216b0c612 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-64-generic 4.4.0-64.85 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd12/18/2008:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6500
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1721953] Re: my first bug report...

2017-10-13 Thread Tyler Hicks
Hi Jan - congrats on creating your first bug report. We appreciate all
feedback and look forward to receiving more from you in the future.

As for this specific bug report, I suspect that it is an issue with the
package in the specific PPA that you're trying to install from. Since
PPAs are maintained by individuals and do not directly correspond to
packages in the Ubuntu archive, you'll need to contact the owner of the
PPA directly. If you let them know what error you're seeing when
attempting to install the problematic package, I'm sure they'll be able
to help you out and/or provide an updated package in the PPA. Good luck!

** Information type changed from Private Security to Public

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

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

Title:
  my first bug report...

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Couldn'T install a PPA-package

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Oct  7 13:47:03 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics 
Controller [1025:040e]
  InstallationDate: Installed on 2017-09-24 (12 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Acer Aspire 1830T
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JV10_CS
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.24:bd05/06/2011:svnAcer:pnAspire1830T:pvrV1.24:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1830T
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Oct  7 13:36:37 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1722700] Re: package libpcre3:i386 2:8.39-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-10-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libpcre3:i386 2:8.39-3 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in pcre3 package in Ubuntu:
  New

Bug description:
  I don't know why this happend?

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpcre3:i386 2:8.39-3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Oct  2 17:04:02 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   multiarch-support 2.24-9ubuntu2.2
  DuplicateSignature:
   package:libpcre3:i386:2:8.39-3
   Unpacking mongodb-clients (1:3.2.11-2) ...
   dpkg: error processing package libpcre3:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-03-25 (199 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: pcre3
  Title: package libpcre3:i386 2:8.39-3 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to zesty on 2017-05-12 (151 days ago)

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

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


[Touch-packages] [Bug 1722700] Re: package libpcre3:i386 2:8.39-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-10-13 Thread Tyler Hicks
** Information type changed from Private Security to Public

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

Title:
  package libpcre3:i386 2:8.39-3 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in pcre3 package in Ubuntu:
  New

Bug description:
  I don't know why this happend?

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpcre3:i386 2:8.39-3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Oct  2 17:04:02 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   multiarch-support 2.24-9ubuntu2.2
  DuplicateSignature:
   package:libpcre3:i386:2:8.39-3
   Unpacking mongodb-clients (1:3.2.11-2) ...
   dpkg: error processing package libpcre3:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-03-25 (199 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: pcre3
  Title: package libpcre3:i386 2:8.39-3 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to zesty on 2017-05-12 (151 days ago)

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

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


[Touch-packages] [Bug 1722319] Re: Totem Player not working correctly on 17.10 Beta 2

2017-10-13 Thread corrado venturini
I don't know how to document this problem, i can just add some experience:
Problem does not happens in wayland.
Problem happens in x11 with many .webm videos created by cheese.
In x11 I click on the video thumbnail and at 1st time usually (not allways) i 
see the video, next time the totem window appears but with a black video. Click 
another thumbnail, sometime ok other time black video.
If I call totem from terminal like 'totem Videos/prova.webm' i have mostly the 
video correctly played.
The attached video is a very small sample giving the problem.

** Attachment added: "video giving the problem"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1722319/+attachment/4970228/+files/prova.webm

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

Title:
  Totem Player not working correctly on 17.10 Beta 2

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 17.10 Beta 2 on my laptop - Dell
  Inspiron N4110, Intel Sandybridge Mobile Graphics, Intel® Core™
  i3-2350M CPU @ 2.30GHz × 4, 6GB of RAM.  If I try to play ANY video on
  the Totem movie player (the default GNOME player), I get sound and
  subtitles but no picture. VLC works just fine. This did not happen on
  my previous 14.04 install on the same laptop. Is this a beta OS bug or
  just a bad media player?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.3-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 08:31:37 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-06 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1722319/+subscriptions

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


[Touch-packages] [Bug 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

2017-10-13 Thread Adam Kwarciak
I was close to submit missing log file. 
The command returned that I am not the owner of this bug (translated from 
Polish :)

How I can contribute?
I would be really happy to get the HDMI working properly on my ASRock J4205-ITX.
I know it is not a major issue nor the hardware popular - but Win10 works 
out-of-the-box.

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

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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


[Touch-packages] [Bug 1708947] Re: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'

2017-10-13 Thread Brian Murray
** Tags removed: bugpattern-needed

** Tags added: bugpattern-written

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

Title:
  gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-
  packages/PyKDE4/__init__.py: No module named 'DLFCN'

Status in gdebi package in Ubuntu:
  Triaged

Bug description:
  app dont start

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gdebi-kde 0.9.5.7+nmu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Sun Aug  6 19:14:57 2017
  ExecutablePath: /usr/share/gdebi/gdebi-kde
  InstallationDate: Installed on 2017-07-11 (25 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170711)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-kde
  ProcEnviron:
   LANGUAGE=de:en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/gdebi-kde']
  SourcePackage: gdebi
  Title: gdebi-kde crashed with ModuleNotFoundError in 
/usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1723484] [NEW] unlocking several crypto volumes with one password during boot

2017-10-13 Thread Volker Wysk
Public bug reported:

This is a feature request.

I have an encrypted SSD which I want to use as a cache (an LVM-Cache)
for my encrypted harddisc.

The cached root filesystem depends on *both* crypto discs. The new
cached root volume is created from the original root volume
("OriginLV"), and two volumes that reside on the encrypted SSD
("CacheMetaDataLV" and "CacheDataLV").

This means that, during boot, we need to set up both crypto volumes,
before we can mount the root filesystem. So we can't use a keyfile.

This is accomplished by querying the user for the password of each
crypto volume, except for the ones which use a key file.

This means that I'll have to enter two passwords every time I boot my
machine.

This could be done better by making the user enter just one password,
and unlocking all matching crypto disks with it. So I would set the same
password for both crypto disks, and would have to enter the password
only once. This is my feature request.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.8
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Oct 13 18:57:11 2017
InstallationDate: Installed on 2015-10-27 (717 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to xenial on 2016-05-01 (530 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  unlocking several crypto volumes with one password during boot

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This is a feature request.

  I have an encrypted SSD which I want to use as a cache (an LVM-Cache)
  for my encrypted harddisc.

  The cached root filesystem depends on *both* crypto discs. The new
  cached root volume is created from the original root volume
  ("OriginLV"), and two volumes that reside on the encrypted SSD
  ("CacheMetaDataLV" and "CacheDataLV").

  This means that, during boot, we need to set up both crypto volumes,
  before we can mount the root filesystem. So we can't use a keyfile.

  This is accomplished by querying the user for the password of each
  crypto volume, except for the ones which use a key file.

  This means that I'll have to enter two passwords every time I boot my
  machine.

  This could be done better by making the user enter just one password,
  and unlocking all matching crypto disks with it. So I would set the
  same password for both crypto disks, and would have to enter the
  password only once. This is my feature request.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Oct 13 18:57:11 2017
  InstallationDate: Installed on 2015-10-27 (717 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (530 days ago)

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

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


[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-10-13 Thread Brian Murray
** Tags added: rls-aa-incoming

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  New

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably 

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread mrvanes
I'm using Ubuntu for all Desktop fonts. Attached is a screenshot of the problem.
Title is Ubuntu 9 bold, menu is Ubuntu 9 and terminal is Ubuntu Mono 9.
This is after updating Artful's libfreetype 2.8.0 to 2.8.1 from Michael 
Marley's PPA.

** Attachment added: "Screenshot_20171013_191730.png"
   
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+attachment/4970166/+files/Screenshot_20171013_191730.png

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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


[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

2017-10-13 Thread Andrew
I am just now affected by this bug, using a DisplayPort monitor for the
first time.

OS: Ubuntu 17.04 x64
Kernel: 4.10.0-37
X.Org X Server : 1.19.3

Monitor 1: 1920 x 1080 - Laptop's Native Monitor
Monitor 2: 1920 x 1080 - DisplayLink (USB-C) connected MB16AC ASUS Monitor


In an interesting twist: my cursor flickers on both screens, but far more often 
on my laptop screen. On my laptop screen, the cursor flickers about 10 
times/second. On my DisplayLink monitor, the cursor flickers about once every 2 
seconds.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1278223/+subscriptions

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


[Touch-packages] [Bug 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package

2017-10-13 Thread John Cooper
There's also sources on the same host for the main project git server under the 
following names:-
https://cgit.libimobiledevice.org/idevicerestore.git/
https://cgit.libimobiledevice.org/libirecovery.git/

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

Title:
  Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils
  package

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Currently all of the other important utilities are included for
  installation on Ubuntu. However currently though a Ubuntu Linux user,
  is unable to perform an iOS device restore. In order to do so
  currently the user needs to have some way of running an up to date
  iTunes software with a usb connection to the iPhone, iPad or iPod
  Touch.

  Which is quite a hassle to go through in order to completely reload
  the device's iOS software. It would be much better if a binary
  compiled version of the software (idevicerestore and libirecovery)
  could be included in the utilities package.

  It would allow the Ubuntu user to be able to quickly and easily
  perform software update or device restore functions. Without the need
  for a virtual machine running a compatible version of Windows and
  iTunes etc. While also saving them from having to run Wine, its
  dependencies, iTunes and its own software requirements.

  All the would need is what is required to install idevicerestore and
  run its actions (the appropriate iOS release download image file).

  The code for idevice restore is available here
  (https://cgit.sukimashita.com/idevicerestore.git/) and the library
  from here (https://cgit.sukimashita.com/libirecovery.git/).

  Running Ubuntu 16.04.3
  libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed

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

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


[Touch-packages] [Bug 1720517] Re: Software and Updates /Other Software greys out when clicking on "Canonical Partners"

2017-10-13 Thread Brian Murray
I saw this error message in the terminal from which I launched software-
properties:

 $ software-properties-gtk 
ERROR:root:Authentication canceled, changes have not been saved


** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Software and Updates /Other Software greys out when clicking on
  "Canonical Partners"

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  "Other Software" only works after having clicked on "Ubuntu Software",
  "Updates", etc and changing some settings on those pages.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.16
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Sep 30 10:44:47 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2017-09-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170919)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu4
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1719983] Re: please add a way to enable proposed

2017-10-13 Thread Brian Murray
** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Wishlist

** Summary changed:

- please add a way to enable proposed
+ please add a cli way to enable proposed

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

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

Title:
  please add a cli way to enable proposed

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  add-apt-repository is already doing so much for ppa's it would be great if 
there would be a nice and consistent cli way through the same tool to enable 
proposed.

  Sure there are UI ways to enable, but on a server that usually isn't
  an option.

  That would be much better than following some wiki pages.

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

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


[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread Denis Kalinin
That's strange because bold letters of "Courier New" certainly look fine with 
freetype 2.8.1. 
Do you mind telling me which font you're using?

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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


[Touch-packages] [Bug 1673717] Re: rsyslog GnuTLS error -50

2017-10-13 Thread Brian Murray
The Ubuntu Stable Release Update process requires a test case,
http://wiki.ubuntu.com/StableReleaseUpdates, if you provide one I'll be
happy to upload the fix.

** Tags added: xenial

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

Title:
  rsyslog GnuTLS error -50

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

Bug description:
  Exactly the same as this:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995

  Error:

  > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The 
  > request is invalid.  [v8.16.0 try http://www.rsyslog.com/e/2078 ]

  Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works.

  Please apply patch or upgrade rsyslog.

  Ubuntu 16.04 AMD64
  Rsyslog 8.16.0-1ubuntu3

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

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


[Touch-packages] [Bug 1721294] Re: Unattended upgrade fails with "Error in function"

2017-10-13 Thread Brian Murray
Can you try manually running the upgrade with the verbose switch? e.g.
'unattended-upgrade -v'.

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

Title:
  Unattended upgrade fails with "Error in function"

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  This is the cron email I received today:

  From: root 
  To: r...@pov.lt
  Subject: unattended-upgrades result for 'iv-4.pov.lt': 'False'
  Date: Wed,  4 Oct 2017 03:40:19 +0300 (EEST)

  Unattended upgrade returned: False

  Packages that attempted to upgrade:
   ca-certificates libidn11 libnss3 libnss3-nssdb

  Package installation log:
  Error in function:

  
  Unattended-upgrades log:
  Initial blacklisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=trusty-security', 
'o=UbuntuESM,a=trusty', 'o=Ubuntu,a=trusty-security', 
'o=Ubuntu,a=trusty-updates', 'origin=LP-PPA-pov,suite=trusty']
  Packages that will be upgraded: ca-certificates libidn11 libnss3 
libnss3-nssdb
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log'
  Installing the upgrades failed!
  error message: 'installArchives() failed'
  dpkg returned a error! See 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log'
 for details
  Packages that are auto removed: ''
  Packages auto-removed

  The named log file, var/log/unattended-upgrades/unattended-upgrades-
  dpkg_2017-10-04_03:40:17.411277.log contains only this:

  Error in function:

  That's it.

  Now given that ca-certificates is involved, I suspect this may be
  related to non-ASCII filenames (see bug 1554365), but unlike that bug,
  here the upgrade fails instead of succeeding, and the actual error is
  not shown anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.5
  Uname: Linux 2.6.32-042stab124.2 x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Wed Oct  4 18:54:54 2017
  PackageArchitecture: all
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread mrvanes
freetype 2.8.1 fixes hinting of normal fonts, but not bold.

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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


[Touch-packages] [Bug 1723105] Re: Upgrade to 1.28-1ubuntu2.2 fails because postrm script is a directory containing kernel modules

2017-10-13 Thread Brian Murray
I was unable to recreate this issue:

After this operation, 389 kB of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu xenial/main amd64 libidn11 amd64 1.32-3ubuntu1 
[45.5 kB]
Get:2 http://192.168.10.7/ubuntu xenial/universe amd64 idn amd64 1.32-3ubuntu1 
[75.6 kB]
Fetched 121 kB in 0s (0 B/s)   
Selecting previously unselected package libidn11:amd64.
(Reading database ... 15457 files and directories currently installed.)
Preparing to unpack .../libidn11_1.32-3ubuntu1_amd64.deb ...
Unpacking libidn11:amd64 (1.32-3ubuntu1) ...
Selecting previously unselected package idn.
Preparing to unpack .../idn_1.32-3ubuntu1_amd64.deb ...
Unpacking idn (1.32-3ubuntu1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Setting up libidn11:amd64 (1.32-3ubuntu1) ...
Setting up idn (1.32-3ubuntu1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
(xenial-amd64)root@impulse:/home/bdmurray#  ls -lh /var/lib/dpkg/info/libidn11*
-rw-r--r-- 1 root root  254 Oct 13 09:18 /var/lib/dpkg/info/libidn11:amd64.list
-rw-r--r-- 1 root root  221 Nov  4  2015 
/var/lib/dpkg/info/libidn11:amd64.md5sums
-rw-r--r-- 1 root root   19 Nov  4  2015 
/var/lib/dpkg/info/libidn11:amd64.shlibs
-rw-r--r-- 1 root root 2.8K Nov  4  2015 
/var/lib/dpkg/info/libidn11:amd64.symbols
-rw-r--r-- 1 root root   60 Nov  4  2015 
/var/lib/dpkg/info/libidn11:amd64.triggers
(xenial-amd64)root@impulse:/home/bdmurray# apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  idn libidn11
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 122 kB of archives.
After this operation, 2048 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://192.168.10.7/ubuntu xenial-updates/main amd64 libidn11 amd64 
1.32-3ubuntu1.2 [46.5 kB]
Get:2 http://192.168.10.7/ubuntu xenial-updates/universe amd64 idn amd64 
1.32-3ubuntu1.2 [75.6 kB]
Fetched 122 kB in 0s (0 B/s)   
(Reading database ... 15476 files and directories currently installed.)
Preparing to unpack .../libidn11_1.32-3ubuntu1.2_amd64.deb ...
Unpacking libidn11:amd64 (1.32-3ubuntu1.2) over (1.32-3ubuntu1) ...
Preparing to unpack .../idn_1.32-3ubuntu1.2_amd64.deb ...
Unpacking idn (1.32-3ubuntu1.2) over (1.32-3ubuntu1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Setting up libidn11:amd64 (1.32-3ubuntu1.2) ...
Setting up idn (1.32-3ubuntu1.2) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
(xenial-amd64)root@impulse:/home/bdmurray# ls -lh /var/lib/dpkg/info/libidn11*  
   
-rw-r--r-- 1 root root  254 Oct 13 09:19 /var/lib/dpkg/info/libidn11:amd64.list
-rw-r--r-- 1 root root  221 Sep 25 11:06 
/var/lib/dpkg/info/libidn11:amd64.md5sums
-rw-r--r-- 1 root root   19 Sep 25 11:06 
/var/lib/dpkg/info/libidn11:amd64.shlibs
-rw-r--r-- 1 root root 2.8K Sep 25 11:06 
/var/lib/dpkg/info/libidn11:amd64.symbols
-rw-r--r-- 1 root root   60 Sep 25 11:06 
/var/lib/dpkg/info/libidn11:amd64.triggers

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

Title:
  Upgrade to 1.28-1ubuntu2.2 fails because postrm script is a directory
  containing kernel modules

Status in libidn package in Ubuntu:
  New

Bug description:
  When trying to upgrade my Ubuntu 14.04.5 LTS server using the command
  sudo apt-get dist-upgrade, the upgrade consistently failed while
  trying to upgrade libidn11 to version 1.28-1ubuntu2.2 with the
  following error message:

  unable to install (supposed) new info file
  `/var/lib/dpkg/tmp.ci/postrm': Is a directory

  I determined that instead of being a script,
  /var/lib/dpkg/info/libidn11:amd64.postrm was in fact a directory! It
  contained two kernel modules, llc.ko and llc2.lo. I will attach the
  two files.

  To get the package to install and the upgrade operation to proceed, I
  renamed /var/lib/dpkg/info/libidn11:amd64.postrm to
  /var/lib/dpkg/info/libidn11:amd64.postrm.bak, after which a renewed
  dist-upgrade proceeded without any warnings or errors.

  After the installation /var/lib/dpkg/info/libidn11:amd64.postrm once
  again existed, and is now a script, as expected.

  What gives? Is this a bug in either this or the previous version of
  libidn? Is it now correctly installed? Was I hacked (I get a bit
  nervous when executable files spontaneously appear in random places)?
  I scanned the two files with virustotal.com, and it found nothing, but
  I don't think that means much.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libidn11 1.28-1ubuntu2.2
  ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Thu Oct 12 14:41:57 2017
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.13
   

[Touch-packages] [Bug 1723470] Re: package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to install new version of '/lib/xtables/libipt_ttl.so': File exists

2017-10-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to
  install new version of '/lib/xtables/libipt_ttl.so': File exists

Status in iptables package in Ubuntu:
  New

Bug description:
  windows bash update from 14.04 to 16.04 using sudo do-version-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iptables 1.4.21-1ubuntu1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Fri Oct 13 10:01:29 2017
  Dmesg: [0.00]
  DuplicateSignature: package:iptables:1.4.21-1ubuntu1:unable to install new 
version of '/lib/xtables/libipt_ttl.so': File exists
  ErrorMessage: unable to install new version of '/lib/xtables/libipt_ttl.so': 
File exists
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: iptables
  Title: package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to 
install new version of '/lib/xtables/libipt_ttl.so': File exists
  UpgradeStatus: Upgraded to xenial on 2017-10-13 (0 days ago)

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

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


[Touch-packages] [Bug 1722427] Re: [error-report]error occurs when reading /etc/profile

2017-10-13 Thread Gunnar Hjalmarsson
I have found another way to fix this issue, which I think is better.
Fcitx is launched at login from the /usr/share/im-
config/data/22_fcitx.rc file. Changing line #6 in that file from

/usr/bin/fcitx &

to

/usr/bin/fcitx 2>/dev/null &

makes the 'noise' from launching Fcitx disappear so it won't trigger the
error dialog. This keeps the fix within the im-config package without
involving lightdm.

At least this worked for me on Unity. It would be great if some Kylin
users could test it on Ubuntu Kylin.

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

Title:
  [error-report]error occurs when reading /etc/profile

Status in Ubuntu Kylin:
  Confirmed
Status in fcitx package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  system:artful-1008-64bit

  process:
  1.start the system
  2.put in password
  3.after the log in screen, an error message shows up, check the attached file

  expectation:
  no error message shows up after log in

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

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


[Touch-packages] [Bug 1723360] Re: blank

2017-10-13 Thread Brian Murray
** Package changed: initramfs-tools (Ubuntu) => null-and-void

** Changed in: null-and-void
   Status: New => Invalid

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

Title:
  blank

Status in NULL Project:
  Invalid

Bug description:
  blank

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1723360/+subscriptions

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


[Touch-packages] [Bug 1723470] [NEW] package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to install new version of '/lib/xtables/libipt_ttl.so': File exists

2017-10-13 Thread Carl Meilahn
Public bug reported:

windows bash update from 14.04 to 16.04 using sudo do-version-upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: iptables 1.4.21-1ubuntu1
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
Date: Fri Oct 13 10:01:29 2017
Dmesg: [0.00]
DuplicateSignature: package:iptables:1.4.21-1ubuntu1:unable to install new 
version of '/lib/xtables/libipt_ttl.so': File exists
ErrorMessage: unable to install new version of '/lib/xtables/libipt_ttl.so': 
File exists
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: iptables
Title: package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to 
install new version of '/lib/xtables/libipt_ttl.so': File exists
UpgradeStatus: Upgraded to xenial on 2017-10-13 (0 days ago)

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


** Tags: amd64 apport-package need-duplicate-check third-party-packages 
uec-images xenial

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

Title:
  package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to
  install new version of '/lib/xtables/libipt_ttl.so': File exists

Status in iptables package in Ubuntu:
  New

Bug description:
  windows bash update from 14.04 to 16.04 using sudo do-version-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iptables 1.4.21-1ubuntu1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Fri Oct 13 10:01:29 2017
  Dmesg: [0.00]
  DuplicateSignature: package:iptables:1.4.21-1ubuntu1:unable to install new 
version of '/lib/xtables/libipt_ttl.so': File exists
  ErrorMessage: unable to install new version of '/lib/xtables/libipt_ttl.so': 
File exists
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: iptables
  Title: package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to 
install new version of '/lib/xtables/libipt_ttl.so': File exists
  UpgradeStatus: Upgraded to xenial on 2017-10-13 (0 days ago)

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

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


[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

2017-10-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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


[Touch-packages] [Bug 1722988] Re: Crash, black screen with lightdm

2017-10-13 Thread Jeremy Bicha
*** This bug is a duplicate of bug 1722920 ***
https://bugs.launchpad.net/bugs/1722920

I'm marking as duplicate since this bug is no longer reproducible after
today's updates according to the comments here.

Till, Ubuntu 17.10 does use GDM by default. And if you upgrade now from
17.04, you should be transitioned from LightDM to GDM automatically
(unless you have other desktop environments installed I think).

LightDM itself does not use either unity-settings-daemon or gnome-
settings-daemon. unity-greeter though does use unity-settings-daemon.
Unity requires unity-settings-daemon to be installed for the lockscreen.

While I'd love to see unity-settings-daemon be removed, it would cause
regressions with keyboard shortcuts ("hotkeys") and gnome-control-
center's Displays panel wouldn't work. These are fixable with developer
effort (GNOME Flashback managed to fix both of these issues) but there
aren't really developers working on improving Unity now.


** This bug has been marked a duplicate of bug 1722920
   unity-settings-daemon crashed with signal 5

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

Title:
  Crash, black screen with lightdm

Status in lightdm package in Ubuntu:
  Incomplete
Status in unity-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  Got a crash when lightdm is selected, but apport warns about a non
  ubuntu package:

  unity-settings-daemon (15.04.1+17.10.20171003-0ubuntu1) artful;
  urgency=medium

    * XSettings: under unity use com.ubuntu.user-interface.desktop keys
  for scaling settings

   -- Marco Trevisan (Treviño)   Tue, 03 Oct 2017
  06:05:23 +

  so i'm joining the crasfh file

  This happen now with each cold boot: get a black screen, does not even get a 
login screen (using lightdm), so startx is ran from a console to finally get 
the gnome-shell loaded.
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Package: unity-settings-daemon 15.04.1+17.10.20171003-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1722940] Re: 17.10 boots to black screen with cursor

2017-10-13 Thread Jeremy Bicha
*** This bug is a duplicate of bug 1722920 ***
https://bugs.launchpad.net/bugs/1722920

** This bug is no longer a duplicate of bug 1722988
   Crash, black screen with lightdm
** This bug has been marked a duplicate of bug 1722920
   unity-settings-daemon crashed with signal 5

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

Title:
  17.10 boots to black screen with cursor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After the following update
  Start-Date: 2017-10-11  21:02:12
  Commandline: aptdaemon role='role-commit-packages' sender=':1.136'
  Install: fonts-gubbi:amd64 (1.3-3, automatic), fonts-indic:amd64 (2:1.2, 
automatic), fonts-beng-extra:amd64 (1.0-6, automatic), fonts-deva:amd64 (2:1.2, 
automatic), fonts-samyak-deva:amd64 (1.2.2-4, automatic), 
fonts-telu-extra:amd64 (2.0-4, automatic), fonts-smc:amd64 (6.0-1, automatic), 
fonts-gargi:amd64 (2.0-4, automatic), fonts-deva-extra:amd64 (3.0-4, 
automatic), fonts-kalapi:amd64 (1.0-2, automatic), 
linux-image-extra-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), 
fonts-navilu:amd64 (1.2-2, automatic), linux-tools-4.13.0-15-generic:amd64 
(4.13.0-15.16, automatic), fonts-orya:amd64 (2:1.2, automatic), 
linux-headers-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), 
fonts-pagul:amd64 (1.0-7, automatic), fonts-knda:amd64 (2:1.2, automatic), 
fonts-sahadeva:amd64 (1.0-4, automatic), fonts-lohit-deva:amd64 (2.95.4-2, 
automatic), fonts-taml:amd64 (2:1.3, automatic), fonts-samyak-taml:amd64 
(1.2.2-4, automatic), fonts-telu:amd64 (2:1.2, automatic), 
fonts-lohit-orya:amd64 (2.91.2-
 1, automatic), linux-headers-4.13.0-15:amd64 (4.13.0-15.16, automatic), 
fonts-lohit-knda:amd64 (2.5.4-1, automatic), fonts-gujr:amd64 (2:1.2, 
automatic), fonts-samyak-gujr:amd64 (1.2.2-4, automatic), 
linux-tools-4.13.0-15:amd64 (4.13.0-15.16, automatic), fonts-nakula:amd64 
(1.0-3, automatic), fonts-lohit-beng-bengali:amd64 (2.91.5-1, automatic), 
fonts-orya-extra:amd64 (2.0-5, automatic), fonts-mlym:amd64 (2:1.2, automatic), 
fonts-lohit-taml:amd64 (2.91.3-1, automatic), fonts-beng:amd64 (2:1.2, 
automatic), fonts-samyak-mlym:amd64 (1.2.2-4, automatic), 
fonts-lohit-telu:amd64 (2.5.5-1, automatic), fonts-gujr-extra:amd64 (1.0-6, 
automatic), linux-image-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), 
fonts-lohit-beng-assamese:amd64 (2.91.5-1, automatic), fonts-lohit-gujr:amd64 
(2.92.4-2, automatic), linux-signed-image-4.13.0-15-generic:amd64 
(4.13.0-15.16, automatic), fonts-sarai:amd64 (1.0-2, automatic), 
fonts-lohit-mlym:amd64 (2.92.2-1, automatic), fonts-lohit-taml-classical:amd64 (
 2.5.4-1, automatic)
  Upgrade: libgraphicsmagick-q16-3:amd64 (1.3.26-12, 1.3.26-13), 
libunity-settings-daemon1:amd64 (15.04.1+17.04.20170619-0ubuntu3, 
15.04.1+17.10.20171003-0ubuntu1), libmpx0:amd64 (5.4.1-13ubuntu1, 
5.5.0-1ubuntu1), empathy-common:amd64 (3.25.90-0ubuntu1, 
3.25.90+really3.12.14-0ubuntu1), libgcj17:amd64 (6.4.0-7ubuntu1, 
6.4.0-8ubuntu1), gnome-control-center-data:amd64 (1:3.26.1-0ubuntu1, 
1:3.26.1-0ubuntu3), libgcc-5-dev:amd64 (5.4.1-13ubuntu1, 5.5.0-1ubuntu1), 
poppler-utils:amd64 (0.57.0-2ubuntu2, 0.57.0-2ubuntu4), postfix:amd64 (3.2.2-1, 
3.2.3-1), libseccomp2:amd64 (2.3.1-2.1ubuntu2, 2.3.1-2.1ubuntu3), 
gnome-settings-daemon-schemas:amd64 (3.26.1-0ubuntu1, 3.26.1-0ubuntu3), 
unity-schemas:amd64 (7.5.0+17.10.20170925.1-0ubuntu1, 
7.5.0+17.10.20171010-0ubuntu1), update-manager-core:amd64 (1:17.10.10, 
1:17.10.11), libsemanage1:amd64 (2.7-1, 2.7-2), linux-headers-generic:amd64 
(4.13.0.12.13, 4.13.0.15.16), gnome-session-common:amd64 (3.26.0-0ubuntu2, 
3.26.1-0ubuntu3), unity-session:amd64 (3.2
 6.0-0ubuntu2, 3.26.1-0ubuntu3), gir1.2-mutter-1:amd64 (3.26.1-1, 3.26.1-2), 
gnome-control-center:amd64 (1:3.26.1-0ubuntu1, 1:3.26.1-0ubuntu3), 
linux-libc-dev:amd64 (4.13.0-12.13, 4.13.0-15.16), 
gnome-software-plugin-snap:amd64 (3.26.0-0ubuntu3, 3.26.1-0ubuntu1), 
va-driver-all:amd64 (1.8.3-1, 1.8.3-2), linux-image-generic:amd64 
(4.13.0.12.13, 4.13.0.15.16), cpp-5:amd64 (5.4.1-13ubuntu1, 5.5.0-1ubuntu1), 
cpp-6:amd64 (6.4.0-7ubuntu1, 6.4.0-8ubuntu1), gsettings-ubuntu-schemas:amd64 
(0.0.7+17.04.20161109-0ubuntu1, 0.0.7+17.10.20170922-0ubuntu1), 
update-manager:amd64 (1:17.10.10, 1:17.10.11), postfix-sqlite:amd64 (3.2.2-1, 
3.2.3-1), libpoppler-qt4-4:amd64 (0.57.0-2ubuntu2, 0.57.0-2ubuntu4), 
linux-signed-image-generic:amd64 (4.13.0.12.13, 4.13.0.15.16), 
gnome-software:amd64 (3.26.0-0ubuntu3, 3.26.1-0ubuntu1), libmutter-1-0:amd64 
(3.26.1-1, 3.26.1-2), ubuntu-standard:amd64 (1.402, 1.403), 
gir1.2-accountsservice-1.0:amd64 (0.6.42-0ubuntu2, 0.6.42-0ubuntu3), 
nodejs:amd64 (6.11.2~dfsg-3ubuntu1
 , 6.11.4~dfsg-1ubuntu1), ubuntu-session:amd64 (3.26.0-0ubuntu2, 
3.26.1-0ubuntu3), gnome-orca:amd64 (3.26.0-1ubuntu1, 3.26.0-1ubuntu2), 
ubuntu-desktop:amd64 (1.402, 1.403), gnome-settings-daemon:amd64 

[Touch-packages] [Bug 1723156] Re: lightdm only shows black screen with cursor on 17.10

2017-10-13 Thread Jeremy Bicha
*** This bug is a duplicate of bug 1722920 ***
https://bugs.launchpad.net/bugs/1722920

** This bug is no longer a duplicate of bug 1722988
   Crash, black screen with lightdm
** This bug has been marked a duplicate of bug 1722920
   unity-settings-daemon crashed with signal 5

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

Title:
  lightdm only shows black screen with cursor on 17.10

Status in lightdm package in Ubuntu:
  New

Bug description:
  after recent updates on 17.10 (development) lightdm fails. It only
  shows a black screen and the cursor. Cant change to tty1 with
  ctrl+alt+f1.

  started from grub with systemd.unit=multi-user.target into tty1 and
  started gdm from there, so i could log on to unity (with broken gtk).

  nothing obvious for me in the log files from syslog or lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 12 17:15:29 2017
  InstallationDate: Installed on 2013-09-28 (1475 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to artful on 2017-06-30 (104 days ago)

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

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


[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

2017-10-13 Thread Dan Streetman
** Changed in: ifupdown (Ubuntu Xenial)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

Title:
  ifup -a does not start dependants last, causes deadlocks with
  vlans/bonding

Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  Confirmed

Bug description:
  This is a problem I've been struggling with since moving to 16.04.1
  from 14.04 (fresh install)

  I don't believe this problem affected 14.04. I have used an almost
  identical interfaces file on 14.04 without problem.

  On 16.04.1, however, 9/10 boots would hang during network
  configuration and leave the network incorrectly configured.

  When calling "ifup -a" all candidate interfaces appear to be started
  in parallel leading to collisions with locks. This causes hanging
  (until timeout) during booting and the network interfaces left
  incorrectly configured

  Imagine this /etc/network/interfaces

  auto eno1 bond0 bond0.1

  iface eno1 inet manual
  bond-master bond0

  iface bond0 inet manual
  bond-slaves eno1
  bond-mode   4
  bond-lacp-rate  1
  bond-miimon 100
  bond-updelay200
  bond-downdelay  200

  iface bond0.5 inet dhcp
  vlan-raw-device bond0

  
  eno1 -> bond0 -> bond0.5 -> dhcp

  When calling "ifup -a" at boot time all three interfaces are started
  at the same time.

  bond0 and bond0.5 both attempt to share the same lock file:

/run/network/ifstate.bond0

  If bond0 wins the race, the system will start correctly (1/10):

* bond0 starts and creates the bond0 device and the ifenslave.bond0 file to 
indicate the bond is ready
* eno1 polls for the ifenslave.bond0 file, when it appears it attaches eno1 
to bond0
* bond0 finishes and releases the lock
* bond0.5 now acquires the lock.
* bond0.5 starts dhclient, which can talk to the network and configure the 
interface

  
  If, however, bond0.2 wins the lock race, the system will hang at boot (5 
mins) and fail to set up the network.

* bond0.5 is awarded the ifstate.bond0 lockfile
* bond0.5 starts dhclient waiting to hear from the network
* bond0 is blocked, so bond0 is not created nor is the bond0.ifenslave file 
* eno1 polls but never finds the ifenslave.bond0 file so never attaches to 
bond0
* bond0.5's dhclient is trying to talk to a disconnected network and never 
receives an answer

! bond0.5 is stuck running dhclient
! bond0 is stuck waiting for bond0.5 to finish
! eno1 is stuck waiting for bond0 to create the ifenslave.bond0 file

  
  I believe ifup should start interfaces (that share lock files) in dependant 
order. The most basic interface must be awarded the lock over its dependants. 
In this case:

1 eno1
2 bond0
3 bond0.5

  but never:

1 eno1
2 bond0.5
3 bond0

  
  As a work arouund, in /etc/network/interfaces

  -auto   eno1 bond0 bond0.1
  +auto   eno1 bond0
  +allow-bond bond0.1

  And also in /lib/systemd/system/networking.service

   ExecStart=/sbin/ifup -a --read-environment
  +ExecStart=/sbin/ifup -a --allow=bond --read-environment
   ExecStop=/sbin/ifdown -a --read-environment

  Then run:

systemctl dameon-reload

  This causes all "auto" interfaces to start then, when they've
  completed, all allow-bond interfaces to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.1 [modified: 
lib/systemd/system/networking.service]
  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: Wed Oct 26 06:32:57 2016
  InstallationDate: Installed on 2016-10-24 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.networking.conf: [modified]
  mtime.conffile..etc.init.networking.conf: 2016-10-26T04:52:05.750927

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

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


[Touch-packages] [Bug 1699294] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

2017-10-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  can not access hplip-3.17.6.run file to be able to use out HP c4280
  photosmart scanner/printer in scan mode.  Getit shows "There was a
  problem opening the file "/home/e/Downloads/hplip-3.17.6.run".  The
  file you opened has some invalid characters.  If you continue editing
  this file you could corrupt this document."

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 20 07:55:10 2017
  DuplicateSignature:
   package:libperl5.22:5.22.1-9
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2015-12-21 (547 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1723403] Re: Gedit doesn't Gain Focus Upon Opening a File in Nautilus

2017-10-13 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Confirmed

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  Gedit doesn't Gain Focus Upon Opening a File in Nautilus

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  If you already have one tab open in gedit, and then minimize gedit, if
  you double click on another file in nautilus, gedit should regain
  focus, but it does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 06:26:01 2017
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1723437] Re: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

2017-10-13 Thread Steve Langasek
The error in your log is:

Processing triggers for shim-signed 
(1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
debconf: unable to initialize frontend: Passthrough
debconf: (Cannot connect to /tmp/aptdaemon-4wk65r8d/debconf.socket: Connection 
refused at (eval 18) line 3.)
debconf: falling back to frontend: Noninteractive
Running in non-interactive mode, doing nothing.
--- /var/lib/shim-signed/dkms-list  2017-10-13 22:05:36.867828964 +0700
+++ /var/lib/shim-signed/dkms-list.new  2017-10-13 22:05:36.871828963 +0700
@@ -0,0 +1,3 @@
+/var/lib/dkms
+/var/lib/dkms/bbswitch
+/var/lib/dkms/nvidia-375
dpkg: error processing package shim-signed (--configure):
 subprocess installed post-installation script returned error exit status 1

This error message indicates that for some reason, software-properties
disconnected the aptdaemon debconf socket before installation completed.

To finish installation of these packages, you can run the following command 
from a terminal:
  sudo dpkg --configure -a

** Package changed: shim-signed (Ubuntu) => software-properties (Ubuntu)

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

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

Title:
  package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  i dont know why could happen to me?

  can u fix this problem?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: 0
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Oct 13 22:05:36 2017
  EFITables:
   Okt 13 22:08:22 laksmana-GE70-2PE kernel: efi: EFI v2.31 by American 
Megatrends
   Okt 13 22:08:22 laksmana-GE70-2PE kernel: efi:  ESRT=0xcbf6f918  
ACPI=0xcb47c000  ACPI 2.0=0xcb47c000  SMBIOS=0xcbf6f418 
   Okt 13 22:08:22 laksmana-GE70-2PE kernel: esrt: Reserving ESRT space from 
0xcbf6f918 to 0xcbf6f950.
   Okt 13 22:08:22 laksmana-GE70-2PE kernel: Secure boot enabled
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim-signed
  Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
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/software-properties/+bug/1723437/+subscriptions

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


[Touch-packages] [Bug 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic

2017-10-13 Thread Brian Murray
** Tags added: zesty

** Package changed: apport (Ubuntu) => linux (Ubuntu)

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

Title:
  Intel graphics problems on kernel 4.10.0-37-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely 
slow.
  The reason is that i915 driver is UNCLAIMED now.

  Error from Xorg logs is:
  [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: 
Permission denied

  Environment:
  Ubuntu 17.04
  Kernel 4.10.0-37
  Intel HD Graphics 520
  INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6

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

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


[Touch-packages] [Bug 1722988] Re: Crash, black screen with lightdm

2017-10-13 Thread dino99
@Till

i have not closed the report as your #12 comment makes sense; so waiting
for Jeremy (or else dev) opinion.

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

Title:
  Crash, black screen with lightdm

Status in lightdm package in Ubuntu:
  Incomplete
Status in unity-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  Got a crash when lightdm is selected, but apport warns about a non
  ubuntu package:

  unity-settings-daemon (15.04.1+17.10.20171003-0ubuntu1) artful;
  urgency=medium

    * XSettings: under unity use com.ubuntu.user-interface.desktop keys
  for scaling settings

   -- Marco Trevisan (Treviño)   Tue, 03 Oct 2017
  06:05:23 +

  so i'm joining the crasfh file

  This happen now with each cold boot: get a black screen, does not even get a 
login screen (using lightdm), so startx is ran from a console to finally get 
the gnome-shell loaded.
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Package: unity-settings-daemon 15.04.1+17.10.20171003-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1723437] [NEW] package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit statu

2017-10-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

i dont know why could happen to me?

can u fix this problem?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Oct 13 22:05:36 2017
EFITables:
 Okt 13 22:08:22 laksmana-GE70-2PE kernel: efi: EFI v2.31 by American Megatrends
 Okt 13 22:08:22 laksmana-GE70-2PE kernel: efi:  ESRT=0xcbf6f918  
ACPI=0xcb47c000  ACPI 2.0=0xcb47c000  SMBIOS=0xcbf6f418 
 Okt 13 22:08:22 laksmana-GE70-2PE kernel: esrt: Reserving ESRT space from 
0xcbf6f918 to 0xcbf6f950.
 Okt 13 22:08:22 laksmana-GE70-2PE kernel: Secure boot enabled
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-10-13 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SecureBoot: 6   0   0   0   1
SourcePackage: shim-signed
Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial
-- 
package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
https://bugs.launchpad.net/bugs/1723437
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to software-properties 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 1722988] Re: Crash, black screen with lightdm

2017-10-13 Thread Till Kamppeter
I can also confirm that LightDM is working again.

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

Title:
  Crash, black screen with lightdm

Status in lightdm package in Ubuntu:
  Incomplete
Status in unity-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  Got a crash when lightdm is selected, but apport warns about a non
  ubuntu package:

  unity-settings-daemon (15.04.1+17.10.20171003-0ubuntu1) artful;
  urgency=medium

    * XSettings: under unity use com.ubuntu.user-interface.desktop keys
  for scaling settings

   -- Marco Trevisan (Treviño)   Tue, 03 Oct 2017
  06:05:23 +

  so i'm joining the crasfh file

  This happen now with each cold boot: get a black screen, does not even get a 
login screen (using lightdm), so startx is ran from a console to finally get 
the gnome-shell loaded.
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Package: unity-settings-daemon 15.04.1+17.10.20171003-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-13 Thread Sebastien Bacher
Till, you should perhaps open a bug on systemd upstream on github since
it's likely an issue there? There might have a clue about it or people
who are available to debug the issue...

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

Title:
  Services asked for by UDEV do not get triggered

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The packages system-config-printer-udev and ippusbxd are installed,
  having the following UDEV rule files:

  /lib/udev/rules.d/70-printers.rules

  --
  # Low-level USB device add trigger
  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", 
TAG+="systemd", PROGRAM="/bin/systemd-escape 
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c"
  # Low-level USB device remove trigger
  ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
  --

  /lib/udev/rules.d/55-ippusbxd.rules

  --
  # ippusbxd udev rules file

  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device" 
ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664", 
PROGRAM="/bin/systemd-escape --template=ippusbxd@.service 
$env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c"
  --

  If I turn on an appropriate printer (USB, supporting IPP-over-USB,
  here the HP DeskJet 2540) I get in the output of "udevadm monitor
  --environment"

  --
  UDEV  [17527.514150] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
  ACTION=add
  BUSNUM=002
  DEVNAME=/dev/bus/usb/002/033
  DEVNUM=033
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2
  DEVTYPE=usb_device
  DRIVER=usb
  ID_BUS=usb
  ID_MODEL=Deskjet_2540_series
  ID_MODEL_ENC=Deskjet\x202540\x20series
  ID_MODEL_ID=c211
  ID_REVISION=0100
  ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK
  ID_SERIAL_SHORT=BR54BFB02C05XK
  ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401:
  ID_VENDOR=HP
  ID_VENDOR_ENC=HP
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  ID_VENDOR_ID=03f0
  MAJOR=189
  MINOR=160
  PRODUCT=3f0/c211/100
  SEQNUM=9891
  SUBSYSTEM=usb
  SYSTEMD_WANTS=ippusbxd@002:033.service 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service 
printer.target
  TAGS=:udev-configure-printer:systemd:
  TYPE=0/0/0
  USEC_INITIALIZED=17527513940

  UDEV  [17527.517724] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
  .MM_USBIFNUM=00
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/204/0
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00
  PRODUCT=3f0/c211/100
  SEQNUM=9892
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527517478

  UDEV  [17527.522565] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 (usb)
  .MM_USBIFNUM=02
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/4/1
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFisc04ip01in02
  PRODUCT=3f0/c211/100
  SEQNUM=9895
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527522332

  UDEV  [17527.523761] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1 (usb)
  .MM_USBIFNUM=01
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1
  DEVTYPE=usb_interface
  DRIVER=usblp
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=7/1/2
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00ic07isc01ip02in01
  PRODUCT=3f0/c211/100
  SEQNUM=9893
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527523500

  UDEV  [17527.527275] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 (usbmisc)
  .MM_USBIFNUM=01
  ACTION=add
  DEVNAME=/dev/usb/lp1
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1
  MAJOR=180
  MINOR=1
  SEQNUM=9894
  SUBSYSTEM=usbmisc
  USEC_INITIALIZED=17527527175
  --

  Here one can see that the UDEV rules files are correct, leading to the
  correct systemd services being requested

  SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer
  @-devices-pci:00-:00:14.0-usb2-2\x2d2.service printer.target

  but neither the service ippusbxd@002:033.service nor the service udev-
  configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service
  get started (note that I have put the .service file for ippusbxd in
  place by "sudo cp /usr/share/doc/ippusbxd/examples/ippusbxd@.service
  /lib/systemd/system/").

  I can start each of these services manually though:

  sudo systemctl start 'udev-configure-printer@-devices-
  pci:00-:00:14.0-usb2-2\x2d2.service'

  sudo systemctl start ippusbxd@002:033.service

  In each case ippusbxd gets started for this printer and a 

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-13 Thread Monique van den Berg
** Attachment removed: "Changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+attachment/4969928/+files/changelog

** Attachment added: "Change"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+attachment/4970030/+files/changelog

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

-- 
Mailing list: https://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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

2017-10-13 Thread Robie Basak
On Fri, Oct 13, 2017 at 01:22:23AM -, Dimitri John Ledkov wrote:
> > Can networkd be made to work without relying on this sysctl tweak? If
> 
> No, as the alternative is what isc-dhcp /sbin/dhcp-client does that is
> flush current dhcp lease IP and add a new IP, meaning that networking
> is dropped =/
> Which to me is horrifying.

This is not an SRU justification, however, as we have been doing this
for decades and it is not a problem in practice, nor a regression from
previous releases.

> Promotion of secondary addresses should actually reduce split-brain
> situations. I don't buy the HA/Neutron argument, as in HA environment
> the underlying nodes have static ip addresses and the management of
> floating ip addresses is not managed by DHCP leases, given the DHCP
> timings and fragility. Are you implying that HA and Neutron rely on
> DHCP lease renew/rebind which can be initiated and spoofed by the
> clients arbitrary?

I think you misunderstand my concern. I'm not talking about DHCP in my
HA use case. I'm talking about whether tweaking the particular sysctl
knob will cause any adverse affects in use cases unrelated to this bug.
All use cases that do unusual things with (layer 3) network
configuration need to be considered or eliminated.

I'm not claiming any particular regression. I'm trying to identify
unknown unknowns ("Regression Potential") here which might happen as a
consequence of tweaking a global sysctl value to change behaviour for
*all* existing users and corresponding use cases in a stable release.

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  In Progress

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that 

[Touch-packages] [Bug 1723403] Re: Gedit doesn't Gain Focus Upon Opening a File in Nautilus

2017-10-13 Thread Sebastien Bacher
Thank you for your bug report, that's a known gtk/wayland issue, see
https://bugzilla.gnome.org/show_bug.cgi?id=766284

** Bug watch added: GNOME Bug Tracker #766284
   https://bugzilla.gnome.org/show_bug.cgi?id=766284

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

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

** Package changed: gedit (Ubuntu) => gtk+3.0 (Ubuntu)

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=766284
   Importance: Unknown
   Status: Unknown

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

Title:
  Gedit doesn't Gain Focus Upon Opening a File in Nautilus

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  If you already have one tab open in gedit, and then minimize gedit, if
  you double click on another file in nautilus, gedit should regain
  focus, but it does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 06:26:01 2017
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1723403] [NEW] Gedit doesn't Gain Focus Upon Opening a File in Nautilus

2017-10-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

If you already have one tab open in gedit, and then minimize gedit, if
you double click on another file in nautilus, gedit should regain focus,
but it does not.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 13 06:26:01 2017
InstallationDate: Installed on 2017-10-13 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session
-- 
Gedit doesn't Gain Focus Upon Opening a File in Nautilus
https://bugs.launchpad.net/bugs/1723403
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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 1723422] [NEW] /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

2017-10-13 Thread dino99
Public bug reported:

Get that error now with each random package upgrade:

/usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid
string constant "murrine-scrollbar", expected valid string constant

Looks like related to that change:

* gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
#961679)

 -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017 05:19:32
+


That installation is a default Ubuntu , no Mate installed

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Oct 13 14:52:43 2017
EcryptfsInUse: Yes
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  
  That installation is a default Ubuntu , no Mate installed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-13 Thread Monique van den Berg
** Patch added: "Patch"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+attachment/4969909/+files/99-increase-receive-buffer-size.patch

** Attachment removed: "Changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+attachment/4969908/+files/changelog

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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


[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-13 Thread Monique van den Berg
** Attachment added: "Changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+attachment/4969908/+files/changelog

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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


[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-13 Thread Monique van den Berg
** Attachment added: "Changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+attachment/4969928/+files/changelog

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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


[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

2017-10-13 Thread Monique van den Berg
## Description: Fix "Message truncated" issue with many VF's
## Origin/Author: Jan Gutter 
## Bug: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126
Index: iproute2/lib/libnetlink.c
===
--- iproute2.orig/lib/libnetlink.c  2017-10-13 14:29:12.313074855 +0200
+++ iproute2/lib/libnetlink.c   2017-10-13 14:29:12.309074887 +0200
@@ -193,7 +193,7 @@
.msg_iov = ,
.msg_iovlen = 1,
};
-   char buf[16384];
+   char buf[65536];
int dump_intr = 0;

iov.iov_base = buf;

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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


[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

2017-10-13 Thread Dan Streetman
> networking.service spawns ifup@.services in parallel with no ordering
information

no, networking.service calls ifup -a, it doesn't spawn ifup@ services.

ifup -a doesn't bring up interfaces in parallel, it brings them up
sequentially as ordered in the /etc/networking/interface file(s).
However, while bringing up an interface frequently other interfaces are
created which does trigger parallel ifup@ service calls - for example,
if bond1 and bond1.2 are both defined, while bond1 is being ifup'ed, the
actual bond1 interface is created and processed by udev, which then
calls /lib/udev/vlan-network-interface with bond1, which then parses the
ifupdown configuration and finds the bond1.2 interface that uses bond1
as its raw-device, and so it runs /etc/network/if-pre-up.d/vlan which
creates the bond1.2 interface - that is then processed by udev, which
then ifup's it in parallel to bond1's ifup, etc.

> To resolve boot time races, you need to provide manual dependency ordering of 
> the
> ifup@.service systemd units

i don't believe that is entirely correct, but if your suggestion fixes
things for @tom-verdaat then great.  ifupdown (and the vlan add-on to
it) is rather a mess, and i can't wait to move on to netplan with
networkd.

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

Title:
  ifup -a does not start dependants last, causes deadlocks with
  vlans/bonding

Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  Confirmed

Bug description:
  This is a problem I've been struggling with since moving to 16.04.1
  from 14.04 (fresh install)

  I don't believe this problem affected 14.04. I have used an almost
  identical interfaces file on 14.04 without problem.

  On 16.04.1, however, 9/10 boots would hang during network
  configuration and leave the network incorrectly configured.

  When calling "ifup -a" all candidate interfaces appear to be started
  in parallel leading to collisions with locks. This causes hanging
  (until timeout) during booting and the network interfaces left
  incorrectly configured

  Imagine this /etc/network/interfaces

  auto eno1 bond0 bond0.1

  iface eno1 inet manual
  bond-master bond0

  iface bond0 inet manual
  bond-slaves eno1
  bond-mode   4
  bond-lacp-rate  1
  bond-miimon 100
  bond-updelay200
  bond-downdelay  200

  iface bond0.5 inet dhcp
  vlan-raw-device bond0

  
  eno1 -> bond0 -> bond0.5 -> dhcp

  When calling "ifup -a" at boot time all three interfaces are started
  at the same time.

  bond0 and bond0.5 both attempt to share the same lock file:

/run/network/ifstate.bond0

  If bond0 wins the race, the system will start correctly (1/10):

* bond0 starts and creates the bond0 device and the ifenslave.bond0 file to 
indicate the bond is ready
* eno1 polls for the ifenslave.bond0 file, when it appears it attaches eno1 
to bond0
* bond0 finishes and releases the lock
* bond0.5 now acquires the lock.
* bond0.5 starts dhclient, which can talk to the network and configure the 
interface

  
  If, however, bond0.2 wins the lock race, the system will hang at boot (5 
mins) and fail to set up the network.

* bond0.5 is awarded the ifstate.bond0 lockfile
* bond0.5 starts dhclient waiting to hear from the network
* bond0 is blocked, so bond0 is not created nor is the bond0.ifenslave file 
* eno1 polls but never finds the ifenslave.bond0 file so never attaches to 
bond0
* bond0.5's dhclient is trying to talk to a disconnected network and never 
receives an answer

! bond0.5 is stuck running dhclient
! bond0 is stuck waiting for bond0.5 to finish
! eno1 is stuck waiting for bond0 to create the ifenslave.bond0 file

  
  I believe ifup should start interfaces (that share lock files) in dependant 
order. The most basic interface must be awarded the lock over its dependants. 
In this case:

1 eno1
2 bond0
3 bond0.5

  but never:

1 eno1
2 bond0.5
3 bond0

  
  As a work arouund, in /etc/network/interfaces

  -auto   eno1 bond0 bond0.1
  +auto   eno1 bond0
  +allow-bond bond0.1

  And also in /lib/systemd/system/networking.service

   ExecStart=/sbin/ifup -a --read-environment
  +ExecStart=/sbin/ifup -a --allow=bond --read-environment
   ExecStop=/sbin/ifdown -a --read-environment

  Then run:

systemctl dameon-reload

  This causes all "auto" interfaces to start then, when they've
  completed, all allow-bond interfaces to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.1 [modified: 
lib/systemd/system/networking.service]
  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: Wed 

[Touch-packages] [Bug 1723413] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-10-13 Thread Apport retracing service
*** This bug is a duplicate of bug 1720653 ***
https://bugs.launchpad.net/bugs/1720653

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1720653
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  i am a new user. i don't know anything.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 13 16:06:39 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-10 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-10-13 (0 days ago)

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

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


[Touch-packages] [Bug 1720653] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-10-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  2 to 5 times diff bugs popped up

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv wl
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Sun Oct  1 18:54:49 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-05-22 (132 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-10-01 (0 days ago)

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

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


[Touch-packages] [Bug 1713086] Re: systemd fails to generate .device units inside LXD containers

2017-10-13 Thread Francis Ginther
** Tags added: id-59df87551899547b7b2171c2

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

Title:
  systemd fails to generate .device units inside LXD containers

Status in systemd package in Ubuntu:
  New

Bug description:
  See LXD issue here for more context:
  https://github.com/lxc/lxd/issues/3638

  After attaching a block device (in my case /dev/sdc3) to a LXD
  container, the dev-sdc3.device unit is not generated. However, the
  dev-sdc3.mount unit is generated correctly.

  Steps to reproduce (from GitHub issue):

  stgraber@castiana:~$ truncate -s 10G test.img
  stgraber@castiana:~$ sudo losetup -f test.img
  stgraber@castiana:~$ sudo losetup -a
  /dev/loop1: [0022]:169383 (/var/lib/snapd/snaps/core_2381.snap)
  /dev/loop2: [0022]:770242 (/var/lib/snapd/snaps/core_2312.snap)
  /dev/loop0: [0022]:1170310 (/var/lib/snapd/snaps/core_2462.snap)
  /dev/loop3: [0045]:309158 (/home/stgraber/test.img)
  stgraber@castiana:~$ lxc launch ubuntu:16.04 issue3638
  Creating issue3638
  Starting issue3638
  stgraber@castiana:~$ lxc config device add issue3638 sda unix-block 
source=/dev/loop3 path=/dev/sda
  Device sda added to issue3638
  stgraber@castiana:~$ lxc exec issue3638 -- mkfs.ext4 /dev/sda
  mke2fs 1.42.13 (17-May-2015)
  Discarding device blocks: done
  Creating filesystem with 2621440 4k blocks and 655360 inodes
  Filesystem UUID: 77832ca2-b16d-4b94-8f7d-9ea08c5e6913
  Superblock backups stored on blocks:
   32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (32768 blocks): done
  Writing superblocks and filesystem accounting information: done

  stgraber@castiana:~$ echo Y | sudo tee 
/sys/module/ext4/parameters/userns_mounts
  Y
  stgraber@castiana:~$ lxc exec issue3638 -- mount /dev/sda /mnt
  stgraber@castiana:~$ lxc exec issue3638 bash
  root@issue3638:~# echo "/dev/sda /mnt ext4 defaults 0 0" >> /etc/fstab
  root@issue3638:~# cat /etc/fstab
  LABEL=cloudimg-rootfs /ext4   defaults0 0
  /dev/sda /mnt ext4 defaults 0 0
  root@issue3638:~# exit
  stgraber@castiana:~$ lxc exec issue3638 -- umount /mnt
  stgraber@castiana:~$ lxc exec issue3638 -- mount /mnt
  stgraber@castiana:~$ lxc stop issue3638
  stgraber@castiana:~$ lxc start issue3638
  stgraber@castiana:~$ lxc exec issue3638 -- mount | grep mnt
  stgraber@castiana:~$ lxc exec issue3638 -- systemctl -a | grep mnt
    mnt.mount  loadedinactive dead  
start /mnt
  stgraber@castiana:~$ lxc exec issue3638 -- systemctl -a | grep sda
    dev-sda.device loadedinactive dead  
start dev-sda.device
    dev-sda.mount  loadedactive   mounted   
  /dev/sda
  stgraber@castiana:~$ lxc exec issue3638 -- ps aux | grep udev
  root54  0.0  0.0  41720  1864 ?Ss   16:55   0:00 
/lib/systemd/systemd-udevd
  stgraber@castiana:~$

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

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


[Touch-packages] [Bug 1723413] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-10-13 Thread kishor kumar
*** This bug is a duplicate of bug 1720653 ***
https://bugs.launchpad.net/bugs/1720653

Public bug reported:

i am a new user. i don't know anything.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Fri Oct 13 16:06:39 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-10-10 (2 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to zesty on 2017-10-13 (0 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  i am a new user. i don't know anything.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 13 16:06:39 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-10 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-10-13 (0 days ago)

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

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


[Touch-packages] [Bug 1721399] Re: Z LPAR 17.10: DNS server provided during the install process is not configured

2017-10-13 Thread Dimitri John Ledkov
*** This bug is a duplicate of bug 1721798 ***
https://bugs.launchpad.net/bugs/1721798

** This bug has been marked a duplicate of bug 1721798
   netcfg does not setup search domains and nameservers via netplan

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

Title:
  Z LPAR 17.10: DNS server provided during the install process is not
  configured

Status in systemd package in Ubuntu:
  New

Bug description:
  The DNS server provided to the debian-installer is not configured

  ubuntu@s5lp7:/var/log/installer$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful

  ubuntu@s5lp7:/var/log/installer$ dig 10.245.208.1 us.ports.ubuntu.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> 10.245.208.1 us.ports.ubuntu.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37759
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;10.245.208.1.IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 04 16:16:33 UTC 2017
  ;; MSG SIZE  rcvd: 41

  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 18831
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;us.ports.ubuntu.com. IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 04 16:16:33 UTC 2017
  ;; MSG SIZE  rcvd: 48

  Works when specifically providing the DNS IP:
  ubuntu@s5lp7:/var/log/installer$ dig @10.245.208.1 us.ports.ubuntu.com
  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @10.245.208.1 us.ports.ubuntu.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37847
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 6

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;us.ports.ubuntu.com. IN  A

  ;; ANSWER SECTION:
  us.ports.ubuntu.com.  299 IN  A   91.189.91.11

  ;; AUTHORITY SECTION:
  ubuntu.com.   76  IN  NS  ns4.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns2.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns3.p27.dynect.net.
  ubuntu.com.   76  IN  NS  ns1.p27.dynect.net.

  ;; ADDITIONAL SECTION:
  ns1.p27.dynect.NET.   63971   IN  A   208.78.70.27
  ns1.p27.dynect.NET.   72  IN  2001:500:90:1::27
  ns2.p27.dynect.NET.   63971   IN  A   204.13.250.27
  ns3.p27.dynect.NET.   63971   IN  A   208.78.71.27
  ns4.p27.dynect.NET.   63971   IN  A   204.13.251.27

  ;; Query time: 0 msec
  ;; SERVER: 10.245.208.1#53(10.245.208.1)
  ;; WHEN: Wed Oct 04 16:21:49 UTC 2017
  ;; MSG SIZE  rcvd: 272

  ubuntu@s5lp7:/var/log/installer$ cat /etc/network/interfaces
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 10.245.208.1
dns-search canonical.com

  ubuntu@s5lp7:/var/log/installer$ cat /etc/resolv.conf 
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  Can be worked around by directly adding a nameserver entry to /etc/resolv.conf
  ubuntu@s5lp7:/var/log/installer$ cat /etc/resolv.conf 
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.245.208.1
  #nameserver 127.0.0.53

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

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


[Touch-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

2017-10-13 Thread Dimitri John Ledkov
Any updates? Have you been able to monitor fs.aio-nr exhaustion?

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in kvm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in procps package in Ubuntu:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/aio-max-nr
  65536


  # Attempt to start more than 17 qcow2 virtual guests on the Ubuntu
  host.  Fails on the 18th XML.

  Script used to start guests..

  
  ubuntu@zm93k8:/home/scottg$ date;./start_privs.sh
  Wed Aug 23 13:21:25 EDT 2017
  virsh start zs93kag70015
  Domain zs93kag70015 started

  Started zs93kag70015 succesfully ...

  virsh start zs93kag70020
  Domain zs93kag70020 started

  Started zs93kag70020 

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

2017-10-13 Thread Bug Watch Updater
** Changed in: totem
   Status: Unknown => Confirmed

** Changed in: totem
   Importance: Unknown => Medium

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Confirmed
Status in Totem:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  In Progress

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1723390] Re: lxd containers have become degraded

2017-10-13 Thread Dimitri John Ledkov
** Tags added: rls-aa-incoming

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

Title:
  lxd containers have become degraded

Status in systemd package in Ubuntu:
  New

Bug description:
  20170920 container boots degraded with 
  Oct 13 10:09:28 test20170920 systemd[256]: systemd-hostnamed.service: Failed 
at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied

  20170919 container boots non-degraded. Package list changes are
  insignificant.

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

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


[Touch-packages] [Bug 1718554] Re: Need updated libimobiledevice to mount IOS 11 devices

2017-10-13 Thread Sebastien Bacher
Thanks for the report and pointing that patch, I uploaded a backport to
artful now

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

** Changed in: libimobiledevice (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Need updated libimobiledevice to mount IOS 11 devices

Status in libimobiledevice package in Ubuntu:
  Fix Committed

Bug description:
  After upgrading to IOS 11, I stopped being able to mount my ipad in
  ubuntu.

  The relevant log lines from gvfs-afc are:

  gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
  gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
  gvfsd[1855]: afc: Lockdown client try #0
  gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client'
  gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown 
error (-3))

  The fix is here in the upstream github:

  
https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12

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

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


[Touch-packages] [Bug 1722427] Re: [error-report]error occurs when reading /etc/profile

2017-10-13 Thread Gunnar Hjalmarsson
Attached a debdiff corresponding to the merge proposal.

This will hopefully be handled on Monday.

** Patch added: "lightdm_fcitx-workaround.debdiff"
   
https://bugs.launchpad.net/ubuntukylin/+bug/1722427/+attachment/4969747/+files/lightdm_fcitx-workaround.debdiff

** Tags added: patch

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

Title:
  [error-report]error occurs when reading /etc/profile

Status in Ubuntu Kylin:
  Confirmed
Status in fcitx package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  system:artful-1008-64bit

  process:
  1.start the system
  2.put in password
  3.after the log in screen, an error message shows up, check the attached file

  expectation:
  no error message shows up after log in

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

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


[Touch-packages] [Bug 1723390] [NEW] lxd containers have become degraded

2017-10-13 Thread Dimitri John Ledkov
Public bug reported:

20170920 container boots degraded with 
Oct 13 10:09:28 test20170920 systemd[256]: systemd-hostnamed.service: Failed at 
step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied

20170919 container boots non-degraded. Package list changes are
insignificant.

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

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

Title:
  lxd containers have become degraded

Status in systemd package in Ubuntu:
  New

Bug description:
  20170920 container boots degraded with 
  Oct 13 10:09:28 test20170920 systemd[256]: systemd-hostnamed.service: Failed 
at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied

  20170919 container boots non-degraded. Package list changes are
  insignificant.

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

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


[Touch-packages] [Bug 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package

2017-10-13 Thread Sebastien Bacher
thank you for your bug report, that would be a nice feature to have
indeed, reading your description it's not simple that those are missing
from the .deb but they are different project/sources so it would need
some work to include, ideally upstream libimobiledevice would ship them
which would make that easier

** Changed in: libimobiledevice (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils
  package

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Currently all of the other important utilities are included for
  installation on Ubuntu. However currently though a Ubuntu Linux user,
  is unable to perform an iOS device restore. In order to do so
  currently the user needs to have some way of running an up to date
  iTunes software with a usb connection to the iPhone, iPad or iPod
  Touch.

  Which is quite a hassle to go through in order to completely reload
  the device's iOS software. It would be much better if a binary
  compiled version of the software (idevicerestore and libirecovery)
  could be included in the utilities package.

  It would allow the Ubuntu user to be able to quickly and easily
  perform software update or device restore functions. Without the need
  for a virtual machine running a compatible version of Windows and
  iTunes etc. While also saving them from having to run Wine, its
  dependencies, iTunes and its own software requirements.

  All the would need is what is required to install idevicerestore and
  run its actions (the appropriate iOS release download image file).

  The code for idevice restore is available here
  (https://cgit.sukimashita.com/idevicerestore.git/) and the library
  from here (https://cgit.sukimashita.com/libirecovery.git/).

  Running Ubuntu 16.04.3
  libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed

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

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


[Touch-packages] [Bug 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

2017-10-13 Thread Bug Watch Updater
** Changed in: cups
   Status: New => Fix Released

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  New

Bug description:
  after updates of cups-filter and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 21 17:43:42 2017
  ExecutablePath: /usr/sbin/cupsd
  Lpstat:
   device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21
   device for PDF: cups-pdf:/
  MachineType: Dell Inc. OptiPlex 960
  Papersize: a4
  PpdFiles:
   PDF: Generic CUPS-PDF Printer (w/ options)
   HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f32dc0c7954 : cmpq   
$0x0,(%rdi)
   PC (0x7f32dc0c7954) 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 artful on 2017-09-19 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0Y958C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1701289] Re: gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat()

2017-10-13 Thread Andrea Azzarone
I think the upstream bug is this one:
https://bugzilla.gnome.org/show_bug.cgi?id=788666

** Bug watch added: GNOME Bug Tracker #788666
   https://bugzilla.gnome.org/show_bug.cgi?id=788666

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

Title:
  gnome-shell crashed with signal 5 in XIGetClientPointer() from
  gdk_x11_display_get_default_seat()

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/fb179bc620e408d216f4b8700f714e6ebb2ebf09

  ---

  cant login to gnome desktop

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 29 16:14:29 2017
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-03-25 (96 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XIGetClientPointer () at /usr/lib/x86_64-linux-gnu/libXi.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

2017-10-13 Thread Daniel van Vugt
Here tis: https://bugzilla.gnome.org/show_bug.cgi?id=788926

** Bug watch added: GNOME Bug Tracker #788926
   https://bugzilla.gnome.org/show_bug.cgi?id=788926

** Changed in: totem
   Importance: High => Unknown

** Changed in: totem
   Status: Incomplete => Unknown

** Changed in: totem
 Remote watch: GNOME Bug Tracker #778766 => GNOME Bug Tracker #788926

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Confirmed
Status in Totem:
  Unknown
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  In Progress

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1722708] Re: Crash when setting laptop display resolution

2017-10-13 Thread Timo Aaltonen
the default session uses gnome-shell with wayland, so could've been a
bug in gnome that got fixed

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

Title:
  Crash when setting laptop display resolution

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  This system has a 4k laptop screen with resolution 3840x2160, and an
  external HP monitor connected via HDMI, resolution 1920x1200. Windows,
  fonts etc are not scaled properly on the external monitor (too large,
  etc), and the only workaround I've found with earlier versions and
  other distros is to set the laptop display to 1920x1080 mode, so
  that's what I'm trying here as well.

  However, when doing that, the X (wayland, not sure if the package is
  correct here) session crashes and brings me back to login screen.

  So to summarize: connect the external monitor, go to Settings >
  Devices > Displays, click primary built in display, observe that it
  shows Resolution 3840x2160 (16:9) and Scale 200%, change resolution to
  1920x1080 (16:9), click Apply --> crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 07:49:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2248]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:2248]
  InstallationDate: Installed on 2017-10-10 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171008)
  MachineType: LENOVO 20H9004MMX
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=182b5236-fa96-4fb5-bea9-f90769b65f3c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1VET35W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20H9004MMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1VET35W(1.25):bd09/06/2017:svnLENOVO:pn20H9004MMX:pvrThinkPadT570:rvnLENOVO:rn20H9004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T570
  dmi.product.name: 20H9004MMX
  dmi.product.version: ThinkPad T570
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1723383] [NEW] Monitor blinks

2017-10-13 Thread Sharif Minhazul Islam
Public bug reported:

Sometimes my monitor keeps blinking after few seconds. But when I
restart it fixes.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Fri Oct 13 15:57:39 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 anbox-modules-ashmem, 9~zesty1, 4.10.0-33-generic, x86_64: installed
 anbox-modules-ashmem, 9~zesty1, 4.10.0-35-generic, x86_64: installed
 anbox-modules-binder, 9~zesty1, 4.10.0-33-generic, x86_64: installed
 anbox-modules-binder, 9~zesty1, 4.10.0-35-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1600]
InstallationDate: Installed on 2017-05-14 (152 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X441UAK
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed 
root=UUID=cb989c7e-a225-416c-b292-35fbef65043b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X441UAK.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X441UAK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX441UAK.302:bd10/18/2016:svnASUSTeKCOMPUTERINC.:pnX441UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X441UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Fri Oct 13 14:36:59 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: modeset

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


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

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

Title:
  Monitor blinks

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes my monitor keeps blinking after few seconds. But when I
  restart it fixes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Fri Oct 13 15:57:39 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   anbox-modules-ashmem, 9~zesty1, 4.10.0-33-generic, x86_64: installed
   anbox-modules-ashmem, 9~zesty1, 4.10.0-35-generic, x86_64: installed
   anbox-modules-binder, 9~zesty1, 4.10.0-33-generic, x86_64: installed
   anbox-modules-binder, 9~zesty1, 4.10.0-35-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1600]
  InstallationDate: Installed 

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

2017-10-13 Thread Daniel van Vugt
Some simple system monitoring:
  cat /proc/`pidof totem`/io
reveals totem's biggest skip coincides with a disk _write_ of some sort.

That should be easy to track down but I'm just about out of time this
week.

** Changed in: totem (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: totem (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Confirmed
Status in Totem:
  Incomplete
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  In Progress

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1723372] [NEW] nmcli pollutes terse output with unrequested information

2017-10-13 Thread Jonathan Cave
Public bug reported:

For example on my system with a wifi device named wlp2s0, run the
following command which should just print out the three requested
fields:

$ nmcli -t -f SSID,CHAN,FREQ d wifi list ifname wlp2s0
wlp2s0
Canonical:1:2412 MHz
Canonical:6:2437 MHz
Canonical:11:2462 MHz
Canonical:40:5200 MHz
Canonical:36:5180 MHz
...


The first line of output is the interface name and should not be included.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3.2
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Fri Oct 13 10:17:13 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-04-18 (177 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
 default via 10.20.64.1 dev enxa0cec802a800 proto static metric 100 
 10.20.64.0/21 dev enxa0cec802a800 proto kernel scope link src 10.20.66.44 
metric 100 
 10.111.44.0/24 dev lxdbr0 proto kernel scope link src 10.111.44.1 
 169.254.0.0/16 dev enxa0cec802a800 scope link metric 1000
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
 lxdbr0   bridgeconnected 
/org/freedesktop/NetworkManager/Devices/3  lxdbr0  
6e757793-2287-4147-8426-7585435bbe4e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enxa0cec802a800  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/5  Wired connection 1  
d7f88012-4a23-3692-bbf2-64f2c5854f29  
/org/freedesktop/NetworkManager/ActiveConnection/9 
 wlp2s0   wifi  disconnected  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
 lo   loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug zesty

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

Title:
  nmcli pollutes terse output with unrequested information

Status in network-manager package in Ubuntu:
  New

Bug description:
  For example on my system with a wifi device named wlp2s0, run the
  following command which should just print out the three requested
  fields:

  $ nmcli -t -f SSID,CHAN,FREQ d wifi list ifname wlp2s0
  wlp2s0
  Canonical:1:2412 MHz
  Canonical:6:2437 MHz
  Canonical:11:2462 MHz
  Canonical:40:5200 MHz
  Canonical:36:5180 MHz
  ...

  
  The first line of output is the interface name and should not be included.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3.2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Oct 13 10:17:13 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-04-18 (177 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 10.20.64.1 dev enxa0cec802a800 proto static metric 100 
   10.20.64.0/21 dev enxa0cec802a800 proto kernel scope link src 10.20.66.44 
metric 100 
   10.111.44.0/24 dev lxdbr0 proto kernel scope link src 10.111.44.1 
   169.254.0.0/16 dev enxa0cec802a800 scope link metric 1000
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH   
   CONNECTION  CON-UUID  CON-PATH   

   lxdbr0   bridge

[Touch-packages] [Bug 1575128] Re: unity dialogues split between 2 monitors

2017-10-13 Thread Andrea Azzarone
** Changed in: unity (Ubuntu)
 Assignee: Andrea Azzarone (azzar1) => (unassigned)

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

Title:
  unity dialogues split between 2 monitors

Status in gtk+3.0 package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  Since upgrading from Ubuntu 15.10 to 16.04, Unity is now shown across
  both my monitors in a hard to use manner: unity dialogues, such as the
  log-out and shutdown popups, are displayed centered between both
  monitors, so the left half is on one monitor, and the right half on
  another. Also, the unity top panel indicators and clock used to be on
  both monitors, but are now only on the right monitor.

  More info since it is likely relevant:
  I have a Dell laptop with an NVidia Prime GPU and Intel built-in GPU. This 
laptop has always been trouble configuring for dual monitors. The 
nvidia-settings controls only shows one monitor, though it is supposed to show 
two. I have never been able to get a working xorg.conf for the two monitors, 
despited 2 days of trying (and I am a software developer well versed in reading 
docs). The instructions in the nvidia docs simply don't work as stated for this 
hardware (Dell XPS 17 L702X). Purging all graphics settings doesn't help. 
Upgrading to a newer nvidia driver didn't help (I've tried the latest official 
nvidia package as well as one newer). As a result, I've been using an xrandr 
command and compiz  display settings since Ubuntu 15.10. This worked perfectly 
in 15.10. But, as stated, the unity top panel and dialogues are not working 
properly in 16.04.

  I tried Nvidia 361.42 and 364.19 from the PPA at
  http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu.

  The xrandr command in use is:
  xrandr --fb 3520x1080 --output HDMI-0 --preferred --primary --mode 1920x1080 
--pos 0x0 --panning 3520x1080+0+0/3520x1080+0+0/0/0/-3520/0 --output LVDS-1 
--mode 1600x900 --pos 1920x180 --panning 0x0

  (I know the fb sets up a wide virtual screen, but as stated, in 15.10,
  that worked perfectly for unity)

  In compiz display settings I have the following "Outputs" set:
  1920x1080+0+0
  1600x900+1920+180

  It would appear in 16.04, Unity ignores the compiz outputs whereas in
  15.10 it does not. But that's just a guess.

  Sorry I cannot get a screenshot of the dialogues. They seem to block
  Ubuntu's screenshot program due to their modal nature.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  364.19  Tue Apr 19 14:44:55 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 07:01:26 2016
  DistUpgraded: 2016-04-25 10:00:42,012 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.2.0-35-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   nvidia-364, 364.19, 4.4.0-21-generic, x86_64: installed
   vboxhost, 5.0.18, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0571]
   NVIDIA Corporation GF116M [GeForce GT 550M] [10de:1246] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF116M [GeForce GT 550M] [1028:0571]
  InstallationDate: Installed on 2016-03-22 (35 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Dell System XPS L702X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=f4247c67-52eb-4dd4-988d-b09205d3c0a1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (0 days ago)
  dmi.bios.date: 02/22/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.asset.tag: Base Board Asset Tag
  

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

2017-10-13 Thread Dimitri John Ledkov
** Changed in: debian-installer (Ubuntu)
Milestone: None => ubuntu-17.10

** Changed in: debian-installer (Ubuntu)
   Status: New => Fix Committed

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Committed
Status in debian-installer-utils package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in debian-installer source package in Trusty:
  New
Status in debian-installer-utils source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer-utils source package in Xenial:
  New
Status in debian-installer source package in Zesty:
  New
Status in debian-installer-utils source package in Zesty:
  New

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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


[Touch-packages] [Bug 1517965] Re: Cursor repainting in Nux text entries damage the all screen area

2017-10-13 Thread Andrea Azzarone
** Changed in: nux (Ubuntu)
 Assignee: Andrea Azzarone (azzar1) => (unassigned)

** Changed in: unity (Ubuntu)
 Assignee: Andrea Azzarone (azzar1) => (unassigned)

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

Title:
  Cursor repainting in Nux text entries damage the all screen area

Status in nux package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  Using Compiz "Show Repaint" plugin it's possible to see that every
  time a cursor is drawn in Nux, the all screen area is damanaged.

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

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


[Touch-packages] [Bug 1723360] [NEW] blank

2017-10-13 Thread Asgar Jamneshan
Public bug reported:

blank

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

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

Title:
  blank

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  blank

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

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


  1   2   >