[Touch-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu

[jean-marc]

The latest patch does work when you realize that the skb_put function
has recently changed from (unsigned char*) to (void *) ( see
https://patchwork.ozlabs.org/patch/776580/ for fix).

The lines where appears "*skb_put" need to be changed to "*(u8
*)skb_put". This was enough for me to get my bluetooth adapter to work
(MSI GS60 6QC). This may not be the best way but I am not a competent
programmer

Thanks for the package !

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

Title:
  Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since some Versions of Linux Kernel and Ubuntu Releases this problem
  exists.

  I am now running ubuntu 16.04 prerelease and still have the same
  problem.

  Bluetooth does not work with the atheros device on  msi gt 72 2qd
  notebook.

  WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4:

  sudo apt install dkms
  wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb
  sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb

  FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS

  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files
  /btusb-lp1542743-dkms_0.2~4.8_all.deb

  dmesg | grep Bluetooth:
  [2.655360] Bluetooth: Core ver 2.21
  [2.655373] Bluetooth: HCI device and connection manager initialized
  [2.655377] Bluetooth: HCI socket layer initialized
  [2.655379] Bluetooth: L2CAP socket layer initialized
  [2.655385] Bluetooth: SCO socket layer initialized
  [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.612794] Bluetooth: BNEP filters: protocol multicast
  [6.612798] Bluetooth: BNEP socket layer initialized
  [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
  [9.016882] Bluetooth: Loading patch file failed

  hwinfo | grep Bluetooth:
  <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    <6>[6.612794] Bluetooth: BNEP filters: protocol multicast
    <6>[6.612798] Bluetooth: BNEP socket layer initialized
    <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
    <3>[9.016882] Bluetooth: Loading patch file failed
  60: USB 00.0: 11500 Bluetooth Device
    Model: "Atheros AR3012 Bluetooth 4.0"
    Device: usb 0x3004 "AR3012 Bluetooth 4.0"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.36-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  7 00:38:04 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-10-24 (105 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. GT72 2QD
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10I:bd12/19/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QD:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QD
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

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

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

[Touch-packages] [Bug 1732612] [NEW] Alt+Printscreen not working (doesn't generate keypress event)

[manfreed]

Public bug reported:

Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my
computer. I'm using Unity DE, with default settings.

The problem is not about taking screnshots.

xev recognizes when I press down the alt key, but nothing happens when I
press Print Screen with alt being pressed (it does when PrintScreen is
pressed by itself)

Here is evtest output when I press Alt+Printscreen:

# Alt pressed down:
Event: time 1510817663.883489, -- SYN_REPORT 
Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
Event: time 1510817663.923476, -- SYN_REPORT 
Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
Event: time 1510817663.963479, -- SYN_REPORT 
Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

# Print screen pressed
Event: time 1510817663.993036, -- SYN_REPORT 
Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

# Alt released
Event: time 1510817664.945032, -- SYN_REPORT 
Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
Event: time 1510817664.945086, -- SYN_REPORT 
Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
Event: time 1510817664.945097, -- SYN_REPORT 

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: udev 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
Date: Thu Nov 16 08:29:46 2017
InstallationDate: Installed on 2017-03-26 (234 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
dmi.bios.date: 10/24/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77-HD3
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.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.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.

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


** Tags: amd64 apport-bug artful

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  New

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- 

[Touch-packages] [Bug 1729892] Re: pango 1.40.13 word break regression

[Bug Watch Updater]

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

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

Title:
  pango 1.40.13 word break regression

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 package in Debian:
  Fix Released

Bug description:
  See upstream bug.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732544] Re: package perl-modules-5.22 5.22.1-9 failed to install/upgrade: не удалось скопировать извлечённые данные «./usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm» в «/

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

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

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

Title:
  package perl-modules-5.22 5.22.1-9 failed to install/upgrade: не
  удалось скопировать извлечённые данные
  «./usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm» в
  «/usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm.dpkg-new»:
  неожиданный конец файла или потока

Status in perl package in Ubuntu:
  Invalid

Bug description:
  Я не знаю

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: perl-modules-5.22 5.22.1-9ubuntu0.2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Nov 16 00:40:57 2017
  ErrorMessage: не удалось скопировать извлечённые данные 
«./usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm» в 
«/usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm.dpkg-new»: неожиданный 
конец файла или потока
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: perl
  Title: package perl-modules-5.22 5.22.1-9 failed to install/upgrade: не 
удалось скопировать извлечённые данные 
«./usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm» в 
«/usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm.dpkg-new»: неожиданный 
конец файла или потока
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Tyler Hicks]

Sigh... Thanks for being patient with me on that. I think my brain just
wrote everything at the top of main() off as setting up the namespace
for some reason. That's embarrassing... :)

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732566] Re: Update request: protobuf-compiler

[Bug Watch Updater]

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

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

Title:
  Update request: protobuf-compiler

Status in protobuf package in Ubuntu:
  New
Status in protobuf package in Debian:
  New

Bug description:
  Please can you update the protobuf-compiler package to something
  fairly recent in the 3.x.x series.

  (a) backport >=3.5.x to Xenial for LTS, (currently 2.6.0)
  (b) update Atomic/Bionic (currently 3.0.0, which is vintage 2016)

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

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

[Touch-packages] [Bug 1726372] Re: Multiple security issues in Apport

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.8-0ubuntu1

---
apport (2.20.8-0ubuntu1) bionic; urgency=medium

   * New upstream release:
 - SECURITY UPDATE: Denial of service via resource exhaustion and
   privilege escalation when handling crashes of tainted processes.
 - When /proc/sys/fs/suid_dumpable is set to 2, do not assume that
   the user and group owning the /proc//stat file is the same
   owner and group that started the process. Rather check the dump
   mode of the crashed process and do not write a core file if its
   value is 2. Thanks to Sander Bos for discovering this issue!
   (CVE-2017-14177, LP: #1726372)
 - SECURITY UPDATE: Denial of service via resource exhaustion,
   privilege escalation, and possible container escape when handling
   crashes of processes inside PID namespaces.
 - Change the method for determining if a crash is from a container
   so that there are no false positives from software using PID
   namespaces. Additionally, disable container crash forwarding by
   ignoring crashes that occur in a PID namespace. This functionality
   may be re-enabled in a future update. Thanks to Sander Bos for
   discovering this issue!
   (CVE-2017-14180, LP: #1726372)
   * apport/hookutils.py: modify package_versions to return an empty string if
 packages is empty. (LP: #1723822)

 -- Brian Murray   Wed, 15 Nov 2017 12:44:24 -0800

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

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

Title:
  Multiple security issues in Apport

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released

Bug description:
  We have received the following advisory:

  Security vulnerability report: multiple vulnerabilies in Apport / Ubuntu
  

  OVERVIEW
  

  Author: Sander Bos
  Author's e-mail address: sbos _at_ sbosnet _dot_ nl
  Author's web site: www.sbosnet.nl
  CVE numbers: requested
  Date: 2017-10-23
  Version: 2

  SUMMARY
  ---

  Several security vulnerabilities were discovered by Sander Bos in the
  "Apport" crash handler program [1] affecting all currently supported
  releases of Ubuntu (12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10)
  and, likely, other distributions and Ubuntu derivatives using Apport
  as well.

  Exploitation types are privilege escalation (root exploitation), full
  disk DoS, and Linux container escaping.

  DESCRIPTION, WITH PROPOSED FIXES / WORKAROUNDS
  --

  Issue 1 (CVE-2017-14177): Incomplete fix for CVE-2015-1324
  -

  Exploitation types: privilege escalation, full disk DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10
  (i.e., all currently supported releases).
  Note: default OS installations might need an extra package installed,
  or a system configuration setting changed, to be exploitable.

  Description:

  The Apport issue I reported in 2015 (CVE-2015-1324) [2], leading to
  privilege escalation, was not fixed properly.  The initial issue and
  vulnerability still apply, although to a lesser extent.

  Since the introduction of the fix [3] Apport detects setuid, unreadable,
  and other types of tainted / protected binaries / processes by
  comparing the real UID and real GID of the crashed process, read from
  /proc//status and which Apport first sets its own UID and GID to,
  with the UID and GID file owner information of /proc//stat.

  For non tainted processes, the file owner information of /proc//stat
  is the UID and GID of the user that started the process.  For tainted
  processes, the file owner information is 0.

  If the comparison does not match, Apport assumes the process to be a
  tainted process, and disables writing a core dump file.  This on itself
  is correct.

  However, if the comparison _does_ match, it is not always correct to
  assume that the process is _not_ a tainted process (and, consequently,
  write a core dump file).  For example, some setuid programs run by users
  receive real UID 0 and real GID 0.  Also, some setuid processes started
  by root (partially) drop privileges at some point (after which users
  could crash them), for example after forking, but retain real UID 0 and
  real GID 0.

  In such cases, Apport writes a core dump file (as root) while in fact
  it should not do so.  This brings back the problem of CVE-2015-1324.

  It should also be noted that, for the same reason, Apport 

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

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.8-0ubuntu1

---
apport (2.20.8-0ubuntu1) bionic; urgency=medium

   * New upstream release:
 - SECURITY UPDATE: Denial of service via resource exhaustion and
   privilege escalation when handling crashes of tainted processes.
 - When /proc/sys/fs/suid_dumpable is set to 2, do not assume that
   the user and group owning the /proc//stat file is the same
   owner and group that started the process. Rather check the dump
   mode of the crashed process and do not write a core file if its
   value is 2. Thanks to Sander Bos for discovering this issue!
   (CVE-2017-14177, LP: #1726372)
 - SECURITY UPDATE: Denial of service via resource exhaustion,
   privilege escalation, and possible container escape when handling
   crashes of processes inside PID namespaces.
 - Change the method for determining if a crash is from a container
   so that there are no false positives from software using PID
   namespaces. Additionally, disable container crash forwarding by
   ignoring crashes that occur in a PID namespace. This functionality
   may be re-enabled in a future update. Thanks to Sander Bos for
   discovering this issue!
   (CVE-2017-14180, LP: #1726372)
   * apport/hookutils.py: modify package_versions to return an empty string if
 packages is empty. (LP: #1723822)

 -- Brian Murray   Wed, 15 Nov 2017 12:44:24 -0800

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

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

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

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

Title:
  uncaught TypeError triggers ValueError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

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

  During handling of the above exception, another exception occurred:

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

  $ Created new window in existing browser session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports:
   640:121:119:20593327:2017-10-14 08:49:43.994080376 -0700:2017-10-14 
08:49:24.682136558 -0700:/var/crash/_usr_bin_gnome-shell.121.crash
   640:0:119:712257:2017-10-13 22:55:49.843941428 -0700:2017-10-13 
22:55:48.723911385 -0700:/var/crash/_usr_lib_udisks2_udisksd.0.crash
   640:1000:119:432238:2017-10-14 07:48:01.498643348 -0700:2017-10-14 
07:48:00.714643372 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.crash
   664:1000:119:0:2017-10-13 19:55:40.447393054 -0700:2017-10-13 
19:55:40.447393054 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.upload
   600:112:119:0:2017-10-13 19:55:42.247460153 -0700:2017-10-13 
19:55:42.247460153 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 17:52:08 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1729892] Re: pango 1.40.13 word break regression

[Jeremy Bicha]

** Changed in: pango1.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  pango 1.40.13 word break regression

Status in Pango:
  Confirmed
Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 package in Debian:
  Fix Released

Bug description:
  See upstream bug.

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

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

[Touch-packages] [Bug 1732566] Re: Update request: protobuf-compiler

[Jeremy Bicha]

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

** Also affects: protobuf (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874498
   Importance: Unknown
   Status: Unknown

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

Title:
  Update request: protobuf-compiler

Status in protobuf package in Ubuntu:
  New
Status in protobuf package in Debian:
  Unknown

Bug description:
  Please can you update the protobuf-compiler package to something
  fairly recent in the 3.x.x series.

  (a) backport >=3.5.x to Xenial for LTS, (currently 2.6.0)
  (b) update Atomic/Bionic (currently 3.0.0, which is vintage 2016)

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

The reproducer does the ulimit itself, that's why you're getting a core.

The example code in 1726372 specifically does:

   corelimit.rlim_cur = RLIM_INFINITY;
   corelimit.rlim_max = RLIM_INFINITY;
   setrlimit(RLIMIT_CORE, );

Which is equivalent to "ulimit -c unlimited"

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732566] [NEW] Update request: protobuf-compiler

[Shevek]

Public bug reported:

Please can you update the protobuf-compiler package to something fairly
recent in the 3.x.x series.

(a) backport >=3.5.x to Xenial for LTS, (currently 2.6.0)
(b) update Atomic/Bionic (currently 3.0.0, which is vintage 2016)

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


** Tags: upgrade-software-version

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

Title:
  Update request: protobuf-compiler

Status in protobuf package in Ubuntu:
  New

Bug description:
  Please can you update the protobuf-compiler package to something
  fairly recent in the 3.x.x series.

  (a) backport >=3.5.x to Xenial for LTS, (currently 2.6.0)
  (b) update Atomic/Bionic (currently 3.0.0, which is vintage 2016)

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Tyler Hicks]

The reason I'm being picky about the pidns thing is because I think this
update needs to go through -security since it fixes regressions caused
by the security update. We try to be as conservative as possible with
those updates.

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Tyler Hicks]

If you don't run the `ulimit -c unlimited` command, your crash program
will not result in apport writing out a core file.

However, even if you don't run that command, the reproducer in bug
1726372 will cause apport to write out a core file.

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

Anyway, for the pidns thing, yes, we can change the condition to trip on
either a different pidns or a different mntns and log a message that
this isn't supported, I'm just not seeing much risk with just supporting
it and it would certainly qualify as a bugfix.

The handling in this case isn't particularly controversial either, if we
see we're in the same mntns but pidns differs we just use the global pid
and move on. We know the filesystem will be the same, so it's fine to
call the hooks and write wherever apport usually writes.

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

** Patch added: "xenial.diff"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732518/+attachment/5009737/+files/xenial.diff

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

stgraber@castiana:~$ cat crash.c 
#include 

int main() {
abort();
return 0;
}
stgraber@castiana:~$ gcc crash.c -o crash
stgraber@castiana:~$ ulimit -c unlimited
stgraber@castiana:~$ ./crash 
Aborted (core dumped)
stgraber@castiana:~$ ls -lh core 
-rw--- 1 stgraber domain admins 260K Nov 15 18:12 core
stgraber@castiana:~$ sudo tail /var/log/apport.log
ERROR: apport (pid 10082) Wed Nov 15 18:12:31 2017: called for pid 10081, 
signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 10082) Wed Nov 15 18:12:31 2017: ignoring implausibly big 
core limit, treating as unlimited
ERROR: apport (pid 10082) Wed Nov 15 18:12:31 2017: executable: 
/home/stgraber/crash (command line "./crash")
ERROR: apport (pid 10082) Wed Nov 15 18:12:31 2017: executable does not belong 
to a package, ignoring
ERROR: apport (pid 10082) Wed Nov 15 18:12:31 2017: writing core dump to 
/home/stgraber/core (limit: -1)
stgraber@castiana:~$

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

Fixed an issue with the mntns check (replaced else with elif).

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

As for the reproducer from the other bug causing a /tmp/core file to be
written, my understanding is that this is normal apport behavior for
when a core file size is set.

** Patch removed: "debdiff for xenial"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732518/+attachment/5009693/+files/xenial.diff

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Tyler Hicks]

I suspect that you're correct but I'd rather not widen the attack
surface of apport without having a strong reason to do so. If there's
not strong justification, maybe enabling the handling of those crashes
in the dev release and seeing how it plays out would be a better
approach.

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

As for the forwarding issue, there is a check now in place to prevent
such things from happening in the future, that's the argument check in
the receiver.

For the case where as user is running the pre-security upload version of
apport in a container and this post-security upload version on the host,
then the container will indeed receive one more argument than it needs
but I don't think there's much we can do about this.

In this case, the host would send "   " to the 
container.
The container would then set its sys.argv to match, effectively putting the 
dump mode as the global pid.

This is obviously not going to work well and will result in apport crashing in 
the container.
As far as I can tell this isn't exploitable and will get resolved as soon as 
the container is upgraded. The check I put in place will prevent this from 
happening again and once we get named arguments, the problem will go away for 
good while retaining backward compatibility.

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

I strongly suspect that us ignoring crashes coming from a different
pidns but same mntns is effectively making us drop crashes from various
web browsers and other piece of server software (I remember some ftp
server using a pidns per connection at some point).

There doesn't seem to be a good reason to drop those as they are
legitimate crashes that we can handle just fine.

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732489] Re: TMPTIME is not honoured

[Bug Watch Updater]

** Changed in: systemd (Debian)
   Status: Unknown => Fix Released

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

Title:
  TMPTIME is not honoured

Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  Fix Released

Bug description:
  TMPTIME is incorrectly migrated on an upgrade from Trusty to Xenial.

  tmp.conf uses D where it should be d. This also has the effect of
  wiping /tmp no matter what.

  This is fixed in Debian.

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

  This could result in data loss, although storing non-volatile files in
  /tmp is madness.

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

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

[Touch-packages] [Bug 1732554] [NEW] package libcups2:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

[Vinissius Radimacker Cavalcanti Fernandes]

Public bug reported:

It is a fresh Ubuntu install

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libcups2:amd64 2.1.3-4ubuntu0.3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CupsErrorLog:
 
Date: Wed Nov 15 12:18:41 2017
ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
InstallationDate: Installed on 2017-11-15 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Inspiron 3437
Papersize: a4
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: cups
Title: package libcups2:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 02JX3T
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/24/2014:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn02JX3T:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3437
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package xenial

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

Title:
  package libcups2:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in cups package in Ubuntu:
  New

Bug description:
  It is a fresh Ubuntu install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcups2:amd64 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Nov 15 12:18:41 2017
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Inspiron 3437
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: cups
  Title: package libcups2:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 02JX3T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/24/2014:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn02JX3T:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Tyler Hicks]

Going back to point #3 in comment 2, I don't see anything that will
protect against an updated apport in the host from forwarding a crash to
a non-updated apport in a container, causing the container's apport to
confuse dump_mode as a global_pid. Am I missing something that protects
against that or do not consider it to be a problem worth worrying about?

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Tyler Hicks]

Do we have a strong reason to start handling crashes inside of "non-
full" containers on stable Ubuntu releases? I'm specifically talking
about when this conditional evaluates to True:

  elif not is_same_ns(host_pid, "pid") and is_same_ns(host_pid, "mnt"):

If there's no strong reason, can we only enable that in Bionic?

Also, did you test that with the the PoC in bug 1726372? I'm fairly
certain that it'll create a core dump in /tmp (/tmp/core) which is
new/undesired.

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

This debdiff re-introduces the forwarding code, it also cleans a number
of things up:

 - It fixes a regression of apport on systems using upstart
 - It replaces the is_container logic with a is_same_ns function that lets us 
check things more carefully.
 - If the pidns differs but mntns doesn't, apport will process the crash 
locally, using the global pid.
 - If the mntns differs but pidns doesn't, then the crash is just plain ignored
 - If pidns and mntns differ and an apport receiver socket can be found, the 
crash is forwarded. If none can be found, the crash is ignored.
 - All arguments except the first and last are now sent to the receiver.
 - The receiver has a check for the number of received arguments, ignoring any 
crash that doesn't match its view of the world.
 - The ucred is used for pid passing, translating the pid across pidns.

I've done the following tests:
 - Standard crash on host => crash in /var/crash of host
 - Crash on host in a different pidns => crash in /var/crash of host
 - Crash on host in a different mtnns => no crash file
 - Crash on host in a different pidns and mntns => no crash file (no receiver 
found)
 - Crash in container with receiver setup => crash in /var/crash of container

** Patch added: "debdiff for xenial"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732518/+attachment/5009693/+files/xenial.diff

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

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

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in apport package in Ubuntu:
  New

Bug description:
  I am not familiar with Linux, so I don't know how to describe the
  issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Nov 16 09:06:19 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-11-08 (7 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.10 failed to install/upgrade: 
subprocess new pre-removal 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/apport/+bug/1732548/+subscriptions

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

[Touch-packages] [Bug 1732548] [NEW] package apport 2.20.1-0ubuntu2.10 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Yuxiang Wang]

Public bug reported:

I am not familiar with Linux, so I don't know how to describe the issue.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.10
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Nov 16 09:06:19 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-11-08 (7 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.10 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

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

Status in apport package in Ubuntu:
  New

Bug description:
  I am not familiar with Linux, so I don't know how to describe the
  issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Nov 16 09:06:19 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-11-08 (7 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.10 failed to install/upgrade: 
subprocess new pre-removal 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/apport/+bug/1732548/+subscriptions

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

[Touch-packages] [Bug 1732546] [NEW] updates will not install

[dan purdy]

Public bug reported:

Updates will not install. I removed firefox  and it will not reinstall.
I am not very knowledgeable I rely could not do any repair work. the ms
is roughly that old programs will not uninstall and new programs will
not install. ubuntu 16.04.3lts oh yes, my up dates told me that a new OS
system was available and I thought I would install it but I found later
on it was not finished and that it was not a long term system any way
opps I think that is where I stubed my tow. Any way I have a mess. I am
tempted to just reinstall this system. Dan Purdy

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Nov 15 16:41:46 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller 
[103c:2a5e]
InstallationDate: Installed on 2015-11-23 (723 days ago)
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
MachineType: HP-Pavilion GC670AA-ABA a6120n
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=af1f516a-d0b7-44cf-9b07-73e07582e598 ro vesafb.invalid=1 
drm.debug=0xe nopat plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.17
dmi.board.name: Leonite2
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 6.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: 
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.17:bd04/20/2007:svnHP-Pavilion:pnGC670AA-ABAa6120n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: GC670AA-ABA a6120n
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Nov 15 16:28:47 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Cordless Mouse   MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   40971 
 vendor DEL
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu xenial

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

Title:
  updates will not install

Status in xorg package in Ubuntu:
  New

Bug description:
  Updates will not install. I removed firefox  and it will not
  reinstall. I am not very knowledgeable I rely could not do any repair
  work. the ms is roughly that old programs will not uninstall and new
  programs will not install. ubuntu 16.04.3lts oh yes, my up dates told
  me that a new OS system was available and I thought I would install it
  but I found later on it was not finished and that it was not a long
  term system any way opps I think that is where I stubed my tow. Any
  way I have a mess. I am tempted to just reinstall this system. Dan
  Purdy

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  

[Touch-packages] [Bug 1732544] [NEW] package perl-modules-5.22 5.22.1-9 failed to install/upgrade: не удалось скопировать извлечённые данные «./usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm» в

[Михаил]

Public bug reported:

Я не знаю

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: perl-modules-5.22 5.22.1-9ubuntu0.2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Nov 16 00:40:57 2017
ErrorMessage: не удалось скопировать извлечённые данные 
«./usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm» в 
«/usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm.dpkg-new»: неожиданный 
конец файла или потока
InstallationDate: Installed on 2017-11-15 (0 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: perl
Title: package perl-modules-5.22 5.22.1-9 failed to install/upgrade: не удалось 
скопировать извлечённые данные 
«./usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm» в 
«/usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm.dpkg-new»: неожиданный 
конец файла или потока
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package perl-modules-5.22 5.22.1-9 failed to install/upgrade: не
  удалось скопировать извлечённые данные
  «./usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm» в
  «/usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm.dpkg-new»:
  неожиданный конец файла или потока

Status in perl package in Ubuntu:
  New

Bug description:
  Я не знаю

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: perl-modules-5.22 5.22.1-9ubuntu0.2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Nov 16 00:40:57 2017
  ErrorMessage: не удалось скопировать извлечённые данные 
«./usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm» в 
«/usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm.dpkg-new»: неожиданный 
конец файла или потока
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: perl
  Title: package perl-modules-5.22 5.22.1-9 failed to install/upgrade: не 
удалось скопировать извлечённые данные 
«./usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm» в 
«/usr/share/perl/5.22.1/Locale/Codes/Language_Codes.pm.dpkg-new»: неожиданный 
конец файла или потока
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1726372] Re: Multiple security issues in Apport

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/bionic/apport/ubuntu

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

Title:
  Multiple security issues in Apport

Status in apport package in Ubuntu:
  New
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released

Bug description:
  We have received the following advisory:

  Security vulnerability report: multiple vulnerabilies in Apport / Ubuntu
  

  OVERVIEW
  

  Author: Sander Bos
  Author's e-mail address: sbos _at_ sbosnet _dot_ nl
  Author's web site: www.sbosnet.nl
  CVE numbers: requested
  Date: 2017-10-23
  Version: 2

  SUMMARY
  ---

  Several security vulnerabilities were discovered by Sander Bos in the
  "Apport" crash handler program [1] affecting all currently supported
  releases of Ubuntu (12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10)
  and, likely, other distributions and Ubuntu derivatives using Apport
  as well.

  Exploitation types are privilege escalation (root exploitation), full
  disk DoS, and Linux container escaping.

  DESCRIPTION, WITH PROPOSED FIXES / WORKAROUNDS
  --

  Issue 1 (CVE-2017-14177): Incomplete fix for CVE-2015-1324
  -

  Exploitation types: privilege escalation, full disk DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10
  (i.e., all currently supported releases).
  Note: default OS installations might need an extra package installed,
  or a system configuration setting changed, to be exploitable.

  Description:

  The Apport issue I reported in 2015 (CVE-2015-1324) [2], leading to
  privilege escalation, was not fixed properly.  The initial issue and
  vulnerability still apply, although to a lesser extent.

  Since the introduction of the fix [3] Apport detects setuid, unreadable,
  and other types of tainted / protected binaries / processes by
  comparing the real UID and real GID of the crashed process, read from
  /proc//status and which Apport first sets its own UID and GID to,
  with the UID and GID file owner information of /proc//stat.

  For non tainted processes, the file owner information of /proc//stat
  is the UID and GID of the user that started the process.  For tainted
  processes, the file owner information is 0.

  If the comparison does not match, Apport assumes the process to be a
  tainted process, and disables writing a core dump file.  This on itself
  is correct.

  However, if the comparison _does_ match, it is not always correct to
  assume that the process is _not_ a tainted process (and, consequently,
  write a core dump file).  For example, some setuid programs run by users
  receive real UID 0 and real GID 0.  Also, some setuid processes started
  by root (partially) drop privileges at some point (after which users
  could crash them), for example after forking, but retain real UID 0 and
  real GID 0.

  In such cases, Apport writes a core dump file (as root) while in fact
  it should not do so.  This brings back the problem of CVE-2015-1324.

  It should also be noted that, for the same reason, Apport "dropping 
privileges"
  to the real UID and real GID read from /proc//status is at times
  incorrect and, thus, unsafe as well.

  Proposed fix:

  The proper fix is to really _never_ write a core dump file for processes
  where suid_dumpable=2 got effectuated.  This was probably what was
  intended with the fix for CVE-2015-1324, but the check that was created
  does not catch all cases of tainted processes.  A better approach would
  be to let Apport read out "%d" from core(5) through "kernel.core_pattern"
  and if it returns "2", not write a core dump file.  Note however that
  "%d" is only present since kernel version 3.7, and would thus not work
  on Ubuntu 12.04 LTS systems running a 3.2 "GA" (General Availability)
  kernel from earlier Ubuntu 12.04.x LTS releases (as opposed to such
  systems running a 3.13 "HWE" (Hardware Enablement Stack) kernel from
  later Ubuntu 12.04.x LTS releases).

  Issue 2 (CVE-2017-14179): Apport lacking container / PID namespace support
  and
  Issue 3 (CVE-2017-14180): Apport broken container / PID namespace support
  -

  Exploitation types: container escape, privilege escalation, full disk
  DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 16.04 LTS, 17.04, 17.10.
  Note: exploitable on default OS installations.

  Description:

  Issue 2 (CVE-2017-14179):
  Ubuntu 12.04 LTS: Apport does not recognize ("support")
  PID namespaces / containers.

  Issue 3 (CVE-2017-14180):
  

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/bionic/apport/ubuntu

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

Title:
  uncaught TypeError triggers ValueError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged

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

  During handling of the above exception, another exception occurred:

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

  $ Created new window in existing browser session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports:
   640:121:119:20593327:2017-10-14 08:49:43.994080376 -0700:2017-10-14 
08:49:24.682136558 -0700:/var/crash/_usr_bin_gnome-shell.121.crash
   640:0:119:712257:2017-10-13 22:55:49.843941428 -0700:2017-10-13 
22:55:48.723911385 -0700:/var/crash/_usr_lib_udisks2_udisksd.0.crash
   640:1000:119:432238:2017-10-14 07:48:01.498643348 -0700:2017-10-14 
07:48:00.714643372 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.crash
   664:1000:119:0:2017-10-13 19:55:40.447393054 -0700:2017-10-13 
19:55:40.447393054 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.upload
   600:112:119:0:2017-10-13 19:55:42.247460153 -0700:2017-10-13 
19:55:42.247460153 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 17:52:08 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1726536] Re: Cant resume after suspend/sleep

[Dario]

This fixed itself, probably by upgrading to 4.14 kernel. Not sure
because I found out accidentally that it no longer stuck on suspend.

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

Title:
  Cant resume after suspend/sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  1) 17.10 
  2) 3.26.1-0ubuntu4
  3) Pressing any button wakes computer from suspend/sleep, expecting GDM login 
screen.
  4) Waking up computer from suspend does nothing, screen remains black as it 
doesn't getting any signal (HDD led is blinking as if computer is doing 
something). Need to hard reset computer at that point.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 20:39:29 2017
  DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (4 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.85+git1710210630.e580be~gd~a
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1727390] Re: New bugfix release 17.2.4

[Boaz Dodin]

Mesa 17.2.5 released with some additional fixes:
https://www.mesa3d.org/relnotes/17.2.5.html

** Summary changed:

- New bugfix release 17.2.4
+ New bugfix release 17.2.5

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

Title:
  New bugfix release 17.2.5

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

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

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

[Touch-packages] [Bug 1726372] Re: Multiple security issues in Apport

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

Title:
  Multiple security issues in Apport

Status in apport package in Ubuntu:
  New
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released

Bug description:
  We have received the following advisory:

  Security vulnerability report: multiple vulnerabilies in Apport / Ubuntu
  

  OVERVIEW
  

  Author: Sander Bos
  Author's e-mail address: sbos _at_ sbosnet _dot_ nl
  Author's web site: www.sbosnet.nl
  CVE numbers: requested
  Date: 2017-10-23
  Version: 2

  SUMMARY
  ---

  Several security vulnerabilities were discovered by Sander Bos in the
  "Apport" crash handler program [1] affecting all currently supported
  releases of Ubuntu (12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10)
  and, likely, other distributions and Ubuntu derivatives using Apport
  as well.

  Exploitation types are privilege escalation (root exploitation), full
  disk DoS, and Linux container escaping.

  DESCRIPTION, WITH PROPOSED FIXES / WORKAROUNDS
  --

  Issue 1 (CVE-2017-14177): Incomplete fix for CVE-2015-1324
  -

  Exploitation types: privilege escalation, full disk DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10
  (i.e., all currently supported releases).
  Note: default OS installations might need an extra package installed,
  or a system configuration setting changed, to be exploitable.

  Description:

  The Apport issue I reported in 2015 (CVE-2015-1324) [2], leading to
  privilege escalation, was not fixed properly.  The initial issue and
  vulnerability still apply, although to a lesser extent.

  Since the introduction of the fix [3] Apport detects setuid, unreadable,
  and other types of tainted / protected binaries / processes by
  comparing the real UID and real GID of the crashed process, read from
  /proc//status and which Apport first sets its own UID and GID to,
  with the UID and GID file owner information of /proc//stat.

  For non tainted processes, the file owner information of /proc//stat
  is the UID and GID of the user that started the process.  For tainted
  processes, the file owner information is 0.

  If the comparison does not match, Apport assumes the process to be a
  tainted process, and disables writing a core dump file.  This on itself
  is correct.

  However, if the comparison _does_ match, it is not always correct to
  assume that the process is _not_ a tainted process (and, consequently,
  write a core dump file).  For example, some setuid programs run by users
  receive real UID 0 and real GID 0.  Also, some setuid processes started
  by root (partially) drop privileges at some point (after which users
  could crash them), for example after forking, but retain real UID 0 and
  real GID 0.

  In such cases, Apport writes a core dump file (as root) while in fact
  it should not do so.  This brings back the problem of CVE-2015-1324.

  It should also be noted that, for the same reason, Apport "dropping 
privileges"
  to the real UID and real GID read from /proc//status is at times
  incorrect and, thus, unsafe as well.

  Proposed fix:

  The proper fix is to really _never_ write a core dump file for processes
  where suid_dumpable=2 got effectuated.  This was probably what was
  intended with the fix for CVE-2015-1324, but the check that was created
  does not catch all cases of tainted processes.  A better approach would
  be to let Apport read out "%d" from core(5) through "kernel.core_pattern"
  and if it returns "2", not write a core dump file.  Note however that
  "%d" is only present since kernel version 3.7, and would thus not work
  on Ubuntu 12.04 LTS systems running a 3.2 "GA" (General Availability)
  kernel from earlier Ubuntu 12.04.x LTS releases (as opposed to such
  systems running a 3.13 "HWE" (Hardware Enablement Stack) kernel from
  later Ubuntu 12.04.x LTS releases).

  Issue 2 (CVE-2017-14179): Apport lacking container / PID namespace support
  and
  Issue 3 (CVE-2017-14180): Apport broken container / PID namespace support
  -

  Exploitation types: container escape, privilege escalation, full disk
  DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 16.04 LTS, 17.04, 17.10.
  Note: exploitable on default OS installations.

  Description:

  Issue 2 (CVE-2017-14179):
  Ubuntu 12.04 LTS: Apport does not recognize ("support")
  PID namespaces / containers.

  Issue 3 (CVE-2017-14180):
  Ubuntu 16.04 LTS, Ubuntu 17.04, and Ubuntu 17.10: 

[Touch-packages] [Bug 1732447] Re: rename no longer included in perl package, but still linked

[Hans Joachim Desserud]

Thanks for taking your time to report this issue and help making Ubuntu
better

I believe the list of suggested packages is maintained in command-not-
found, so I've marked that as also affected.

** Also affects: command-not-found (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  rename no longer included in perl package, but still linked

Status in command-not-found package in Ubuntu:
  New
Status in perl package in Ubuntu:
  New

Bug description:
  typing "rename" in a terminal responds with...
   
  The program 'rename' can be found in the following packages:
   * perl
   * rename
  Ask your administrator to install one of them

  ...but perl is already installed.  Internet reports suggest this has
  started in 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: perl 5.26.0-8ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Wed Nov 15 16:24:29 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   LC_PAPER=en_GB.UTF-8
  SourcePackage: perl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1732447/+subscriptions

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

[Touch-packages] [Bug 1726372] Re: Multiple security issues in Apport

[Launchpad Bug Tracker]

** Branch linked: lp:apport

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

Title:
  Multiple security issues in Apport

Status in apport package in Ubuntu:
  New
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released

Bug description:
  We have received the following advisory:

  Security vulnerability report: multiple vulnerabilies in Apport / Ubuntu
  

  OVERVIEW
  

  Author: Sander Bos
  Author's e-mail address: sbos _at_ sbosnet _dot_ nl
  Author's web site: www.sbosnet.nl
  CVE numbers: requested
  Date: 2017-10-23
  Version: 2

  SUMMARY
  ---

  Several security vulnerabilities were discovered by Sander Bos in the
  "Apport" crash handler program [1] affecting all currently supported
  releases of Ubuntu (12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10)
  and, likely, other distributions and Ubuntu derivatives using Apport
  as well.

  Exploitation types are privilege escalation (root exploitation), full
  disk DoS, and Linux container escaping.

  DESCRIPTION, WITH PROPOSED FIXES / WORKAROUNDS
  --

  Issue 1 (CVE-2017-14177): Incomplete fix for CVE-2015-1324
  -

  Exploitation types: privilege escalation, full disk DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10
  (i.e., all currently supported releases).
  Note: default OS installations might need an extra package installed,
  or a system configuration setting changed, to be exploitable.

  Description:

  The Apport issue I reported in 2015 (CVE-2015-1324) [2], leading to
  privilege escalation, was not fixed properly.  The initial issue and
  vulnerability still apply, although to a lesser extent.

  Since the introduction of the fix [3] Apport detects setuid, unreadable,
  and other types of tainted / protected binaries / processes by
  comparing the real UID and real GID of the crashed process, read from
  /proc//status and which Apport first sets its own UID and GID to,
  with the UID and GID file owner information of /proc//stat.

  For non tainted processes, the file owner information of /proc//stat
  is the UID and GID of the user that started the process.  For tainted
  processes, the file owner information is 0.

  If the comparison does not match, Apport assumes the process to be a
  tainted process, and disables writing a core dump file.  This on itself
  is correct.

  However, if the comparison _does_ match, it is not always correct to
  assume that the process is _not_ a tainted process (and, consequently,
  write a core dump file).  For example, some setuid programs run by users
  receive real UID 0 and real GID 0.  Also, some setuid processes started
  by root (partially) drop privileges at some point (after which users
  could crash them), for example after forking, but retain real UID 0 and
  real GID 0.

  In such cases, Apport writes a core dump file (as root) while in fact
  it should not do so.  This brings back the problem of CVE-2015-1324.

  It should also be noted that, for the same reason, Apport "dropping 
privileges"
  to the real UID and real GID read from /proc//status is at times
  incorrect and, thus, unsafe as well.

  Proposed fix:

  The proper fix is to really _never_ write a core dump file for processes
  where suid_dumpable=2 got effectuated.  This was probably what was
  intended with the fix for CVE-2015-1324, but the check that was created
  does not catch all cases of tainted processes.  A better approach would
  be to let Apport read out "%d" from core(5) through "kernel.core_pattern"
  and if it returns "2", not write a core dump file.  Note however that
  "%d" is only present since kernel version 3.7, and would thus not work
  on Ubuntu 12.04 LTS systems running a 3.2 "GA" (General Availability)
  kernel from earlier Ubuntu 12.04.x LTS releases (as opposed to such
  systems running a 3.13 "HWE" (Hardware Enablement Stack) kernel from
  later Ubuntu 12.04.x LTS releases).

  Issue 2 (CVE-2017-14179): Apport lacking container / PID namespace support
  and
  Issue 3 (CVE-2017-14180): Apport broken container / PID namespace support
  -

  Exploitation types: container escape, privilege escalation, full disk
  DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 16.04 LTS, 17.04, 17.10.
  Note: exploitable on default OS installations.

  Description:

  Issue 2 (CVE-2017-14179):
  Ubuntu 12.04 LTS: Apport does not recognize ("support")
  PID namespaces / containers.

  Issue 3 (CVE-2017-14180):
  Ubuntu 16.04 LTS, Ubuntu 17.04, and Ubuntu 

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Tyler Hicks]

The patch in comment #4 of bug 1726372 was mostly complete but issues
were discovered late as we were approached the CRD for the CVEs
described in that bug:

1) The patch should be updated to forward the new dump_mode argument into the 
container. This is a trivial change.
2) The patch changed the functionality of apport so that it processes, in the 
host, all crashes that come from a "non-full" container. The PoC in the 
description of bug 1726372 simply creates a PID namespace, without a new mount 
namespace, and then calls abort(). The behavioral change introduced by the 
patch resulted in apport writing the core dump to /tmp/core when it didn't do 
that before because it ignored such crashes.
3) The combination of the patch and the fix for CVE-2017-14177, which added a 
new required dump_mode command line option to Apport, made it potentially 
dangerous for an updated Apport in the host to forward a crash to a non-updated 
Apport in a container as the dump_mode parameter would be treated as the 
global_pid in the container's Apport.

These three issues are why we had to make the decision to (temporarily)
drop container crash forwarding.

I won't be directly involved in re-enabling the container crash
forwarding support but please feel free to ping me for a review, if
needed.

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

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1726372] Re: Multiple security issues in Apport

[Stéphane Graber]

Filed an SRU regression bug here
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732518 to track
re-enabling of container support.

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

Title:
  Multiple security issues in Apport

Status in apport package in Ubuntu:
  New
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released

Bug description:
  We have received the following advisory:

  Security vulnerability report: multiple vulnerabilies in Apport / Ubuntu
  

  OVERVIEW
  

  Author: Sander Bos
  Author's e-mail address: sbos _at_ sbosnet _dot_ nl
  Author's web site: www.sbosnet.nl
  CVE numbers: requested
  Date: 2017-10-23
  Version: 2

  SUMMARY
  ---

  Several security vulnerabilities were discovered by Sander Bos in the
  "Apport" crash handler program [1] affecting all currently supported
  releases of Ubuntu (12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10)
  and, likely, other distributions and Ubuntu derivatives using Apport
  as well.

  Exploitation types are privilege escalation (root exploitation), full
  disk DoS, and Linux container escaping.

  DESCRIPTION, WITH PROPOSED FIXES / WORKAROUNDS
  --

  Issue 1 (CVE-2017-14177): Incomplete fix for CVE-2015-1324
  -

  Exploitation types: privilege escalation, full disk DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10
  (i.e., all currently supported releases).
  Note: default OS installations might need an extra package installed,
  or a system configuration setting changed, to be exploitable.

  Description:

  The Apport issue I reported in 2015 (CVE-2015-1324) [2], leading to
  privilege escalation, was not fixed properly.  The initial issue and
  vulnerability still apply, although to a lesser extent.

  Since the introduction of the fix [3] Apport detects setuid, unreadable,
  and other types of tainted / protected binaries / processes by
  comparing the real UID and real GID of the crashed process, read from
  /proc//status and which Apport first sets its own UID and GID to,
  with the UID and GID file owner information of /proc//stat.

  For non tainted processes, the file owner information of /proc//stat
  is the UID and GID of the user that started the process.  For tainted
  processes, the file owner information is 0.

  If the comparison does not match, Apport assumes the process to be a
  tainted process, and disables writing a core dump file.  This on itself
  is correct.

  However, if the comparison _does_ match, it is not always correct to
  assume that the process is _not_ a tainted process (and, consequently,
  write a core dump file).  For example, some setuid programs run by users
  receive real UID 0 and real GID 0.  Also, some setuid processes started
  by root (partially) drop privileges at some point (after which users
  could crash them), for example after forking, but retain real UID 0 and
  real GID 0.

  In such cases, Apport writes a core dump file (as root) while in fact
  it should not do so.  This brings back the problem of CVE-2015-1324.

  It should also be noted that, for the same reason, Apport "dropping 
privileges"
  to the real UID and real GID read from /proc//status is at times
  incorrect and, thus, unsafe as well.

  Proposed fix:

  The proper fix is to really _never_ write a core dump file for processes
  where suid_dumpable=2 got effectuated.  This was probably what was
  intended with the fix for CVE-2015-1324, but the check that was created
  does not catch all cases of tainted processes.  A better approach would
  be to let Apport read out "%d" from core(5) through "kernel.core_pattern"
  and if it returns "2", not write a core dump file.  Note however that
  "%d" is only present since kernel version 3.7, and would thus not work
  on Ubuntu 12.04 LTS systems running a 3.2 "GA" (General Availability)
  kernel from earlier Ubuntu 12.04.x LTS releases (as opposed to such
  systems running a 3.13 "HWE" (Hardware Enablement Stack) kernel from
  later Ubuntu 12.04.x LTS releases).

  Issue 2 (CVE-2017-14179): Apport lacking container / PID namespace support
  and
  Issue 3 (CVE-2017-14180): Apport broken container / PID namespace support
  -

  Exploitation types: container escape, privilege escalation, full disk
  DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 16.04 LTS, 17.04, 17.10.
  Note: exploitable on default OS installations.

  Description:

  Issue 2 (CVE-2017-14179):
  Ubuntu 12.04 LTS: Apport does not recognize 

[Touch-packages] [Bug 1729892] Re: pango 1.40.13 word break regression

[Bug Watch Updater]

** Changed in: pango1.0 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  pango 1.40.13 word break regression

Status in Pango:
  Confirmed
Status in pango1.0 package in Ubuntu:
  Triaged
Status in pango1.0 package in Debian:
  Fix Released

Bug description:
  See upstream bug.

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

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

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

Tagged as regression-update since the security update technically
regressed this (albeit on purpose).

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1732518] [NEW] Please re-enable container support in apport

[Stéphane Graber]

Public bug reported:

The latest security update for apport disabled container crash
forwarding, this is a feature which users do rely on in production and
while it may have been appropriate to turn it off to put a security
update out, this needs to be re-enabled ASAP.

I provided a patch which fixed the security issue before the security
issue was publicly disclosed so pushing an SRU to all Ubuntu releases
re-enabling this code should be pretty trivial.

** Affects: apport (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: apport (Ubuntu Xenial)
 Importance: High
 Status: Triaged

** Affects: apport (Ubuntu Zesty)
 Importance: High
 Status: Triaged

** Affects: apport (Ubuntu Artful)
 Importance: High
 Status: Triaged

** Affects: apport (Ubuntu Bionic)
 Importance: High
 Status: Triaged


** Tags: regression-update

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

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

** Also affects: apport (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: apport (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

** Tags added: regression-update

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

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

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

[Touch-packages] [Bug 1726372] Re: Multiple security issues in Apport

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.14.1-0ubuntu3.27

---
apport (2.14.1-0ubuntu3.27) trusty-security; urgency=medium

  * SECURITY UPDATE: Denial of service via resource exhaustion and
privilege escalation when handling crashes of tainted processes
(LP: #1726372)
- When /proc/sys/fs/suid_dumpable is set to 2, do not assume that
  the user and group owning the /proc//stat file is the same
  user and group that started the process. Rather check the dump
  mode of the crashed process and do not write a core file if its
  value is 2. Thanks to Sander Bos for discovering this issue!
- CVE-2017-14177
  * SECURITY UPDATE: Denial of service via resource exhaustion,
privilege escalation, and possible container escape when handling
crashes of processes inside PID namespaces (LP: #1726372)
- Change the method for determining if a crash is from a container
  so that there are no false positives from software using PID
  namespaces. Additionally, disable container crash forwarding by
  ignoring crashes that occur in a PID namespace. This functionality
  may be re-enabled in a future update. Thanks to Sander Bos for
  discovering this issue!
- CVE-2017-14180

 -- Brian Murray   Mon, 13 Nov 2017 08:54:04 -0800

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

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

Title:
  Multiple security issues in Apport

Status in apport package in Ubuntu:
  New
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released

Bug description:
  We have received the following advisory:

  Security vulnerability report: multiple vulnerabilies in Apport / Ubuntu
  

  OVERVIEW
  

  Author: Sander Bos
  Author's e-mail address: sbos _at_ sbosnet _dot_ nl
  Author's web site: www.sbosnet.nl
  CVE numbers: requested
  Date: 2017-10-23
  Version: 2

  SUMMARY
  ---

  Several security vulnerabilities were discovered by Sander Bos in the
  "Apport" crash handler program [1] affecting all currently supported
  releases of Ubuntu (12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10)
  and, likely, other distributions and Ubuntu derivatives using Apport
  as well.

  Exploitation types are privilege escalation (root exploitation), full
  disk DoS, and Linux container escaping.

  DESCRIPTION, WITH PROPOSED FIXES / WORKAROUNDS
  --

  Issue 1 (CVE-2017-14177): Incomplete fix for CVE-2015-1324
  -

  Exploitation types: privilege escalation, full disk DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10
  (i.e., all currently supported releases).
  Note: default OS installations might need an extra package installed,
  or a system configuration setting changed, to be exploitable.

  Description:

  The Apport issue I reported in 2015 (CVE-2015-1324) [2], leading to
  privilege escalation, was not fixed properly.  The initial issue and
  vulnerability still apply, although to a lesser extent.

  Since the introduction of the fix [3] Apport detects setuid, unreadable,
  and other types of tainted / protected binaries / processes by
  comparing the real UID and real GID of the crashed process, read from
  /proc//status and which Apport first sets its own UID and GID to,
  with the UID and GID file owner information of /proc//stat.

  For non tainted processes, the file owner information of /proc//stat
  is the UID and GID of the user that started the process.  For tainted
  processes, the file owner information is 0.

  If the comparison does not match, Apport assumes the process to be a
  tainted process, and disables writing a core dump file.  This on itself
  is correct.

  However, if the comparison _does_ match, it is not always correct to
  assume that the process is _not_ a tainted process (and, consequently,
  write a core dump file).  For example, some setuid programs run by users
  receive real UID 0 and real GID 0.  Also, some setuid processes started
  by root (partially) drop privileges at some point (after which users
  could crash them), for example after forking, but retain real UID 0 and
  real GID 0.

  In such cases, Apport writes a core dump file (as root) while in fact
  it should not do so.  This brings back the problem of CVE-2015-1324.

  It should also be noted that, for the same reason, Apport "dropping 
privileges"
  to the real UID and real GID read from /proc//status is at times
  incorrect and, thus, unsafe as well.

  Proposed fix:

  The proper fix is to 

[Touch-packages] [Bug 1726372] Re: Multiple security issues in Apport

[Tyler Hicks]

** Information type changed from Private Security to Public Security

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

Title:
  Multiple security issues in Apport

Status in apport package in Ubuntu:
  New
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released

Bug description:
  We have received the following advisory:

  Security vulnerability report: multiple vulnerabilies in Apport / Ubuntu
  

  OVERVIEW
  

  Author: Sander Bos
  Author's e-mail address: sbos _at_ sbosnet _dot_ nl
  Author's web site: www.sbosnet.nl
  CVE numbers: requested
  Date: 2017-10-23
  Version: 2

  SUMMARY
  ---

  Several security vulnerabilities were discovered by Sander Bos in the
  "Apport" crash handler program [1] affecting all currently supported
  releases of Ubuntu (12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10)
  and, likely, other distributions and Ubuntu derivatives using Apport
  as well.

  Exploitation types are privilege escalation (root exploitation), full
  disk DoS, and Linux container escaping.

  DESCRIPTION, WITH PROPOSED FIXES / WORKAROUNDS
  --

  Issue 1 (CVE-2017-14177): Incomplete fix for CVE-2015-1324
  -

  Exploitation types: privilege escalation, full disk DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 14.04 LTS, 16.04 LTS, 17.04, 17.10
  (i.e., all currently supported releases).
  Note: default OS installations might need an extra package installed,
  or a system configuration setting changed, to be exploitable.

  Description:

  The Apport issue I reported in 2015 (CVE-2015-1324) [2], leading to
  privilege escalation, was not fixed properly.  The initial issue and
  vulnerability still apply, although to a lesser extent.

  Since the introduction of the fix [3] Apport detects setuid, unreadable,
  and other types of tainted / protected binaries / processes by
  comparing the real UID and real GID of the crashed process, read from
  /proc//status and which Apport first sets its own UID and GID to,
  with the UID and GID file owner information of /proc//stat.

  For non tainted processes, the file owner information of /proc//stat
  is the UID and GID of the user that started the process.  For tainted
  processes, the file owner information is 0.

  If the comparison does not match, Apport assumes the process to be a
  tainted process, and disables writing a core dump file.  This on itself
  is correct.

  However, if the comparison _does_ match, it is not always correct to
  assume that the process is _not_ a tainted process (and, consequently,
  write a core dump file).  For example, some setuid programs run by users
  receive real UID 0 and real GID 0.  Also, some setuid processes started
  by root (partially) drop privileges at some point (after which users
  could crash them), for example after forking, but retain real UID 0 and
  real GID 0.

  In such cases, Apport writes a core dump file (as root) while in fact
  it should not do so.  This brings back the problem of CVE-2015-1324.

  It should also be noted that, for the same reason, Apport "dropping 
privileges"
  to the real UID and real GID read from /proc//status is at times
  incorrect and, thus, unsafe as well.

  Proposed fix:

  The proper fix is to really _never_ write a core dump file for processes
  where suid_dumpable=2 got effectuated.  This was probably what was
  intended with the fix for CVE-2015-1324, but the check that was created
  does not catch all cases of tainted processes.  A better approach would
  be to let Apport read out "%d" from core(5) through "kernel.core_pattern"
  and if it returns "2", not write a core dump file.  Note however that
  "%d" is only present since kernel version 3.7, and would thus not work
  on Ubuntu 12.04 LTS systems running a 3.2 "GA" (General Availability)
  kernel from earlier Ubuntu 12.04.x LTS releases (as opposed to such
  systems running a 3.13 "HWE" (Hardware Enablement Stack) kernel from
  later Ubuntu 12.04.x LTS releases).

  Issue 2 (CVE-2017-14179): Apport lacking container / PID namespace support
  and
  Issue 3 (CVE-2017-14180): Apport broken container / PID namespace support
  -

  Exploitation types: container escape, privilege escalation, full disk
  DoS.

  Ubuntu releases affected: 12.04 LTS (ESM), 16.04 LTS, 17.04, 17.10.
  Note: exploitable on default OS installations.

  Description:

  Issue 2 (CVE-2017-14179):
  Ubuntu 12.04 LTS: Apport does not recognize ("support")
  PID namespaces / containers.

  Issue 3 (CVE-2017-14180):
  

[Touch-packages] [Bug 1732513] [NEW] Unable to access windows on second display

[Andrew Vian]

Public bug reported:

I am running Ubuntu 16.04.3 on a Macbook Pro using a dock with two
monitors. While docked, the internal display is not operational, instead
using only the two monitors. I have repeatedly encountered issues where
application windows that are active on the left display are not
selectable with the mouse. I can still use the Unity launcher bar and
the top menu bar but not any open windows. The windows on the right
monitor still work properly. If I drag applications from the right
display to the left display, that application also becomes unclickable
with the mouse. Windows that span across both display and clickable on
the right display, but not the left display. This behavior happens
occasionally (about once a week) with any running applications, and I
have not been able to cause the behavior repeatably. I can still use the
applications by using the Unity launcher to switch to the application,
then using keyboard commands. I would note that usually when this
happens, I have a Windows virtual machine running in Virtualbox. I'm not
sure if that is related or just a coincidence. At times, I can get the
OS operating correctly again by closing all open application windows.
Other times, it requires a complete reboot to restore operation to the
left side monitor.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Nov 15 11:39:50 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00f7]
 NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2]
InstallationDate: Installed on 2016-05-04 (559 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Apple Inc. MacBookPro10,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=398390d3-f6be-4e80-8a20-f036f9ec4d26 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B09.1506081405
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B09.1506081405:bd06/08/2015:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Nov 15 11:32:04 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu1~16.04.4

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install ubuntu 
xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 238755] RE

[Kennedyshead]

Check 
Re: Jag klarar inte plдdar mцte idag

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

Title:
  'Account has expired' message when adding a new user, after "passwd -l
  root"

Status in landscape-client package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in landscape-client source package in Hardy:
  Won't Fix
Status in shadow source package in Hardy:
  Won't Fix
Status in landscape-client source package in Intrepid:
  Invalid
Status in shadow source package in Intrepid:
  Fix Released
Status in shadow package in Debian:
  Fix Released

Bug description:
  Binary package hint: adduser

  I've repeatedly added new users, but receive a seemingly spurious
  error:

  rich@aias:~$ sudo adduser james
  Adding user `james' ...
  Adding new group `james' (1004) ...
  Adding new user `james' (1004) with group `james' ...
  Creating home directory `/home/james' ...
  Copying files from `/etc/skel' ...
  Enter new UNIX password: 
  Retype new UNIX password: 
  passwd: password updated successfully
  Your account has expired; please contact your system administrator
  chfn: PAM authentication failed
  adduser: `/usr/bin/chfn james' returned error code 1. Exiting.

  However, the user can log in.

  rich@aias:~$ finger james
  Login: james  Name: 
  Directory: /home/jamesShell: /bin/bash
  On since Mon Jun  9 21:19 (PDT) on tty1   4 minutes 57 seconds idle
   (messages off)
  No mail.
  No Plan.

  adduser version: 3.105ubuntu1
  ubuntu version: 8.04 , fully updated

  I've marked this as a security issue, since pam is part of the error
  message.

  Update:

  This seems to be related to the use of "passwd -l root".
  Until the Debian fix shows up in hardy, here is a workaround, thanks to 
Nicolas François:

   sudo passwd --unlock root
   sudo usermod --lock root

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

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

[Touch-packages] [Bug 411688] Re: pulseaudio floods network with multicast packets

[Mark Stosberg]

I ran into this flooding today on Ubuntu 17.10. This "fixed" it, at
least temporarily:

pactl unload-module module-rtp-send

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

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d17 4000 0111 2d65 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 efee 800a ee96
0x0020:  0071 b380 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 

[Touch-packages] [Bug 774071] Re: Indicator-datetime-service renders 100% CPU usage

[Anders Hall]

(#51 was a mistake)

Sorry, wrote incorrect. Reported for 17.04 LTS above.

Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show
a clock in the menu bar" in System Settings for Time & Date. Worked
after cold reboot.

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

Title:
  Indicator-datetime-service renders 100% CPU usage

Status in Indicator Date and Time:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: indicator-datetime

  On my laptop "indicator-datetime-service" occasionally make my CPU to
  use 100% of its resources. It does not happen every time I log in to
  Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill
  the process. If it helps, I've noticed in "System Monitor" that there
  are two instances of "indicator-datetime-service" running, but only
  one of them is hogging recourses. So far I was unable to determine
  after what actions/events this bug pups up.

  I'm using Ubuntu 11.04 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: indicator-datetime 0.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Apr 30 15:27:58 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/774071/+subscriptions

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

[Touch-packages] [Bug 774071] Re: Indicator-datetime-service renders 100% CPU usage

[Anders Hall]

Sorry, wrote incorrect. Reported for 17.04 LTS above.

Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the t

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

Title:
  Indicator-datetime-service renders 100% CPU usage

Status in Indicator Date and Time:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: indicator-datetime

  On my laptop "indicator-datetime-service" occasionally make my CPU to
  use 100% of its resources. It does not happen every time I log in to
  Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill
  the process. If it helps, I've noticed in "System Monitor" that there
  are two instances of "indicator-datetime-service" running, but only
  one of them is hogging recourses. So far I was unable to determine
  after what actions/events this bug pups up.

  I'm using Ubuntu 11.04 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: indicator-datetime 0.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Apr 30 15:27:58 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/774071/+subscriptions

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

[Touch-packages] [Bug 1731939] Re: Indicator-datetime-service renders 25% CPU usage and 100% RAM

[Anders Hall]

Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show
a clock in the menu bar" in System Settings for Time & Date. Worked
after cold reboot.

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

Title:
   Indicator-datetime-service renders 25% CPU usage and 100% RAM

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Same as Bug #774071 but with 100% RAM instead. Collected info while
  the Indicator-datetime-service was acting up. I.e., writing this with
  a few hundred megabytes RAM available..

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Nov 13 15:41:39 2017
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2015-07-18 (848 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago)

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

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

[Touch-packages] [Bug 1726318] Re: Destructive actions on headerbar aren't properly themed

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

Accepted ubuntu-themes into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/16.10+17.10.20171115-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Destructive actions on headerbar aren't properly themed

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [ Impact ]

  On simple scan (for example) there's a .destructive-action button in
  the headerbar and it's not drawn as red unless the button is hovered,
  clicked or unfocused. It also uses inconsistent gradients

  [ Test case ]

  1. Run gnome-scan
  2. Start a scan session (or use the inspector to set the "Stop" button as 
visible)
  3. Expect it to be red in all the cases (focused, pressed, unfocused, hovered)

  [ Regression Potential]

  Destructive buttons in headerbar could be broken

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

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

[Touch-packages] [Bug 1721102] Re: Thin line at the left of Simple Scan's "Scan" headerbar button

[Łukasz Zemczak]

Hello Jean-Baptiste, or anyone else affected,

Accepted ubuntu-themes into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/16.10+17.10.20171115-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Thin line at the left of Simple Scan's "Scan" headerbar button

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  There is a thin colored line (green or red) at the left of rounded button, 
for example in simple-scan in the screenshot attached (I didn't find any other 
app affected ATM)

  [Test case]
  1. Run simple scan
  2. Expect "Scan" button background color to fill all the space.

  4. Start scanning and expect the same for "Stop" button too

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170930-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 20:16:32 2017
  InstallationDate: Installed on 2013-09-03 (1490 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719355] Re: Switcher widget background goes outside its border

[Łukasz Zemczak]

Hello Carlo, or anyone else affected,

Accepted ubuntu-themes into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/16.10+17.10.20171115-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Switcher widget background goes outside its border

Status in Ubuntu theme:
  In Progress
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  In both Ambiance and Radiance themes, the switcher background is
  visible outside the widget border when inside a headerbar.

  See picture from Gnome Control Settings -> Search

  [Test case]

  1. Open Gnome Control Settings -> Search
  2. Ensure that no extra border is around the switcher (especially in the 
headerbar)

  [Regression potential]

  Switchers  borders are incorrect

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

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

[Touch-packages] [Bug 1724808] Re: osd progress looks odd using Ambiance or Radiance

[Łukasz Zemczak]

Hello Andrea, or anyone else affected,

Accepted ubuntu-themes into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/16.10+17.10.20171115-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  osd progress looks odd using Ambiance or Radiance

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  == Impact ==
  osd progress bars look poor with Ambiance or Radiance in Ubuntu 17.10.
  osd progress bars are used e.g. in epiphany web browser.

  == Test Case ==
  1. Open gnome control center
  2. Go to online accounts panel
  3. Add a google account
  4. Make sure the progress bar close to the title bar of the login dialog does 
not present borders and paddings.

  == Potential Regressions ==
  Please check thare are no regressions with osd toolbars. An example of 
application using osd toolbars is totem. Make sure the overlay with play/pause 
controls is not affected by the fix.

  == Original Bug Report ==
  osd progress bar, used e.g. the one used by epiphany-browser when loading 
pages, looks odd with Ambiance or Radiance.

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

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

[Touch-packages] [Bug 1726322] Re: Suggested and Destructive action buttons in headerbar have wrong gradients in maximized windows

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

Accepted ubuntu-themes into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/16.10+17.10.20171115-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Suggested and Destructive action buttons in headerbar have wrong
  gradients in maximized windows

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Suggested and Desctructive action (simple-scan is an example for both)
  buttons still have the "normal" gradient when the window is maximized,
  while this should be inverted.

  See https://usercontent.irccloud-cdn.com/file/hm2uCy3D/image.png
  (shown both for reference)

  [Test case]

  1. Run simple scan
  2. Maximize the window
  3. The gradient should have consistent direction with other buttons around

  [Regression potential]

  Background gradients for windows with such buttons might be wrong in
  normal windows.

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

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

[Touch-packages] [Bug 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[Łukasz Zemczak]

Hello dino99, or anyone else affected,

Accepted ubuntu-themes into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/16.10+17.10.20171115-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1726322] Re: Suggested and Destructive action buttons in headerbar have wrong gradients in maximized windows

[Łukasz Zemczak]

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-themes/artful

** Also affects: ubuntu-themes (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

Title:
  Suggested and Destructive action buttons in headerbar have wrong
  gradients in maximized windows

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Suggested and Desctructive action (simple-scan is an example for both)
  buttons still have the "normal" gradient when the window is maximized,
  while this should be inverted.

  See https://usercontent.irccloud-cdn.com/file/hm2uCy3D/image.png
  (shown both for reference)

  [Test case]

  1. Run simple scan
  2. Maximize the window
  3. The gradient should have consistent direction with other buttons around

  [Regression potential]

  Background gradients for windows with such buttons might be wrong in
  normal windows.

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

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

[Touch-packages] [Bug 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: New => Confirmed

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1724808] Re: osd progress looks odd using Ambiance or Radiance

[Łukasz Zemczak]

** Also affects: ubuntu-themes (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

Title:
  osd progress looks odd using Ambiance or Radiance

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  New

Bug description:
  == Impact ==
  osd progress bars look poor with Ambiance or Radiance in Ubuntu 17.10.
  osd progress bars are used e.g. in epiphany web browser.

  == Test Case ==
  1. Open gnome control center
  2. Go to online accounts panel
  3. Add a google account
  4. Make sure the progress bar close to the title bar of the login dialog does 
not present borders and paddings.

  == Potential Regressions ==
  Please check thare are no regressions with osd toolbars. An example of 
application using osd toolbars is totem. Make sure the overlay with play/pause 
controls is not affected by the fix.

  == Original Bug Report ==
  osd progress bar, used e.g. the one used by epiphany-browser when loading 
pages, looks odd with Ambiance or Radiance.

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

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

[Touch-packages] [Bug 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[Łukasz Zemczak]

** Also affects: ubuntu-themes (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719355] Re: Switcher widget background goes outside its border

[Łukasz Zemczak]

** Also affects: ubuntu-themes (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

Title:
  Switcher widget background goes outside its border

Status in Ubuntu theme:
  In Progress
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  New

Bug description:
  [Impact]

  In both Ambiance and Radiance themes, the switcher background is
  visible outside the widget border when inside a headerbar.

  See picture from Gnome Control Settings -> Search

  [Test case]

  1. Open Gnome Control Settings -> Search
  2. Ensure that no extra border is around the switcher (especially in the 
headerbar)

  [Regression potential]

  Switchers  borders are incorrect

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

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

[Touch-packages] [Bug 1726318] Re: Destructive actions on headerbar aren't properly themed

[Łukasz Zemczak]

** Also affects: ubuntu-themes (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

Title:
  Destructive actions on headerbar aren't properly themed

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  New

Bug description:
  [ Impact ]

  On simple scan (for example) there's a .destructive-action button in
  the headerbar and it's not drawn as red unless the button is hovered,
  clicked or unfocused. It also uses inconsistent gradients

  [ Test case ]

  1. Run gnome-scan
  2. Start a scan session (or use the inspector to set the "Stop" button as 
visible)
  3. Expect it to be red in all the cases (focused, pressed, unfocused, hovered)

  [ Regression Potential]

  Destructive buttons in headerbar could be broken

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

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

[Touch-packages] [Bug 1724604] Re: umockdev 0.9.4-1 causes test suite failures in fwupd

[Mario Limonciello]

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

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

Title:
  umockdev 0.9.4-1 causes test suite failures in fwupd

Status in umockdev:
  Fix Released
Status in umockdev package in Ubuntu:
  Won't Fix

Bug description:
  Updating to umockdev 0.9.4-1 is causing failures in the fwupd test
  suite (which will lead to FTBFS on fwupd)

  The output from the failed tests:
   8/10 thunderbolt-self-test   FAIL 0.20 s
  --- command ---
  LD_PRELOAD='libumockdev-preload.so.0' 
/build/build/obj-x86_64-linux-gnu/plugins/thunderbolt/thunderbolt-self-test
  --- stderr ---
  
(/build/build/obj-x86_64-linux-gnu/plugins/thunderbolt/thunderbolt-self-test:1058):
 FuPluginThunderbolt-WARNING **: Need to run within umockdev wrapper 
(umockdev-wrapper thunderbolt-self-test)!

  It worked properly with the previous version.

  Interestingly enough it works properly in Debian with 0.9.4-1.

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

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

[Touch-packages] [Bug 1724604] Re: umockdev 0.9.4-1 causes test suite failures in fwupd

[Bug Watch Updater]

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

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

Title:
  umockdev 0.9.4-1 causes test suite failures in fwupd

Status in umockdev:
  Fix Released
Status in umockdev package in Ubuntu:
  New

Bug description:
  Updating to umockdev 0.9.4-1 is causing failures in the fwupd test
  suite (which will lead to FTBFS on fwupd)

  The output from the failed tests:
   8/10 thunderbolt-self-test   FAIL 0.20 s
  --- command ---
  LD_PRELOAD='libumockdev-preload.so.0' 
/build/build/obj-x86_64-linux-gnu/plugins/thunderbolt/thunderbolt-self-test
  --- stderr ---
  
(/build/build/obj-x86_64-linux-gnu/plugins/thunderbolt/thunderbolt-self-test:1058):
 FuPluginThunderbolt-WARNING **: Need to run within umockdev wrapper 
(umockdev-wrapper thunderbolt-self-test)!

  It worked properly with the previous version.

  Interestingly enough it works properly in Debian with 0.9.4-1.

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

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

[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32

---
nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

 -- Mathieu Trudel-Lapierre   Tue, 14 Nov 2017
08:53:51 -0500

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

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

Title:
  enabling networkd appears to eat up entropy

Status in nplan package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in nplan source package in Xenial:
  New
Status in openssh source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  New
Status in openssh source package in Zesty:
  New
Status in systemd source package in Zesty:
  New
Status in nplan source package in Artful:
  In Progress
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Triaged
Status in nplan source package in Bionic:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  Booting systems have a limited amount of entropy, especially in some of the 
cloud cases. We should avoid using it up unnecessarily.

  [Test cases]

  == netplan ==
  1) Boot system with netplan config; using networkd renderer
  2) Validate that it starts and does not cause undue delay.
  2b) strace nplan at boottime (the netplan generator at 
/lib/systemd/system-generators/netplan) and validate it does not call 
get_random() / uuid_generate().
  3) Validate that config with NetworkManager renderer generates UUIDs.

  [Regression potential]
  Netplan depends on UUID generation to create correct networkManager 
configuration for VLANs. This is a specific use-case that is typically not hit, 
but any failure to generate valid NetworkManager configuration would be a 
regression from this SRU.

  ---

  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

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

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

[Touch-packages] [Bug 1732489] [NEW] TMPTIME is not honoured

[Ken Sharp]

Public bug reported:

TMPTIME is incorrectly migrated on an upgrade from Trusty to Xenial.

tmp.conf uses D where it should be d. This also has the effect of wiping
/tmp no matter what.

This is fixed in Debian.

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

This could result in data loss, although storing non-volatile files in
/tmp is madness.

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

** Affects: systemd (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: xenial

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

** Also affects: systemd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795269
   Importance: Unknown
   Status: Unknown

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

Title:
  TMPTIME is not honoured

Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  Unknown

Bug description:
  TMPTIME is incorrectly migrated on an upgrade from Trusty to Xenial.

  tmp.conf uses D where it should be d. This also has the effect of
  wiping /tmp no matter what.

  This is fixed in Debian.

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

  This could result in data loss, although storing non-volatile files in
  /tmp is madness.

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

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

[Touch-packages] [Bug 1732410] Re: connecting dock hangs system

[Brian Murray]

** Tags added: artful

** Package changed: ubuntu => xorg (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/1732410

Title:
  connecting dock hangs system

Status in xorg package in Ubuntu:
  New

Bug description:
  Description of problem:
  connection usb type c dock with 2 displays attached freezes the system and 
requires cold boot. sometimes only disconnecting the dock makes the system 
usable again, sometimes not. sometime the dock works with only 1 display 
attached, sometimes even with both but 90% of the time connecting any display 
to the dock hangs the system (or booting ubuntu with the dock and displays 
already connected makes the system unbootable). 
  dock is https://us-store.acer.com/acer-usb-type-c-dock

  Version-Release number of selected component (if applicable):
  Ubuntu 17.10

  Steps to Reproduce:
  1. Connect Dock
  2. Experience Crash

  Actual results:
  crash

  Expected results:
  Working dock with external displays

  
  Additional info:
  works fine under windows. crashes X and wayland.

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

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

[Touch-packages] [Bug 1732410] [NEW] connecting dock hangs system

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Description of problem:
connection usb type c dock with 2 displays attached freezes the system and 
requires cold boot. sometimes only disconnecting the dock makes the system 
usable again, sometimes not. sometime the dock works with only 1 display 
attached, sometimes even with both but 90% of the time connecting any display 
to the dock hangs the system (or booting ubuntu with the dock and displays 
already connected makes the system unbootable). 
dock is https://us-store.acer.com/acer-usb-type-c-dock

Version-Release number of selected component (if applicable):
Ubuntu 17.10

Steps to Reproduce:
1. Connect Dock
2. Experience Crash

Actual results:
crash

Expected results:
Working dock with external displays


Additional info:
works fine under windows. crashes X and wayland.

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


** Tags: artful bot-comment
-- 
connecting dock hangs system
https://bugs.launchpad.net/bugs/1732410
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1732484] Re: package libperl5.22 5.22.1-9 [modified: usr/share/doc/libperl5.22/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in perl package in Ubuntu:
  New

Bug description:
  Ubuntu bug reporting guidelines:

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
  Uname: Linux 4.4.0-100-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov 15 16:09:42 2017
  DuplicateSignature:
   package:libperl5.22:5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz]
   Unpacking libperl5.22:amd64 (5.22.1-9ubuntu0.2) over (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9ubuntu0.2_amd64.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:amd64
  InstallationDate: Installed on 2014-07-21 (1213 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', 
which is different from other instances of package libperl5.22:amd64
  UpgradeStatus: Upgraded to xenial on 2017-08-02 (105 days ago)

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

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

[Touch-packages] [Bug 1732484] [NEW] package libperl5.22 5.22.1-9 [modified: usr/share/doc/libperl5.22/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libper

[Andrea]

Public bug reported:

Ubuntu bug reporting guidelines:

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libperl5.22 5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
Uname: Linux 4.4.0-100-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Nov 15 16:09:42 2017
DuplicateSignature:
 package:libperl5.22:5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz]
 Unpacking libperl5.22:amd64 (5.22.1-9ubuntu0.2) over (5.22.1-9) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9ubuntu0.2_amd64.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', 
which is different from other instances of package libperl5.22:amd64
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:amd64
InstallationDate: Installed on 2014-07-21 (1213 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: perl
Title: package libperl5.22 5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', 
which is different from other instances of package libperl5.22:amd64
UpgradeStatus: Upgraded to xenial on 2017-08-02 (105 days ago)

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


** Tags: amd64 apport-package package-conflict xenial

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

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

Status in perl package in Ubuntu:
  New

Bug description:
  Ubuntu bug reporting guidelines:

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
  Uname: Linux 4.4.0-100-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov 15 16:09:42 2017
  DuplicateSignature:
   package:libperl5.22:5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz]
   Unpacking libperl5.22:amd64 (5.22.1-9ubuntu0.2) over (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9ubuntu0.2_amd64.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:amd64
  InstallationDate: Installed on 2014-07-21 (1213 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', 
which is different from other instances of package libperl5.22:amd64
  UpgradeStatus: Upgraded to xenial on 2017-08-02 (105 days ago)

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

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

[Touch-packages] [Bug 1728791] Re: [SRU] pulseaudio-droid module crashes on start

[Jonathan Riddell]

I've uploaded
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.7 with
only this debdiff.  Please test it still works


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

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

Title:
  [SRU] pulseaudio-droid module crashes on start

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4

  [Impact]

   * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) 
from using the pulseaudio-modules-droid on android devices.
   * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates 
enabled.
   * Last 3 releases of pulseaudio included multiple patches which modified 
behavior of pulsecore library but required changes were not made in 
pulseaudio-module-droid.
   * This results in crash in pulseaudio-modules-droid

  
  #0  init_profile (u=0x59528) at modules/droid/module-droid-card.c:370
  #1  module_droid_card_22_LTX_pa__init (m=0x3c3f8) at 
modules/droid/module-droid-card.c:923
  #2  0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 
"module-droid-card-22", argument=0x0) at pulsecore/module.c:180
  #3  0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, 
fail=0x3c1f4) at pulsecore/cli-command.c:439
  #4  0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at 
pulsecore/cli-command.c:2134
  #5  0xf76f6fc8 in pa_cli_command_execute_line (c=, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155
  #6  0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module 
module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153
  #7  0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at 
pulsecore/ioline.c:269
  #8  do_read (l=0x3c208) at pulsecore/ioline.c:337
  #9  do_work (l=0x3c208) at pulsecore/ioline.c:386
  #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655
  #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898
  #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, 
retval=0xfffef1c4) at pulse/mainloop.c:929
  #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, 
retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944
  #14 0x000158ca in main (argc=, argv=) at 
daemon/main.c:1152

  
  [Test Case]

   * Start pulseaudio
   * From another session run pacmd
   * In prompt type load-module module-droid-discover
   * On ubuntu touch devices, it will crash at startup

  [Regression Potential]

   * There is no regression potential for other parts of pulseaudio
  components.

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

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

[Touch-packages] [Bug 1732416] Re: two cursors on dual screen setup

[Lars Pedersen]

Works with xorgs for me. Guess this is a wayland issue

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

Title:
  two cursors on dual screen setup

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My secondary monitor (in portrait mode) is left of the primary
  monitor. When I move the cursor into the top left corner of my
  primary, a second cursor will show up on my secondary screen. It has
  no function, its just there. The area is about 4cm x 10cm starting at
  the top left corner. The second cursor is rotated to the left. Doesn't
  happen if I move the secondary screen to the right of my primary.
  Disappears when I move the cursor onto second screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 12:12:20 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:120f]
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a2c4c090-f120-42fb-895f-11cfe3a2bfe4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: Z270M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/27/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Konrad Zapałowicz]

The only relevant log files that can be provided for this issue is a HCI
trace. It is in .snoop format therefore can be viewed in wireshark.

Attaching two log files:

1) failure-case: without proposed patch
2) success-case: with proposed patch

** Attachment added: "1731467-success-case.snoop"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+attachment/5009472/+files/1731467-success-case.snoop

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  Confirmed

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth=150824844606937=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

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

[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Konrad Zapałowicz]

** Attachment added: "1731467-failure-case.snoop"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+attachment/5009473/+files/1731467-failure-case.snoop

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

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  Confirmed

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth=150824844606937=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

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

[Touch-packages] [Bug 1679989] Re: CVE-2016-10165: heap OOB read parsing crafted ICC profile

[Jeremy Bicha]

** No longer affects: lcms2 (Ubuntu Yakkety)

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

Title:
  CVE-2016-10165: heap OOB read parsing crafted ICC profile

Status in lcms2 package in Ubuntu:
  Confirmed
Status in lcms2 source package in Precise:
  Confirmed
Status in lcms2 source package in Trusty:
  Confirmed
Status in lcms2 source package in Xenial:
  Confirmed
Status in lcms2 source package in Zesty:
  Confirmed
Status in lcms2 source package in Artful:
  Confirmed
Status in lcms2 package in Debian:
  Fix Released

Bug description:
  The Type_MLU_Read function in cmstypes.c in Little CMS (aka lcms2)
  allows remote attackers to obtain sensitive information or cause a
  denial of service via an image with a crafted ICC profile, which
  triggers an out-of-bounds heap read.

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

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

[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Stefan Bader]

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

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

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  New

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth=150824844606937=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

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

[Touch-packages] [Bug 1732416] Re: two cursors on dual screen setup

[Launchpad Bug Tracker]

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

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

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

Title:
  two cursors on dual screen setup

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My secondary monitor (in portrait mode) is left of the primary
  monitor. When I move the cursor into the top left corner of my
  primary, a second cursor will show up on my secondary screen. It has
  no function, its just there. The area is about 4cm x 10cm starting at
  the top left corner. The second cursor is rotated to the left. Doesn't
  happen if I move the secondary screen to the right of my primary.
  Disappears when I move the cursor onto second screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 12:12:20 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:120f]
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a2c4c090-f120-42fb-895f-11cfe3a2bfe4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: Z270M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/27/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1732447] [NEW] rename no longer included in perl package, but still linked

[Justin Luth]

Public bug reported:

typing "rename" in a terminal responds with...
 
The program 'rename' can be found in the following packages:
 * perl
 * rename
Ask your administrator to install one of them

...but perl is already installed.  Internet reports suggest this has
started in 17.10.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: perl 5.26.0-8ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
Date: Wed Nov 15 16:24:29 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_PAPER=en_GB.UTF-8
SourcePackage: perl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  rename no longer included in perl package, but still linked

Status in perl package in Ubuntu:
  New

Bug description:
  typing "rename" in a terminal responds with...
   
  The program 'rename' can be found in the following packages:
   * perl
   * rename
  Ask your administrator to install one of them

  ...but perl is already installed.  Internet reports suggest this has
  started in 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: perl 5.26.0-8ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Wed Nov 15 16:24:29 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   LC_PAPER=en_GB.UTF-8
  SourcePackage: perl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1728188] Re: Don't build pulseaudio with trust-store support

[Łukasz Zemczak]

@vanvugt Any update on this? We would like to get rid of trust-store as
soon as possible and its built-in support in pulseaudio is making things
blocked. We need to get rid of trust-store for the boost transition.

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

Title:
  Don't build pulseaudio with trust-store support

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Please check whether we still need to build pulseaudio with trust-
  store support or if we can drop it and remove trust-store from Ubuntu.

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

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

[Touch-packages] [Bug 1732416] Re: two cursors on dual screen setup

[Benedikt Kentsch]

works fine now with the proprietary nvidia driver instead of nouveau

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

Title:
  two cursors on dual screen setup

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My secondary monitor (in portrait mode) is left of the primary
  monitor. When I move the cursor into the top left corner of my
  primary, a second cursor will show up on my secondary screen. It has
  no function, its just there. The area is about 4cm x 10cm starting at
  the top left corner. The second cursor is rotated to the left. Doesn't
  happen if I move the secondary screen to the right of my primary.
  Disappears when I move the cursor onto second screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 12:12:20 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:120f]
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a2c4c090-f120-42fb-895f-11cfe3a2bfe4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: Z270M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/27/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1732416] Re: two cursors on dual screen setup

[Benedikt Kentsch]

or xorg instead of wayland...

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

Title:
  two cursors on dual screen setup

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My secondary monitor (in portrait mode) is left of the primary
  monitor. When I move the cursor into the top left corner of my
  primary, a second cursor will show up on my secondary screen. It has
  no function, its just there. The area is about 4cm x 10cm starting at
  the top left corner. The second cursor is rotated to the left. Doesn't
  happen if I move the secondary screen to the right of my primary.
  Disappears when I move the cursor onto second screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 12:12:20 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:120f]
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a2c4c090-f120-42fb-895f-11cfe3a2bfe4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: Z270M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/27/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 723739] Re: Cannot cross compile 32-bit curl apps on x86_64

[Vadim Kotov]

Issue in curl's Github repo -- https://github.com/curl/curl/issues/1456

** Bug watch added: github.com/curl/curl/issues #1456
   https://github.com/curl/curl/issues/1456

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

Title:
  Cannot cross compile 32-bit curl apps on x86_64

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Cross compiling (-m32) a 32-bit application that relies on libcurl in
  a 64-bit host fails with:

  In file included from /usr/include/curl/curl.h:35,
   from :
  /usr/include/curl/curlrules.h:143: error: size of array '__curl_rule_01__' is 
negative
  /usr/include/curl/curlrules.h:153: error: size of array '__curl_rule_02__' is 
negative

  This is due to libcurl's installation of a generated, architecture
  dependent, header file "curlbuild.h". Design decisions aside, I think
  the package should handle this so the user doesn't have to install a
  parallel installation of 32-bit libcurl to cross-compile curl apps.

  One possible solution is to the use approach Fedora takes and install
  both curlbuild.h's side-by-side and switch on __WORDSIZE:

  $ ls /usr/include/curl/curlbuild*
  /usr/include/curl/curlbuild-32.h /usr/include/curl/curlbuild-64.h 
/usr/include/curl/curlbuild.h

  $ cat /usr/include/curl/curlbuild.h
  #include 

  #if __WORDSIZE == 32
  #include "curlbuild-32.h"
  #elif __WORDSIZE == 64
  #include "curlbuild-64.h"
  #else
  #error "Unknown word size"
  #endif

  There is also a forum thread discussing this same issue:
  http://ubuntuforums.org/showthread.php?t=1680426

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

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

[Touch-packages] [Bug 1730536] Re: "Unable to open external link" in Evince when google-chrome-unstable is the default browser

[intrigeri]

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

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

Title:
  "Unable to open external link" in Evince when google-chrome-unstable
  is the default browser

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor package in Debian:
  Confirmed

Bug description:
  TO REPRODUCE:

  I attempt to open a URL from a PDF document in Evince.

  
  EXPECTED:

  The browser opens the URL.

  
  OBSERVED:

  I'm shown an error message:

  Unable to open external link
  Failed to execute child process “/usr/bin/google-chrome-unstable” (Permission 
denied)

  journalctl shows:

  Nov 06 19:19:18 khaeru-laptop audit[22110]: AVC apparmor="DENIED" 
operation="exec" profile="/usr/bin/evince" 
name="/opt/google/chrome-unstable/google-chrome-unstable" pid=22110 
comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
  Nov 06 19:19:18 khaeru-laptop kernel: audit: type=1400 
audit(1510013958.773:590): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" 
name="/opt/google/chrome-unstable/google-chrome-unstable" pid=22110 
comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  
  EXTRA INFORMATION:

  - As the messages imply, I'm using Google Chrome "unstable".
  - The file
/usr/bin/google-chrome-unstable
…is symlinked to:
/opt/google/chrome-unstable/google-chrome-unstable
  - I note that previous bugs, eg. bug #964510, resulted in lines being added 
to 
/etc/apparmor.d/abstractions/ubuntu-helpers that refer to paths in
/opt/google/chrome/. This directory does not exist on my system.

  $ lsb_release -rd && apt-cache policy apparmor evince google-chrome-unstable 
  Description:Ubuntu 17.10
  Release:17.10
  apparmor:
Installed: 2.11.0-2ubuntu17
Candidate: 2.11.0-2ubuntu17
Version table:
   *** 2.11.0-2ubuntu17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  evince:
Installed: 3.26.0-1
Candidate: 3.26.0-1
Version table:
   *** 3.26.0-1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  google-chrome-unstable:
Installed: 64.0.3251.0-1
Candidate: 64.0.3253.3-1
Version table:
   64.0.3253.3-1 500
  500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
   *** 64.0.3251.0-1 100
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor 2.11.0-2ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 19:20:34 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (26 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=39ca3c53-0313-4699-a5da-403522e2ff14 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to artful on 2017-10-19 (18 days ago)

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

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

[Touch-packages] [Bug 1732416] Re: two cursors on dual screen setup

[Lars Pedersen]

Just upgraded to fedora 27 and got the exact same problem in a dual
setup where the left monitor is in portrait mode.

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

Title:
  two cursors on dual screen setup

Status in xorg package in Ubuntu:
  New

Bug description:
  My secondary monitor (in portrait mode) is left of the primary
  monitor. When I move the cursor into the top left corner of my
  primary, a second cursor will show up on my secondary screen. It has
  no function, its just there. The area is about 4cm x 10cm starting at
  the top left corner. The second cursor is rotated to the left. Doesn't
  happen if I move the secondary screen to the right of my primary.
  Disappears when I move the cursor onto second screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 12:12:20 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:120f]
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a2c4c090-f120-42fb-895f-11cfe3a2bfe4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: Z270M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/27/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

[Dan]

This may be a duplicate of bug 1660100.

However, I'm also suffering from the same issue. But I'd like to add
that, after trying to edit any of the entries and clicking "OK" in the
dialog that shows up, the password prompts shows up. After we input the
password, the ability to check/uncheck entries in the "Other Software"
tab becomes possible.

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1732422] [NEW] glue-sprite: Inconsistent dependencies

[Evgeniy Egorov]

Public bug reported:

It's about the glue-sprite package (sudo apt install glue-sprite).
The latest version of glue-sprite (0.11.1) does not work due to the dependency:
Python package (/usr/lib/python3/dist-packages/glue-0.11.1.egg-info) depends on 
Jinja2>=2.7,<2.8 (requires.txt) but there is no appropriate version

/etc/apt$ sudo dpkg -l | grep jinj
ii  python3-jinja2   2.8-1  all 
 small but fast and easy to use stand-alone template engine

So the dependancy is "Jinja2>=2.7,<2.8" but the latest version is 2.8-1
!

The original bug on Debian is here https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=860169

System info:
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

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

** Description changed:

  It's about the glue-sprite package (sudo apt install glue-sprite).
  The latest version of glue-sprite (0.11.1) does not work due to the 
dependency:
  Python package (/usr/lib/python3/dist-packages/glue-0.11.1.egg-info) depends 
on Jinja2>=2.7,<2.8 (requires.txt) but there is no appropriate version
  
  /etc/apt$ sudo dpkg -l | grep jinj
  ii  python3-jinja2   2.8-1  all   
   small but fast and easy to use stand-alone template engine
+ 
+ So the dependancy is "Jinja2>=2.7,<2.8" but the latest version is 2.8-1
+ !
  
  The original bug on Debian is here https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=860169
  
  System info:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

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

Title:
  glue-sprite: Inconsistent dependencies

Status in apport package in Ubuntu:
  New

Bug description:
  It's about the glue-sprite package (sudo apt install glue-sprite).
  The latest version of glue-sprite (0.11.1) does not work due to the 
dependency:
  Python package (/usr/lib/python3/dist-packages/glue-0.11.1.egg-info) depends 
on Jinja2>=2.7,<2.8 (requires.txt) but there is no appropriate version

  /etc/apt$ sudo dpkg -l | grep jinj
  ii  python3-jinja2   2.8-1  all   
   small but fast and easy to use stand-alone template engine

  So the dependancy is "Jinja2>=2.7,<2.8" but the latest version is
  2.8-1 !

  The original bug on Debian is here https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=860169

  System info:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

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

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

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

[Marius Gedminas]

This happened again, while trying to upgrade libpq-dev libpq5
postgresql-9.3 postgresql-client-9.3.

Running `unattended-upgrade -v` over an interactive SSH session
succeeded.

I'm not sure what's different.  Locale?  The successful installation log
contains some non-ASCII characters, specifically dpkg's

(Skaitoma duomenų bazė ... 53857 files and directories currently
installed.)

But if that were the problem, then every upgrade would fail, not just
some of them.  (Besides, if the locale were missing from the cron
environment, dpkg wouldn't be using translations.)

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

Title:
  Unattended upgrade fails with "Error in function"

Status in unattended-upgrades package in Ubuntu:
  Confirmed

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

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

  Unattended upgrade returned: False

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

  Package installation log:
  Error in function:

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

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

  Error in function:

  That's it.

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

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

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

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

[Touch-packages] [Bug 1689585] Re: ntp doesn't unload its apparmor profile on purge

[ChristianEhrhardt]

How about suggesting the following to openntpd in Debian then?
Simon would you be so kind and open a bug there if that would find a consensus?

diff --git a/debian/openntpd.preinst b/debian/openntpd.preinst
index 4cb3147..3e55947 100644
--- a/debian/openntpd.preinst
+++ b/debian/openntpd.preinst
@@ -7,6 +7,12 @@ if dpkg-maintscript-helper supports rm_conffile 2>/dev/null; 
then
 dpkg-maintscript-helper rm_conffile /etc/apparmor.d/usr.sbin.ntpd 
1:5.7p4-1 -- "$@"
 fi
 
+# due to former installations of ntp the system could still have an apparmor
+# loaded at the shared binary path /usr/sbin/ntpd. There are various reasons
+# discussed that dh_appamor nor ntp can unload it. But it could block openntp
+# to work, so remove it unconditionally.
+echo -n /usr/sbin/ntpd > /sys/kernel/security/apparmor/.remove 2>/dev/null || 
/bin/true
+
 #DEBHELPER#
 
 exit 0

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

Title:
  ntp doesn't unload its apparmor profile on purge

Status in apparmor package in Ubuntu:
  Won't Fix
Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1) install ntp
apt install ntp
  2) confirm it has loaded its AA profile
aa-status | grep ntpd
  3) purge ntp
apt purge ntp
  4) the profile is left behind but shouldn't
aa-status | grep ntpd


  Additional info:

  This was found by first install ntp then changing my mind and deciding to go 
with OpenNTPD.
  FYI, just installing openntpd while ntp is still there works because openntpd 
has a kludge
  to unload ntpd's profile but that only works if the ntp package wasn't purged 
before.

   /var/lib/dpkg/info/openntpd.preinst:
   if [ -f /etc/apparmor.d/usr.sbin.ntpd ] && pathfind apparmor_parser ; then
   apparmor_parser -R /etc/apparmor.d/usr.sbin.ntpd
   fi
   
  Since a purge deletes /etc/apparmor.d/usr.sbin.ntpd, openntpd.preinst's 
kludge is ineffective.
  In any case, having implementation B include workaround for implementation A 
not cleaning up
  after itself seems wrong and the issue should be fixed at the source IMHO.

  # lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  # apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p4+dfsg-3ubuntu5.4
Candidate: 1:4.2.8p4+dfsg-3ubuntu5.4
Version table:
   *** 1:4.2.8p4+dfsg-3ubuntu5.4 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:4.2.8p4+dfsg-3ubuntu5.3 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1:4.2.8p4+dfsg-3ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue May  9 15:48:42 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1732416] [NEW] two cursors on dual screen setup

[Benedikt Kentsch]

Public bug reported:

My secondary monitor (in portrait mode) is left of the primary monitor.
When I move the cursor into the top left corner of my primary, a second
cursor will show up on my secondary screen. It has no function, its just
there. The area is about 4cm x 10cm starting at the top left corner. The
second cursor is rotated to the left. Doesn't happen if I move the
secondary screen to the right of my primary. Disappears when I move the
cursor onto second screen.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 15 12:12:20 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:120f]
InstallationDate: Installed on 2017-11-15 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a2c4c090-f120-42fb-895f-11cfe3a2bfe4 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: Z270M-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/27/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  two cursors on dual screen setup

Status in xorg package in Ubuntu:
  New

Bug description:
  My secondary monitor (in portrait mode) is left of the primary
  monitor. When I move the cursor into the top left corner of my
  primary, a second cursor will show up on my secondary screen. It has
  no function, its just there. The area is about 4cm x 10cm starting at
  the top left corner. The second cursor is rotated to the left. Doesn't
  happen if I move the secondary screen to the right of my primary.
  Disappears when I move the cursor onto second screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 12:12:20 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:120f]
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a2c4c090-f120-42fb-895f-11cfe3a2bfe4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: Z270M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By 

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[dino99]

Colin, Steve

please do something about the message output that newbies does not
understand.

"locked by another process" that says it all; its enough for experienced
users, but let think the others there is a bug. This is not a bug
indeed, but a lack of user's knowledge.

"Resource temporarily unavailable" might not be scary for the crowd, but
some should possibly prefer something more informative, like "please
close first the other package manager, then you will be able to
continue"

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Invalid
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1732411] [NEW] On upgrade, daemon-reexec should only be issued if safe

[Pierre Schweitzer]

Public bug reported:

Dear all,

Following up the bug report #1713674, when executing systemd in a
hardened LXC context, it might not be suitable to reexec systemd daemon,
that would not be able to perform.

For instance, in our LXC, we drop several capabilities, including
sys_admin and we set /sys to read-only (in which, systemd will find its
cgroups). This means, systemd cannot be reexecuted, it will fail to
restart and will freeze (properly) at restart making the LXC container
in frozen state (still working, but no new services startable, no
interaction with systemd possible anymore).

When upgrading systemd the debian package, as postinst, will always
attempt to reexecute systemd, possibly breaking every other upgrade
where a daemon restart is made in postinst, and leaving the system in a
degraded state.

It would likely be appropriate the check whether the reexecute can work
will before performing it: checking capabilities, sys mount point perms,
etc. If not applicable, not performing a reexucte and possibly print a
message to the user.

Occurs with Ubuntu Xenial 16.04.3 LTS and systemd 229-4ubuntu21.

Cheers

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

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

Title:
  On upgrade, daemon-reexec should only be issued if safe

Status in systemd package in Ubuntu:
  New

Bug description:
  Dear all,

  Following up the bug report #1713674, when executing systemd in a
  hardened LXC context, it might not be suitable to reexec systemd
  daemon, that would not be able to perform.

  For instance, in our LXC, we drop several capabilities, including
  sys_admin and we set /sys to read-only (in which, systemd will find
  its cgroups). This means, systemd cannot be reexecuted, it will fail
  to restart and will freeze (properly) at restart making the LXC
  container in frozen state (still working, but no new services
  startable, no interaction with systemd possible anymore).

  When upgrading systemd the debian package, as postinst, will always
  attempt to reexecute systemd, possibly breaking every other upgrade
  where a daemon restart is made in postinst, and leaving the system in
  a degraded state.

  It would likely be appropriate the check whether the reexecute can
  work will before performing it: checking capabilities, sys mount point
  perms, etc. If not applicable, not performing a reexucte and possibly
  print a message to the user.

  Occurs with Ubuntu Xenial 16.04.3 LTS and systemd 229-4ubuntu21.

  Cheers

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[dino99]

** Changed in: aptdaemon
 Assignee: j.fred muggs (fredmuggs) => (unassigned)

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

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Invalid
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1732408] [NEW] package tzdata 2017c-0ubuntu0.16.04 failed to install/upgrade: нет доступа к архиву: Нет такого файла или каталога

[eugene.raynor]

Public bug reported:

during update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tzdata 2017c-0ubuntu0.16.04
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Nov 15 13:00:07 2017
ErrorMessage: нет доступа к архиву: Нет такого файла или каталога
InstallationDate: Installed on 2017-10-09 (37 days ago)
InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: tzdata
Title: package tzdata 2017c-0ubuntu0.16.04 failed to install/upgrade: нет 
доступа к архиву: Нет такого файла или каталога
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package tzdata 2017c-0ubuntu0.16.04 failed to install/upgrade: нет
  доступа к архиву: Нет такого файла или каталога

Status in tzdata package in Ubuntu:
  New

Bug description:
  during update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2017c-0ubuntu0.16.04
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov 15 13:00:07 2017
  ErrorMessage: нет доступа к архиву: Нет такого файла или каталога
  InstallationDate: Installed on 2017-10-09 (37 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: tzdata
  Title: package tzdata 2017c-0ubuntu0.16.04 failed to install/upgrade: нет 
доступа к архиву: Нет такого файла или каталога
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules

[Toni Lähdekorpi]

How is this still an issue?

I tried the patch with 0.35-0ubuntu2 in xenial:

+ if r.position != 0 and r.position <= num_v4:
+ r.position = num_v4 + 1

And it works perfectly. Couldn't this be merged as there is no obvious
downside on recalculating the rule position for IPv6 addresses?

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

Title:
  Cannot insert IPV6 rule before IPV4 rules

Status in ufw package in Ubuntu:
  Confirmed

Bug description:
  I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when 
IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered  6 to 10,  the 
following command:
  [code]
  ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  errors with "ERROR: Invalid position '1'".

  However, the command
  [code]
  ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  succeeds.

  In my case, this poses a problem, since I am trying to insert rules
  from a script against brute force attacks. The script needs to insert
  blocking rules before a number of other rules that open up some ports
  (since the order of rules is important in ufw). However since the
  number of IPV4 rules will be changing all the time, the position of
  the first available number for an IPV6 address is hard to determine.

  Proposed solution: either allow IPV6 rules to precede IPV4 rules, or
  implement a keyword defining the first available position; e.g. "ufw
  insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1".

  BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu
  12.04.5 LTS,

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

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

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

[Hui Wang]

@Daniel,

The commit https://git.launchpad.net/~ubuntu-audio-
dev/pulseaudio/commit/?h=ubuntu-
xenial=312b9b8d36b90c6bae520722cf68e01b53832eeb is not sufficient to
fix this problem, this commit only adds the conf file in the source
repository, but forgot to add the conf in the build-sys. I already
submitted a simple patch to upstream to fix it, but looks like the
maintainer is on vacation, he has not shown up in the maillist for
several days.

I am wondering if we could merge this simple fix ahead of upstream, if
we could, may I send an independent commit and set the version to
1:8.0-0ubuntu3.6; or you revert my previous commit, then I send one
commit which contains both my previous commit and this new simple fix?


And the simple fix like this:

src/Makefile.am | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/Makefile.am b/src/Makefile.am
index e610db7..0348250 100644
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -1312,7 +1312,8 @@ dist_alsaprofilesets_DATA = \

modules/alsa/mixer/profile-sets/native-instruments-korecontroller.conf \
modules/alsa/mixer/profile-sets/kinect-audio.conf \
modules/alsa/mixer/profile-sets/sb-omni-surround-5.1.conf \
-   
modules/alsa/mixer/profile-sets/steelseries-arctis-usb-audio.conf
+   
modules/alsa/mixer/profile-sets/steelseries-arctis-usb-audio.conf \
+   modules/alsa/mixer/profile-sets/dell-dock-tb16-usb-audio.conf
 
 if HAVE_UDEV
 dist_udevrules_DATA = \
-- 
2.7.4

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

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

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

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

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

  Expected results: Line-out port can work

  Actual results: Line-out port not work

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

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

[Touch-packages] [Bug 1716203] Re: Backport packages for 16.04.4 HWE stack

[Timo Aaltonen]

** Also affects: xorg-server-hwe-16.04 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-hwe-16.04 (Ubuntu Xenial)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server-hwe-16.04 (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in llvm-toolchain-5.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[j.fred muggs]

** Changed in: aptdaemon
 Assignee: (unassigned) => j.fred muggs (fredmuggs)

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Incomplete
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1732377] [NEW] package libperl5.24 5.24.1-2ubuntu1 [modified: usr/share/doc/libperl5.24/changelog.Debian.gz] failed to install/upgrade: попытка перезаписать общий «/usr/share/doc

[Андрей Говорко]

Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libperl5.24 5.24.1-2ubuntu1 [modified: 
usr/share/doc/libperl5.24/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Tue Nov 14 06:16:12 2017
ErrorMessage: попытка перезаписать общий 
«/usr/share/doc/libperl5.24/changelog.Debian.gz», который отличается от других 
экземпляров пакета libperl5.24:amd64
InstallationDate: Installed on 2017-05-25 (173 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: perl
Title: package libperl5.24 5.24.1-2ubuntu1 [modified: 
usr/share/doc/libperl5.24/changelog.Debian.gz] failed to install/upgrade: 
попытка перезаписать общий «/usr/share/doc/libperl5.24/changelog.Debian.gz», 
который отличается от других экземпляров пакета libperl5.24:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package libperl5.24 5.24.1-2ubuntu1 [modified:
  usr/share/doc/libperl5.24/changelog.Debian.gz] failed to
  install/upgrade: попытка перезаписать общий
  «/usr/share/doc/libperl5.24/changelog.Debian.gz», который отличается
  от других экземпляров пакета libperl5.24:amd64

Status in perl package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libperl5.24 5.24.1-2ubuntu1 [modified: 
usr/share/doc/libperl5.24/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Nov 14 06:16:12 2017
  ErrorMessage: попытка перезаписать общий 
«/usr/share/doc/libperl5.24/changelog.Debian.gz», который отличается от других 
экземпляров пакета libperl5.24:amd64
  InstallationDate: Installed on 2017-05-25 (173 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: perl
  Title: package libperl5.24 5.24.1-2ubuntu1 [modified: 
usr/share/doc/libperl5.24/changelog.Debian.gz] failed to install/upgrade: 
попытка перезаписать общий «/usr/share/doc/libperl5.24/changelog.Debian.gz», 
который отличается от других экземпляров пакета libperl5.24:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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