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

[Malte Schmidt]

Test case

Step 1:

Create a rsyslog-config using gtls:

/etc/rsyslog.d/10-tlstest.conf

Step 2:

To generate the needed ca-, key-, cert-files, follow the guide at
http://www.rsyslog.com/doc/v8-stable/tutorials/tls.html#certificates

Step 3:

Setup a client, which relays logs to the server that was just set up

Step 4:

Check the rsyslog-log for the errors mentioned in the initial post.


** Attachment added: "10-tlstest.conf"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+attachment/4973253/+files/10-tlstest.conf

-- 
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 1723577] Re: Artful won't start with Wayland activated (AMD?)

[Daniel van Vugt]

A new idea: libdrm was also upgraded on 5 October:

  https://launchpad.net/ubuntu/+source/libdrm/2.4.83-1

That might cause this problem since it provides:

  libdrm-amdgpu1

So try downgrading to:

  https://launchpad.net/ubuntu/+source/libdrm/2.4.82-1/+build/13171669

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

Title:
  Artful won't start with Wayland activated (AMD?)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On a fresch install, ubuntu stop and freeze before gdm is opened
  With no splah i have "started user manager for uid 121" and then it freeze

  need to uncomment WaylandEnable=false in custom.conf to start ubuntu
  so with xorg.

  
  lspci -nn | grep VGA

  return

  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  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: Sat Oct 14 07:36:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 
'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  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=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

Sorry for the delay. More comments in the merge request.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Touch-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)

[frenchy82]

i've tested to revert mesa AND mutter but didn't help

** Attachment added: "mesa"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4973252/+files/mesa

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

Title:
  Artful won't start with Wayland activated (AMD?)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On a fresch install, ubuntu stop and freeze before gdm is opened
  With no splah i have "started user manager for uid 121" and then it freeze

  need to uncomment WaylandEnable=false in custom.conf to start ubuntu
  so with xorg.

  
  lspci -nn | grep VGA

  return

  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  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: Sat Oct 14 07:36:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 
'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  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=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)

[Xavier Guillot]

Daniel, sorry, I did not complete my post after #18 and apt policy
result - we were discussing with didrocks and frenchy82 on the French
forum with the details, I tried to resume here all steps in order other
people and developers involved in bug also got the informations.

http://forum.ubuntu-fr.org/viewtopic.php?pid=21810017#p21810017

So I did (always in chroot mode) :
sudo dpkg -i libegl1-mesa_17.2.1-0ubuntu1_amd64.deb 
libgbm1_17.2.1-0ubuntu1_amd64.deb libgl1-mesa-dri_17.2.1-0ubuntu1_amd64.deb 
libgl1-mesa-glx_17.2.1-0ubuntu1_amd64.deb 
libglapi-mesa_17.2.1-0ubuntu1_amd64.deb libgles2-mesa_17.2.1-0ubuntu1_amd64.deb 
libwayland-egl1-mesa_17.2.1-0ubuntu1_amd64.deb 
libxatracker2_17.2.1-0ubuntu1_amd64.deb 
mesa-va-drivers_17.2.1-0ubuntu1_amd64.deb 
mesa-vdpau-drivers_17.2.1-0ubuntu1_amd64.deb

It downgraded the 10 packages installed in 17.2.1 version.

But when I rebooted normally, it was still frozen at Ubuntu screen and
message 'Started User Manager for UID 121'

My graphic card : Gallium 0.4 on AMD CAPE VERDE (DRM 2.49.0 /
4.10.0-19-generic, LLVM 4.0.0)

After dpwngrading mesa, I tried downgrading mutter, xserver-xorg-video-
ati, xorg-server, then booting on the grub to older kernels : nothing
worked, I still have the bug on startup.

You're right, I don't know if I missed something on the instructions to
come back on previous versions with the risk to eliminate the good
direction to search, or if bug comes from something else...

I was afraid of that, but frenchy82 test seems to confirm downgrading
mesa is not enough to solve the problem. I can continue to do some
testings if you need.

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

Title:
  Artful won't start with Wayland activated (AMD?)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On a fresch install, ubuntu stop and freeze before gdm is opened
  With no splah i have "started user manager for uid 121" and then it freeze

  need to uncomment WaylandEnable=false in custom.conf to start ubuntu
  so with xorg.

  
  lspci -nn | grep VGA

  return

  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  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: Sat Oct 14 07:36:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 
'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  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=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

[Bug Watch Updater]

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

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

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  First two characters typed in urlbar show immediately, other
  characters take up to 30 seconds to appear, or url will appear in full
  once enter key is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)

[Daniel van Vugt]

Thanks. We can /probably/ exclude Mesa then.

Next I would suggest downgrading mutter which is used to render gdm3
(and because the 3.26.1 release happened at the time of the bug too) but
comment #21 seems to suggest that's already been tried.

Still, we can't definitively exclude Mesa or Mutter fully because
there's always a chance that some mistake was made during testing. And
there's also a chance that different people are experiencing different
bugs. Please keep experimenting...

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

Title:
  Artful won't start with Wayland activated (AMD?)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On a fresch install, ubuntu stop and freeze before gdm is opened
  With no splah i have "started user manager for uid 121" and then it freeze

  need to uncomment WaylandEnable=false in custom.conf to start ubuntu
  so with xorg.

  
  lspci -nn | grep VGA

  return

  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  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: Sat Oct 14 07:36:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 
'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  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=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1694623] Re: package apt 1.2.20 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2

[Launchpad Bug Tracker]

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

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

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

Title:
  package apt 1.2.20 failed to install/upgrade: subprocess new pre-
  removal script returned error exit status 2

Status in apt package in Ubuntu:
  Expired

Bug description:
  Everything apart the System error pop-up at machine start up looks
  fine.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.20
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 30 10:17:42 2017
  Df:
   Filesystem 1K-blocks Used Available Use% Mounted on
   /dev/sda1  114752072 48694416  60205496  45% /
   tmpfs 810472 9584800888   2% /run
  DpkgTerminalLog:
   Log ended: 2017-05-29  17:24:19
 Log started: 2017-05-30  10:17:40
  ErrorMessage: subprocess new pre-removal script returned error exit status 2
  InstallationDate: Installed on 2017-04-11 (49 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apt
  Title: package apt 1.2.20 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1711428] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-upgrade.service execution

[Launchpad Bug Tracker]

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

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

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

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-
  upgrade.service execution

Status in cloud-init:
  Incomplete
Status in apt package in Ubuntu:
  Expired

Bug description:
  This is the same problem as https://bugs.launchpad.net/cloud-
  init/+bug/1693361, but with a different APT invoking service.  In this
  case it is apt-daily-upgrade.service.

  So, I guess add apt-daily-upgrade.service to the Before line in
  /lib/systemd/system/cloud-final.service along side apt-daily.service.

  Or wait for an APT fix.  Or retry APT commands when executing
  "packages:"

  Reporting this to save someone else trouble, but I think we'll be
  rolling back to Trusty at this point.  Hopefully the B LTS will have
  an alternative to systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1711428/+subscriptions

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

[Touch-packages] [Bug 1680045] Re: AbiWord opens 2 transparent windows on top in Unity8

[Launchpad Bug Tracker]

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

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

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

Title:
  AbiWord opens 2 transparent windows on top in Unity8

Status in Canonical System Image:
  Won't Fix
Status in abiword package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Expired

Bug description:
  Ubuntu 17.04 Unity8

  AbiWord opens 2 transparent windows on top (see screenshot) and if
  closed while the transparent windows are opened it will leave a
  process running 160% cpu forever

  run abiword (without Xmir), close

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

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

[Touch-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)

[frenchy82]

I've made too the revert to mesa 17.2.1-0ubuntu1_amd64 but it didn't
help

** Attachment added: "mesa"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4973251/+files/mesa

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

Title:
  Artful won't start with Wayland activated (AMD?)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On a fresch install, ubuntu stop and freeze before gdm is opened
  With no splah i have "started user manager for uid 121" and then it freeze

  need to uncomment WaylandEnable=false in custom.conf to start ubuntu
  so with xorg.

  
  lspci -nn | grep VGA

  return

  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  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: Sat Oct 14 07:36:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 
'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  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=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1723644

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

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

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

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

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

Title:
  NetworkManager hang

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Recently I had issues with NetworkManager. When I try to restart or close
  NetworkManager, the process hangs. First it sends a SIGTERM to the
  NetworkManager process, and after a while it sends SIGKILL, yet nothing
  happens. After the attempt to restart/close NetworkManager, the OS behaves
  badly:
  - journalctl doesn't work, doesn't output anything, SIGTERMing/SIGABRTing/
  SIGKILLing it causes the kill command to hang (no matter how many times I try
  it), it also hangs the terminal
  - 'sudo dmesg' hangs (killing it with SIGKILL/SIGTERM/SIGABRT hangs the kill
  command, can't close the terminal)
  - the OS won't reboot/suspend/shutdown (it does only after holding the restart
  button)

  Suspending/rebooting normally/shutdowning normally the laptop hangs the OS
  (because of NetworkManager).

  What I've tried:
  - reinstalling NetworkManager (uninstalling it using --purge, installing it 
clean)
  - deleting ~/.config
  - deleting ~/.cache
  - installing a version from NetworkManager from Debian (version: 1.8.4.2),
  reinstalling NetworkManager from Ubuntu back

   affects ubuntu
   affects ubuntu/network-manager
   affects ubuntu/systemd

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

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

[Touch-packages] [Bug 1723644] Re: NetworkManager hang

[Kai-Heng Feng]

So it's more likely to be a driver issue.

** Also affects: linux (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/1723644

Title:
  NetworkManager hang

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Recently I had issues with NetworkManager. When I try to restart or close
  NetworkManager, the process hangs. First it sends a SIGTERM to the
  NetworkManager process, and after a while it sends SIGKILL, yet nothing
  happens. After the attempt to restart/close NetworkManager, the OS behaves
  badly:
  - journalctl doesn't work, doesn't output anything, SIGTERMing/SIGABRTing/
  SIGKILLing it causes the kill command to hang (no matter how many times I try
  it), it also hangs the terminal
  - 'sudo dmesg' hangs (killing it with SIGKILL/SIGTERM/SIGABRT hangs the kill
  command, can't close the terminal)
  - the OS won't reboot/suspend/shutdown (it does only after holding the restart
  button)

  Suspending/rebooting normally/shutdowning normally the laptop hangs the OS
  (because of NetworkManager).

  What I've tried:
  - reinstalling NetworkManager (uninstalling it using --purge, installing it 
clean)
  - deleting ~/.config
  - deleting ~/.cache
  - installing a version from NetworkManager from Debian (version: 1.8.4.2),
  reinstalling NetworkManager from Ubuntu back

   affects ubuntu
   affects ubuntu/network-manager
   affects ubuntu/systemd

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

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[MAAS Lander]

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

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact] 
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in 

http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  
  [Regression Potential] 
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.

  b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]
   
  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.

  ubuntu@manual:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 192.168.122.2
  search maas

  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 

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

[m.desouza20]

Source: zulucrypt
Source-Version: 5.2.0-2

We believe that the bug you reported is fixed in the latest version of
zulucrypt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Format: 1.8
Date: Sun, 10 Sep 2017 23:32:46 +
Source: zulucrypt
Binary: zulucrypt-cli zulumount-cli zulucrypt-gui zulumount-gui zulupolkit 
zulusafe-cli libzulucrypt-exe1.2.0 libzulucrypt-exe-dev libzulucrypt1.2.0 
libzulucrypt-dev libzulucryptpluginmanager1.0.0 libzulucryptpluginmanager-dev 
libzulucrypt-plugins
Architecture: source amd64
Version: 5.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Marcio de Souza Oliveira 
Changed-By: Marcio de Souza Oliveira 
Description:
 libzulucrypt-dev - development files for libzulucrypt-1.2.0
 libzulucrypt-exe-dev - development files for the libzulucrypt-exe
 libzulucrypt-exe1.2.0 - provide the main functions of zulucrypt
 libzulucrypt-plugins - collection of plugins for zulucrypt
 libzulucrypt1.2.0 - provide the functions of zulumount
 libzulucryptpluginmanager-dev - development files for libzulucryptpluginmanager
 libzulucryptpluginmanager1.0.0 - provides support for plugins
 zulucrypt-cli - tool for encrypting volumes
 zulucrypt-gui - graphical front end for zulucrypt-cli
 zulumount-cli - tool that manages encrypted volumes
 zulumount-gui - graphical front end for zulumount-cli
 zulupolkit - handler the polkit privileges
 zulusafe-cli - cli that manages encrypted volumes

Changes:
 zulucrypt (5.2.0-2) unstable; urgency=medium
 .
   * Created the files zulupolkit.install and zuluPolkit.1.
   * debian/control:
   - Bumped Standards-Version to 4.1.0.
   - Created the package zulupolkit to acomodated the new tool
 zuluPolkit.
   - Removed qtkeychain-dev from Build-Depends.
 Thanks Mhogo Mchungu (Closes: #875291).
   * debian/rules:
   - Enabled the polkit support at build time.
   - Updated file.
   * Removed the files because are unnecessary with zulupolkit:
   - The files zulu*-gui-pkexec and zulu*-gui-pkexec.1.
   - The files org.debian.pkexec.zulu*-gui.policy.
   - The files zulu*-gui.links.
   * Removed the files zulu*-gui.menu.
   * Updated the files zulu*-gui.desktop.
   * Updated the files zulu*-gui.install.

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

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

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.

  
  

[Touch-packages] [Bug 1724079] Re: bluetooth applet hangs - 17.10 artful

[Daniel van Vugt]

Please look in /var/crash for a relevant crash file and when found
upload it using this command:

  ubuntu-bug /PATH/TO/WHATEVER.crash

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

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

Title:
  bluetooth applet hangs - 17.10 artful

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.10 
  bluez 5.46-0ubuntu3

  after failing to search for bluetooth mouse, bluetooth applet crashes. 
  restarting bluetooth.service yields "adapter not found" message upon trying 
to turn on bluetooth.

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

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/332330

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact] 
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in 

http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  
  [Regression Potential] 
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.

  b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]
   
  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.

  ubuntu@manual:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 192.168.122.2
  search maas

  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net 

[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Hui Wang]

@Daniel,

The fix is not in the artful and zesty, they also need this patch.

And here is the merge request for Artful and Zesty.
https://code.launchpad.net/~hui.wang/pulseaudio/+git/pulseaudio/+merge/331390

If you need me to do anything, please let me know.

Thanks.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Touch-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)

[Daniel van Vugt]

I don't really understand comment #17-#18 but it looks like nobody has
successfully tested downgrading Mesa yet (per comment #13).

You may have to download and install the previous version manually:
https://launchpad.net/ubuntu/+source/mesa/17.2.1-0ubuntu1/+build/13388627

That's the version which was in 17.10 until 5/6 October.


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

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

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

Title:
  Artful won't start with Wayland activated (AMD?)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On a fresch install, ubuntu stop and freeze before gdm is opened
  With no splah i have "started user manager for uid 121" and then it freeze

  need to uncomment WaylandEnable=false in custom.conf to start ubuntu
  so with xorg.

  
  lspci -nn | grep VGA

  return

  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  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: Sat Oct 14 07:36:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 
'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  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=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723753] Re: packagekitd crashed with SIGSEGV in std::vector<pkgIndexFile*, std::allocator<pkgIndexFile*> >::push_back()

[Seth Arnold]

** 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 packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1723753

Title:
  packagekitd crashed with SIGSEGV in std::vector >::push_back()

Status in packagekit package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: packagekit 1.1.7-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 15 17:07:08 2017
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2017-10-12 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/sh
  SegvAnalysis:
   Segfault happened at: 0x7fa8863ea861 
<_ZN13pkgSourceList15AddVolatileFileEP12pkgIndexFile+17>:   mov
0x18(%rdi),%rsi
   PC (0x7fa8863ea861) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   pkgSourceList::AddVolatileFile(pkgIndexFile*) () at 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   pkgSourceList::AddVolatileFile(std::__cxx11::basic_string const&, 
std::vector, std::allocator > >*) () at 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   AptIntf::init(char**) () at 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   ()
  Title: packagekitd crashed with SIGSEGV in pkgSourceList::AddVolatileFile()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1724094] Re: wpasupplicant nonce vulnerability (DSA-3999-1)

[Tyler Hicks]

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

Please see https://usn.ubuntu.com/usn/usn-3455-1/

** Information type changed from Public to Public Security

** This bug has been marked a duplicate of bug 1723909
   [security] WPA2: Many vulnerabilities discovered

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

Title:
  wpasupplicant nonce vulnerability (DSA-3999-1)

Status in wpa package in Ubuntu:
  New

Bug description:
  Having asked "When is this going to be merged into the Ubuntu package
  set?" question #659543 I was advised to raise this as a bug by
  "actionparsnip":

  Given this, please would you investigate the following security
  vulnerability as a bug:

  wpasupplicant nonce vulnerability (DSA-3999-1):

  In Mitre's CVE dictionary the following vulnerabilities for wpa
  clients have been identified: CVE-2017-13077, CVE-2017-13078,
  CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082,
  CVE-2017-13086, CVE-2017-13087, CVE-2017-13088

  Details from the Debian Security Advisory is here
  https://www.debian.org/security/2017/dsa-3999

  As the Debian wpasupplicant Maintainers have already provided a patch:

  For the oldstable distribution (jessie), these problems have been fixed in 
version 2.3-1+deb8u5.
  For the stable distribution (stretch), these problems have been fixed in 
version 2:2.4-1+deb9u1.
  For the testing distribution (buster), these problems have been fixed in 
version 2:2.4-1.1.
  For the unstable distribution (sid), these problems have been fixed in 
version 2:2.4-1.1.

  I believe this covers LTS 14.04, 16.04 and all versions of Ubuntu
  after 16.04 (16.10, 17.04, 17.10)

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

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

[Touch-packages] [Bug 1723744] Re: My ubuntu software not working

[Seth Arnold]

** 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1723744

Title:
  My ubuntu software not working

Status in xorg package in Ubuntu:
  New

Bug description:
  My ubuntu software not working. when i click on ubuntu software it
  processes and lastly failure. It is not opening .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 287586/60301312 files, 8149164/241200384 blocks
  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: Sun Oct 15 19:09:41 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   ath9k-msi, 1.1, 4.4.0-34-generic, x86_64: installed
   oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-34-generic, x86_64: 
installed
   oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-97-generic, x86_64: 
installed
  GraphicsCard:
   Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0764]
  InstallationDate: Installed on 2017-08-14 (61 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 3268
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=80718718-9c53-4401-aad9-03604b9f5eda ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 07F37C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd05/08/2017:svnDellInc.:pnInspiron3268:pvr:rvnDellInc.:rn07F37C:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Inspiron 3268
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Oct 15 19:08:53 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   61550 
   vendor DEL
  xserver.version: 2:1.18.4-0ubuntu0.6

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

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

[Touch-packages] [Bug 1724094] [NEW] wpasupplicant nonce vulnerability (DSA-3999-1)

[Aardvark Llama]

Public bug reported:

Having asked "When is this going to be merged into the Ubuntu package
set?" question #659543 I was advised to raise this as a bug by
"actionparsnip":

Given this, please would you investigate the following security
vulnerability as a bug:

wpasupplicant nonce vulnerability (DSA-3999-1):

In Mitre's CVE dictionary the following vulnerabilities for wpa clients
have been identified: CVE-2017-13077, CVE-2017-13078, CVE-2017-13079,
CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13086,
CVE-2017-13087, CVE-2017-13088

Details from the Debian Security Advisory is here
https://www.debian.org/security/2017/dsa-3999

As the Debian wpasupplicant Maintainers have already provided a patch:

For the oldstable distribution (jessie), these problems have been fixed in 
version 2.3-1+deb8u5.
For the stable distribution (stretch), these problems have been fixed in 
version 2:2.4-1+deb9u1.
For the testing distribution (buster), these problems have been fixed in 
version 2:2.4-1.1.
For the unstable distribution (sid), these problems have been fixed in version 
2:2.4-1.1.

I believe this covers LTS 14.04, 16.04 and all versions of Ubuntu after
16.04 (16.10, 17.04, 17.10)

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


** Tags: krack wifi wpasupplicant

** 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 wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1724094

Title:
  wpasupplicant nonce vulnerability (DSA-3999-1)

Status in wpa package in Ubuntu:
  New

Bug description:
  Having asked "When is this going to be merged into the Ubuntu package
  set?" question #659543 I was advised to raise this as a bug by
  "actionparsnip":

  Given this, please would you investigate the following security
  vulnerability as a bug:

  wpasupplicant nonce vulnerability (DSA-3999-1):

  In Mitre's CVE dictionary the following vulnerabilities for wpa
  clients have been identified: CVE-2017-13077, CVE-2017-13078,
  CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082,
  CVE-2017-13086, CVE-2017-13087, CVE-2017-13088

  Details from the Debian Security Advisory is here
  https://www.debian.org/security/2017/dsa-3999

  As the Debian wpasupplicant Maintainers have already provided a patch:

  For the oldstable distribution (jessie), these problems have been fixed in 
version 2.3-1+deb8u5.
  For the stable distribution (stretch), these problems have been fixed in 
version 2:2.4-1+deb9u1.
  For the testing distribution (buster), these problems have been fixed in 
version 2:2.4-1.1.
  For the unstable distribution (sid), these problems have been fixed in 
version 2:2.4-1.1.

  I believe this covers LTS 14.04, 16.04 and all versions of Ubuntu
  after 16.04 (16.10, 17.04, 17.10)

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

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

[Touch-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

[Bug Watch Updater]

** Changed in: gtk+3.0 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  First two characters typed in urlbar show immediately, other
  characters take up to 30 seconds to appear, or url will appear in full
  once enter key is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => 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/1721839

Title:
  Services asked for by UDEV do not get triggered

Status in systemd:
  New
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 print queue
  auto-created.

  What I expect is that the services get automatically started (and that
  

[Touch-packages] [Bug 1707502] Re: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: el
  subproceso instalado el script pre-removal devolvió el código de
  salida de error 1

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Jul 30 01:07:03 2017
  ErrorMessage: el subproceso instalado el script pre-removal devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2017-07-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: el 
subproceso instalado el script pre-removal devolvió el código de salida de 
error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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

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

[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Launchpad Bug Tracker]

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

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

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs

  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-04 (214 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  IpRoute:
   default via 192.168.0.5 dev eth0  proto static  metric 100 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166  metric 
100
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  

[Touch-packages] [Bug 1724079] [NEW] bluetooth applet hangs - 17.10 artful

[Jonathan Polak]

Public bug reported:

ubuntu 17.10 
bluez 5.46-0ubuntu3

after failing to search for bluetooth mouse, bluetooth applet crashes. 
restarting bluetooth.service yields "adapter not found" message upon trying to 
turn on bluetooth.

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


** Tags: artful bluetooth bluez

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

Title:
  bluetooth applet hangs - 17.10 artful

Status in bluez package in Ubuntu:
  New

Bug description:
  ubuntu 17.10 
  bluez 5.46-0ubuntu3

  after failing to search for bluetooth mouse, bluetooth applet crashes. 
  restarting bluetooth.service yields "adapter not found" message upon trying 
to turn on bluetooth.

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

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

[Touch-packages] [Bug 1721948] Re: gvfs-open/xdg-open shows message about 'gio open' which confuses user

[Brian Murray]

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

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

** Tags added: rls-bb-incoming

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

Title:
  gvfs-open/xdg-open shows message about 'gio open' which confuses user

Status in gvfs:
  Fix Released
Status in apport package in Ubuntu:
  Triaged
Status in gvfs package in Ubuntu:
  Invalid
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Try to report bug with Apport by terminal command `apport-bug apport`

  Expected results:
apport-bug reports bug silently

  Actual results:
get output in the terminal
$ apport-bug apport
This tool has been deprecated, use 'gio open' instead.
See 'gio help open' for more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sat Oct  7 13:50:23 2017
  InstallationDate: Installed on 2017-08-26 (41 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached

[aaronfranke]

Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=776147

** Bug watch added: GNOME Bug Tracker #776147
   https://bugzilla.gnome.org/show_bug.cgi?id=776147

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

Title:
  various apps abort on assertion - g_file_monitor_source_handle_event:
  code should not be reached

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  I was opening "War Thunder"- Steam game and when I changed settings in
  game and it restarted I saw also in desktop error-message. I do not
  remember did I have anything from "nautilus" open.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu10
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 11 22:00:01 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910)
  ProcCmdline: nautilus -n
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_file_monitor_source_handle_event () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo

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

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

[Touch-packages] [Bug 1712491] Re: Add backported bnxt driver to the initramfs

[Dan Streetman]

failing autopkg tests for this:
linux-lts-xenial (and other EOL linux-lts-*)
  these failures are due to bug 1723223; known bug that is not related to this 
bug.
linux-exynos5 on armhf
  this failed due to a testbed failure, unrelated to this bug.
linux on armhf
  this failure is due to bug 1724044; known bug this is not related to this bug.

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

Title:
  Add backported bnxt driver to the initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  We're adding a backported bnxt driver to Xenial (LP #1711056). It's an 
alternate for the regular Xenial driver that only manages NICs that are not 
supported by the regular Xenial driver. Since the backported driver lives in 
the special location kernel/ubuntu/bnxt it's not automatically included in the 
initramfs. But it's boot-critical so it needs to be added to the initramfs.

  [Test Case]
  Install the Xenial kernel on hardware that contains a newer Broadcom NIC and 
boots over that NIC. The machine will not come up because the NIC is not 
recognized.

  [Regression Risk]
  The driver is only loaded for newer Broadcom NICs. Older NICs are still 
managed by the regular Xenial driver, so there should be no regression.

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

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

[Touch-packages] [Bug 1721176] Re: util-linux blkid -o export is not working in 16.04

[Phillip Susi]

The version of blkid in 16.04 is 2.27.0 and is from 02-Nov-2015, and it
supports this option.  You are either running an older release than
16.04, or have an old locally built version.


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

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

Title:
   util-linux blkid -o export is not working in 16.04

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  patrikx3@workstation:~$ blkid -o export
  Invalid output format export. Choose from value,
device, list, or full

  I says export is not an available export (which is expected by update-
  grub) although the program is long ago is updated with this format.

  blkid --versions is 12-Feb-2003.

  When will be updated?
  I cannot update grub because of it.

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

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

[Touch-packages] [Bug 1724057] [NEW] Cannot change language when password is needed to update a package

[shaal]

Public bug reported:

I use my computer with both Hebrew & English.
My password is set in English.

I wanted to install an update of a software (Atom) through gdebi.
Because my keyboard was set on Hebrew, once the password pop up came on the 
screen, I could only type letters in Hebrew, there was no way to click on 
anything, or use the keyboard shortcut - to switch the keyboard back to 
English. 

I had to exit gdebi, switch the keyboard to English, and then run the
update again, so I can finally type the password in English.


Description:Ubuntu 17.04
Release:17.04

gdebi:
  Installed: 0.9.5.7+nmu1
  Candidate: 0.9.5.7+nmu1
  Version table:
 *** 0.9.5.7+nmu1 500
500 http://us.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu zesty/universe i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gdebi 0.9.5.7+nmu1
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct 16 11:07:07 2017
ExecutablePath: /usr/share/gdebi/gdebi-gtk
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdebi (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 gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1724057

Title:
  Cannot change language when password is needed to update a package

Status in gdebi package in Ubuntu:
  New

Bug description:
  I use my computer with both Hebrew & English.
  My password is set in English.

  I wanted to install an update of a software (Atom) through gdebi.
  Because my keyboard was set on Hebrew, once the password pop up came on the 
screen, I could only type letters in Hebrew, there was no way to click on 
anything, or use the keyboard shortcut - to switch the keyboard back to 
English. 

  I had to exit gdebi, switch the keyboard to English, and then run the
  update again, so I can finally type the password in English.

  
  Description:  Ubuntu 17.04
  Release:  17.04

  gdebi:
Installed: 0.9.5.7+nmu1
Candidate: 0.9.5.7+nmu1
Version table:
   *** 0.9.5.7+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu zesty/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gdebi 0.9.5.7+nmu1
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 16 11:07:07 2017
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

[Andrew]

As of ubuntu 16.04.3, the problem demonstrated below, still exists.
Here is the solution as to how to install it on a clean system.  Note
carefully, I always use apt-get, not synaptic.  Also note that the _apt
user already exists.

sudo chown _apt /var/lib/update-notifier/package-data-downloads/partial/
sudo apt-get install ttf-mscorefonts-installer

First, the Broken before chown to demonstrate the issue:
sudo apt-get install ttf-mscorefonts-installer
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  cabextract libmspack0
The following NEW packages will be installed:
  cabextract libmspack0 ttf-mscorefonts-installer
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 87.9 kB of archives.
After this operation, 338 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmspack0 
amd64 0.5-1ubuntu0.16.04.1 [37.0 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 cabextract 
amd64 1.6-1 [21.4 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
ttf-mscorefonts-installer all 3.4+nmu1ubuntu2 [29.5 kB]
Fetched 87.9 kB in 0s (118 kB/s)
Preconfiguring packages ...
Selecting previously unselected package libmspack0:amd64.
(Reading database ... 241441 files and directories currently installed.)
Preparing to unpack .../libmspack0_0.5-1ubuntu0.16.04.1_amd64.deb ...
Unpacking libmspack0:amd64 (0.5-1ubuntu0.16.04.1) ...
Selecting previously unselected package cabextract.
Preparing to unpack .../cabextract_1.6-1_amd64.deb ...
Unpacking cabextract (1.6-1) ...
Selecting previously unselected package ttf-mscorefonts-installer.
Preparing to unpack .../ttf-mscorefonts-installer_3.4+nmu1ubuntu2_all.deb ...
Unpacking ttf-mscorefonts-installer (3.4+nmu1ubuntu2) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
Processing triggers for update-notifier-common (3.168.5) ...
ttf-mscorefonts-installer: processing...
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/andale32.exe
Get:1 http://downloads.sourceforge.net/corefonts/andale32.exe [198 kB]
Fetched 198 kB in 1s (132 kB/s)
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/andale32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/arial32.exe
Get:1 http://downloads.sourceforge.net/corefonts/arial32.exe [554 kB]
Fetched 554 kB in 1s (364 kB/s)
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/arial32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/arialb32.exe
Get:1 http://downloads.sourceforge.net/corefonts/arialb32.exe [168 kB]
Fetched 168 kB in 1s (136 kB/s)
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/arialb32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
[..snip..]

After purging and then
sudo chown _apt /var/lib/update-notifier/package-data-downloads/partial/
We get the fixed:
sudo apt-get install ttf-mscorefonts-installerReading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  ttf-mscorefonts-installer
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/29.5 kB of archives.
After this operation, 134 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package ttf-mscorefonts-installer.
(Reading database ... 241463 files and directories currently installed.)
Preparing to unpack .../ttf-mscorefonts-installer_3.4+nmu1ubuntu2_all.deb ...
Unpacking ttf-mscorefonts-installer (3.4+nmu1ubuntu2) ...
Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
Processing triggers for update-notifier-common (3.168.5) ...
ttf-mscorefonts-installer: processing...
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/andale32.exe
Get:1 http://downloads.sourceforge.net/corefonts/andale32.exe [198 kB]
Fetched 198 kB in 0s (230 kB/s)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/arial32.exe
Get:1 http://downloads.sourceforge.net/corefonts/arial32.exe [554 kB]
Fetched 554 kB in 1s (422 kB/s)

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Launchpad Bug Tracker]

This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.5

---
dkms (2.2.0.3-2ubuntu11.5) xenial; urgency=medium

  * 0014-remove-initrd-backup.patch: When removing a kernel also remove
related .old-dkms file from /boot after its been created not before.
(LP: #1515513)

 -- Brian Murray   Thu, 05 Oct 2017 13:14:20 -0700

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

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Released
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Launchpad Bug Tracker]

This bug was fixed in the package dkms - 2.3-3ubuntu1.2

---
dkms (2.3-3ubuntu1.2) zesty; urgency=medium

  * 0014-remove-initrd-backup.patch: When removing a kernel also remove
related .old-dkms file from /boot after its been created not before.
(LP: #1515513)

 -- Brian Murray   Thu, 05 Oct 2017 11:45:16 -0700

** Changed in: dkms (Ubuntu Zesty)
   Status: Fix Committed => 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/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Released
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515513] Update Released

[Brian Murray]

The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Released
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723909] Re: [security] WPA2: Many vulnerabilities discovered

[Marc Deslauriers]

An update has already been uploaded to artful and is awaiting approval
by the release team.

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

Title:
  [security] WPA2: Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723909] Re: [security] WPA2: Many vulnerabilities discovered

[Anthony Harrington]

Thanks for the info, I'm just jumping the gun a little :D

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

Title:
  [security] WPA2: Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Till Kamppeter]

Reported this bug upstream:

https://github.com/systemd/systemd/issues/7109

** Bug watch added: github.com/systemd/systemd/issues #7109
   https://github.com/systemd/systemd/issues/7109

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/7109
   Importance: Unknown
   Status: Unknown

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

[Touch-packages] [Bug 1723909] Re: [security] WPA2: Many vulnerabilities discovered

[Anthony Harrington]

As 17.10 is also affected, what's the plan for artful?

Can 2.4-0ubuntu9.1 (or something else/numbered differently) simply be
copied over?

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

Title:
  [security] WPA2: Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723909] Re: [security] WPA2: Many vulnerabilities discovered

[Tyler Hicks]

Updates have been released:

  https://usn.ubuntu.com/usn/usn-3455-1/

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

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

Title:
  [security] WPA2: Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start

[Till Kamppeter]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  cupsd crashes with SIGSEGV on ubuntu 17.04 on start

Status in cups package in Ubuntu:
  Triaged

Bug description:
  Hey,
  I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it 
segfaults. Attaching strace ouput.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2012-12-20 (1698 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: cups 2.2.2-1ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 
pcie_aspm=force drm.vblankoffdelay=1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago)
  UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev 
nvidia-persistenced plugdev sambashare sudo usrp
  _MarkForUpload: True
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915

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

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

[Touch-packages] [Bug 1720525] Re: Update package to newer version

[Hans Joachim Desserud]

Sounds good. If there's no Ubuntu-only changes, then this report can
probably be converted to a sync request
https://wiki.ubuntu.com/SyncRequestProcess#Content_of_a_sync_request

(Unless someone beats me to it, I can probably do this once the new
development cycle starts)

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

Title:
  Update package to newer version

Status in python-evdev package in Ubuntu:
  New

Bug description:
  In Artful (and older releases) the version of the package is 0.4.7 even 
though 0.7.0 is already out. Debian Buster and Sid has 0.7.0 in the repos.
  The changes are bug fixes and features (see 
http://python-evdev.readthedocs.io/en/latest/changelog.html).

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Kai-Heng Feng]

Yea, all ath10k devices are affected. Linux kernel based on 4.13.6
should land in Artful soon.

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

** No longer affects: network-manager (Ubuntu)

-- 
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 linux package in Ubuntu:
  New

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/linux/+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 1724013] [NEW] mount does not correctly process x-* options

[DaytonaJohn]

Public bug reported:

According to the mount(8) man page:

All options prefixed with "x-" are interpreted as comments or as
userspace application-specific options.  These options are not stored
in  the  mtab  file,  nor  sent  to  the mount.type helpers nor to the
mount(2) system call.  The suggested format is x-appname.option (e.g.
x-systemd.automount).

However, adding any such option to cifs entry, such as "x-test.opt"
(other than x-systemd.automount) results in:

mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

No options starting with "x-" should be passed to mount.cifs, so the
mount should succeed.

Running Ubuntu 16.04.3 LTS
mount package installed is 2.27.1-6ubuntu3.3

This error always happens when such an option is specified. Here is an example 
fstab line that causes this failure:
//192.168.1.3/Public/mnt/mybookcifs   
noauto,x-test.opt,rw,users,noperm,guest,soft,cache=none,sec=none  0  0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mount 2.27.1-6ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Oct 16 12:29:40 2017
InstallationDate: Installed on 2016-04-22 (542 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/tcsh
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug fstab mount xenial

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

Title:
  mount does not correctly process x-* options

Status in util-linux package in Ubuntu:
  New

Bug description:
  According to the mount(8) man page:

  All options prefixed with "x-" are interpreted as comments or as
  userspace application-specific options.  These options are not stored
  in  the  mtab  file,  nor  sent  to  the mount.type helpers nor to the
  mount(2) system call.  The suggested format is x-appname.option (e.g.
  x-systemd.automount).

  However, adding any such option to cifs entry, such as "x-test.opt"
  (other than x-systemd.automount) results in:

  mount error(22): Invalid argument
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  No options starting with "x-" should be passed to mount.cifs, so the
  mount should succeed.

  Running Ubuntu 16.04.3 LTS
  mount package installed is 2.27.1-6ubuntu3.3

  This error always happens when such an option is specified. Here is an 
example fstab line that causes this failure:
  //192.168.1.3/Public/mnt/mybookcifs   
noauto,x-test.opt,rw,users,noperm,guest,soft,cache=none,sec=none  0  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mount 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 16 12:29:40 2017
  InstallationDate: Installed on 2016-04-22 (542 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723909] Re: [security] WPA2: Many vulnerabilities discovered

[Anthony Harrington]

This has been a mighty fine (and speedy) response to a big WPA2 flaw.
Kudos!

wpa (2.4-0ubuntu9.1) for zesty;
wpa (2.4-0ubuntu6.2) for xenial;
and wpa (2.1-0ubuntu1.5) for trusty are done so far and they address this bug.

(Obviously yakkety is no longer supported and ubuntu 16.10 users who
have stumbled upon this bug (or otherwise) are strongly encouraged to
upgrade. Ubuntu 16.10 reached EOL on July 20th 2017.)

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

Title:
  [security] WPA2: Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1579451] Re: Network manager doesn't ask for password in new connections

[peeesk]

** Attachment added: "syslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1579451/+attachment/4972822/+files/syslog.txt

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

Title:
  Network manager doesn't ask for password in new connections

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When trying to connect to a new WPA-PSK encrypted network, I click in the 
wireless icon and select the network I want to connect. Then the wireless icon 
suffers a glitch, I'm not prompted a password, and I'm informed that I'm 
offline.
  There's the first time in 2 or 3 months that I tried to connect to a new 
network.
  Despite this, in /etc/NetworkManager/system-connections/ there is the file 
matching the network I tried to connect, without a psk=... item on it. Then I 
edited it, put the password and could connect to the network like if I was 
already connected to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  7 21:30:11 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-05 (92 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
   default via 192.168.2.1 dev wlan0  proto static 
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.6  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   eth1   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

[Joseph Salisbury]

@Dimitri, yes I'll submit an SRU request.

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

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Tyler Hicks]

Hi - I tested the libseccomp SRU in Zesty using the following libseccomp
package version:

 - libseccomp2 2.3.1-2.1ubuntu2~17.04.1

I tested it with the following kernels:

 - linux-image-4.10.0-37-generic 4.10.0-37.41
   + does not contain seccomp logging patches
 - linux-image-4.10.0-38-generic 4.10.0-38.42
   + contains seccomp logging patches
   + installed from zesty-proposed

The libseccomp SRU testing was successful and followed what's documented
in the [libseccomp Test Case] section of this bug description.

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

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in libseccomp source package in Zesty:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [libseccomp Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:

  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid 

[Touch-packages] [Bug 1579451] Re: Network manager doesn't ask for password in new connections

[peeesk]

I use Ubuntu 16.04 LTS and this bug appeared after some more then half a
year of using it.

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

Title:
  Network manager doesn't ask for password in new connections

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When trying to connect to a new WPA-PSK encrypted network, I click in the 
wireless icon and select the network I want to connect. Then the wireless icon 
suffers a glitch, I'm not prompted a password, and I'm informed that I'm 
offline.
  There's the first time in 2 or 3 months that I tried to connect to a new 
network.
  Despite this, in /etc/NetworkManager/system-connections/ there is the file 
matching the network I tried to connect, without a psk=... item on it. Then I 
edited it, put the password and could connect to the network like if I was 
already connected to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  7 21:30:11 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-05 (92 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
   default via 192.168.2.1 dev wlan0  proto static 
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.6  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   eth1   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1579451] Re: Network manager doesn't ask for password in new connections

[Launchpad Bug Tracker]

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

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

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

Title:
  Network manager doesn't ask for password in new connections

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When trying to connect to a new WPA-PSK encrypted network, I click in the 
wireless icon and select the network I want to connect. Then the wireless icon 
suffers a glitch, I'm not prompted a password, and I'm informed that I'm 
offline.
  There's the first time in 2 or 3 months that I tried to connect to a new 
network.
  Despite this, in /etc/NetworkManager/system-connections/ there is the file 
matching the network I tried to connect, without a psk=... item on it. Then I 
edited it, put the password and could connect to the network like if I was 
already connected to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  7 21:30:11 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-05 (92 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
   default via 192.168.2.1 dev wlan0  proto static 
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.6  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   eth1   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1723822] Re: uncaught TypeError triggers ValueError

[Brian Murray]

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

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

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

Title:
  uncaught TypeError triggers ValueError

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  $ ubuntu-bug nautilus
  ERROR: hook /usr/share/apport/package-hooks/source_nautilus.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in 
_run_hook
  symb['add_info'](report)
File "/usr/share/apport/package-hooks/source_nautilus.py", line 23, in 
add_info
  report["usr_lib_nautilus"] = package_versions(*sorted(plugin_packages))
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 785, in 
package_versions
  map(max, [map(len, t) for t in zip(*versions)])
  ValueError: not enough values to unpack (expected 2, got 0)
  This tool has been deprecated, use 'gio open' instead.
  See 'gio help open' for more info.

  $ Created new window in existing browser session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  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
  CrashReports:
   640:121:119:20593327:2017-10-14 08:49:43.994080376 -0700:2017-10-14 
08:49:24.682136558 -0700:/var/crash/_usr_bin_gnome-shell.121.crash
   640:0:119:712257:2017-10-13 22:55:49.843941428 -0700:2017-10-13 
22:55:48.723911385 -0700:/var/crash/_usr_lib_udisks2_udisksd.0.crash
   640:1000:119:432238:2017-10-14 07:48:01.498643348 -0700:2017-10-14 
07:48:00.714643372 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.crash
   664:1000:119:0:2017-10-13 19:55:40.447393054 -0700:2017-10-13 
19:55:40.447393054 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.upload
   600:112:119:0:2017-10-13 19:55:42.247460153 -0700:2017-10-13 
19:55:42.247460153 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 17:52:08 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  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/1723822/+subscriptions

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

[Touch-packages] [Bug 1723909] Re: [security] WPA2: Many vulnerabilities discovered

[LocutusOfBorg]

** Changed in: wpa (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  [security] WPA2: Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

[Dimitri John Ledkov]

@jsalisbury that kernel is very nice, could you please cherrypick that
patch and include it in the next available/convenient src:linux SRU?

I have added the SRU template to the bug report.

** Description changed:

+ [Impact]
+ Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.
+ 
+ [Fix]
+ Generate change uevent when size of /dev/nbd0 changes
+ 
+ [Testcase]
+ * Start udevadm monitor
+ * modprobe nbd
+ * use ndb-client to connect something to /dev/nbd0
+ * observe that there are change udev events generated on /dev/nbd0 itself
+ 
+ [Regression Potential]
+ There is no change to existing uevents, or their ordering.
+ There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions
+ 
+ [Original Bug Report]
+ 
  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.
  
  Using Ubuntu Natty, related packages versions:
- nbd-client 1:2.9.16-6ubuntu1 
- initramfs-tools 0.98.1ubuntu9
+ nbd-client 1:2.9.16-6ubuntu1
+ initramfs-tools 0.98.1ubuntu9
  
  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
-   while [ -z "${FSTYPE}" ]; do
-   FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})
+  while [ -z "${FSTYPE}" ]; do
+   FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})
  
-   # Run failure hooks, hoping one of them can fix up the system
-   # and we can restart the wait loop.  If they all fail, abort
-   # and move on to the panic handler and shell.
-   if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
-   break
-   fi
-   done
+   # Run failure hooks, hoping one of them can fix up the system
+   # and we can restart the wait loop.  If they all fail, abort
+   # and move on to the panic handler and shell.
+   if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
+    break
+   fi
+  done
  
  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'
  
  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked and
  while it was still waiting. But I tried adding a "sleep 5" as the last
  line of local-top/nbd, so that the nbd message was displayed a lot
  before wait-for-root was called, and it didn't make a difference. So I
  don't think a race condition is involved in this problem.
  
  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after 

[Touch-packages] [Bug 1721217] Re: package ca-certificates 20170717~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Launchpad Bug Tracker]

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  package ca-certificates 20170717~16.04.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  ..at installation of the update, the update installer reported the bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20170717~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Oct  4 11:46:21 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2013-09-23 (1471 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.25
  SourcePackage: ca-certificates
  Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-08-18 (411 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-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] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From swgre...@us.ibm.com 2017-10-16 11:27 EDT---
(In reply to comment #19)
> Any updates? Have you been able to monitor fs.aio-nr exhaustion?

Sorry, no.  Is this data critical for debug?  I would have to disrupt
our current configuration in order to bring up the Ubuntu KVM host.  If
so, I'll see what I can do.  Thanks...

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

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

[Pasquale Pompeo]

Hi, for me it happens everytime. But it happens also with other distros running 
kernel 4.13 so I think it's a kernel-related problem. 
For example, on my Opensuse Leap with upstream kernels, the problem went away 
with the upgrade to 4.13.6 version.

-- 
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 1723907] Re: 16.04 server can't reboot

[Valeri Rangelov]

May I ask you for your VM setup, host or anything else which can point
to something specific. Is it working with one / few days uptime of VM ?

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

Title:
  16.04 server can't reboot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  I run 5 (five) Ubuntu 16.04 VMs on Centos7 host, i.e. inside of kvm.
  After several months of uptime I can't shutdown or reboot any of this VMs-
  if I type reboot or shutdown then it runs forever...
  No error messages, nothing...

  Thank you!

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

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

[Touch-packages] [Bug 1718966] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Installing snaps is not possible on Ubuntu 14.04 when having /var on
  its own partition, whether its LVM or not.

  The issue is with the core snap being unable to mount:

  The error with /var isolated and using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  The error with /var isolated but without using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service
 failed to load: No such file or directory. See system logs and 'systemctl 
status 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service'
 for details.
  )

  The same error happens if I try to install the hello-world snap (with
  LVM in this example):

  root@ubuntu:~# snap install hello-world
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  I cannot reproduce the issue in Ubuntu 16.04.

  I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image
  which doesn't isolate /var on its own partition. I tried adding a
  secondary disk to that cloud image VM and create a dummy VG and LV,
  but couldn't reproduce the issue.

  Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with
  only a / partition and swap.

  [Test Case]

  # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and
  configure /, /var and swap on their own partitions (with LVM or not,
  the issue happens in both situations).

  root@ubuntu:~# lvs
  LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
  rootvol vg00 -wi-ao--- 3.72g
  swap vg00 -wi-ao--- 3.72g
  varvol vg00 -wi-ao--- 3.72g

  root@ubuntu:~# df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 484M 4.0K 484M 1% /dev
  tmpfs 100M 988K 99M 1% /run
  /dev/dm-0 3.7G 1.7G 1.8G 49% /
  none 4.0K 0 4.0K 0% /sys/fs/cgroup
  none 5.0M 0 5.0M 0% /run/lock
  none 497M 0 497M 0% /run/shm
  none 100M 0 100M 0% /run/user
  /dev/mapper/vg00-varvol 3.7G 716M 2.8G 21% /var

  # Upgrade system, install snapd and reboot

  root@ubuntu:~# apt update
  root@ubuntu:~# apt upgrade -y
  root@ubuntu:~# apt install -y snapd
  root@ubuntu:~# reboot

  # After reboot, check kernel version and try to install the canonical-
  livepatch snap:

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# snap list
  No snaps are installed yet. Try "snap install hello-world".

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  [Regression Potential]

  - Unit file has been added to systemd, could cause an error in some units 
initialization. Since systemd is not used as "init" system for Trusty, this is 
minor regression.
  - Could break all systemd units depending (After=/Wants=) 
systemd-fsck@.service but they are already broken.

  ** A "pre-SRU" test package provided in Tinoco's PPA has been also
  intensively 

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 204-5ubuntu20.25

---
systemd (204-5ubuntu20.25) trusty; urgency=medium

  * rules: introduce fsck@.service for snappy (LP: #1718966)

 -- Rafael David Tinoco   Mon, 02 Oct 2017
21:39:38 +

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

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

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Installing snaps is not possible on Ubuntu 14.04 when having /var on
  its own partition, whether its LVM or not.

  The issue is with the core snap being unable to mount:

  The error with /var isolated and using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  The error with /var isolated but without using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service
 failed to load: No such file or directory. See system logs and 'systemctl 
status 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service'
 for details.
  )

  The same error happens if I try to install the hello-world snap (with
  LVM in this example):

  root@ubuntu:~# snap install hello-world
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  I cannot reproduce the issue in Ubuntu 16.04.

  I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image
  which doesn't isolate /var on its own partition. I tried adding a
  secondary disk to that cloud image VM and create a dummy VG and LV,
  but couldn't reproduce the issue.

  Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with
  only a / partition and swap.

  [Test Case]

  # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and
  configure /, /var and swap on their own partitions (with LVM or not,
  the issue happens in both situations).

  root@ubuntu:~# lvs
  LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
  rootvol vg00 -wi-ao--- 3.72g
  swap vg00 -wi-ao--- 3.72g
  varvol vg00 -wi-ao--- 3.72g

  root@ubuntu:~# df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 484M 4.0K 484M 1% /dev
  tmpfs 100M 988K 99M 1% /run
  /dev/dm-0 3.7G 1.7G 1.8G 49% /
  none 4.0K 0 4.0K 0% /sys/fs/cgroup
  none 5.0M 0 5.0M 0% /run/lock
  none 497M 0 497M 0% /run/shm
  none 100M 0 100M 0% /run/user
  /dev/mapper/vg00-varvol 3.7G 716M 2.8G 21% /var

  # Upgrade system, install snapd and reboot

  root@ubuntu:~# apt update
  root@ubuntu:~# apt upgrade -y
  root@ubuntu:~# apt install -y snapd
  root@ubuntu:~# reboot

  # After reboot, check kernel version and try to install the canonical-
  livepatch snap:

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# snap list
  No snaps are installed yet. Try "snap install hello-world".

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  [Regression Potential]

  - Unit file has been added to systemd, could cause an error in some units 
initialization. Since systemd is not used as "init" system for Trusty, this is 
minor regression.
  - Could break all systemd units depending (After=/Wants=) 
systemd-fsck@.service but they are already broken.

  ** A "pre-SRU" test package provided in Tinoco's PPA has been also
  intensively tested with success, which bring even more confidence for
  this change. Note that the same 

[Touch-packages] [Bug 1723907] Re: 16.04 server can't reboot

[Valeri Rangelov]

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

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

Title:
  16.04 server can't reboot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  I run 5 (five) Ubuntu 16.04 VMs on Centos7 host, i.e. inside of kvm.
  After several months of uptime I can't shutdown or reboot any of this VMs-
  if I type reboot or shutdown then it runs forever...
  No error messages, nothing...

  Thank you!

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

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Eric Desrochers]

** Tags removed: patch

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

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Installing snaps is not possible on Ubuntu 14.04 when having /var on
  its own partition, whether its LVM or not.

  The issue is with the core snap being unable to mount:

  The error with /var isolated and using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  The error with /var isolated but without using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service
 failed to load: No such file or directory. See system logs and 'systemctl 
status 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service'
 for details.
  )

  The same error happens if I try to install the hello-world snap (with
  LVM in this example):

  root@ubuntu:~# snap install hello-world
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  I cannot reproduce the issue in Ubuntu 16.04.

  I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image
  which doesn't isolate /var on its own partition. I tried adding a
  secondary disk to that cloud image VM and create a dummy VG and LV,
  but couldn't reproduce the issue.

  Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with
  only a / partition and swap.

  [Test Case]

  # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and
  configure /, /var and swap on their own partitions (with LVM or not,
  the issue happens in both situations).

  root@ubuntu:~# lvs
  LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
  rootvol vg00 -wi-ao--- 3.72g
  swap vg00 -wi-ao--- 3.72g
  varvol vg00 -wi-ao--- 3.72g

  root@ubuntu:~# df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 484M 4.0K 484M 1% /dev
  tmpfs 100M 988K 99M 1% /run
  /dev/dm-0 3.7G 1.7G 1.8G 49% /
  none 4.0K 0 4.0K 0% /sys/fs/cgroup
  none 5.0M 0 5.0M 0% /run/lock
  none 497M 0 497M 0% /run/shm
  none 100M 0 100M 0% /run/user
  /dev/mapper/vg00-varvol 3.7G 716M 2.8G 21% /var

  # Upgrade system, install snapd and reboot

  root@ubuntu:~# apt update
  root@ubuntu:~# apt upgrade -y
  root@ubuntu:~# apt install -y snapd
  root@ubuntu:~# reboot

  # After reboot, check kernel version and try to install the canonical-
  livepatch snap:

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# snap list
  No snaps are installed yet. Try "snap install hello-world".

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  [Regression Potential]

  - Unit file has been added to systemd, could cause an error in some units 
initialization. Since systemd is not used as "init" system for Trusty, this is 
minor regression.
  - Could break all systemd units depending (After=/Wants=) 
systemd-fsck@.service but they are already broken.

  ** A "pre-SRU" test package provided in Tinoco's PPA has been also
  intensively tested with success, which bring even more confidence for
  this change. Note that the same level/quality of testing will be
  performed one more time when the package will be found in trusty-
  proposed. **

  * Manual autopkgtest againts the systemd .dsc file :
  adt-run [12:31:42]:  summary
  timedatedPASS
  hostnamedPASS
  localed-locale   PASS
  localed-x11-keymap   PASS
  logind 

[Touch-packages] [Bug 1710377] Re: "Additional Drivers" desktop shortcut missing in Ubuntu 17.10

[Sebastien Bacher]

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

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

Title:
  "Additional Drivers" desktop shortcut missing in Ubuntu 17.10

Status in software-properties package in Ubuntu:
  New

Bug description:
  There used to be an "Additional Drivers" shortcut in the applications
  list in Unity. This shortcut is missing in the GNOME Shell Overview in
  Ubuntu 17.10.

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

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

Verifying...

http://pastebin.ubuntu.com/25753116/

After using -proposed version:

http://paste.ubuntu.com/25753146/

Considering this fixed. Verified!

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

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

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Installing snaps is not possible on Ubuntu 14.04 when having /var on
  its own partition, whether its LVM or not.

  The issue is with the core snap being unable to mount:

  The error with /var isolated and using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  The error with /var isolated but without using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service
 failed to load: No such file or directory. See system logs and 'systemctl 
status 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service'
 for details.
  )

  The same error happens if I try to install the hello-world snap (with
  LVM in this example):

  root@ubuntu:~# snap install hello-world
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  I cannot reproduce the issue in Ubuntu 16.04.

  I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image
  which doesn't isolate /var on its own partition. I tried adding a
  secondary disk to that cloud image VM and create a dummy VG and LV,
  but couldn't reproduce the issue.

  Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with
  only a / partition and swap.

  [Test Case]

  # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and
  configure /, /var and swap on their own partitions (with LVM or not,
  the issue happens in both situations).

  root@ubuntu:~# lvs
  LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
  rootvol vg00 -wi-ao--- 3.72g
  swap vg00 -wi-ao--- 3.72g
  varvol vg00 -wi-ao--- 3.72g

  root@ubuntu:~# df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 484M 4.0K 484M 1% /dev
  tmpfs 100M 988K 99M 1% /run
  /dev/dm-0 3.7G 1.7G 1.8G 49% /
  none 4.0K 0 4.0K 0% /sys/fs/cgroup
  none 5.0M 0 5.0M 0% /run/lock
  none 497M 0 497M 0% /run/shm
  none 100M 0 100M 0% /run/user
  /dev/mapper/vg00-varvol 3.7G 716M 2.8G 21% /var

  # Upgrade system, install snapd and reboot

  root@ubuntu:~# apt update
  root@ubuntu:~# apt upgrade -y
  root@ubuntu:~# apt install -y snapd
  root@ubuntu:~# reboot

  # After reboot, check kernel version and try to install the canonical-
  livepatch snap:

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# snap list
  No snaps are installed yet. Try "snap install hello-world".

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  [Regression Potential]

  - Unit file has been added to systemd, could cause an error in some units 
initialization. Since systemd is not used as "init" system for Trusty, this is 
minor regression.
  - Could break all systemd units depending (After=/Wants=) 
systemd-fsck@.service but they are already broken.

  ** A "pre-SRU" test package provided in Tinoco's PPA has been also
  intensively tested with success, which bring even more confidence for
  this change. Note that the same level/quality of testing will be
  performed one more time when the package will be found in 

[Touch-packages] [Bug 1723956] [NEW] busybox-static: several network applets segfaulting

[Simon Rettberg]

Public bug reported:

On a fully up-to-date Ubuntu 17.04, running most applets from busybox-
static that are network-related lead to a segfault. Example:

$ busybox nslookup google.com 8.8.8.8
Server:8.8.8.8
Segmentation fault

$ busybox
BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) multi-call binary.
[...]

$ apt-cache policy busybox
busybox:
  Installed: (none)
  Candidate: 1:1.22.0-19ubuntu2
  Version table:
 1:1.22.0-19ubuntu2 500
500 http://ftp.fau.de/ubuntu zesty/universe amd64 Packages

$ dpkg -S /bin/busybox 
busybox-static: /bin/busybox

$ apt-cache policy busybox-static
busybox-static:
  Installed: 1:1.22.0-19ubuntu2
  Candidate: 1:1.22.0-19ubuntu2
  Version table:
 *** 1:1.22.0-19ubuntu2 500
500 http://ftp.fau.de/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status


This even happens when passing invalid domains or DNS servers to use
that don't actually run any DNS service. (like "busybox nslookup
google.com 1.2.3.4" or "busybox nslookup bar.foof00 8.8.8.8"), so it
seems to be early in the network setup.

I could not reproduce the problem on the very same system when compiling stock 
busybox 1.22.1 (why even? we're at 1.27.x!) myself, neither with a recent git 
clone. Also two VMs I had at hand running Ubuntu 14.04 and 16.04 didn't show 
this problem with busybox-static. Installing the package "busybox" (which 
removes busybox-static) fixes the problem on 17.04.
The only thing that might be related in any way about my system is that it has 
no IPv6 connectivity (apart from the link-local address).

I also sent a crash report when the apport window popped up, but I have
no idea where this ends up and how to add further information, hence
this report here. Please let me know if this seemingly trivial bug
cannot be reproduced instantly, so I can try to assist with further
information.

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

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

Title:
  busybox-static: several network applets segfaulting

Status in busybox package in Ubuntu:
  New

Bug description:
  On a fully up-to-date Ubuntu 17.04, running most applets from busybox-
  static that are network-related lead to a segfault. Example:

  $ busybox nslookup google.com 8.8.8.8
  Server:8.8.8.8
  Segmentation fault

  $ busybox
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) multi-call binary.
  [...]

  $ apt-cache policy busybox
  busybox:
Installed: (none)
Candidate: 1:1.22.0-19ubuntu2
Version table:
   1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/universe amd64 Packages

  $ dpkg -S /bin/busybox 
  busybox-static: /bin/busybox

  $ apt-cache policy busybox-static
  busybox-static:
Installed: 1:1.22.0-19ubuntu2
Candidate: 1:1.22.0-19ubuntu2
Version table:
   *** 1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status


  This even happens when passing invalid domains or DNS servers to use
  that don't actually run any DNS service. (like "busybox nslookup
  google.com 1.2.3.4" or "busybox nslookup bar.foof00 8.8.8.8"), so it
  seems to be early in the network setup.

  I could not reproduce the problem on the very same system when compiling 
stock busybox 1.22.1 (why even? we're at 1.27.x!) myself, neither with a recent 
git clone. Also two VMs I had at hand running Ubuntu 14.04 and 16.04 didn't 
show this problem with busybox-static. Installing the package "busybox" (which 
removes busybox-static) fixes the problem on 17.04.
  The only thing that might be related in any way about my system is that it 
has no IPv6 connectivity (apart from the link-local address).

  I also sent a crash report when the apport window popped up, but I
  have no idea where this ends up and how to add further information,
  hence this report here. Please let me know if this seemingly trivial
  bug cannot be reproduced instantly, so I can try to assist with
  further information.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Sebastien Bacher]

that has been fixed in
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/1.2.0+dfsg-3.1ubuntu3

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 Released

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 1723909] Re: [security] WPA2: Many vulnerabilities discovered

[Launchpad Bug Tracker]

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

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

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

Title:
  [security] WPA2: Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723909] Re: [security] WPA2: Many vulnerabilities discovered

[Eero]

Debian has patched the following CVEs:
CVE-2017-13077 CVE-2017-13078 CVE-2017-13079 CVE-2017-13080 
CVE-2017-13081 CVE-2017-13082 CVE-2017-13086 CVE-2017-13087 
CVE-2017-13088

https://lists.debian.org/debian-security-announce/2017/msg00261.html

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13077

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13078

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13079

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13080

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13081

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13082

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13086

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13087

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13088

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

Title:
  [security] WPA2: Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  New

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

[Jeremy Bicha]

** Package changed: mutter (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => In Progress

** Project changed: mutter => gtk

** Package changed: mutter (Debian) => gtk+3.0 (Debian)

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

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Debian:
  Confirmed

Bug description:
  First two characters typed in urlbar show immediately, other
  characters take up to 30 seconds to appear, or url will appear in full
  once enter key is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723909] Re: [security] WPA2: Many vulnerabilities discovered

[dino99]

** Summary changed:

- [security] Many vulnerabilities discovered
+ [security] WPA2: Many vulnerabilities discovered

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

Title:
  [security] WPA2: Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  New

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719043] [NEW] Gnome web urlbar very slow to show typed input

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

First two characters typed in urlbar show immediately, other characters
take up to 30 seconds to appear, or url will appear in full once enter
key is pressed.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: epiphany-browser 3.26.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 22 18:42:19 2017
InstallationDate: Installed on 2017-09-22 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: epiphany-browser
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mutter
 Importance: Medium
 Status: Confirmed

** Affects: epiphany-browser (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: In Progress

** Affects: mutter (Debian)
 Importance: Unknown
 Status: Confirmed


** Tags: amd64 apport-bug artful wayland-session
-- 
Gnome web urlbar very slow to show typed input
https://bugs.launchpad.net/bugs/1719043
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 278095] RE

[Troels]

Check 
[Bug 278095] Re: MASTER crash in getenv() ... spi_atk_bridge_exit_func()

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

Title:
  MASTER crash in getenv() ... spi_atk_bridge_exit_func()

Status in at-spi:
  Expired
Status in apport package in Ubuntu:
  Invalid
Status in at-spi package in Ubuntu:
  Fix Released
Status in firefox-3.0 package in Ubuntu:
  Invalid
Status in apport source package in Intrepid:
  Invalid
Status in at-spi source package in Intrepid:
  Fix Released
Status in firefox-3.0 source package in Intrepid:
  Invalid
Status in apport source package in Jaunty:
  Invalid
Status in at-spi source package in Jaunty:
  Fix Released
Status in firefox-3.0 source package in Jaunty:
  Invalid

Bug description:
  This crash seems to occur most frequently when opening a new URL in an
  existing Firefox process.  The URL is successfully opened, but the
  client process then crashes while exiting.  The result is that the
  operation appears to work, but there has been a crash in the
  background (which is then displayed by update-notifier and apport).

  Steps to reproduce:

  1. check "Enable assisitive technologies"  in Preferences -> Assistive 
Technologies
  2. restart X session
  3. start firefox
  4. start from terminal: firefox http://www.ubuntu.com 

  Result: see crash.

  Verify: with updated package it shouldnt crash.

  ===

  I am using Ubuntu 8.10 beta

  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/lib/firefox-3.0.3/firefox
  Package: firefox-3.0 3.0.3+build1+nobinonly-0ubuntu1
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/lib/firefox-3.0.3/firefox 
https://bugs.launchpad.net/ubuntu/+source/seahorse-plugins/+filebug/7cEBHSr9Xvdab5iSpVMC09PXb6N?field.title=seahorse-agent+crashed+with+SIGSEGV+in+_XIOError%28%29
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: firefox-3.0
  StacktraceTop:
   getenv () from /lib/tls/i686/cmov/libc.so.6
   g_getenv () from /usr/lib/libglib-2.0.so.0
   ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
   exit () from /lib/tls/i686/cmov/libc.so.6
   __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
  Title: firefox crashed with SIGSEGV in getenv()
  Uname: Linux 2.6.27-4-generic i686
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev 
video

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/278095/+subscriptions

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

[Touch-packages] [Bug 238755] RE

[Kennedyshead]

Check 
Re: Jag klarar inte plдdar mцte idag

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

Title:
  'Account has expired' message when adding a new user, after "passwd -l
  root"

Status in landscape-client package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in landscape-client source package in Hardy:
  Won't Fix
Status in shadow source package in Hardy:
  Won't Fix
Status in landscape-client source package in Intrepid:
  Invalid
Status in shadow source package in Intrepid:
  Fix Released
Status in shadow package in Debian:
  Fix Released

Bug description:
  Binary package hint: adduser

  I've repeatedly added new users, but receive a seemingly spurious
  error:

  rich@aias:~$ sudo adduser james
  Adding user `james' ...
  Adding new group `james' (1004) ...
  Adding new user `james' (1004) with group `james' ...
  Creating home directory `/home/james' ...
  Copying files from `/etc/skel' ...
  Enter new UNIX password: 
  Retype new UNIX password: 
  passwd: password updated successfully
  Your account has expired; please contact your system administrator
  chfn: PAM authentication failed
  adduser: `/usr/bin/chfn james' returned error code 1. Exiting.

  However, the user can log in.

  rich@aias:~$ finger james
  Login: james  Name: 
  Directory: /home/jamesShell: /bin/bash
  On since Mon Jun  9 21:19 (PDT) on tty1   4 minutes 57 seconds idle
   (messages off)
  No mail.
  No Plan.

  adduser version: 3.105ubuntu1
  ubuntu version: 8.04 , fully updated

  I've marked this as a security issue, since pam is part of the error
  message.

  Update:

  This seems to be related to the use of "passwd -l root".
  Until the Debian fix shows up in hardy, here is a workaround, thanks to 
Nicolas François:

   sudo passwd --unlock root
   sudo usermod --lock root

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

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

[Touch-packages] [Bug 1714803] Re: Search list in resolv.conf breaks resolving for that domain

[Matthias Fratz]

In fact it's slightly simpler in that both a.example.com and
b.example.com are public domains. (This is why I put them in the global
config to begin with; these domains will resolve over any nameserver.)
Thus it's not so much that queries for b.example.com don't go to
W.X.Y.Z; it's that they don't go anywhere.

More precisely: By default, ie. without a Domains= line in
resolved.conf, b.example.com resolves correctly: the query goes to some
random nameserver, which can resolve it because it's a public domain.
With Domains=b.example.com, b.example.com fails to resolve, and systemd-
resolve reports "No appropriate name servers or networks for name found"
without querying any server. (At least I cannot observe any DNS or LLMNR
traffic on the network connection of my test VM.)

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

Title:
  Search list in resolv.conf breaks resolving for that domain

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.04
  systemd 232-21ubuntu5

  Adding a domain to the search list in /etc/resolv.conf breaks
  resolving for that domain. Not only does the search list not get used
  as expected, but host names in the domain cannot be resolved by
  systemd-resolved at all.

  I just ran into this after upgrading from ubuntu 16.04 to 17.04 which
  enabled systemd-resolved. I have for a long time used resolveconf to
  add a 'search my-domain'-line to my /etc/resolv.conf.

  
  Example of expected behaviour. With Googles DNS server (8.8.8.8) and 
ubuntu.com in the search list in /etc/resolv.conf. Both dig and systemd-resolve 
can resolve www.ubuntu.com and www:

  $ cat /etc/resolv.conf 
  nameserver 8.8.8.8
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55037
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   501 IN  A   91.189.89.115
  
  $ dig +search +nostat +nocmd www
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25772
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   382 IN  A   91.189.89.103
  
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.89.115
  
  -- Information acquired via protocol DNS in 2.7ms.
  -- Data is authenticated: no
  $ systemd-resolve www
  www: 91.189.90.59
   (www.ubuntu.com)
  
  -- Information acquired via protocol DNS in 3.8ms.
  -- Data is authenticated: no

  Ubuntu 17.04 default config, with the systemd-resolved name server in
  /etc/resolv.conf and no search list. www.ubuntu.com can still be
  resolved correctly:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64646
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   482 IN  A   91.189.89.110
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.90.58
  
  -- Information acquired via protocol DNS in 18.2ms.
  -- Data is authenticated: no

  Broken behaviour, using the systemd-resolved name server and specify
  ubuntu.com in search list. Resolving fails for www.ubuntu.com and www,
  both using dig (DNS) and using sytemd-resolve:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  $ dig +search +nostat +nocmd www
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50588
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  $ 

[Touch-packages] [Bug 1723909] Re: [security] Many vulnerabilities discovered

[dino99]

Does not know why Ubuntu has a delta with Debian Experimental. Some cve were 
fixed.
http://metadata.ftp-master.debian.org/changelogs/main/w/wpa/wpa_2.6-4_changelog

well, maybe due to grave & serious reported bugs : 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=wpasupplicant;dist=unstable

Source: http://w1.fi/security/2017-1/

** Information type changed from Public to Public Security

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

Title:
  [security] Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  New

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718869] Re: Migrate to hunspell-en-us in libreoffice-dictionaries

[Gunnar Hjalmarsson]

Sure, if that can be accomplished somehow. But if I understood it
correctly, Rene failed to do so.

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

Title:
  Migrate to hunspell-en-us in libreoffice-dictionaries

Status in hunspell-en-us package in Ubuntu:
  New
Status in libreoffice-dictionaries package in Ubuntu:
  New
Status in hunspell-en-us package in Debian:
  New
Status in libreoffice-dictionaries package in Debian:
  Won't Fix

Bug description:
  libreoffice-dictionaries upstream ships hunspell-en-us, which is
  properly maintained and is newer than the one currently in Debian and
  Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in
  libreoffice-dictionaries. The other English variants (British,
  Australian and others) are already provided by libreoffice-
  dictionaries and are more up-to-date than the US variant.

  Debian bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159

  Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff 
and en_US.dic but there is not a built package for them.
  
https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/

  See this README from the Libreoffice/dictionaries git,
  https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt

  It seems that this is now dead,
  https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hunspell-en-us 20070829-6ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 09:43:32 2017
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: hunspell-en-us
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+subscriptions

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

[Touch-packages] [Bug 1723909] [NEW] [security] Many vulnerabilities discovered

[dino99]

Public bug reported:

This is a high vulnerability problem:

The attack works against all modern protected Wi-Fi networks

All details:
https://www.krackattacks.com/

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: wpasupplicant 2.4-0ubuntu9
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: Mon Oct 16 11:54:57 2017
EcryptfsInUse: Yes
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session

** Summary changed:

- [security] Many vulnerabilies discovered
+ [security] Many vulnerabilities discovered

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

Title:
  [security] Many vulnerabilities discovered

Status in wpa package in Ubuntu:
  New

Bug description:
  This is a high vulnerability problem:

  The attack works against all modern protected Wi-Fi networks

  All details:
  https://www.krackattacks.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu9
  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: Mon Oct 16 11:54:57 2017
  EcryptfsInUse: Yes
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723907] [NEW] 16.04 server can't reboot

[sles]

Public bug reported:

Hello!

I run 5 (five) Ubuntu 16.04 VMs on Centos7 host, i.e. inside of kvm.
After several months of uptime I can't shutdown or reboot any of this VMs-
if I type reboot or shutdown then it runs forever...
No error messages, nothing...

Thank you!

** 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/1723907

Title:
  16.04 server can't reboot

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello!

  I run 5 (five) Ubuntu 16.04 VMs on Centos7 host, i.e. inside of kvm.
  After several months of uptime I can't shutdown or reboot any of this VMs-
  if I type reboot or shutdown then it runs forever...
  No error messages, nothing...

  Thank you!

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

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

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

[Rafael David Tinoco]

** Changed in: libnl3 (Ubuntu)
 Assignee: Rafael David Tinoco (inaddy) => (unassigned)

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

Title:
  nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

Status in libnl3 package in Ubuntu:
  In Progress

Bug description:
  Retrieving information about configured neighbors fail 
  my application is running the following procedure:

  neigh = NULL;
  cache = rtnl_neigh_alloc_cache(sk);
  while(NULL == neigh){
  nl_cache_refill(sk, chache);
  neigh = rtnl_neigh_get(cache, ifindex, dst_addr);
  }

  with libnl3 3.2.21-1 this loop will never end, even when adding a static arp 
entry.
  However, with libnl-3.2.24 the neighbor lookup succeed.

  additional general info:
  $ lsb_release -rd
  Description:Ubuntu 14.04 LTS
  Release:14.04
  $ uname -r
  3.13.0-24-generic
  $ apt-cache policy libnl-genl-3-200 libnl-route-3-200
  libnl-genl-3-200:
Installed: 3.2.21-1
Candidate: 3.2.21-1
Version table:
   *** 3.2.21-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  libnl-route-3-200:
Installed: 3.2.21-1
Candidate: 3.2.21-1
Version table:
   *** 3.2.21-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://launchpad.net/~touch-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

[mrvanes]

I think I'm looking at a Qt problem, but still relevant for 17.10 as a whole I 
guess?
https://bugreports.qt.io/browse/QTBUG-63792

-- 
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 1694367] Re: Screen tearing in 16.10 onwards

[Bug Watch Updater]

** Changed in: mesa
   Importance: Medium => High

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

Title:
  Screen tearing in 16.10 onwards

Status in Mesa:
  Confirmed
Status in kernel-package package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  In 16.10 onwards my laptop has always shown screen tearing globally,
  additionally GL applications will not v-sync despite attempting to,
  they appear to sync slightly off from the [integrated] display.

  This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not
  entirely sure if it's a bug with either or a default miss-
  configuration in ubuntu...

  ubuntu-bug also appears to be broken...

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

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

[Touch-packages] [Bug 1718869] Re: Migrate to hunspell-en-us in libreoffice-dictionaries

[Mattia Rizzolo]

I also disagree with Rene here, but I'd rather not go against his
explicit wishes.

It would be more interesting to try to update src:hunspell-en-us, to at
least try to update it, at this point.

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

Title:
  Migrate to hunspell-en-us in libreoffice-dictionaries

Status in hunspell-en-us package in Ubuntu:
  New
Status in libreoffice-dictionaries package in Ubuntu:
  New
Status in hunspell-en-us package in Debian:
  New
Status in libreoffice-dictionaries package in Debian:
  Won't Fix

Bug description:
  libreoffice-dictionaries upstream ships hunspell-en-us, which is
  properly maintained and is newer than the one currently in Debian and
  Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in
  libreoffice-dictionaries. The other English variants (British,
  Australian and others) are already provided by libreoffice-
  dictionaries and are more up-to-date than the US variant.

  Debian bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159

  Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff 
and en_US.dic but there is not a built package for them.
  
https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/

  See this README from the Libreoffice/dictionaries git,
  https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt

  It seems that this is now dead,
  https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hunspell-en-us 20070829-6ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 09:43:32 2017
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: hunspell-en-us
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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"

[Launchpad Bug Tracker]

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

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

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

Title:
  Unattended upgrade fails with "Error in function"

Status in unattended-upgrades package in Ubuntu:
  Confirmed

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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Monique van den Berg]

This is a debdiff for iproute2 applicable to 3.12.0-2ubuntu1. I built this in 
pbuilder
and it builds successfully, and I installed it, the patch works as intended.

** Patch added: "iproute2_3.12.0-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+attachment/4972559/+files/iproute2_3.12.0-2ubuntu1.debdiff

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

[Monique van den Berg]

This is a debdiff for iproute2 applicable to 3.12.0-2ubuntu1. I built this in 
pbuilder
and it builds successfully, and I installed it, the patch works as intended.

** Patch removed: "iproute2_3.12.0-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+attachment/4972550/+files/iproute2_3.12.0-2ubuntu1.debdiff

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

[Monique van den Berg]

This is a debdiff for iproute2 applicable to 3.12.0-2. I built this in pbuilder
and it builds successfully, and I installed it, the patch works as intended.

** Patch added: "iproute2_3.12.0-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/xenial/+source/iproute2/+bug/1720126/+attachment/4972550/+files/iproute2_3.12.0-2ubuntu1.debdiff

-- 
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 1703898] Re: systemd-journald crashed with SIGABRT in journal_file_append_object()

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-journald crashed with SIGABRT in journal_file_append_object()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 Desktop
  On boot, I receive an error.

  Sorry Ubuntu 17.04 has experienced an internal error.
  ExecutablePath
/lib/systemd/systemd-hournald
  Package
systemd 232-21ubuntu5
  ProblemType
Crash
  Title
systemd-journald crashed with SIGABRT in journal_file_append_object()
  ApportVersion
2.20.4-Oubuntu4.4
  Architecture
amd64
  CoreDump
(binary data)

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

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

[Touch-packages] [Bug 1538865] Re: display arrangement fails to load after login

[Launchpad Bug Tracker]

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

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

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

Title:
  display arrangement fails to load after login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Only a dialog with

  could not assign CRTCs to outputs:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1366x768@60Hz with output at 1366x768@60Hz (pass 0)
  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0)
  CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0)
  CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0)
  CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0)
  CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1)

  CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 1280x720@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 1024x768@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 1024x576@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 960x540@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 800x600@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 800x600@56Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 864x486@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 640x480@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 720x405@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 680x384@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 640x360@60Hz with output at 1366x768@60Hz (pass 0)
  CRTC 63: trying mode 1366x768@60Hz with output at 1366x768@60Hz (pass 1)
  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0)
  CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0)
  CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0)
  CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0)
  CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1)

  CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 1280x720@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 1024x768@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 1024x576@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 960x540@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 800x600@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 800x600@56Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 864x486@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 640x480@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 720x405@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 680x384@60Hz with output at 1366x768@60Hz (pass 1)
  CRTC 63: trying mode 640x360@60Hz with output at 1366x768@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1366x768@60Hz with output at 1366x768@60Hz (pass 0)
  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0)
  CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0)
  CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1)