date:20181011

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

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

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

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

Status in cups package in Ubuntu:
  Expired

Bug description:
   printer-driver-postscript-hp зависит от hplip (>= 3.12.2-1ubuntu3.1), однако:
Пакет hplip пока не настроен.
  dpkg: не удалось обработать параметр printer-driver-postscript-hp 
(--configure):
   проблемы зависимостей -- оставляем не настроенным
  dpkg: зависимости пакетов не позволяют настроить пакет 
printer-driver-gutenprint:
   printer-driver-gutenprint зависит от cups (>= 1.3.0), однако:
Пакет cups пока не настроен.
  dpkg: не удалось обработать параметр printer-driver-gutenprint (--configure):
   проблемы зависимостей -- оставляем не настроенным
  dpkg: зависимости пакетов не позволяют настроить пакет cups-driver-gutenprint:
   cups-driver-gutenprint зависит от printer-driver-gutenprint, однако:
Пакет printer-driver-gutenprint пока не настроен.
  dpkg: не удалось обработать параметр cups-driver-gutenprint (--configure):
   проблемы зависимостей -- оставляем не настроенным
  dpkg: зависимости пакетов не позволяют настроить пакет hplip-cups:
   hplip-cups зависит от printer-driver-hpcups, однако:
Пакет printer-driver-hpcups пока не настроен.
  dpkg: не удалось обработать параметр hplip-cups (--configure):
   проблемы зависимостей -- оставляем не настроенным
  При обработке следующих пакетов произошли ошибки:
   cups
   printer-driver-hpcups
   hplip
   printer-driver-postscript-hp
   printer-driver-gutenprint
   cups-driver-gutenprint
   hplip-cups
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-43.68-generic 3.2.42
  Uname: Linux 3.2.0-43-generic i686
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: i386
  CupsErrorLog:
   
  Date: Sat May 25 00:05:31 2013
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
  MachineType: Hewlett-Packard HP Compaq nx7400 (RU429EA#ACB)
  MarkForUpload: True
  Papersize: a4
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  PpdFiles: HP_M1120n: HP LaserJet m1120n MFP hpijs, 3.11.7, requires 
proprietary plugin
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-43-generic 
root=UUID=5d693b65-b6c2-408b-b60e-16442713563b ro quiet splash vt.handoff=7
  SourcePackage: cups
  Title: package cups 1.5.3-0ubuntu1 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: Upgraded to precise on 2012-05-16 (373 days ago)
  dmi.bios.date: 08/27/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YGU Ver. F.0E
  dmi.board.name: 30A2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.17
  dmi.chassis.asset.tag: CNU7140BNW
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YGUVer.F.0E:bd08/27/2008:svnHewlett-Packard:pnHPCompaqnx7400(RU429EA#ACB):pvrF.0E:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx7400 (RU429EA#ACB)
  dmi.product.version: F.0E
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1044801] Re: [Gnome-Control-Center] ticking for backport updates erase the sources.list

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

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

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

Title:
  [Gnome-Control-Center] ticking for backport updates erase the
  sources.list

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  This is how to reproduce the bug.
  1-go to "system parameter" in top left corner menu (or launch 
gnome-control-center in a terminal).
  2-in the panel "updates" just tick as if you want to add quantal-proposed or 
quantal-backport repositories.

  By doing this, it will modified the file /etc/apt/sources.list .

  I give 2 files :
  sources.list.init : sources.list before i add quantal-proposed
  sources.list.modified : sources.list after i add quantal-proposed

  luckily, the sources.list is saved before the modification and the
  command mv sources.list.save sources.list resolve the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu13
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: i386
  Date: Sat Sep  1 21:03:01 2012
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120606.2)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.90-0ubuntu1
   gnome-control-center-signon 0.0.13-0ubuntu1
   indicator-datetime  12.10.0-0ubuntu1

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

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

[Touch-packages] [Bug 1182813] Re: package cups 1.5.3-0ubuntu6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100

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

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

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

Title:
  package cups 1.5.3-0ubuntu6 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 100

Status in cups package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04

  cups:
Installed: 1.5.3-0ubuntu6
Candidate: 1.5.3-0ubuntu8
Version table:
   1.5.3-0ubuntu8 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
   *** 1.5.3-0ubuntu6 0
  100 /var/lib/dpkg/status
   1.5.3-0ubuntu5.1 0
  500 http://security.ubuntu.com/ubuntu/ precise-security/main i386 
Packages
   1.5.2-9ubuntu1 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

  Crash reported during apt-get upgrade
  Preparing to replace cups 1.5.3-0ubuntu6 (using 
.../cups_1.5.3-0ubuntu8_i386.deb) ...
  invoke-rc.d: unknown initscript, /etc/init.d/cups not found.
  dpkg: warning: subprocess old pre-removal script returned error exit status 
100
  dpkg - trying script from the new package instead ...
  invoke-rc.d: unknown initscript, /etc/init.d/cups not found.
  dpkg: error processing /var/cache/apt/archives/cups_1.5.3-0ubuntu8_i386.deb 
(--unpack):
   subprocess new pre-removal script returned error exit status 100
  invoke-rc.d: unknown initscript, /etc/init.d/cups not found.
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 100

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu6
  ProcVersionSignature: Ubuntu 3.2.0-43.68-generic-pae 3.2.42
  Uname: Linux 3.2.0-43-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: i386
  CupsErrorLog:
   
  Date: Wed May 22 11:11:49 2013
  ErrorMessage: subprocess new pre-removal script returned error exit status 100
  InstallationMedia: Xubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  Lpstat:
   device for brother: dnssd://Brother%20MFC-5440CN._pdl-datastream._tcp.local/
   device for MX920LAN: cnijnet:/18-0C-AC-30-50-7B
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  MarkForUpload: True
  Papersize: letter
  PpdFiles:
   MX920LAN: Canon MX920 series Ver.3.90
   brother: Brother MFC-5440CN CUPS v1.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-43-generic-pae 
root=UUID=45b533bc-6544-482b-90e6-d1ebd91ddcf3 ro quiet splash
  SourcePackage: cups
  Title: package cups 1.5.3-0ubuntu6 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 100
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UD5H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd05/11/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

2018-10-11 Thread Daniel van Vugt

It looks like this crash was fixed in PulseAudio 12.0 (Ubuntu 18.10) by
commit 9e5be0899f60208046f1c5e2d32a2dd207d8fa00.

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

** Bug watch added: freedesktop.org Bugzilla #104385
   https://bugs.freedesktop.org/show_bug.cgi?id=104385

** Also affects: pulseaudio via
   https://bugs.freedesktop.org/show_bug.cgi?id=104385
   Importance: Unknown
   Status: Unknown

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

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

  ---

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

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

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

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2018-10-11 Thread Ryan Finnie

** Patch added: 
"bionic-upstream-delay-bailout-for-invalid-authenticating-user.patch"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200217/+files/bionic-upstream-delay-bailout-for-invalid-authenticating-user.patch

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2018-10-11 Thread Ryan Finnie

FYI, Qualys is now considering CVE-2018-15473 a PCI-DSS fail condition
(QID: 38726).

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1174015] Re: package cups 1.6.2-1ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

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

Title:
  package cups 1.6.2-1ubuntu5 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in cups package in Ubuntu:
  Expired

Bug description:
  Happened during a broken update (from ubuntu gnome 12.10.1 x64 to
  ubuntu gnome 13.04) that required a livecd ( mount /dev/sda1 /mnt;
  chroot /mnt; apt-get update; apt-get install -f; apt get upgrade) to
  even boot to X, and afterwards another (sudo apt-get upgrade) for the
  system to function properly again. I have not tested if it can be
  recreated somehow.

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: cups 1.6.2-1ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun Apr 28 18:23:36 2013
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-02-12 (74 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Release 
amd64(20121023)
  Lpstat: device for Photosmart-C5300-series: 
hp:/usb/Photosmart_C5300_series?serial=MY8AB570B1054V
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4A/300E5A/300E7A
  MarkForUpload: True
  Papersize: letter
  PpdFiles: Photosmart-C5300-series: HP Photosmart c5300 Series, hpcups 3.13.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=3cf3dccb-5cc9-4ed6-b8a2-26eea7ebc866 ro splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=3cf3dccb-5cc9-4ed6-b8a2-26eea7ebc866 ro splash vt.handoff=7
  SourcePackage: cups
  Title: package cups 1.6.2-1ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to raring on 2013-04-27 (0 days ago)
  dmi.bios.date: 09/05/2011
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 01QA
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 300E4A/300E5A/300E7A
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01QA:bd09/05/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4A/300E5A/300E7A:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4A/300E5A/300E7A:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 300E4A/300E5A/300E7A
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Touch-packages] [Bug 1179101] Re: package cups 1.5.3-0ubuntu6 failed to install/upgrade

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

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

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

Title:
  package cups 1.5.3-0ubuntu6 failed to install/upgrade

Status in cups package in Ubuntu:
  Expired

Bug description:
  package cups 1.5.3-0ubuntu6 failed to install/upgrade. failed with the
  exit status error code 1

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu6
  ProcVersionSignature: Ubuntu 3.5.0-27.46~precise1-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic i686
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: i386
  CupsErrorLog:
   E [30/Apr/2013:12:46:11 +0900] Unknown directive SystemGroup on line 16 of 
/etc/cups/cupsd.conf.
   E [30/Apr/2013:16:29:28 +0900] Unknown directive SystemGroup on line 16 of 
/etc/cups/cupsd.conf.
  Date: Sat May 11 14:14:24 2013
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
  MachineType: Hewlett-Packard Compaq Presario CQ40 Notebook PC
  MarkForUpload: True
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-27-generic 
root=UUID=1e657d3e-4188-4cdd-a6e3-4fb9e52ac4f2 ro init=/bin/systemd quiet 
splash vt.handoff=7
  SourcePackage: cups
  Title: package cups 1.5.3-0ubuntu6 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2009
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3607
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.BF
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsyde:bvrF.60:bd10/22/2009:svnHewlett-Packard:pnCompaqPresarioCQ40NotebookPC:pvr049313000D100:rvnHewlett-Packard:rn3607:rvr99.BF:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Compaq Presario CQ40 Notebook PC
  dmi.product.version: 049313000D100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1181423] Re: Cannot print at all with USB to parallel adapter and HP 4L

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

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

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

Title:
  Cannot print at all with USB to parallel adapter and HP 4L

Status in cups package in Ubuntu:
  Expired

Bug description:
  Since upgrading to raring I am unable to print anything at all using
  Prolific 2303 USB to parallel adapter and a HP LaserJet 4L. cups error
  log attached. This is the output when adding the printer and trying to
  print a test page.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: cups 1.6.2-1ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri May 17 23:29:30 2013
  InstallationDate: Installed on 2013-04-26 (20 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  KernLog:
   
  Lpstat:
   device for HP-LaserJet-4L: usb://Unknown/Printer
   device for M175nw: hp:/net/HP_LaserJet_100_colorMFP_M175nw?ip=192.168.0.175
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: a4
  PpdFiles:
   HP-LaserJet-4L: HP LaserJet 4L Foomatic/ljet4 (recommended)
   M175nw: HP LaserJet 100 color MFP M175 Postscript (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=52fbfaf1-aa35-45f8-9a1c-b867ce923edd ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A79XTD EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0X
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1186234] Re: package cups 1.6.1-0ubuntu11.4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

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

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

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

Title:
  package cups 1.6.1-0ubuntu11.4 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 1 zurück

Status in cups package in Ubuntu:
  Expired

Bug description:
  since a few days cups quit working; reinstall fails

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: cups 1.6.1-0ubuntu11.4
  ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
  Uname: Linux 3.2.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: amd64
  Date: Fri May 31 20:42:52 2013
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Transport endpoint is not connected
  MachineType: Dell Inc. XPS 8300
  MarkForUpload: True
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-40-generic 
root=UUID=cdf23203-ba9c-41d7-84d5-b9e4ad6732f3 ro quiet splash vt.handoff=7
  SourcePackage: cups
  Title: package cups 1.6.1-0ubuntu11.4 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to precise on 2013-04-30 (31 days ago)
  dmi.bios.date: 02/15/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0Y2MRG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/15/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8300
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1217362] Re: package cups 1.7.0~rc1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

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

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

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

Title:
  package cups 1.7.0~rc1-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in cups package in Ubuntu:
  Expired

Bug description:
  on system start

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: cups 1.7.0~rc1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic i686
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  CupsErrorLog:
   
  Date: Tue Aug 27 15:23:40 2013
  DuplicateSignature: package:cups:1.7.0~rc1-0ubuntu1:subprocess installed 
post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2013-05-28 (90 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic 
root=UUID=2dc3a76c-3463-4420-88e1-847aaa71c04e ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic 
root=UUID=2dc3a76c-3463-4420-88e1-847aaa71c04e ro quiet splash vt.handoff=7
  SourcePackage: cups
  Title: package cups 1.7.0~rc1-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: Upgraded to saucy on 2013-05-29 (89 days ago)
  dmi.bios.date: 04/15/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd04/15/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1195909] Re: Samsung CLX-3180 does not print - Unable to add document to print job

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

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

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

Title:
  Samsung CLX-3180 does not print - Unable to add document to print job

Status in cups package in Ubuntu:
  Expired

Bug description:
  Problems to send jobs to print for samsung clx-3180, network connected
  The scanner is working without problems
  attached debug output files following the procedure of site
  https://wiki.ubuntu.com/DebuggingPrintingProblems

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

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

[Touch-packages] [Bug 1231630] Re: Prints to DYMO LabelWriter 450 are cut by prints to OKI printer

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

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

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

Title:
  Prints to DYMO LabelWriter 450 are cut by prints to OKI printer

Status in cups package in Ubuntu:
  Expired

Bug description:
  I have 2 printers attached to my work station: DYMO LabelWriter 450 for 
printing labels and OKI B410d for printing invoices.
  My business environment sends 2 jobs at about the same time, one to print a 
label and one to print the invoice.

  After moving to 13.04 sometimes I see that labels printing is stopped in the 
middle (only half of the label gets out of the printer), the DYMO's print queue 
shows that the job is "Held" for some reason.
  When I manually resume the held job the label is printed again on the second 
half of the label and first half of the next label, thus wasting 2 label pages 
in that case.

  It's hard to reproduce, but it happens pretty frequently when printing
  to both of the printers.

  There is another symptom that I think is related to the same issue:
  Rarely the prints are not coming out at all and than I can see in print 
queues that jobs sizes are with smaller sizes than I can generally see there.
  That happens for both of the printers from time to time, probably current 
printing job is cut by the new one.

  Couldn't reproduce the problem when printing only to 1 printer at a
  time and waiting for all the jobs to come out before printing to the
  other.

  There was no problem on 11.10 to print to both of the printers at the
  same time.

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

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

[Touch-packages] [Bug 1232067] Re: package cups-daemon 1.6.2-1ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

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

Title:
  package cups-daemon 1.6.2-1ubuntu5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in cups package in Ubuntu:
  Expired

Bug description:
  jjj

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: cups-daemon 1.6.2-1ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  CupsErrorLog:
   
  Date: Fri Sep 27 17:56:53 2013
  DuplicateSignature: package:cups-daemon:1.6.2-1ubuntu5:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-07-14 (439 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Transport endpoint is not connected
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic 
root=UUID=ffd65bb1-9f49-4223-a682-55d1f9e39fb3 ro quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic 
root=UUID=ffd65bb1-9f49-4223-a682-55d1f9e39fb3 ro quiet splash
  SourcePackage: cups
  Title: package cups-daemon 1.6.2-1ubuntu5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to raring on 2013-04-06 (173 days ago)
  dmi.bios.date: 11/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.cups.cups.files.conf: [deleted]
  modified.conffile..etc.cups.cupsd.conf.default: [deleted]

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

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

[Touch-packages] [Bug 1257254] Re: cupsaddsmb doesn't filter out all PJL commands from PPD

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

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

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

Title:
  cupsaddsmb doesn't filter out all PJL commands from PPD

Status in cups package in Ubuntu:
  Expired

Bug description:
  Summury
  --
  Windows clients printing to the cups server get an error page from the 
printer:
  ERROR: undefined
  OFFENDING COMMAND: @PJL
  STACK:

  
  Description
  -
  Our "HP LaserJet 400 MFP M425" ppd has the following lines containing PJL 
commands:

  line #47:
  *Protocols: TBCP PJL
  *JCLBegin: "<1B>%-12345X@PJL JOB<0A>"
  *JCLToPSInterpreter: "@PJL ENTER LANGUAGE = PostScript <0A>"
  *JCLEnd: "<1B>%-12345X@PJL EOJ <0A><1B>%-12345X"

  line #410
  *HPEconoMode True/On: "@PJL SET ECONOMODE=ON<0A>@PJL SET 
RESOLUTION=600<0A>@PJL SET BITSPERPIXEL=2<0A>"
  *HPEconoMode False/Off: "@PJL SET ECONOMODE=OFF<0A>@PJL SET 
RESOLUTION=600<0A>@PJL SET BITSPERPIXEL=2<0A>"

  The 4 lines from #47 are correctly commented out by cupsaddsmb when 
registering the drivers for windows clients:
  *% Commented out for CUPS Windows Driver...
  *%Protocols: TBCP PJL
  *% Commented out for CUPS Windows Driver...
  *%JCLBegin: "<1B>%-12345X@PJL JOB<0A>"
  *% Commented out for CUPS Windows Driver...
  *%JCLToPSInterpreter: "@PJL ENTER LANGUAGE = PostScript <0A>"
  *% Commented out for CUPS Windows Driver...
  *%JCLEnd: "<1B>%-12345X@PJL EOJ <0A><1B>%-12345X"

  However, the 2 lines from #410 are not filtered out

  Cause
  --

  In the source file adminutil.c the function cupsAdminExport Samba() 
specifically searches for certain JCL commands:
  else if (!strncmp(line, "*JCLBegin:", 10) ||
   !strncmp(line, "*JCLToPSInterpreter:", 20) ||
 !strncmp(line, "*JCLEnd:", 8) ||
 !strncmp(line, "*Protocols:", 11))

  however, all PJL commands should be either replaced or removed.

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

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

[Touch-packages] [Bug 1245175] Re: package cups 1.5.3-0ubuntu8 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 1 terug

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

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

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

Title:
  package cups 1.5.3-0ubuntu8 failed to install/upgrade: subproces
  installed post-installation script gaf een foutwaarde 1 terug

Status in cups package in Ubuntu:
  Expired

Bug description:
  HP Color LaserJet CP1215 connted wit USB for printserver. Sharing
  error

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  AptOrdering:
   cups: Install
   printer-driver-gutenprint: Install
   cups: Configure
   printer-driver-gutenprint: Configure
  Architecture: amd64
  Date: Sun Oct 27 12:49:39 2013
  DuplicateSignature: package:cups:1.5.3-0ubuntu8:subproces installed 
post-installation script gaf een foutwaarde 1 terug
  ErrorMessage: subproces installed post-installation script gaf een foutwaarde 
1 terug
  InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release 
amd64 (20130820.2)
  Lpstat: device for HP-Color-LaserJet-CP1215: 
usb://HP/Color%20LaserJet%20CP1215?serial=LJ04LVW
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: a4
  PpdFiles: HP-Color-LaserJet-CP1215: HP Color LaserJet CP1215 Foomatic/foo2hp 
(recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic 
root=UUID=1ec0a073-3701-467b-b180-17a066f54ddb ro
  SourcePackage: cups
  Title: package cups 1.5.3-0ubuntu8 failed to install/upgrade: subproces 
installed post-installation script gaf een foutwaarde 1 terug
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd08/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1233766] Re: NX printing fails because cupsd is denied access to $HOME/.nx/*/cups by apparmor

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

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

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

Title:
  NX printing fails because cupsd is denied access to $HOME/.nx/*/cups
  by apparmor

Status in cups package in Ubuntu:
  Expired

Bug description:
  When using OpenNX client with FreeNX server, printing support via cups
  is prevented by apparmor settings that prevent access to
  $HOME/.nx/*/cupsd.

  Modifying the apparmor configuration settings for cupsd resolves the
  problem:

  --- /etc/apparmor.d/usr.sbin.cupsd-orig2013-09-27 11:29:52.0 -0400
  +++ /etc/apparmor.d/usr.sbin.cupsd2013-09-27 11:19:48.0 -0400
  @@ -127,6 +127,10 @@
 # likewise authentication
 /etc/likewise r,
 /etc/likewise/* r,
  +
  +  # nx-launched cupsd
  +  @{HOME}/.nx/C-ip*/cups/ rw,
  +  @{HOME}/.nx/C-ip*/cups/** rwckl,
   }

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

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

[Touch-packages] [Bug 1245249] Re: Failed /usr/lib/libstdc++.so.5 in amd64 architecture

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

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

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

Title:
  Failed /usr/lib/libstdc++.so.5 in amd64 architecture

Status in cups package in Ubuntu:
  Expired

Bug description:
  When I print pdf with Okular (KDE4 pdf viewer) or in Adobe Acrobat 9.5 I get 
error in console like "lpr: can not find libstdc++.so.5".
  I can see:
  $ ldd /usr/bin/lpr | grep libstdc
  libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x7f7b8e53)
  But this file not present in my system.
  But it present in /usr/lib64
  I create symlink and all works fine. My wife's computer have this bug in 
12.04 too.

  When I search for this file with 'apt-file search' I can not find it...(((
  But I find with 'apt-file search' that 'lpr' included in my system in 
installed package 'cups-bsd'.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cups-bsd 1.7.0~rc1-0ubuntu5 [modified: usr/bin/lpr]
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   E [27/Oct/2013:08:34:32 +0200] [Client 17] Returning IPP 
client-error-bad-request for Create-Printer-Subscription (/) from localhost
   E [27/Oct/2013:17:25:28 +0200] [Client 15] Returning IPP 
client-error-bad-request for Create-Printer-Subscription (/) from localhost
   E [27/Oct/2013:18:30:38 +0200] [Client 15] Returning IPP 
client-error-bad-request for Create-Printer-Subscription (/) from localhost
  Date: Sun Oct 27 20:12:41 2013
  InstallationDate: Installed on 2013-10-19 (7 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lpstat: device for ML-1670: lpd://192.168.1.1/lp1
  MachineType: Acer TravelMate B113
  MarkForUpload: True
  Papersize: a4
  PpdFiles: ML-1670: Samsung ML-1670 Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=94f29b75-e824-41b5-aa40-c5734a2d4804 ro pciehp.pciehp_force=1 
pciehp.pciehp_poll=1 quiet splash pcie_aspm=force i915.i915_enable_fbc=1 
drm.vblankoffdelay=1 i915.semaphores=1 i915.lvds_downclock=1 nmi_watchdog=0 
acpi_backlight=vendor elevator=noop
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA10_HX
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnAcer:bvrV1.09:bd10/30/2012:svnAcer:pnTravelMateB113:pvrV1.09:rvnAcer:rnBA10_HX:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.09:
  dmi.product.name: TravelMate B113
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1670022] Re: Pulseaudio volume master breaks after plugging in headphones

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

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

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

Title:
  Pulseaudio volume master breaks after plugging in headphones

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  The only way I've found to restore it is by rebooting. I can control
  the volume with amixer, and pavucontrol's per-application sliders work
  fine, but the master in pavucontrol doesn't work. (So naturally the
  volume keys don't work either.)

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

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

[Touch-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update

2018-10-11 Thread Daniel van Vugt

That's strange. Your Bluetooth chip looks like a common one that any Linux 
kernel version should support:
  
https://ark.intel.com/products/66889/Intel-Centrino-Wireless-N-2230-Single-Band

As a quick check, please live boot the original 18.04.0 release:
  http://old-releases.ubuntu.com/releases/18.04.0/
and verify it was working in that version before any updates.

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

Title:
  all my bluetooth headsets skips terribly after todays update

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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

[Touch-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update

2018-10-11 Thread Ivan

After downgrading core bluetooth device disappeared, and installing most recent 
one didn't help to bring it back.
I am just not enough familiar with linux to be able reinstall it manually.
had to reinstall whole ubuntu from scratch - still have same problems.

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

Title:
  all my bluetooth headsets skips terribly after todays update

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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

[Touch-packages] [Bug 1797493] [NEW] xset blank does not work

2018-10-11 Thread dman777

Public bug reported:

one@localhost:~$ xset -version
xset 1.2.3

one@localhost:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

X.Org X Server 1.19.6

xset blank is not working. Nothing happens when I do `xset s blank; xset
s 100`. While this works on my laptop with Xenial, it does not on my PC
with Bionic Beaver server edition. What I expect is the screen to go
blank and it does not.

However, dps features do work... just not the blank screen saver
feature.

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


** Tags: xset

** Tags added: xset

** Description changed:

  one@localhost:~$ xset -version
  xset 1.2.3
  
  one@localhost:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic
  
- 
  X.Org X Server 1.19.6
  
- xset blank is not working. Nothing happens when I do xset s blank, xset
- s 100. While this works on my laptop with Xenial, it does not on my PC
+ xset blank is not working. Nothing happens when I do `xset s blank; xset
+ s 100`. While this works on my laptop with Xenial, it does not on my PC
  with Bionic Beaver server edition. What I expect is the screen to go
  blank and it does not.
  
- 
- However, dps features do work... just not the blank screen saver feature.
+ However, dps features do work... just not the blank screen saver
+ feature.

** Package changed: e2fsprogs (Ubuntu) => xset (Ubuntu)

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

Title:
  xset blank does not work

Status in xset package in Ubuntu:
  New

Bug description:
  one@localhost:~$ xset -version
  xset 1.2.3

  one@localhost:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  X.Org X Server 1.19.6

  xset blank is not working. Nothing happens when I do `xset s blank;
  xset s 100`. While this works on my laptop with Xenial, it does not on
  my PC with Bionic Beaver server edition. What I expect is the screen
  to go blank and it does not.

  However, dps features do work... just not the blank screen saver
  feature.

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

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

According to the documentation, the recommendation is to mask dev-
hugepages.mount, but in my current test doing it was preventing the
tmp.mount failure, but not preventing to go into "Emergency mode". In my
lab masking tmp.mount had better result.

Feel free to try both and let me know the outcome, results may varies
from one setup to another.

- Eric

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

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

[Touch-packages] [Bug 1797282] Re: fsck not running at all on reboot

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

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

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

Title:
  fsck not running at all on reboot

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  After upgrading some servers from 16.04 to 18.04 I'm met with a MOTD
  that says:

  *** /dev/xvda1 should be checked for errors ***

  I added "fsck.mode=force" to GRUB_CMDLINE_LINUX_DEFAULT in
  /etc/default/grub before running 'sudo update-grub'. I also verified
  that fsck was present in /boot/grub/grub.cfg afterwards, before
  rebooting the server.

  Surprisingly I was met with the same error message in MOTD when
  logging in. I then ran tune2fs to see when the last check was
  performed and this is the output:

  $ sudo tune2fs -l /dev/xvda1  | grep checked
  Last checked: Wed Sep 12 16:17:00 2018

  I then tried to change mount count to 1 with tune2fs -c 1 /dev/xvda1,
  but after another reboot I was still met with the same error message
  and the timestamp for last checked was unchanged.

  I have the same problem on all the servers that was upgraded from
  16.04 to 18.04, but also on a new server installed directly with
  18.04.

  In should be mentioned that the servers are AWS EC2 instances, so I
  have no way of trying to run fsck from a liveusb.

  Another user has reported the same issue here:
  https://ubuntuforums.org/showthread.php?t=2403368

  I'm not quite sure what information is needed, but attached are some
  basic information about the system.

  Please let me know if you need any any other outputs or logs.

  Edit1: I tested fsck.mode=force on my laptop running Ubuntu 18.04.1
  LTS (Xubuntu) and it works fine. Seems to be related to the server
  edition.

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

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

[Touch-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update

2018-10-11 Thread Ivan

Thanks for you help.

doubt about environmental reason because this laptop also has windows and 
everything continue to work fine in windows. even tried to reconnect my 
headsets in windows - still works. but it not convenient to boot in to win in 
order to use my headset.
Anyway- trying  to downgrade my kernel, will key you posted.

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

Title:
  all my bluetooth headsets skips terribly after todays update

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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

[Touch-packages] [Bug 1797275] Re: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent.

2018-10-11 Thread S. Randall Sawyer

Thank you, Sebastian!

Yes, I have found the file per your instructions:

 |$ dpkg -S gtk-query-immodules-3.0
 |libgtk-3-doc: /usr/share/doc/libgtk-3-doc/gtk3/gtk-query-immodules-3.0.html
 |libgtk-3-0:i386: /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0
 |libgtk-3-bin: /usr/share/man/man1/gtk-query-immodules-3.0.1.gz

However, if I attempt to execute it, I get the following error message:

 |$ . /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 
 |bash: .: /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: cannot 
execute binary file

I thought I ought to inspect the file further:

 |$ ls -l /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 
 |-rwxr-xr-x 1 root root 13672 Apr 16 20:23 
/usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0

 |$ file /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 
 |/usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: ELF 32-bit LSB 
shared object, Intel 80386, version 1 (SYSV), dynamically linked, interpreter 
/lib/ld-linux.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=b7c03cbac4882fe78ea6f0b92d1dc98dbeb13017, stripped

Thus, my system does not in fact contain an executable utility named
"gtk-query-immodules-3.0".

Thanks again for any further assistance and/or explanation.

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

Title:
  libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is
  absent.

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  The binary "gtk-query-immodules-3.0" is absent from package. The
  package DOES include the man-page for "gtk-query-immodules-3.0", but
  not the actual utility it documents.

  I downloaded the source tarball
  "gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz" and untar-ed it:

   |$ ls ./
   |debian
   |gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz

   |$ ls ./debian/libgtk-3-bin*
   |debian/libgtk-3-bin.install
   |debian/libgtk-3-bin.links.in

   |$ cat ./debian/libgtk-3-bin.install
   |usr/bin/broadwayd
   |usr/bin/gtk-builder-tool
   |usr/bin/gtk-launch
   |usr/bin/gtk-query-settings
   |usr/share/gettext/its/gtkbuilder.its
   |usr/share/gettext/its/gtkbuilder.loc
   |usr/share/man/man1/broadwayd.1
   |usr/share/man/man1/gtk-builder-tool.1
   |usr/share/man/man1/gtk-launch.1
   |usr/share/man/man1/gtk-query-immodules-3.0.1
   |usr/share/man/man1/gtk-query-settings.1

  Qualifiers:
  1)
   |$ lsb_release -rd
   |Description:Linux Mint 19 Tara
   |Release:19

  2)
   |$ apt-cache policy libgtk-3-bin
   |libgtk-3-bin:
   |  Installed: 3.22.30-1ubuntu1
   |  Candidate: 3.22.30-1ubuntu1
   |  Version table:
   | *** 3.22.30-1ubuntu1 500
   |500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
   |100 /var/lib/dpkg/status

   |$ ls /usr/share/man/man1/gtk-query*
   |/usr/share/man/man1/gtk-query-immodules-2.0.1.gz
   |/usr/share/man/man1/gtk-query-immodules-3.0.1.gz
   |/usr/share/man/man1/gtk-query-settings.1.gz

   |$ ls /usr/bin/gtk-query*
   |/usr/bin/gtk-query-settings

  3) I am experimenting with development of specialized immodules for
  GtkEntry widget. I expect to be able to install these additional
  modules and for my application to access them per the instructions in
  the Gtk+3 documentation.

  4)
   |$ whereis gtk-query-immodules-3.0
   |gtk-query-immodules-3:

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1797275/+subscriptions

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

[Touch-packages] [Bug 1797425] Re: printing docs with images is very slow - PCL printer

2018-10-11 Thread Paul White

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

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

Title:
  printing docs with images is very slow - PCL printer

Status in cups package in Ubuntu:
  New

Bug description:
  ubuntu 18.04 - Intel Xeon 8 core workstation - default driver for
  samsung ML-4600

  The printer is an old Samsung ML-4600 USB laser printer, but it does
  its job. On a 8core workstation, printing starts immediately if it's
  text only. The print itself is always done in 10" or so.

  A 26kB LibO doc, containing a tiny 8k image only, needs 2'6" till the
  printer starts printing. With a 900kB image in the doc, the time is
  the same.

  With scribus and the tiny 8K image, it takes 45s till the printer
  starts action.

  When trying to print a heavy 2MB per page doc, it takes more than 10'
  till the printer starts to act.

  Odd - with top I cannot see any printing activity causing relevant cpu
  load, but I think at least one core should do heavy rasterizing work.

  I love linux to support old hardware - but this is not state-of-the-
  art, hope improvements are possible.

  Cheers,
  Wolf

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

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

[Touch-packages] [Bug 1797425] [NEW] printing docs with images is very slow - PCL printer

You have been subscribed to a public bug:

ubuntu 18.04 - Intel Xeon 8 core workstation - default driver for
samsung ML-4600

The printer is an old Samsung ML-4600 USB laser printer, but it does its
job. On a 8core workstation, printing starts immediately if it's text
only. The print itself is always done in 10" or so.

A 26kB LibO doc, containing a tiny 8k image only, needs 2'6" till the
printer starts printing. With a 900kB image in the doc, the time is the
same.

With scribus and the tiny 8K image, it takes 45s till the printer starts
action.

When trying to print a heavy 2MB per page doc, it takes more than 10'
till the printer starts to act.

Odd - with top I cannot see any printing activity causing relevant cpu
load, but I think at least one core should do heavy rasterizing work.

I love linux to support old hardware - but this is not state-of-the-art,
hope improvements are possible.

Cheers,
Wolf

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


** Tags: printing
-- 
printing docs with images is very slow - PCL printer
https://bugs.launchpad.net/bugs/1797425
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

** Tags added: sts

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

By reading this article :
https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems/

I really start thinking the easiest way to fix it is as describe here :

... 
/tmp as location for volatile, temporary userspace file system objects (X) 
... 
It is possible to disable the automatic mounting of some (but not all) of these 
file systems, if that is required. These are marked with (X) in the list above. 
You may disable them simply by masking them: 
systemctl mask dev-hugepages.mount 
... 

I have tested by masking "tmp.mount", but the official documentation
recommend "dev-hegepages.mount" instead.

pxe configuration line :
" 
APPEND initrd=bionic-desktop-amd64/initrd root=/dev/nfs boot=casper netboot=nfs 
nfsroot=192.168.100.2:/bionic-desktop-amd64 splash systemd.mask=tmp.mount 
systemd.debug-shell=1 systemd.log_level=debug systemd.log_target=console 
console=ttyS0,38400 console=tty1 -- 
" 

I'm starting to think that this may become the final solution to the new
systemd behaviour as indicated in official documentation above and not
only a workaround.

Thoughts ?

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

Does someone impacted can test the dev-hugepages.mount masking within
their PXE configuration and let me know how it works ?

systemd.mask=dev-hugepages.mount

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

The "existing" /tmp come from casper code :

bionic/casper-1.394/scripts/casper-bottom/12fstab
...
cat > $FSTAB

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

Additionally,

tmp.mount unit configuration : 
https://github.com/systemd/systemd/blob/master/units/tmp.mount 

# tmp.mount 
-- 
.. 
ConditionPathIsSymbolicLink=!/tmp 
.. 
-- 

ConditionPathIsSymbolicLink = Verifies whether a certain path exists and is a 
symbolic link. 
When there is an exclamation mark ("!"), the validation is negated 

For "ConditionPathIsSymbolicLink=!/tmp" the unit is making sure /tmp
doesn't exist and is not a symbolink link, if it exist and is a symbolic
link like then it will fail and create the actual situation.

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

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

[Touch-packages] [Bug 1771340] Re: sshd failed on config reload

2018-10-11 Thread Andreas Hasenack

Thanks for the confirmation @tronde, much appreciated.

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

Title:
  sshd failed on config reload

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

Bug description:
  [Impact]

  sshd doesn't check the configuration when reloading.

  If a user generates an invalid configuration file, sshd will shut down
  and not come back up when the user issues a reload.

  [Test Case]

  $ lxc launch ubuntu:xenial tester
  $ lxc exec tester bash

  # echo "blah blah" >>/etc/ssh/sshd_config
  # systemctl reload sshd
  Job for ssh.service failed because the control process exited with error 
code. See "systemctl status ssh.service" and "journalctl -xe" for details.
  # systemctl status ssh.service
  ● ssh.service - OpenBSD Secure Shell server
     Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
     Active: failed (Result: exit-code) since Tue 2018-08-21 18:15:41 UTC; 19s 
ago

  * The service should have checked the config file, failed to reload,
  but remained active in its current configuration. In this case ssh has
  shut down.

  [Regression Potential]

  This code will only trigger on an invalid configuration file (in which
  case sshd would not load anyway), so there should be no regressions.

  [Other Info]

  autopkgtest [13:45:46]: test regress: ---]
  autopkgtest [13:45:47]: test regress:  - - - - - - - - - - results - - - - - 
- - - - -
  regress  PASS
  autopkgtest [13:45:47]:  summary
  regress  PASS

  [Original Description]

  After adding some lines to /etc/ssh/sshd_config I tried to reload the
  configuration with the command:

  ```
  sudo systemctl reload sshd
  ```

  No error message was returned. So I assumed that the sshd was running
  with the current config. But `sudo systemctl status sshd` told me that
  the service failed due to a wrong option in /etc/ssh/sshd_config.
  Please see the following output:

  ~~~
  :~$ sudo vim /etc/ssh/sshd_config
  :~$ sudo systemctl reload sshd
  :~$ sudo systemctl status sshd
  ● ssh.service - OpenBSD Secure Shell server
     Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
     Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s 
ago
    Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
    Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 7536 (code=exited, status=255)
  ~~~

  I would expect that a warning or error message is returned when the
  service fails while reloading it's configuration.

  A fix for this behaviour would be appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Tue May 15 10:18:25 2018
  InstallationDate: Installed on 2013-01-10 (1950 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago)
  mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420

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

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

[Touch-packages] [Bug 1765690] Re: wget-log file created despite -q when run in background with

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

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

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

Title:
  wget-log file created despite -q when run in background with &

Status in wget package in Ubuntu:
  Confirmed

Bug description:
  == Steps to reproduce ==
  `wget -q https://www.google.com/ &`

  
  == What happens ==
  wget says it's "Redirecting output to 'wget-log'" and creates an empty 
wget-log file in the current directory.

  
  == What I expect to happen ==
  No wget-log file to be created.

  
  == Details ==
  Wget has a -b (--background) option, for which the man page says: "If no 
output file is specified via the -o, output is redirected to wget-log." There's 
also the -q (--quiet) option, for which the man page says: "Turn off Wget's 
output."

  When both are given, wget goes to background, and no wget-log gets
  created, as expected.

  When only -b is given, wget goes to background, and creates wget-log,
  also as expected.

  When only -q is given, wget runs in the foreground, and no wget-log is
  created, still as expected.

  When only -q is given, but & is added to the end of the command line,
  wget goes to background, but also creates wget-log, which I find
  unexpected (and inconsistent).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: wget 1.19.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 20 14:56:17 2018
  InstallationDate: Installed on 2016-10-13 (553 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: wget
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

2018-10-11 Thread Marcos

Actually, sent the wrong patch... this is the right one:

root@netplan:~# cat fix-bug-1770082.diff
--- a/netplan/cli/commands/apply.py
+++ b/netplan/cli/commands/apply.py
@@ -170,15 +170,15 @@
 link = netifaces.ifaddresses(interface)[netifaces.AF_LINK][0]
 macaddress = link.get('addr')
 if driver_name in matches['by-driver']:
- new_name = matches['by-driver'][driver_name]
- logging.debug(new_name)
+ current_name = matches['by-driver'][driver_name]
+ logging.debug(current_name)
 logging.debug(interface)
- if new_name != interface:
- changes.update({interface: {'name': new_name}})
+ if current_name != newname:
+ changes.update({interface: {'name': newname}})
 if macaddress in matches['by-mac']:
- new_name = matches['by-mac'][macaddress]
- if new_name != interface:
- changes.update({interface: {'name': new_name}})
+ current_name = matches['by-mac'][macaddress]
+ if current_name != newname:
+ changes.update({interface: {'name': newname}})

 logging.debug(changes)
 return changes

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # 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}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

2018-10-11 Thread Marcos

After some debugging, I could make it work... I'm not a programmer, so
it might be wrong, but it's working:

root@netplan:~# cat fix-bug-1770082.diff 
--- a/netplan/cli/commands/apply.py
+++ b/netplan/cli/commands/apply.py
@@ -170,15 +170,15 @@
 link = netifaces.ifaddresses(interface)[netifaces.AF_LINK][0]
 macaddress = link.get('addr')
 if driver_name in matches['by-driver']:
-new_name = matches['by-driver'][driver_name]
-logging.debug(new_name)
+current_name = matches['by-driver'][driver_name]
+logging.debug(current_name)
 logging.debug(interface)
-if new_name != interface:
-changes.update({interface: {'name': new_name}})
+if current_name != interface:
+changes.update({interface: {'name': newname}})
 if macaddress in matches['by-mac']:
-new_name = matches['by-mac'][macaddress]
-if new_name != interface:
-changes.update({interface: {'name': new_name}})
+current_name = matches['by-mac'][macaddress]
+if current_name != interface:
+changes.update({interface: {'name': newname}})
 
 logging.debug(changes)
 return changes


After applying the patch, it's working both on reboot and on netplan apply, 
with the interface down, of course.

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # 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}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state

[Touch-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all

2018-10-11 Thread Cristian Aravena Romero

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out,
  Left] No sound at all

Status in alsa-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Headphone jack stopped working. Speakers do work. Nevermind issue was
  on my end not sure how to close bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 11 13:12:34 2018
  InstallationDate: Installed on 2018-01-05 (279 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, 
Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1574746] Re: Enable support for libsoxr

2018-10-11 Thread Neo

Hi,
Thanks.
I test it and I feel that sound is better with this re-sampler, as well lower 
on CPU.
Regards

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

Title:
  Enable support for libsoxr

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I'd like to ask to enable support for libsoxr-based resamplers in the 
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr 
and automatically detects its availability, so the only change really needed is 
to add the build dependency to debian/control.
   
  The resamplers based in libsoxr offer better quality and better performace 
while introducing more delay compared to the speex resamplers that are used by 
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu 
16.04 but unfortunately are not enabled at build time ('pulseaudio 
--dump-resample-methods' doesn't list them). I've built local packages with 
libsoxr and verified that the resampler works as expected.

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

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

Re: [Touch-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all

2018-10-11 Thread James Miller

Sorry i couldn't figure out how to close the bug. The issue was on my
end.


On 10/11/2018 01:50 PM, Cristian Aravena Romero wrote:
> @EoflaOE
>
> You could try the version [0]'Ubuntu Desktop > 18.04'
> [0] https://www.ubuntu.com/#download
>
> Best regards,
> --
> Cristian Aravena Romero (caravena)
>

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

Title:
  [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out,
  Left] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Headphone jack stopped working. Speakers do work. Nevermind issue was
  on my end not sure how to close bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 11 13:12:34 2018
  InstallationDate: Installed on 2018-01-05 (279 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, 
Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all

2018-10-11 Thread Cristian Aravena Romero

@EoflaOE

You could try the version [0]'Ubuntu Desktop > 18.04'
[0] https://www.ubuntu.com/#download

Best regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out,
  Left] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Headphone jack stopped working. Speakers do work. Nevermind issue was
  on my end not sure how to close bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 11 13:12:34 2018
  InstallationDate: Installed on 2018-01-05 (279 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, 
Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1797236] Re: network-manager openvpn settings not being saved

This bug was fixed in the package network-manager-openvpn -
1.8.6-1ubuntu1

---
network-manager-openvpn (1.8.6-1ubuntu1) cosmic; urgency=medium

  * debian/patches/editor-fix-memory-corruption-when-creating-advanced-.patch:
Cherry-pick from upstream. Fix a missing unref when constructing the
"advanced" dialog of the VPN connection editor. (LP: #1797236)

 -- Iain Lane   Thu, 11 Oct 2018 16:40:07
+0100

** Changed in: network-manager-openvpn (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1797236

Title:
  network-manager openvpn settings not being saved

Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager-openvpn package in Ubuntu:
  Fix Released

Bug description:
  I'm seeing some weird issue with the new NM + openvpn; if I create a
  new VPN connection, and add certificate options (verify name exactly,
  plus TLS auth), these options are not saved, leading to the connection
  failing.

  The following versions lead to an invalid connection:
  ii  network-manager   1.12.4-1ubuntu1 amd64   
network management framework (daemon and userspace tools)
  ii  network-manager-openvpn   1.8.6-1 amd64   
network management framework (OpenVPN plugin core)

  
  Reverting to the following versions, things work again:
  ii  network-manager   1.12.2-0ubuntu4 amd64   
network management framework (daemon and userspace tools)
  ii  network-manager-openvpn   1.8.4-1 amd64   
network management framework (OpenVPN plugin core)

  
  If I use an existing connection saved with a prior version of NM, the 
connection will be successful. If I go open the settings, hit Apply, all 
advanced TLS settings are wiped.

  The connection then fails:

  Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]91.189.91.19:443
  Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET]91.189.91.19:443 [nonblock]
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP connection established with 
[AF_INET]91.189.91.19:443
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link local: (not bound)
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link remote: 
[AF_INET]xx.xx.xx.xx:443
  Oct 10 16:58:53 demeter nm-openvpn[6538]: Connection reset, restarting [0]
  Oct 10 16:58:53 demeter nm-openvpn[6538]: SIGUSR1[soft,connection-reset] 
received, process restarting
  Oct 10 16:58:58 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
  Oct 10 16:58:58 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Oct 10 16:58:58 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET6]2001:67c:1562:0:1::1:443
  Oct 10 16:58:58 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET6]2001:67c:1562:0:1::1:443 [nonblock]
  Oct 10 16:58:59 demeter nm-openvpn[6538]: TCP: connect to 
[AF_INET6]:xxx:xx:xx::xx:443 failed: Network is unreachable
  Oct 10 16:58:59 demeter nm-openvpn[6538]: SIGUSR1[connection 
failed(soft),init_instance] received, process restarting
  Oct 10 16:59:04 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.

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

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

[Touch-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all

2018-10-11 Thread Cristian Aravena Romero

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19-rc7 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7

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

** 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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1797432

Title:
  [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out,
  Left] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Headphone jack stopped working. Speakers do work. Nevermind issue was
  on my end not sure how to close bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 11 13:12:34 2018
  InstallationDate: Installed on 2018-01-05 (279 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, 
Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all

2018-10-11 Thread James Miller

Never mind issue was on my end

** Description changed:

- Headphone jack stopped working. Speakers do work.
+ Headphone jack stopped working. Speakers do work. Nevermind issue was on
+ my end not sure how to close bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
-  /dev/snd/controlC0:  james  2649 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
+  /dev/snd/controlC0:  james  2649 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 11 13:12:34 2018
  InstallationDate: Installed on 2018-01-05 (279 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
-  /dev/snd/controlC0:  james  2649 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
+  /dev/snd/controlC0:  james  2649 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, 
Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

Title:
  [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out,
  Left] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Headphone jack stopped working. Speakers do work. Nevermind issue was
  on my end not sure how to close bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 11 13:12:34 2018
  InstallationDate: Installed on 2018-01-05 (279 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, 
Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1797432] [NEW] [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all

2018-10-11 Thread James Miller

Public bug reported:

Headphone jack stopped working. Speakers do work. Nevermind issue was on
my end not sure how to close bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
 /dev/snd/controlC0:  james  2649 F pulseaudio
CurrentDesktop: Unity
Date: Thu Oct 11 13:12:34 2018
InstallationDate: Installed on 2018-01-05 (279 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
 /dev/snd/controlC0:  james  2649 F pulseaudio
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: No sound at all
Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] 
No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83F9
dmi.board.vendor: HP
dmi.board.version: 46.40
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cc1xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug xenial

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

Title:
  [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out,
  Left] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Headphone jack stopped working. Speakers do work. Nevermind issue was
  on my end not sure how to close bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 11 13:12:34 2018
  InstallationDate: Installed on 2018-01-05 (279 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, 
Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1693948] Re: useless diagnostics in dpkg.log from journalctl due to ellipses

** Package changed: dpkg (Ubuntu) => init-system-helpers (Ubuntu)

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

Title:
  useless diagnostics in dpkg.log from journalctl due to ellipses

Status in init-system-helpers package in Ubuntu:
  Confirmed

Bug description:
  Many of the apport hooks try to include some information about why a
  service didn't start correctly. One recent report included the
  following:

  May 26 18:39:19 ux305ua-linux systemd[1]: Starting OpenBSD Secure Shell 
serv
  May 26 18:39:19 ux305ua-linux sshd[2500]: /etc/ssh/sshd_config line 64: 
miss
  May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Main process 
exited, ...a[0m
  May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;31mFailed to start OpenBSD 
Secure She[0m
  May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Unit entered 
failed s[0m
  May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Failed with 
result 'e[0m
  Hint: Some lines were ellipsized, use -l to show in full.

  
  The actual error information is this:

  /etc/ssh/sshd_config line 64: miss
  and
  Failed with result 'e

  This is very nearly useless.

  We should include the -l parameter as suggested so that we stand a
  chance of seeing an error that doesn't occur in the first twenty
  characters of program output.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1693948/+subscriptions

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

[Touch-packages] [Bug 1797236] Re: network-manager openvpn settings not being saved

It's been accepted, should make its way to cosmic soon.

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

** Changed in: network-manager-openvpn (Ubuntu)
   Status: New => Fix Committed

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

Title:
  network-manager openvpn settings not being saved

Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager-openvpn package in Ubuntu:
  Fix Committed

Bug description:
  I'm seeing some weird issue with the new NM + openvpn; if I create a
  new VPN connection, and add certificate options (verify name exactly,
  plus TLS auth), these options are not saved, leading to the connection
  failing.

  The following versions lead to an invalid connection:
  ii  network-manager   1.12.4-1ubuntu1 amd64   
network management framework (daemon and userspace tools)
  ii  network-manager-openvpn   1.8.6-1 amd64   
network management framework (OpenVPN plugin core)

  
  Reverting to the following versions, things work again:
  ii  network-manager   1.12.2-0ubuntu4 amd64   
network management framework (daemon and userspace tools)
  ii  network-manager-openvpn   1.8.4-1 amd64   
network management framework (OpenVPN plugin core)

  
  If I use an existing connection saved with a prior version of NM, the 
connection will be successful. If I go open the settings, hit Apply, all 
advanced TLS settings are wiped.

  The connection then fails:

  Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]91.189.91.19:443
  Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET]91.189.91.19:443 [nonblock]
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP connection established with 
[AF_INET]91.189.91.19:443
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link local: (not bound)
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link remote: 
[AF_INET]xx.xx.xx.xx:443
  Oct 10 16:58:53 demeter nm-openvpn[6538]: Connection reset, restarting [0]
  Oct 10 16:58:53 demeter nm-openvpn[6538]: SIGUSR1[soft,connection-reset] 
received, process restarting
  Oct 10 16:58:58 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
  Oct 10 16:58:58 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Oct 10 16:58:58 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET6]2001:67c:1562:0:1::1:443
  Oct 10 16:58:58 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET6]2001:67c:1562:0:1::1:443 [nonblock]
  Oct 10 16:58:59 demeter nm-openvpn[6538]: TCP: connect to 
[AF_INET6]:xxx:xx:xx::xx:443 failed: Network is unreachable
  Oct 10 16:58:59 demeter nm-openvpn[6538]: SIGUSR1[connection 
failed(soft),init_instance] received, process restarting
  Oct 10 16:59:04 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.

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

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

[Touch-packages] [Bug 1693948] [NEW] useless diagnostics in dpkg.log from journalctl due to ellipses

You have been subscribed to a public bug:

Many of the apport hooks try to include some information about why a
service didn't start correctly. One recent report included the
following:

May 26 18:39:19 ux305ua-linux systemd[1]: Starting OpenBSD Secure Shell serv
May 26 18:39:19 ux305ua-linux sshd[2500]: /etc/ssh/sshd_config line 64: miss
May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Main process 
exited, ...a[0m
May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;31mFailed to start OpenBSD 
Secure She[0m
May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Unit entered 
failed s[0m
May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Failed with 
result 'e[0m
Hint: Some lines were ellipsized, use -l to show in full.


The actual error information is this:

/etc/ssh/sshd_config line 64: miss
and
Failed with result 'e

This is very nearly useless.

We should include the -l parameter as suggested so that we stand a
chance of seeing an error that doesn't occur in the first twenty
characters of program output.

Thanks

** Affects: init-system-helpers (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: id-59ea53165a72f7114d0742ef rls-bb-incoming
-- 
useless diagnostics in dpkg.log from journalctl due to ellipses
https://bugs.launchpad.net/bugs/1693948
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to init-system-helpers 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 1797415] Re: DNS stops working when disconnecting PPTP VPN on desktop

** Attachment added: "and when the VPN is down again"

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797415/+attachment/5200104/+files/vpn_down.log

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

Title:
DNS stops working when disconnecting PPTP VPN on desktop

Status in systemd package in Ubuntu:
New

Bug description:
On Cosmic I was testing some VPN setups. I created a PPTP VPN connection to
my server.
Everything connected and worked as it should.

When I disconnect the VPN, DNS resolution stops working.

Looking at "systemd-resolve --status" shows that the correct DNS
server is listed for the interface when the connection is torn down,
and I can ping it. Doing a nslookup setting the server to the IP
address shown in --status shows that DNS resolution is working
correctly.

resolv.conf says nameserver 127.0.0.53

Restart resolved makes things work again.
(Also, restarting Network Manager makes it work again.)

Trying to ping a hostname from the cli when in the broken state yields
zero output from resolved logs when in debug mode. Almost like it's
not even hitting resolved, so this bug could very well be somewhere
else.

I've checked, and I can ping 127.0.0.1 and the default routes look OK,
although there is a route to the VPN server left over.

I'm all out of ideas. Any ideas?

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

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

[Touch-packages] [Bug 1797415] [NEW] DNS stops working when disconnecting PPTP VPN on desktop

Public bug reported:

On Cosmic I was testing some VPN setups.  I created a PPTP VPN connection to my 
server.
Everything connected and worked as it should.

When I disconnect the VPN, DNS resolution stops working.

Looking at "systemd-resolve --status" shows that the correct DNS server
is listed for the interface  when the connection is torn down, and I can
ping it.  Doing a nslookup setting the server to the IP address shown in
--status shows that DNS resolution is working correctly.

resolv.conf says nameserver 127.0.0.53

Restart resolved makes things work again.
(Also, restarting Network Manager makes it work again.)

Trying to ping a hostname from the cli when in the broken state yields
zero output from resolved logs when in debug mode.  Almost like it's not
even hitting resolved, so this bug could very well be somewhere else.

I've checked, and I can ping 127.0.0.1 and the default routes look OK,
although there is a route to the VPN server left over.

I'm all out of ideas.  Any ideas?

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

** Attachment added: "When the VPN is up"
   https://bugs.launchpad.net/bugs/1797415/+attachment/5200103/+files/vpn_up.log

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

Title:
  DNS stops working when disconnecting PPTP VPN on desktop

Status in systemd package in Ubuntu:
  New

Bug description:
  On Cosmic I was testing some VPN setups.  I created a PPTP VPN connection to 
my server.
  Everything connected and worked as it should.

  When I disconnect the VPN, DNS resolution stops working.

  Looking at "systemd-resolve --status" shows that the correct DNS
  server is listed for the interface  when the connection is torn down,
  and I can ping it.  Doing a nslookup setting the server to the IP
  address shown in --status shows that DNS resolution is working
  correctly.

  resolv.conf says nameserver 127.0.0.53

  Restart resolved makes things work again.
  (Also, restarting Network Manager makes it work again.)

  Trying to ping a hostname from the cli when in the broken state yields
  zero output from resolved logs when in debug mode.  Almost like it's
  not even hitting resolved, so this bug could very well be somewhere
  else.

  I've checked, and I can ping 127.0.0.1 and the default routes look OK,
  although there is a route to the VPN server left over.

  I'm all out of ideas.  Any ideas?

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

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

[Touch-packages] [Bug 1797236] Re: network-manager openvpn settings not being saved

Actually, I can reproduce the fix in a live session so I'll just upload
what we have.

Here's a screencast showing what I did - let me know if I'm not
reproducing the same bug.

** Attachment added: "nm-connection-editor-vpn.webm"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1797236/+attachment/5200101/+files/nm-connection-editor-vpn.webm

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

Title:
  network-manager openvpn settings not being saved

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  I'm seeing some weird issue with the new NM + openvpn; if I create a
  new VPN connection, and add certificate options (verify name exactly,
  plus TLS auth), these options are not saved, leading to the connection
  failing.

  The following versions lead to an invalid connection:
  ii  network-manager   1.12.4-1ubuntu1 amd64   
network management framework (daemon and userspace tools)
  ii  network-manager-openvpn   1.8.6-1 amd64   
network management framework (OpenVPN plugin core)

  
  Reverting to the following versions, things work again:
  ii  network-manager   1.12.2-0ubuntu4 amd64   
network management framework (daemon and userspace tools)
  ii  network-manager-openvpn   1.8.4-1 amd64   
network management framework (OpenVPN plugin core)

  
  If I use an existing connection saved with a prior version of NM, the 
connection will be successful. If I go open the settings, hit Apply, all 
advanced TLS settings are wiped.

  The connection then fails:

  Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]91.189.91.19:443
  Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET]91.189.91.19:443 [nonblock]
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP connection established with 
[AF_INET]91.189.91.19:443
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link local: (not bound)
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link remote: 
[AF_INET]xx.xx.xx.xx:443
  Oct 10 16:58:53 demeter nm-openvpn[6538]: Connection reset, restarting [0]
  Oct 10 16:58:53 demeter nm-openvpn[6538]: SIGUSR1[soft,connection-reset] 
received, process restarting
  Oct 10 16:58:58 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
  Oct 10 16:58:58 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Oct 10 16:58:58 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET6]2001:67c:1562:0:1::1:443
  Oct 10 16:58:58 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET6]2001:67c:1562:0:1::1:443 [nonblock]
  Oct 10 16:58:59 demeter nm-openvpn[6538]: TCP: connect to 
[AF_INET6]:xxx:xx:xx::xx:443 failed: Network is unreachable
  Oct 10 16:58:59 demeter nm-openvpn[6538]: SIGUSR1[connection 
failed(soft),init_instance] received, process restarting
  Oct 10 16:59:04 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.

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

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

With systemd on Xenial & Artful, there is no instruction in the case of
MOUNT_MOUNTING which re-enforce why it is working with these releases :

# src/core/mount.c 
1182 case MOUNT_MOUNTING: 
1183 case MOUNT_MOUNTING_DONE: 
1184 case MOUNT_MOUNTING_SIGKILL: 
1185 case MOUNT_MOUNTING_SIGTERM:
1186 
1187if (f == MOUNT_SUCCESS)
1188mount_enter_mounted(m, f);
1189else if (m->from_proc_self_mountinfo)
1190mount_enter_mounted(m, f);
1191else
1192mount_enter_dead(m, f);
1193break;

So most likely, falls in the MOUNT_MOUNTING_SIGTERM and then break the
case statement flow.


# src/basic/unit-def.h 
MOUNT_MOUNTING, /* /usr/bin/mount is running, but the mount is not done yet. */

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

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

[Touch-packages] [Bug 1726803] Re: unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess insta

** Changed in: shim-signed (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-
  signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1)

Status in shim-signed package in Ubuntu:
  Fix Committed
Status in unattended-upgrades package in Ubuntu:
  Incomplete
Status in shim-signed source package in Bionic:
  Triaged
Status in unattended-upgrades source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * When Secure Boot is enabled and a new dkms module is installed sim-
  signed asks for a new Secure Boot key, or aborts package installation
  in non-interactive mode. When unattended-upgrades performed the
  upgrade the aborted installation leaves an unconfigured system behind
  that may even fail to boot.

   * The fix in u-u detects new dkms-related packages and holds them
  back from installation.

  [Test Case]

  1. Set up a fully - or almost fully updated Bionic system.

  2. Install packagages to trigger the block:
  apt install dkms shim-signed r8168-dkms

  3. Fake enabled secure boot:
  echo "shim-signed shim/enable_secureboot boolean true" | 
debconf-set-selections

  4. Add and enable PPA hosting updated dkms package pulling in a new dkms-like 
dependency:
  add-apt-repository ppa:rbalint/scratch
  echo 'Unattended-Upgrade::Allowed-Origins 
{"LP-PPA-rbalint-scratch:${distro_codename}";}' > 
/etc/apt/apt.conf.d/51unattended-upgrades-all

  5. Observe u-u keeping back the new package:
  unattended-upgrade --verbose --dry-run --debug
  ...
  Checking: r8168-dkms ([])
  pkg new-dkms-dep may trigger secure boot key prompt
  sanity check failed
  ...

  [Regression Potential]

  * Since the fix is holding back packages from installation it is
  expected that systems that would have otherwise broke during the
  installation would not receive all updates. Since exact detection of
  the installation failure reported here does not seem possible u-u
  holds back more packages than it would be absolutely necessary.

  * Administrators are expected to set up email notifications about the
  updates performed by u-u and act on held back packages.

  * Since updates pulling in new packages are fairly rare especially in
  the -security pocket which u-u installs from by default unwanted
  regressions are unlikely to show up.

  [Original Bug Text]

  Occurred a minute after logging in

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: 0
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Oct 24 11:35:53 2017
  EFITables:
   Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends
   Oct 24 11:33:04 paddy-laptop kernel: efi:  ACPI=0x7866  ACPI 
2.0=0x7866  SMBIOS=0xf  SMBIOS 3.0=0xf0020  ESRT=0x79360598
   Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from 
0x79360598 to 0x793605d0.
   Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-09-11 (42 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim-signed
  Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1797236] Re: network-manager openvpn settings not being saved

I don't agree that I should be assigned to this bug. I simply tried a
patch, but it didn't work for the person that initially reported the
bug.

cyphermox, would you please try to debug further to see what your
problem is? I'll help upload once we have a proper fix, if you like.

** Changed in: network-manager-openvpn (Ubuntu)
 Assignee: Iain Lane (laney) => (unassigned)

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

Title:
  network-manager openvpn settings not being saved

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  I'm seeing some weird issue with the new NM + openvpn; if I create a
  new VPN connection, and add certificate options (verify name exactly,
  plus TLS auth), these options are not saved, leading to the connection
  failing.

  The following versions lead to an invalid connection:
  ii  network-manager   1.12.4-1ubuntu1 amd64   
network management framework (daemon and userspace tools)
  ii  network-manager-openvpn   1.8.6-1 amd64   
network management framework (OpenVPN plugin core)

  
  Reverting to the following versions, things work again:
  ii  network-manager   1.12.2-0ubuntu4 amd64   
network management framework (daemon and userspace tools)
  ii  network-manager-openvpn   1.8.4-1 amd64   
network management framework (OpenVPN plugin core)

  
  If I use an existing connection saved with a prior version of NM, the 
connection will be successful. If I go open the settings, hit Apply, all 
advanced TLS settings are wiped.

  The connection then fails:

  Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]91.189.91.19:443
  Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET]91.189.91.19:443 [nonblock]
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP connection established with 
[AF_INET]91.189.91.19:443
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link local: (not bound)
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link remote: 
[AF_INET]xx.xx.xx.xx:443
  Oct 10 16:58:53 demeter nm-openvpn[6538]: Connection reset, restarting [0]
  Oct 10 16:58:53 demeter nm-openvpn[6538]: SIGUSR1[soft,connection-reset] 
received, process restarting
  Oct 10 16:58:58 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
  Oct 10 16:58:58 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Oct 10 16:58:58 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET6]2001:67c:1562:0:1::1:443
  Oct 10 16:58:58 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET6]2001:67c:1562:0:1::1:443 [nonblock]
  Oct 10 16:58:59 demeter nm-openvpn[6538]: TCP: connect to 
[AF_INET6]:xxx:xx:xx::xx:443 failed: Network is unreachable
  Oct 10 16:58:59 demeter nm-openvpn[6538]: SIGUSR1[connection 
failed(soft),init_instance] received, process restarting
  Oct 10 16:59:04 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-10-11 Thread Jan Smed

Same problem for me...

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1797236] Re: network-manager openvpn settings not being saved

2018-10-11 Thread Sebastien Bacher

Hey Laney, Mathieu said you add an upstream bug/patch that works for you
so assigning according

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

** Changed in: network-manager-openvpn (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

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

Title:
  network-manager openvpn settings not being saved

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  I'm seeing some weird issue with the new NM + openvpn; if I create a
  new VPN connection, and add certificate options (verify name exactly,
  plus TLS auth), these options are not saved, leading to the connection
  failing.

  The following versions lead to an invalid connection:
  ii  network-manager   1.12.4-1ubuntu1 amd64   
network management framework (daemon and userspace tools)
  ii  network-manager-openvpn   1.8.6-1 amd64   
network management framework (OpenVPN plugin core)

  
  Reverting to the following versions, things work again:
  ii  network-manager   1.12.2-0ubuntu4 amd64   
network management framework (daemon and userspace tools)
  ii  network-manager-openvpn   1.8.4-1 amd64   
network management framework (OpenVPN plugin core)

  
  If I use an existing connection saved with a prior version of NM, the 
connection will be successful. If I go open the settings, hit Apply, all 
advanced TLS settings are wiped.

  The connection then fails:

  Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]91.189.91.19:443
  Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET]91.189.91.19:443 [nonblock]
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP connection established with 
[AF_INET]91.189.91.19:443
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link local: (not bound)
  Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link remote: 
[AF_INET]xx.xx.xx.xx:443
  Oct 10 16:58:53 demeter nm-openvpn[6538]: Connection reset, restarting [0]
  Oct 10 16:58:53 demeter nm-openvpn[6538]: SIGUSR1[soft,connection-reset] 
received, process restarting
  Oct 10 16:58:58 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
  Oct 10 16:58:58 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Oct 10 16:58:58 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET6]2001:67c:1562:0:1::1:443
  Oct 10 16:58:58 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET6]2001:67c:1562:0:1::1:443 [nonblock]
  Oct 10 16:58:59 demeter nm-openvpn[6538]: TCP: connect to 
[AF_INET6]:xxx:xx:xx::xx:443 failed: Network is unreachable
  Oct 10 16:58:59 demeter nm-openvpn[6538]: SIGUSR1[connection 
failed(soft),init_instance] received, process restarting
  Oct 10 16:59:04 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.

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

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

[Touch-packages] [Bug 1797275] Re: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent.

2018-10-11 Thread Sebastien Bacher

Thank you for your bug report

$ wget  
https://launchpad.net/ubuntu/+source/gtk+3.0/3.22.30-1ubuntu1/+build/14769632/+files/libgtk-3-0_3.22.30-1ubuntu1_amd64.deb
$ dpkg -c libgtk-3-0_3.22.30-1ubuntu1_amd64.deb | grep gtk-query-i

-> the fix is in the deb under /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-
query-immodules-3.0

you can get to the same result on an installed system with 
$ dpkg -S gtk-query-immodules-3.0

Is it really missing for you or did you look at the wrong location?

** Changed in: ubuntu
   Importance: Undecided => Low

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

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

Title:
  libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is
  absent.

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  The binary "gtk-query-immodules-3.0" is absent from package. The
  package DOES include the man-page for "gtk-query-immodules-3.0", but
  not the actual utility it documents.

  I downloaded the source tarball
  "gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz" and untar-ed it:

   |$ ls ./
   |debian
   |gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz

   |$ ls ./debian/libgtk-3-bin*
   |debian/libgtk-3-bin.install
   |debian/libgtk-3-bin.links.in

   |$ cat ./debian/libgtk-3-bin.install
   |usr/bin/broadwayd
   |usr/bin/gtk-builder-tool
   |usr/bin/gtk-launch
   |usr/bin/gtk-query-settings
   |usr/share/gettext/its/gtkbuilder.its
   |usr/share/gettext/its/gtkbuilder.loc
   |usr/share/man/man1/broadwayd.1
   |usr/share/man/man1/gtk-builder-tool.1
   |usr/share/man/man1/gtk-launch.1
   |usr/share/man/man1/gtk-query-immodules-3.0.1
   |usr/share/man/man1/gtk-query-settings.1

  Qualifiers:
  1)
   |$ lsb_release -rd
   |Description:Linux Mint 19 Tara
   |Release:19

  2)
   |$ apt-cache policy libgtk-3-bin
   |libgtk-3-bin:
   |  Installed: 3.22.30-1ubuntu1
   |  Candidate: 3.22.30-1ubuntu1
   |  Version table:
   | *** 3.22.30-1ubuntu1 500
   |500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
   |100 /var/lib/dpkg/status

   |$ ls /usr/share/man/man1/gtk-query*
   |/usr/share/man/man1/gtk-query-immodules-2.0.1.gz
   |/usr/share/man/man1/gtk-query-immodules-3.0.1.gz
   |/usr/share/man/man1/gtk-query-settings.1.gz

   |$ ls /usr/bin/gtk-query*
   |/usr/bin/gtk-query-settings

  3) I am experimenting with development of specialized immodules for
  GtkEntry widget. I expect to be able to install these additional
  modules and for my application to access them per the instructions in
  the Gtk+3 documentation.

  4)
   |$ whereis gtk-query-immodules-3.0
   |gtk-query-immodules-3:

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1797275/+subscriptions

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

[Touch-packages] [Bug 1685484] Re: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work

2018-10-11 Thread Brian Murray

** Tags removed: rls-aa-incoming

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

Title:
  DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  I think it's regression for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1578663 in
  zesty.

  1. NTP servers are send via DHCP and seen by NM:

  $ nmcli con show connection1 | grep ntp
  DHCP4.OPTION[30]:   requested_ntp_servers = 1
  DHCP4.OPTION[31]:   ntp_servers = 80.50.231.226 
217.96.29.26 212.160.106.226

  2. timesyncd is using hardcoded default NTP server:

  $ systemctl -n 200 status systemd-timesyncd.service
  * systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
    Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
     `-disable-with-time-daemon.conf
     Active: active (running) since Sat 2017-04-22 13:12:23 CEST; 16min ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 576 (systemd-timesyn)
     Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
  Tasks: 2 (limit: 4915)
     Memory: 1.5M
    CPU: 20ms
     CGroup: /system.slice/systemd-timesyncd.service
     `-576 /lib/systemd/systemd-timesyncd

  Apr 22 13:12:23 slodki systemd[1]: Starting Network Time Synchronization...
  Apr 22 13:12:23 slodki systemd[1]: Started Network Time Synchronization.
  Apr 22 13:12:53 slodki systemd-timesyncd[576]: Synchronized to time server 
91.189.89.199:123 (ntp.ubuntu.com).

  3. There are not other time sync deamons installed:

  $ cat 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  [Unit]
  # don't run timesyncd if we have another NTP daemon installed
  ConditionFileIsExecutable=!/usr/sbin/ntpd
  ConditionFileIsExecutable=!/usr/sbin/openntpd
  ConditionFileIsExecutable=!/usr/sbin/chronyd
  ConditionFileIsExecutable=!/usr/sbin/VBoxService

  $ ls -l /usr/sbin/{ntpd,openntpd,chronyd,VBoxService}
  ls: cannot access '/usr/sbin/ntpd': No such file or directory
  ls: cannot access '/usr/sbin/openntpd': No such file or directory
  ls: cannot access '/usr/sbin/chronyd': No such file or directory
  ls: cannot access '/usr/sbin/VBoxService': No such file or directory

  4. There is only one default timesyncd.conf file with default values:

  $ sudo find / -iname \*timesync\*
  /etc/systemd/timesyncd.conf
  /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
  /etc/dhcp/dhclient-exit-hooks.d/timesyncd
  /usr/share/man/man5/timesyncd.conf.d.5.gz
  /usr/share/man/man5/timesyncd.conf.5.gz
  /usr/share/man/man8/systemd-timesyncd.8.gz
  /usr/share/man/man8/systemd-timesyncd.service.8.gz
  
/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-6NwdRT
  /lib/systemd/systemd-timesyncd
  /lib/systemd/system/systemd-timesyncd.service
  /lib/systemd/system/systemd-timesyncd.service.d
  
/var/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-jz0q47

  $ cat /etc/systemd/timesyncd.conf
  #  This file is part of systemd.
  #
  #  systemd is free software; you can redistribute it and/or modify it
  #  under the terms of the GNU Lesser General Public License as published by
  #  the Free Software Foundation; either version 2.1 of the License, or
  #  (at your option) any later version.
  #
  # Entries in this file show the compile time defaults.
  # You can change settings by editing this file.
  # Defaults can be restored by simply deleting this file.
  #
  # See timesyncd.conf(5) for details.

  [Time]
  #NTP=
  #FallbackNTP=ntp.ubuntu.com

  5. DHCP hook installed as /etc/dhcp/dhclient-exit-hooks.d/timesyncd is
  not working,
  TIMESYNCD_CONF=/run/systemd/timesyncd.conf.d/01-dhclient.conf is not
  created.

  6. After manually executing steps from hook all works as expected:

  $ sudo mkdir -p /run/systemd/timesyncd.conf.d/
  $ sudo cat  [Time]
  > NTP=80.50.231.226 217.96.29.26 212.160.106.226
  > EOF
  $ sudo systemctl try-restart systemd-timesyncd.service
  $ sudo systemctl status systemd-timesyncd.service
  * systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
    Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
     `-disable-with-time-daemon.conf
     Active: active (running) since Sat 2017-04-22 13:47:28 CEST; 2min 6s ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 3094 (systemd-timesyn)
     Status: "Synchronized to time server 80.50.231.226:123

[Touch-packages] [Bug 1797275] [NEW] libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent.

You have been subscribed to a public bug:

The binary "gtk-query-immodules-3.0" is absent from package. The package
DOES include the man-page for "gtk-query-immodules-3.0", but not the
actual utility it documents.

I downloaded the source tarball "gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz"
and untar-ed it:

 |$ ls ./
 |debian
 |gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz

 |$ ls ./debian/libgtk-3-bin*
 |debian/libgtk-3-bin.install
 |debian/libgtk-3-bin.links.in

 |$ cat ./debian/libgtk-3-bin.install
 |usr/bin/broadwayd
 |usr/bin/gtk-builder-tool
 |usr/bin/gtk-launch
 |usr/bin/gtk-query-settings
 |usr/share/gettext/its/gtkbuilder.its
 |usr/share/gettext/its/gtkbuilder.loc
 |usr/share/man/man1/broadwayd.1
 |usr/share/man/man1/gtk-builder-tool.1
 |usr/share/man/man1/gtk-launch.1
 |usr/share/man/man1/gtk-query-immodules-3.0.1
 |usr/share/man/man1/gtk-query-settings.1

Qualifiers:
1)
 |$ lsb_release -rd
 |Description:  Linux Mint 19 Tara
 |Release:  19

2)
 |$ apt-cache policy libgtk-3-bin
 |libgtk-3-bin:
 |  Installed: 3.22.30-1ubuntu1
 |  Candidate: 3.22.30-1ubuntu1
 |  Version table:
 | *** 3.22.30-1ubuntu1 500
 |500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
 |100 /var/lib/dpkg/status

 |$ ls /usr/share/man/man1/gtk-query*
 |/usr/share/man/man1/gtk-query-immodules-2.0.1.gz
 |/usr/share/man/man1/gtk-query-immodules-3.0.1.gz
 |/usr/share/man/man1/gtk-query-settings.1.gz

 |$ ls /usr/bin/gtk-query*
 |/usr/bin/gtk-query-settings

3) I am experimenting with development of specialized immodules for
GtkEntry widget. I expect to be able to install these additional modules
and for my application to access them per the instructions in the Gtk+3
documentation.

4)
 |$ whereis gtk-query-immodules-3.0
 |gtk-query-immodules-3:

Thank you!

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Incomplete


** Tags: gtk-query-immodules-3.0 immodule libgtk-3-bin
-- 
libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent.
https://bugs.launchpad.net/bugs/1797275
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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2018-10-11 Thread Dimitri John Ledkov

** Description changed:

  [Impact]
  
-  * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
+  * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.
  
-  * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be
+  * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be
  rapidly adopted due to increased set of supported hashes & algoes, as
  well as improved handshake [re-]negotiation.
  
-  * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.
+  * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.
  
-  * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software
+  * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software
  is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.
  
- 
  [Test Case]
  
-  * Rebuild all reverse dependencies
+  * Rebuild all reverse dependencies
  
-  * Execute autopkg tests for all of them
+  * Execute autopkg tests for all of them
  
-  * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. 
mongodb)
-  
-  * Backport TLS v1.3 support patches, where applicable
+  * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g.
+ mongodb)
+ 
+  * Backport TLS v1.3 support patches, where applicable
  
  [Regression Potential]
  
-  * Connectivity interop is the biggest issues which will be unavoidable
+  * Connectivity interop is the biggest issues which will be unavoidable
  with introducing TLS v1.3. However, tests on cosmic demonstrate that
  curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3
  without issues.
  
-  * Mitigation of discovered connectivity issues will be possible by
+  * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side software
  or by backporting relevant support fixes
  
+ [Other Info]
  
- [Other Info]
-  
-  * Previous FFe for OpenSSL in 18.10 is at
-https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092
+  * Previous FFe for OpenSSL in 18.10 is at
+    https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092
  
-  * TLS v1.3 support in NSS is expected to make it to 18.04 via security
+  * TLS v1.3 support in NSS is expected to make it to 18.04 via security
  updates
  
-  * TLS v1.3 support in GnuTLS is expected to be available in 19.04
+  * TLS v1.3 support in GnuTLS is expected to be available in 19.04
+ 
+  * Test OpenSSL is being prepared in
+https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3
  (e.g. mongodb)

   * Backport TLS v1.3 support patches, where applicable

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes

  [Other Info]

   * Previous FFe for OpenSSL in 18.10 is at
     https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

   * TLS v1.3 support in NSS is expected to make it to 18.04 via
  security updates

   * TLS v1.3 support in GnuTLS is expected to be available in 19.04

   * Test OpenSSL is being prepared in
 https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473

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

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

[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy

Putting this on hold a bit; once we have a fix for the other PackageKit
bug in the SRU queue, so we don't cause breakage again.

** Tags added: block-proposed

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

Title:
  
/usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  pkcon what-provides and other tools querying codecs do not work, they crash 
(unless you happen to be lucky with your apt cache). Also, cancalled 
transactions crash as well, even if you're lucky with your apt cache, as the 
"matcher" object is deleted twice.

  There are two reasons: A duplicate delete statement in providesCodec
  entered when cancelling the lookup, and a invalid pointer dereference
  in there.

  [Test case]
  The daemon should not crash as below, but should print a useful message.

  $ lxc launch -e ubuntu:bionic bbb
  $ lxc exec bbb apt update
  $ lxc exec bbb -- apt  -y  install packagekit
  $ lxc exec bbb pkcon what-provides  "gstreamer1.0(decoder-audio/ac3)"
  [...] The daemon crashed mid-transaction!

  (empty lxd container seems to be able to reproduce easily)

  This only tests the pointer dereference, I don't have a test for the
  duplicate. But the code is obviously correct:

   for ... [
 if (m_cancel) {
   // here used to be "delete matcher" - that's deleted
   break;
 }
   }
   delete matcher;

  That is, matcher is always deleted once now, and was always deleted
  twice when cancelling before.

  [Regression potential]
  I don't think it's possible to have a regression here, given the nature of 
the fix, but if there were one, we'd see different behavior in codec lookup.

  For the duplicate delete on cancelled transactions, you'd be looking
  at memory leaks if there were a regression.

  [Other info]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
1.1.10-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2018-10-11 Thread Dimitri John Ledkov

** Summary changed:

- SRU OpenSSL 1.1.1 to 18.04 LTS
+ [SRU] OpenSSL 1.1.1 to 18.04 LTS

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  
  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. 
mongodb)
   
   * Backport TLS v1.3 support patches, where applicable

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes


  [Other Info]
   
   * Previous FFe for OpenSSL in 18.10 is at
 https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

   * TLS v1.3 support in NSS is expected to make it to 18.04 via
  security updates

   * TLS v1.3 support in GnuTLS is expected to be available in 19.04

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

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

[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version

2018-10-11 Thread Matthias Klumpp

Yes, I completely missed that change, this needs to be changed.
I need to prepare a new upload for Debian anyway, maybe I can change this 
behavior on the weekend at Debian.

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

Title:
  Regression: packagekit crashes updating itself to a new version

Status in packagekit package in Ubuntu:
  Triaged
Status in plasma-discover package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Triaged
Status in plasma-discover source package in Bionic:
  Confirmed

Bug description:
  Bionic: 18.04
  Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1

  Updating with pkcon upgrade or plasma-discover crashes packagekit mid
  transaction, requiring user intervention on the command line.

  In plasma-discover the gui reports the crash briefly, but then stalls
  in apparent mid update, requiring the user to force close it and again
  resolve the issue on the command line.

  Example transactions:

  $ pkcon update
  Getting updates   [=] 
  Finished  [=] 
  Loading cache [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be updated:
   gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection 
data for the PackageKit GLib library
   libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing 
PackageKit using GLib
   packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management 
service
   packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64  Provides PackageKit 
command-line tools
  Proceed with changes? [N/y] y

[=] 
  Updating packages [=] 
  Waiting for authentication[=] 
  Loading cache [=] 
  Running   [=] 
  Installing packages   [ ] (80%)  The daemon 
crashed mid-transaction!

  $ sudo apt-get upgrade 
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  and obviously after that doing anything meaningful with packagekit
  like installing a package fails

  $pkcon install kaffeine
  Resolving [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be installed:
   kaffeine-2.0.14-1.amd64versatile media player for KDE
  Proceed with changes? [N/y] y

[=] 
  Installing[=] 
  Waiting for authentication[=] 
  Waiting for package manager lock[=] 
  Finished  [=] 
  Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure 
-a' to correct the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-26 (69 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: packagekit 1.1.9-1ubuntu2.18.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1797387] Re: bash crashes on PS1 set, wait, press enter, Ctrl-C, enter

2018-10-11 Thread Eric Curtin

Doesn't occur on 18.04, CentOS 6 or CentOS 7

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

Title:
  bash crashes on PS1 set, wait, press enter, Ctrl-C, enter

Status in bash package in Ubuntu:
  New

Bug description:
  Reproducible on xubuntu 16.04 x86_64 (reproduced on two machines I
  tried). Steps to reproduce:

  export PS1="\e[1;32m\u@$HOSTNAME \t \$()\e[1;36m\$(sleep 1)\e[m\n\w>"
  Press enter
  wait
  Press enter
  Ctrl-C
  Press enter

  bash will crash. My PS1 line calls (and forks) a little shell script
  to report a status I want to see. It seems to be specific to bash on
  16.04

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

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

[Touch-packages] [Bug 1797387] Re: bash crashes on PS1 set, wait, press enter, Ctrl-C, enter

2018-10-11 Thread Eric Curtin

Reproduced on Ubuntu 14.04 and 16.04

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

Title:
  bash crashes on PS1 set, wait, press enter, Ctrl-C, enter

Status in bash package in Ubuntu:
  New

Bug description:
  Reproducible on xubuntu 16.04 x86_64 (reproduced on two machines I
  tried). Steps to reproduce:

  export PS1="\e[1;32m\u@$HOSTNAME \t \$()\e[1;36m\$(sleep 1)\e[m\n\w>"
  Press enter
  wait
  Press enter
  Ctrl-C
  Press enter

  bash will crash. My PS1 line calls (and forks) a little shell script
  to report a status I want to see. It seems to be specific to bash on
  16.04

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

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

[Touch-packages] [Bug 1795658] Re: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently

2018-10-11 Thread Mauricio Faria de Oliveira

Positive test results with xenial-proposed have also been verified by a
company interested in this fix, in their scenario/application.

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

Title:
  xenial systemd reports 'inactive' instead of 'failed' for service
  units that repeatedly failed to restart / failed permanently

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * In case a service unit has repeatedly failed to restart, it should be
 reported as 'failed' permanently, but currently it's instead reported
 as 'inactive'.

   * System monitoring tools that evaluate the status of systemd service units
 and act upon it (for example: restart service, report permanent failure)
 are currently misled by information in 'systemctl status .service'.

   * System management tools based on such information may take wrong and/or
 sub-optimal actions in the managed systems regarding such service units.

   * This systemd patch [1] directly addresses this issue (see systemd github
 PR #3166 [2]), and its code is still effectice in upstream systemd today,
 without further fixes/changes (the only changes were in doc text and the
 busname files that were removed, but still without further fixes to this).

  [Test Case]

   * This is copied from systemd PR #3166 [2].

   * This has been tested by a customer as well, and with its system monitoring
 and management solution, for interoperability verification.

  $ cat

[Touch-packages] [Bug 1797386] [NEW] SRU OpenSSL 1.1.1 to 18.04 LTS

2018-10-11 Thread Dimitri John Ledkov

Public bug reported:

[Impact]

 * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.

 * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be
rapidly adopted due to increased set of supported hashes & algoes, as
well as improved handshake [re-]negotiation.

 * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

 * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software
is sensitive to the negotiation handshake and may either need
patches/improvements or clamp-down to maximum v1.2.


[Test Case]

 * Rebuild all reverse dependencies

 * Execute autopkg tests for all of them

 * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb)
 
 * Backport TLS v1.3 support patches, where applicable

[Regression Potential]

 * Connectivity interop is the biggest issues which will be unavoidable
with introducing TLS v1.3. However, tests on cosmic demonstrate that
curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3
without issues.

 * Mitigation of discovered connectivity issues will be possible by
clamping down to TLS v1.2 in either server-side or client-side software
or by backporting relevant support fixes


[Other Info]
 
 * Previous FFe for OpenSSL in 18.10 is at
   https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

 * TLS v1.3 support in NSS is expected to make it to 18.04 via security
updates

 * TLS v1.3 support in GnuTLS is expected to be available in 19.04

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


** Tags: bionic

** Tags added: bionic

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

Title:
  SRU OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  
  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. 
mongodb)
   
   * Backport TLS v1.3 support patches, where applicable

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes


  [Other Info]
   
   * Previous FFe for OpenSSL in 18.10 is at
 https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

   * TLS v1.3 support in NSS is expected to make it to 18.04 via
  security updates

   * TLS v1.3 support in GnuTLS is expected to be available in 19.04

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

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

[Touch-packages] [Bug 1797387] [NEW] bash crashes on PS1 set, wait, press enter, Ctrl-C, enter

2018-10-11 Thread Eric Curtin

Public bug reported:

Reproducible on xubuntu 16.04 x86_64 (reproduced on two machines I
tried). Steps to reproduce:

export PS1="\e[1;32m\u@$HOSTNAME \t \$()\e[1;36m\$(sleep 1)\e[m\n\w>"
Press enter
wait
Press enter
Ctrl-C
Press enter

bash will crash. My PS1 line calls (and forks) a little shell script to
report a status I want to see. It seems to be specific to bash on 16.04

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

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

Title:
  bash crashes on PS1 set, wait, press enter, Ctrl-C, enter

Status in bash package in Ubuntu:
  New

Bug description:
  Reproducible on xubuntu 16.04 x86_64 (reproduced on two machines I
  tried). Steps to reproduce:

  export PS1="\e[1;32m\u@$HOSTNAME \t \$()\e[1;36m\$(sleep 1)\e[m\n\w>"
  Press enter
  wait
  Press enter
  Ctrl-C
  Press enter

  bash will crash. My PS1 line calls (and forks) a little shell script
  to report a status I want to see. It seems to be specific to bash on
  16.04

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

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

[Touch-packages] [Bug 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk

2018-10-11 Thread David Chen

Investigation found that DAD timeout for IPv6 seems to be not
implemented for network manager [1]. And only support up to IPv4. It
looks like a limitation but couldn't find any writing confirmation for
this limitation.

[1] https://developer.gnome.org/NetworkManager/stable/settings-ipv6.html

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

Title:
  NetworkManager IPv6 DAD lifetime behavior introduce security risk

Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:
  When performing IPv6 certification test, two DAD test cases (3.2.5c and d) 
check the remaining lifetime feature of the IPv6 packets.  The Network trace 
shows that the remaining lifetime becomes infinite when running these test 
cases.  Hence when running in IPv6 environment with Network Manager enabled, 
there is a risk of packets travelling in network which has valid lifetime 
always. If these packets are snooped by a hacker he can reply to these packets 
and they can send legitimate packets which are actually not.  

  According to https://tools.ietf.org/search/rfc4862, page 19:
  "The above rules address a specific denial-of-service attack in which a bogus 
advertisement could contain prefixes with very small Valid Lifetimes.  Without 
the above rules, a single unauthenticated advertisement containing bogus Prefix 
Information options with short Valid Lifetimes could cause all of a node's 
addresses to expire prematurely.  The above rules ensure that legitimate 
advertisements (which are sent periodically) will "cancel" the short Valid 
Lifetimes before they actually take effect."

  Other notes:
  - 2 test cases pass without NetworkManager.
  - Tested with different Linux Desktop Distributions, as long as 
NetworkManager is running, those DAD test cases fail.

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

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

[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version

The default changed to restart in debhelper 10. I think we need (one
of?) --no-restart-on-upgrade --no-restart-after-upgrade passed to
dh_installsystemd.

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

Title:
  Regression: packagekit crashes updating itself to a new version

Status in packagekit package in Ubuntu:
  Triaged
Status in plasma-discover package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Triaged
Status in plasma-discover source package in Bionic:
  Confirmed

Bug description:
  Bionic: 18.04
  Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1

  Updating with pkcon upgrade or plasma-discover crashes packagekit mid
  transaction, requiring user intervention on the command line.

  In plasma-discover the gui reports the crash briefly, but then stalls
  in apparent mid update, requiring the user to force close it and again
  resolve the issue on the command line.

  Example transactions:

  $ pkcon update
  Getting updates   [=] 
  Finished  [=] 
  Loading cache [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be updated:
   gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection 
data for the PackageKit GLib library
   libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing 
PackageKit using GLib
   packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management 
service
   packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64  Provides PackageKit 
command-line tools
  Proceed with changes? [N/y] y

[=] 
  Updating packages [=] 
  Waiting for authentication[=] 
  Loading cache [=] 
  Running   [=] 
  Installing packages   [ ] (80%)  The daemon 
crashed mid-transaction!

  $ sudo apt-get upgrade 
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  and obviously after that doing anything meaningful with packagekit
  like installing a package fails

  $pkcon install kaffeine
  Resolving [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be installed:
   kaffeine-2.0.14-1.amd64versatile media player for KDE
  Proceed with changes? [N/y] y

[=] 
  Installing[=] 
  Waiting for authentication[=] 
  Waiting for package manager lock[=] 
  Finished  [=] 
  Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure 
-a' to correct the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-26 (69 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: packagekit 1.1.9-1ubuntu2.18.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version

Of course we do:

if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
deb-systemd-invoke try-restart 
'packagekit-offline-update.service' 'packagekit.service' >/dev/null || true
fi
fi
fi

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

Title:
  Regression: packagekit crashes updating itself to a new version

Status in packagekit package in Ubuntu:
  Triaged
Status in plasma-discover package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Triaged
Status in plasma-discover source package in Bionic:
  Confirmed

Bug description:
  Bionic: 18.04
  Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1

  Updating with pkcon upgrade or plasma-discover crashes packagekit mid
  transaction, requiring user intervention on the command line.

  In plasma-discover the gui reports the crash briefly, but then stalls
  in apparent mid update, requiring the user to force close it and again
  resolve the issue on the command line.

  Example transactions:

  $ pkcon update
  Getting updates   [=] 
  Finished  [=] 
  Loading cache [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be updated:
   gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection 
data for the PackageKit GLib library
   libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing 
PackageKit using GLib
   packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management 
service
   packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64  Provides PackageKit 
command-line tools
  Proceed with changes? [N/y] y

[=] 
  Updating packages [=] 
  Waiting for authentication[=] 
  Loading cache [=] 
  Running   [=] 
  Installing packages   [ ] (80%)  The daemon 
crashed mid-transaction!

  $ sudo apt-get upgrade 
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  and obviously after that doing anything meaningful with packagekit
  like installing a package fails

  $pkcon install kaffeine
  Resolving [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be installed:
   kaffeine-2.0.14-1.amd64versatile media player for KDE
  Proceed with changes? [N/y] y

[=] 
  Installing[=] 
  Waiting for authentication[=] 
  Waiting for package manager lock[=] 
  Finished  [=] 
  Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure 
-a' to correct the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-26 (69 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: packagekit 1.1.9-1ubuntu2.18.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk

Upstream fix:  https://github.com/NetworkManager/NetworkManager/pull/228

This will be ported to all supported releases soon, so we should be able
to pick that up easily enough.

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

Title:
  NetworkManager IPv6 DAD lifetime behavior introduce security risk

Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:
  When performing IPv6 certification test, two DAD test cases (3.2.5c and d) 
check the remaining lifetime feature of the IPv6 packets.  The Network trace 
shows that the remaining lifetime becomes infinite when running these test 
cases.  Hence when running in IPv6 environment with Network Manager enabled, 
there is a risk of packets travelling in network which has valid lifetime 
always. If these packets are snooped by a hacker he can reply to these packets 
and they can send legitimate packets which are actually not.  

  According to https://tools.ietf.org/search/rfc4862, page 19:
  "The above rules address a specific denial-of-service attack in which a bogus 
advertisement could contain prefixes with very small Valid Lifetimes.  Without 
the above rules, a single unauthenticated advertisement containing bogus Prefix 
Information options with short Valid Lifetimes could cause all of a node's 
addresses to expire prematurely.  The above rules ensure that legitimate 
advertisements (which are sent periodically) will "cancel" the short Valid 
Lifetimes before they actually take effect."

  Other notes:
  - 2 test cases pass without NetworkManager.
  - Tested with different Linux Desktop Distributions, as long as 
NetworkManager is running, those DAD test cases fail.

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

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

[Touch-packages] [Bug 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk

2018-10-11 Thread David Chen

Upstream issue reported:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/57

Thanks for looking into 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/1796622

Title:
  NetworkManager IPv6 DAD lifetime behavior introduce security risk

Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:
  When performing IPv6 certification test, two DAD test cases (3.2.5c and d) 
check the remaining lifetime feature of the IPv6 packets.  The Network trace 
shows that the remaining lifetime becomes infinite when running these test 
cases.  Hence when running in IPv6 environment with Network Manager enabled, 
there is a risk of packets travelling in network which has valid lifetime 
always. If these packets are snooped by a hacker he can reply to these packets 
and they can send legitimate packets which are actually not.  

  According to https://tools.ietf.org/search/rfc4862, page 19:
  "The above rules address a specific denial-of-service attack in which a bogus 
advertisement could contain prefixes with very small Valid Lifetimes.  Without 
the above rules, a single unauthenticated advertisement containing bogus Prefix 
Information options with short Valid Lifetimes could cause all of a node's 
addresses to expire prematurely.  The above rules ensure that legitimate 
advertisements (which are sent periodically) will "cancel" the short Valid 
Lifetimes before they actually take effect."

  Other notes:
  - 2 test cases pass without NetworkManager.
  - Tested with different Linux Desktop Distributions, as long as 
NetworkManager is running, those DAD test cases fail.

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

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

[Touch-packages] [Bug 1797324] Re: Software Updater show empty panels, stuck in ProblemResolver.resolve of apt_pkg.cpython-36m-x86_64-linux-gnu.so

2018-10-11 Thread  Christian Ehrhardt 

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

Our last ideas were around:
- one process waiting on the GIL, but not getting it (deadlock)
- the thread that would update the package list (resolver) dying which would 
leave the GTK/Ui 
  threads spinning (as we see them), but never populate the objects to be 
displayed.
  I see plenty of processes get created and die, but no clear point to fix.
  Many of them end with:
0.000126 futex(0x7fbc78003160, FUTEX_WAIT_PRIVATE, 0, {tv_sec=14, 
tv_nsec=99129}) = -1 ETIMEDOUT (Connection timed out) <15.000111>
0.795429 madvise(0x7fbc69a07000, 8368128, MADV_DONTNEED) = 0 <0.17> 
0.49 exit(0)   = ?
  But I have not found a link what they actually try to get before they die 
(they don't do much 
  more)

But the debug data wasn't strong enough for either to further debug or
try a fix.

I was trying rbalints fix from [1] where I put it.
And even thou the sytmptom was rather different IMHO it resolved the issue.

Marking as a Dup

[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3472

** This bug has been marked a duplicate of bug 1795898
   TypeError: _action_done() got an unexpected keyword argument 'trans_failed'

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

Title:
  Software Updater show empty panels, stuck in ProblemResolver.resolve
  of apt_pkg.cpython-36m-x86_64-linux-gnu.so

Status in python-apt package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  I just happened to see that Software Updater popped up with an actually empty 
window:
  1. nothing in "install or remove"
  2. obviously no details for changes/descriptions

  But at the same time it says "26.3 MB will be downloaded"
  I'll attach a screenshot of that to show what I mean.

  At the same time there are upgradable packages:
  $ apt list --upgradable
  Listing... Done
  apturl/bionic-updates 0.5.2ubuntu14.2 amd64 [upgradable from: 0.5.2ubuntu14]
  apturl-common/bionic-updates 0.5.2ubuntu14.2 amd64 [upgradable from: 
0.5.2ubuntu14]
  flashplugin-installer/bionic-updates,bionic-security 
31.0.0.122ubuntu0.18.04.1 amd64 [upgradable from: 31.0.0.108ubuntu0.18.04.1]
  gir1.2-javascriptcoregtk-4.0/bionic-updates,bionic-security 
2.22.2-0ubuntu0.18.04.2 amd64 [upgradable from: 2.22.2-0ubuntu0.18.04.1]
  [...]

  And that matches the 26.3MB
  $ sudo apt upgrade
  [...]
  22 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 26,3 MB of archives.

  
  I can restart it to get the same symptom, done in console one indicator of a 
problem is:
  $ /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map
  Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check 
your Internet connection or proxy settings

  Also https://changelogs.ubuntu.com/meta-release-lts is reachable for
  me.

  But even if it would be not reachable, why then "26.3MB will be
  downloaded" - it seems to know some things?

  I'd either expect a user visible error (UI) or listing the packages apt knows 
about to upgrade.
  But not "nothing"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: update-manager 1:18.04.11.5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.4
  Aptdaemon:
   
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 09:36:19 2018
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'625'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'645'
   b'com.ubuntu.update-manager' b'launch-time' b'int64 1539243337'
  InstallationDate: Installed on 2016-02-19 (964 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: update-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (160 days ago)

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-10-11 Thread Tomasz Przybył

Also affected Asus VivoBook R542UF

```
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook 15_ASUS Laptop X542UF 
  v: 1.0 serial:  
  Mobo: ASUSTeK model: X542UF v: 1.0 serial:  
  UEFI: American Megatrends v: X542UF.303 date: 03/15/2018 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 
  Sound Server: ALSA Kernel: 4.19
```
```
aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
```
Dmesg parts
```
[   12.342528] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   12.342531] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   12.342533] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   12.342535] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   12.342536] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   12.342538] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1b
```
```
[   12.634171] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input18
[   12.634389] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input19
[   12.634563] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input20
[   12.634737] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
[   12.634905] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
[   12.635045] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
```

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

2018-10-11 Thread Łukasz Zemczak

Ok, I also re-read Daniel's comment and I see that he mentioned it
working on the previous upload. This really seems like a regression -
for the time being let's mark this verification-failed-bionic so that no
one accidentally releases it to -updates.

** Tags removed: verification-done-bionic
** Tags added: verification-failed-bionic

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # 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}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link

[Touch-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries

2018-10-11 Thread john smith

Bluetooth is one of the best technology to share a data, image, song,
picture to one device with another device.

if anyone faces Microsoft Outlook click here
https://www.outlooktechnicalsupportnumbers.com/blog/microsoft-outlook-
not-implemented/

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

Title:
  Treats bluetooth input device batteries as batteries

Status in gnome-power-manager package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-power-manager source package in Precise:
  Invalid
Status in upower source package in Precise:
  Fix Released
Status in gnome-power-manager source package in Quantal:
  Invalid
Status in upower source package in Quantal:
  Won't Fix
Status in gnome-power-manager source package in Raring:
  Invalid
Status in upower source package in Raring:
  Fix Released
Status in gnome-power-manager source package in Saucy:
  Invalid
Status in upower source package in Saucy:
  Fix Released

Bug description:
  [Impact]

   * There are many Bluetooth devices with battery information inside.
  When they are treated as system battery, it will make the system
  poweroff/suspend/hibernate when some Bluetooth device has critical low
  battery. It is a very annoying behavior for the users. Originally,
  there is no such Bluetooth battery information until Ubuntu 12.04
  brings linux-quantal-lts and linux-raring-lts, so those linux kernels
  also bring this issue.

  [Test Case]

   * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple 
Wireless Keyboard.
   * Click the power indicator and you can find Apple Wireless Mouse is listed 
as system battery, and there is no Apple Wireless Keyboard. If you open 
gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse 
is 'Yes' but it should not be.

  [Regression Potential]

   * There is no obvious regression as I know.

  [Other Info]

   * Most patches are from upstream, modified to fix the conflicts, and made by 
the same developer (i.e. fourdollars).
   * We need another patch from 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2
 to make Apple Wireless Keyboard showing.

  [Original Bug Description]

  This is a weird one... the system is an HP Pavilion 23 All In One and
  is powered by a large power supply brick.

  I currently have an Apple Magic Mouse connected via Bluetooth.  As
  soon as the mouse is connected, the Battery indicator shows up and
  clicking on that shows that the system is reading my mouse as a
  battery!

  See the attached screen shot for what I see in the Power status.

  Looking at hcitool:
  ubuntu@201206-11396:~$ hcitool dev
  Devices:
   hci0 9C:B7:0D:80:71:DB

  To make matters even more weird, I actually observed the battery
  indicator go from full to "Critically Low" and the system suspended
  itself.  Keep in mind, again, that this system has NO battery, it's
  reading my bluetooth mouse as a battery device.

  I disconnected the magic mouse and the battery indicator went to Empty
  Red outline and status showed Battery Disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: wl fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1726 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16'
     Mixer name : 'Realtek ALC269VC'
     Components : 'HDA:10ec0269,103c2aee,00100202'
     Controls  : 21
     Simple ctrls  : 10
  Date: Mon Mar 11 03:54:36 2013
  HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MachineType: Hewlett-Packard a654
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-23-generic N/A

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

2018-10-11 Thread Marcos

Just confirmed the regression... It's working as expected on boot, but is 
renaming to the "ID" key, instead of the "set-name" when live.
E.g. if we have:
ens0p3:
match:
macaddress: 01:02:03:04:05:06
set-name: eth0
It will be renamed to ens0p3 on netplan apply.
eth0:
match:
macaddress: 01:02:03:04:05:06
set-name: ens0p3
It will be renamed to eth0...

So basically, on boot it picks up "set-name", and afterwards it picks
the ID. If you keep both equal, no problem, but if have different "ID"
and "set-name"...

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # 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}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6

[Touch-packages] [Bug 1797324] Re: Software Updater show empty panels, stuck in ProblemResolver.resolve of apt_pkg.cpython-36m-x86_64-linux-gnu.so

2018-10-11 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Software Updater show empty panels, stuck in ProblemResolver.resolve
  of apt_pkg.cpython-36m-x86_64-linux-gnu.so

Status in python-apt package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  I just happened to see that Software Updater popped up with an actually empty 
window:
  1. nothing in "install or remove"
  2. obviously no details for changes/descriptions

  But at the same time it says "26.3 MB will be downloaded"
  I'll attach a screenshot of that to show what I mean.

  At the same time there are upgradable packages:
  $ apt list --upgradable
  Listing... Done
  apturl/bionic-updates 0.5.2ubuntu14.2 amd64 [upgradable from: 0.5.2ubuntu14]
  apturl-common/bionic-updates 0.5.2ubuntu14.2 amd64 [upgradable from: 
0.5.2ubuntu14]
  flashplugin-installer/bionic-updates,bionic-security 
31.0.0.122ubuntu0.18.04.1 amd64 [upgradable from: 31.0.0.108ubuntu0.18.04.1]
  gir1.2-javascriptcoregtk-4.0/bionic-updates,bionic-security 
2.22.2-0ubuntu0.18.04.2 amd64 [upgradable from: 2.22.2-0ubuntu0.18.04.1]
  [...]

  And that matches the 26.3MB
  $ sudo apt upgrade
  [...]
  22 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 26,3 MB of archives.

  
  I can restart it to get the same symptom, done in console one indicator of a 
problem is:
  $ /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map
  Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check 
your Internet connection or proxy settings

  Also https://changelogs.ubuntu.com/meta-release-lts is reachable for
  me.

  But even if it would be not reachable, why then "26.3MB will be
  downloaded" - it seems to know some things?

  I'd either expect a user visible error (UI) or listing the packages apt knows 
about to upgrade.
  But not "nothing"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: update-manager 1:18.04.11.5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.4
  Aptdaemon:
   
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 09:36:19 2018
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'625'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'645'
   b'com.ubuntu.update-manager' b'launch-time' b'int64 1539243337'
  InstallationDate: Installed on 2016-02-19 (964 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: update-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (160 days ago)

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

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

[Touch-packages] [Bug 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic

Confirming that todays pending ISO boots correctly on Vbox.

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

Title:
  Desktop live cd boots corrupted screen in Virtualbox on Bionic

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Fix Released
Status in xorg-server source package in Cosmic:
  Confirmed

Bug description:
  On a Bionic host running the standard archive version of Virtualbox
  and the daily ISO of Cosmic, the live session starts with a corrupted
  graphical display, as can be seen here:

  https://imgur.com/a/rkTId4S

  (also attached)

  Switching VTs to 2 and back to 1 clears the display and things work
  again.

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

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

[Touch-packages] [Bug 1610479] Re: interface-order needs definitions for systemd predictable names

2018-10-11 Thread Suho Meso

Hi,

I've an issue using resolvconf in combination with rdnssd. The host is getting 
the nameserver stuff via RDNSS, not DHCPv6.
The interface order doesn't cover the rdnssd method?! Interface name should be 
ens3.

/run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::47
/run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::48
/run/resolvconf/interface/ens3.dhclient:domain abz.com
/run/resolvconf/interface/ens3.dhclient:search abz.com
/run/resolvconf/interface/ens3.dhclient:nameserver 10.x.x.47


root@host:/etc/resolvconf# cat /etc/network/interfaces
# Interface lo
auto lo
iface lo inet loopback
# Interface lo_ipv6
iface lo inet6 loopback
# Interface ens3
auto ens3
iface ens3 inet dhcp
# Interface ens3_ipv6
iface ens3 inet6 auto

root@host:/etc/resolvconf# dpkg -l | grep resolvconf
ii  resolvconf  1.78ubuntu6 
   all  name server information handler
root@host:/etc/resolvconf# dpkg -l | grep rdnssd
ii  rdnssd  1.0.1-1ubuntu2  
   amd64IPv6 recursive DNS server discovery daemo

root@host:/etc/resolvconf# cat /etc/issue
Ubuntu 16.04.4 LTS \n \l

root@host:/etc/resolvconf# uname -a
Linux ermscn01 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  interface-order needs definitions for systemd predictable names

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  Another release, another round of interface name changes.

  This time systemd has gotten into the fray to make things even more
  interesting.

  
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

  As such, IPv4 resolvers are now being preferred over IPv6 again on
  these new interface names.

  kjotte@flounder:~$ grep '' /run/resolvconf/interface/ens3.*
  /run/resolvconf/interface/ens3.dhclient:search nivex.lan.
  /run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30
  /run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net.
  /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10
  /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug  5 19:53:25 2016
  InstallationDate: Installed on 2016-08-04 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version

2018-10-11 Thread Matthias Klumpp

We don't actively kill PackageKit when updating it, we just tell the daemon to 
quit itself as soon as possible if it can do so.
Also, a packagekitd times out automatically when inactive.
So this crash really shouldn't happen...

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

Title:
  Regression: packagekit crashes updating itself to a new version

Status in packagekit package in Ubuntu:
  Triaged
Status in plasma-discover package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Triaged
Status in plasma-discover source package in Bionic:
  Confirmed

Bug description:
  Bionic: 18.04
  Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1

  Updating with pkcon upgrade or plasma-discover crashes packagekit mid
  transaction, requiring user intervention on the command line.

  In plasma-discover the gui reports the crash briefly, but then stalls
  in apparent mid update, requiring the user to force close it and again
  resolve the issue on the command line.

  Example transactions:

  $ pkcon update
  Getting updates   [=] 
  Finished  [=] 
  Loading cache [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be updated:
   gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection 
data for the PackageKit GLib library
   libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing 
PackageKit using GLib
   packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management 
service
   packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64  Provides PackageKit 
command-line tools
  Proceed with changes? [N/y] y

[=] 
  Updating packages [=] 
  Waiting for authentication[=] 
  Loading cache [=] 
  Running   [=] 
  Installing packages   [ ] (80%)  The daemon 
crashed mid-transaction!

  $ sudo apt-get upgrade 
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  and obviously after that doing anything meaningful with packagekit
  like installing a package fails

  $pkcon install kaffeine
  Resolving [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be installed:
   kaffeine-2.0.14-1.amd64versatile media player for KDE
  Proceed with changes? [N/y] y

[=] 
  Installing[=] 
  Waiting for authentication[=] 
  Waiting for package manager lock[=] 
  Finished  [=] 
  Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure 
-a' to correct the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-26 (69 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: packagekit 1.1.9-1ubuntu2.18.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version

I don't think there is a solution for this problem. We can stop
restarting packagekit to fix the crash, but then you end up with old
packagekitd's running. So if there is a security update in packagekit or
one of its libraries, it would not take effect. Not sure how to fix this
properly.

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

Title:
  Regression: packagekit crashes updating itself to a new version

Status in packagekit package in Ubuntu:
  Triaged
Status in plasma-discover package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Triaged
Status in plasma-discover source package in Bionic:
  Confirmed

Bug description:
  Bionic: 18.04
  Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1

  Updating with pkcon upgrade or plasma-discover crashes packagekit mid
  transaction, requiring user intervention on the command line.

  In plasma-discover the gui reports the crash briefly, but then stalls
  in apparent mid update, requiring the user to force close it and again
  resolve the issue on the command line.

  Example transactions:

  $ pkcon update
  Getting updates   [=] 
  Finished  [=] 
  Loading cache [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be updated:
   gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection 
data for the PackageKit GLib library
   libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing 
PackageKit using GLib
   packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management 
service
   packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64  Provides PackageKit 
command-line tools
  Proceed with changes? [N/y] y

[=] 
  Updating packages [=] 
  Waiting for authentication[=] 
  Loading cache [=] 
  Running   [=] 
  Installing packages   [ ] (80%)  The daemon 
crashed mid-transaction!

  $ sudo apt-get upgrade 
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  and obviously after that doing anything meaningful with packagekit
  like installing a package fails

  $pkcon install kaffeine
  Resolving [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be installed:
   kaffeine-2.0.14-1.amd64versatile media player for KDE
  Proceed with changes? [N/y] y

[=] 
  Installing[=] 
  Waiting for authentication[=] 
  Waiting for package manager lock[=] 
  Finished  [=] 
  Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure 
-a' to correct the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-26 (69 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: packagekit 1.1.9-1ubuntu2.18.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1797324] Re: Software Updater show empty panels, stuck in ProblemResolver.resolve of apt_pkg.cpython-36m-x86_64-linux-gnu.so

Could you please check if this is a duplicate of LP: #1795898 and give a
try to u-m in bionic Unapproved to fix it?

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

Title:
  Software Updater show empty panels, stuck in ProblemResolver.resolve
  of apt_pkg.cpython-36m-x86_64-linux-gnu.so

Status in python-apt package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  I just happened to see that Software Updater popped up with an actually empty 
window:
  1. nothing in "install or remove"
  2. obviously no details for changes/descriptions

  But at the same time it says "26.3 MB will be downloaded"
  I'll attach a screenshot of that to show what I mean.

  At the same time there are upgradable packages:
  $ apt list --upgradable
  Listing... Done
  apturl/bionic-updates 0.5.2ubuntu14.2 amd64 [upgradable from: 0.5.2ubuntu14]
  apturl-common/bionic-updates 0.5.2ubuntu14.2 amd64 [upgradable from: 
0.5.2ubuntu14]
  flashplugin-installer/bionic-updates,bionic-security 
31.0.0.122ubuntu0.18.04.1 amd64 [upgradable from: 31.0.0.108ubuntu0.18.04.1]
  gir1.2-javascriptcoregtk-4.0/bionic-updates,bionic-security 
2.22.2-0ubuntu0.18.04.2 amd64 [upgradable from: 2.22.2-0ubuntu0.18.04.1]
  [...]

  And that matches the 26.3MB
  $ sudo apt upgrade
  [...]
  22 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 26,3 MB of archives.

  
  I can restart it to get the same symptom, done in console one indicator of a 
problem is:
  $ /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map
  Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check 
your Internet connection or proxy settings

  Also https://changelogs.ubuntu.com/meta-release-lts is reachable for
  me.

  But even if it would be not reachable, why then "26.3MB will be
  downloaded" - it seems to know some things?

  I'd either expect a user visible error (UI) or listing the packages apt knows 
about to upgrade.
  But not "nothing"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: update-manager 1:18.04.11.5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.4
  Aptdaemon:
   
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 09:36:19 2018
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'625'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'645'
   b'com.ubuntu.update-manager' b'launch-time' b'int64 1539243337'
  InstallationDate: Installed on 2016-02-19 (964 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: update-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (160 days ago)

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

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

[Touch-packages] [Bug 1797324] Re: Software Updater show empty panels, stuck in ProblemResolver.resolve of apt_pkg.cpython-36m-x86_64-linux-gnu.so

2018-10-11 Thread  Christian Ehrhardt 

The chaining of python -> cc -> pytohn -> cc code here let me fail to follow it.
It seemed like a loop between python/depcache.cc and cache.py, but that might 
only be my lack of understanding of how this was architectured.
But due to that I wasn't able to debug further and would let it up to you to go 
on on this.

I'll give the upload rbalint mentioned a try, but it doesn't feel to be
the same thing ...

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

Title:
  Software Updater show empty panels, stuck in ProblemResolver.resolve
  of apt_pkg.cpython-36m-x86_64-linux-gnu.so

Status in python-apt package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  I just happened to see that Software Updater popped up with an actually empty 
window:
  1. nothing in "install or remove"
  2. obviously no details for changes/descriptions

  But at the same time it says "26.3 MB will be downloaded"
  I'll attach a screenshot of that to show what I mean.

  At the same time there are upgradable packages:
  $ apt list --upgradable
  Listing... Done
  apturl/bionic-updates 0.5.2ubuntu14.2 amd64 [upgradable from: 0.5.2ubuntu14]
  apturl-common/bionic-updates 0.5.2ubuntu14.2 amd64 [upgradable from: 
0.5.2ubuntu14]
  flashplugin-installer/bionic-updates,bionic-security 
31.0.0.122ubuntu0.18.04.1 amd64 [upgradable from: 31.0.0.108ubuntu0.18.04.1]
  gir1.2-javascriptcoregtk-4.0/bionic-updates,bionic-security 
2.22.2-0ubuntu0.18.04.2 amd64 [upgradable from: 2.22.2-0ubuntu0.18.04.1]
  [...]

  And that matches the 26.3MB
  $ sudo apt upgrade
  [...]
  22 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 26,3 MB of archives.

  
  I can restart it to get the same symptom, done in console one indicator of a 
problem is:
  $ /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map
  Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check 
your Internet connection or proxy settings

  Also https://changelogs.ubuntu.com/meta-release-lts is reachable for
  me.

  But even if it would be not reachable, why then "26.3MB will be
  downloaded" - it seems to know some things?

  I'd either expect a user visible error (UI) or listing the packages apt knows 
about to upgrade.
  But not "nothing"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: update-manager 1:18.04.11.5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.4
  Aptdaemon:
   
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 09:36:19 2018
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'625'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'645'
   b'com.ubuntu.update-manager' b'launch-time' b'int64 1539243337'
  InstallationDate: Installed on 2016-02-19 (964 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: update-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (160 days ago)

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

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

[Touch-packages] [Bug 1794843] Re: New release of 'gstreamer1.0' (1.14.4)

** Changed in: gstreamer1.0 (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 gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1794843

Title:
  New release of 'gstreamer1.0' (1.14.4)

Status in gstreamer1.0 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  https://packages.debian.org/source/sid/gstreamer1.0

  'Source Package: gstreamer1.0 (1.14.3-1)'

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ---

  https://gstreamer.freedesktop.org/releases/1.14/#1.14.3

  == 1.14.3 ==

  The third 1.14 bug-fix release (1.14.3) was released on 16 September
  2018.

  This release only contains bugfixes and it should be safe to update
  from 1.14.x.

  Highlighted bugfixes in 1.14.3
  opusenc: fix crash on 32-bit platforms
  compositor: fix major buffer leak when doing crossfading on some but not all 
pads
  wasapi: various fixes for wasapisrc and wasapisink regressions
  x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. 
Rebuild to..." runtime errors with x264 version ≥ 153
  audioaggregator, audiomixer: caps negotiation fixes
  input-selector: latency handling fixes
  playbin, playsink: audio visualization support fixes
  dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand 
profile
  opencv: Fix build for opencv >= 3.4.2
  h265parse: miscellaneous fixes backported from h264parse
  pads: fix changing of pad offsets from inside pad probes
  pads: ensure that pads are blocked for IDLE probes if they are called from 
the streaming thread too

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.2-2
  Uname: Linux 4.18.10-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 27 13:43:05 2018
  InstallationDate: Installed on 2017-10-13 (349 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

2018-10-11 Thread Łukasz Zemczak

So the bug here is about renaming interfaces on boot and this seems to
be resolved by the new upload. Does this regress previous behavior? Did
renaming interfaces on a running system work in the previous version and
this upload introduces a regression? If not, we should fill in a
separate bug and try getting it fixed with the next upload.

Will be waiting with releasing this package until it's clear what's the
situation here.

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # 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}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3

[Touch-packages] [Bug 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk

Spoke to upstream.  They will look in to this and get it fixed.  I've
asked David to log it upstream and we can link to that here.

We should look at backport the fixes and SRUing to Bionic.

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

Title:
  NetworkManager IPv6 DAD lifetime behavior introduce security risk

Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:
  When performing IPv6 certification test, two DAD test cases (3.2.5c and d) 
check the remaining lifetime feature of the IPv6 packets.  The Network trace 
shows that the remaining lifetime becomes infinite when running these test 
cases.  Hence when running in IPv6 environment with Network Manager enabled, 
there is a risk of packets travelling in network which has valid lifetime 
always. If these packets are snooped by a hacker he can reply to these packets 
and they can send legitimate packets which are actually not.  

  According to https://tools.ietf.org/search/rfc4862, page 19:
  "The above rules address a specific denial-of-service attack in which a bogus 
advertisement could contain prefixes with very small Valid Lifetimes.  Without 
the above rules, a single unauthenticated advertisement containing bogus Prefix 
Information options with short Valid Lifetimes could cause all of a node's 
addresses to expire prematurely.  The above rules ensure that legitimate 
advertisements (which are sent periodically) will "cancel" the short Valid 
Lifetimes before they actually take effect."

  Other notes:
  - 2 test cases pass without NetworkManager.
  - Tested with different Linux Desktop Distributions, as long as 
NetworkManager is running, those DAD test cases fail.

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

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

[Touch-packages] [Bug 1574746] Re: Enable support for libsoxr

2018-10-11 Thread Lastique

Yay, finally! Thank you Daniel.

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

Title:
  Enable support for libsoxr

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I'd like to ask to enable support for libsoxr-based resamplers in the 
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr 
and automatically detects its availability, so the only change really needed is 
to add the build dependency to debian/control.
   
  The resamplers based in libsoxr offer better quality and better performace 
while introducing more delay compared to the speex resamplers that are used by 
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu 
16.04 but unfortunately are not enabled at build time ('pulseaudio 
--dump-resample-methods' doesn't list them). I've built local packages with 
libsoxr and verified that the resampler works as expected.

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

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

[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version

2018-10-11 Thread Gordon Lack

>> I don't think there is a solution for this problem.

So why has it only started to happen recently?

What about treating it like a kernel update - don't restart the process
but schedule/request a reboot?

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

Title:
  Regression: packagekit crashes updating itself to a new version

Status in packagekit package in Ubuntu:
  Triaged
Status in plasma-discover package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Triaged
Status in plasma-discover source package in Bionic:
  Confirmed

Bug description:
  Bionic: 18.04
  Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1

  Updating with pkcon upgrade or plasma-discover crashes packagekit mid
  transaction, requiring user intervention on the command line.

  In plasma-discover the gui reports the crash briefly, but then stalls
  in apparent mid update, requiring the user to force close it and again
  resolve the issue on the command line.

  Example transactions:

  $ pkcon update
  Getting updates   [=] 
  Finished  [=] 
  Loading cache [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be updated:
   gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection 
data for the PackageKit GLib library
   libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing 
PackageKit using GLib
   packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management 
service
   packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64  Provides PackageKit 
command-line tools
  Proceed with changes? [N/y] y

[=] 
  Updating packages [=] 
  Waiting for authentication[=] 
  Loading cache [=] 
  Running   [=] 
  Installing packages   [ ] (80%)  The daemon 
crashed mid-transaction!

  $ sudo apt-get upgrade 
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  and obviously after that doing anything meaningful with packagekit
  like installing a package fails

  $pkcon install kaffeine
  Resolving [=] 
  Testing changes   [=] 
  Finished  [ ] (0%)  
  The following packages have to be installed:
   kaffeine-2.0.14-1.amd64versatile media player for KDE
  Proceed with changes? [N/y] y

[=] 
  Installing[=] 
  Waiting for authentication[=] 
  Waiting for package manager lock[=] 
  Finished  [=] 
  Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure 
-a' to correct the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-26 (69 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: packagekit 1.1.9-1ubuntu2.18.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1797349] Re: GPU hang, full freeze / lockup

2018-10-11 Thread Daniel van Vugt

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

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

Title:
  GPU hang, full freeze / lockup

Status in linux package in Ubuntu:
  New

Bug description:
  Oct 11 10:48:38 L-UXX0MPSM3 kernel: [10459.830646] [drm] GPU HANG: ecode 
9:0:0x85db, in Xorg [1101], reason: Hang on rcs0, action: reset
  Oct 11 10:48:38 L-UXX0MPSM3 kernel: [10459.830652] i915 :00:02.0: 
Resetting rcs0 after gpu hang
  Oct 11 10:48:39 L-UXX0MPSM3 kernel: [10460.844423] asynchronous wait on fence 
i915:kwin_x11[2217]/1:2888a timed out
  Oct 11 10:48:39 L-UXX0MPSM3 ntpd[2505]: Soliciting pool server 91.121.7.182
  Oct 11 10:48:40 L-UXX0MPSM3 ntpd[2505]: Soliciting pool server 129.250.35.251
  Oct 11 10:48:46 L-UXX0MPSM3 kernel: [10467.788461] i915 :00:02.0: 
Resetting rcs0 after gpu hang
  Oct 11 10:48:54 L-UXX0MPSM3 kernel: [10475.756465] i915 :00:02.0: 
Resetting rcs0 after gpu hang
  Oct 11 10:49:02 L-UXX0MPSM3 kernel: [10483.756405] i915 :00:02.0: 
Resetting rcs0 after gpu hang
  Oct 11 10:49:02 L-UXX0MPSM3 systemd[1]: Started Getty on tty6.
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Received SIGINT.
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Timers.
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Sound Card.
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily apt upgrade and clean 
activities.
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Disk Manager...
  Oct 11 10:49:04 L-UXX0MPSM3 obexd[2425]: Terminating
  Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Authentication error: "Process 
crashed"
  Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Auth: sddm-helper crashed (exit code 
15)
  Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Authentication error: "Process 
crashed"
  Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Auth: sddm-helper exited with 15
  Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Socket server stopping...
  Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Socket server stopped.
  Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Display server stopping...
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Session 2 of user manu.
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily Cleanup of Temporary 
Directories.
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Closed Load/Save RF Kill Switch 
Status /dev/rfkill Watch.
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Daemon for power 
management...
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily apt download activities.
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Daemon for generating 
UUIDs...
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping User Manager for UID 1002...
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Stop ureadahead data 
collection 45s after completed startup.
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Authenticate and Authorize 
Users to Run Privileged Tasks...
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping ACPI event daemon...
  Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Graphical Interface.
  Oct 11 10:49:04 L-UXX0MPSM3 rsyslogd: [origin software="rsyslogd" 
swVersion="8.16.0" x-pid="870" x-info="http://www.rsyslog.com;] exiting on 
signal 15.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Oct 11 10:52:40 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:5062]
  InstallationDate: Installed on 2018-04-20 (173 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20K5S0T200
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET36W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20K5S0T200
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET36W(1.14):bd05/02/2017:svnLENOVO:pn20K5S0T200:pvrThinkPadX270W10DG:rvnLENOVO:rn20K5S0T200:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-10-11 Thread Thomas

Also affects me (ASUS Zenbook UX931U)

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1797349] [NEW] GPU hang, full freeze / lockup

2018-10-11 Thread Manuel López-Ibáñez

Public bug reported:

Oct 11 10:48:38 L-UXX0MPSM3 kernel: [10459.830646] [drm] GPU HANG: ecode 
9:0:0x85db, in Xorg [1101], reason: Hang on rcs0, action: reset
Oct 11 10:48:38 L-UXX0MPSM3 kernel: [10459.830652] i915 :00:02.0: Resetting 
rcs0 after gpu hang
Oct 11 10:48:39 L-UXX0MPSM3 kernel: [10460.844423] asynchronous wait on fence 
i915:kwin_x11[2217]/1:2888a timed out
Oct 11 10:48:39 L-UXX0MPSM3 ntpd[2505]: Soliciting pool server 91.121.7.182
Oct 11 10:48:40 L-UXX0MPSM3 ntpd[2505]: Soliciting pool server 129.250.35.251
Oct 11 10:48:46 L-UXX0MPSM3 kernel: [10467.788461] i915 :00:02.0: Resetting 
rcs0 after gpu hang
Oct 11 10:48:54 L-UXX0MPSM3 kernel: [10475.756465] i915 :00:02.0: Resetting 
rcs0 after gpu hang
Oct 11 10:49:02 L-UXX0MPSM3 kernel: [10483.756405] i915 :00:02.0: Resetting 
rcs0 after gpu hang
Oct 11 10:49:02 L-UXX0MPSM3 systemd[1]: Started Getty on tty6.
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Received SIGINT.
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Timers.
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Sound Card.
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily apt upgrade and clean 
activities.
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Disk Manager...
Oct 11 10:49:04 L-UXX0MPSM3 obexd[2425]: Terminating
Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Authentication error: "Process crashed"
Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Auth: sddm-helper crashed (exit code 15)
Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Authentication error: "Process crashed"
Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Auth: sddm-helper exited with 15
Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Socket server stopping...
Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Socket server stopped.
Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Display server stopping...
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Session 2 of user manu.
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily Cleanup of Temporary 
Directories.
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Closed Load/Save RF Kill Switch Status 
/dev/rfkill Watch.
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Daemon for power management...
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily apt download activities.
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Daemon for generating UUIDs...
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping User Manager for UID 1002...
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Stop ureadahead data collection 
45s after completed startup.
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Authenticate and Authorize 
Users to Run Privileged Tasks...
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping ACPI event daemon...
Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Graphical Interface.
Oct 11 10:49:04 L-UXX0MPSM3 rsyslogd: [origin software="rsyslogd" 
swVersion="8.16.0" x-pid="870" x-info="http://www.rsyslog.com;] exiting on 
signal 15.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Oct 11 10:52:40 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: kubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:5062]
InstallationDate: Installed on 2018-04-20 (173 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: LENOVO 20K5S0T200
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/02/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R0IET36W (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20K5S0T200
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET36W(1.14):bd05/02/2017:svnLENOVO:pn20K5S0T200:pvrThinkPadX270W10DG:rvnLENOVO:rn20K5S0T200:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X270 W10DG
dmi.product.name: 20K5S0T200
dmi.product.version: ThinkPad X270 W10DG
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core:

[Touch-packages] [Bug 1685484] Re: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work