[Touch-packages] [Bug 1818201] Re: packagekitd crashed with SIGSEGV in __memmove_{sse2, avx}_unaligned_erms() from std::char_traits::copy() from ... from show_errors (errorCode=PK_ERROR_ENUM_CAN

[Mathew Hodson]

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

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

** Changed in: packagekit (Ubuntu Cosmic)
   Importance: Undecided => High

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

Title:
  packagekitd crashed with SIGSEGV in
  __memmove_{sse2,avx}_unaligned_erms() from
  std::char_traits::copy() from ... from show_errors
  (errorCode=PK_ERROR_ENUM_CANNOT_FETCH_SOURCES)

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  Won't Fix
Status in packagekit source package in Bionic:
  Fix Committed
Status in packagekit source package in Cosmic:
  Fix Committed
Status in packagekit source package in Disco:
  Fix Released

Bug description:
  [Impact]
  packagekit (sometimes) crashes when there are errors.

  https://errors.ubuntu.com/problem/1bdc3e539949aa164d276979f62ca0282a54fcbd
  https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034

  [Test case]
  Check that there are no further cases on the error tracker with the proposed 
version.

  [Regression potential]
  Given that this just changes the return type of a function only used in 
calls, and the code compiles, there should be no possibility for a regression. 
Of course, if there were, it'd be segfaults or stuff.

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

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

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

[Touch-packages] [Bug 1815882] Re: Update evolution-data-server to 3.30.5

[Mathew Hodson]

** Changed in: evolution-data-server (Ubuntu Cosmic)
   Importance: Undecided => High

** Tags added: upgrade-software-version

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

Title:
   Update evolution-data-server to 3.30.5

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Cosmic:
  Fix Committed

Bug description:
  * Impact

  That's a new bug-fix only update from GNOME

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-30/NEWS
  https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-30

  * Test Case
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  * Regression Potential

  It's a new version with a bug of changes and fixes including in imap,
  calendar and gpg signing code so those features need to be well
  tested.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815882/+subscriptions

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

[Touch-packages] [Bug 1813268] Re: connection issues with Kopano IMAP servers

[Mathew Hodson]

** Changed in: evolution-data-server (Ubuntu Cosmic)
   Importance: Undecided => Low

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

Title:
  connection issues with Kopano IMAP servers

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  Evolution doesn't work with Kopano IMAP servers:

  * Test case
  Configure an account on a Kopano IMAP server and try to use it from evolution

  * Regression potential
  The change is in the imap handling code so it would be good to test on a few 
different type of server that things still work correctly

  -

  3.30.1-1 has the following issue with Kopano IMAP servers:

  Disable request of BODYSTRUCTURE when its response is broken
  https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37

  In 3.30.4-1 it's fixed, so a backport to cosmic would be great.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+subscriptions

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

[Touch-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install

[amano]

Hmm. I upgraded to Disco today and the icon is back. Is that expected?

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

Title:
  UIFe: Drop imagemagick-display from the default install

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in imagemagick package in Debian:
  New

Bug description:
  Impact
  ==
  I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.

  It is visible in the Show Applications view of the Activities Overview
  so this could impact screenshots.

  Justification
  =
  imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things and will still be 
installed by default.

  Bundled with imagemagick is the "display" app, which is an app with an
  unusual, difficult-to-use UI. It was not intentionally included in the
  default Ubuntu install but was only there because it was packaged
  together.

  I am proposing splitting the display app to a separate binary package
  so that it is available for install for the few who do want to use the
  app.

  I tried proposing this to Debian. See comment #60 on the attached
  Debian bug but the Debian maintainer doesn't seem interested in
  accepting my proposal any time soon. (I emailed him directly a few
  months ago too.)

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

  Other Info
  ==
  I will be attaching a patch for review by the Desktop Team here soon.

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

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

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

[Launchpad Bug Tracker]

This bug was fixed in the package ldb - 2:1.5.4-0ubuntu1

---
ldb (2:1.5.4-0ubuntu1) disco; urgency=medium

  * New upstream version: 1.5.4 (LP: #1818525):
- d/libldb1.symbols: update for this version
- d/p/00_Enable-make-test-even-without-lmdb.patch: refreshed
- Removed patches, applied upstream:
  + d/p/03_EBADE
  + d/p/CVE-2019-3824-*.patch
- d/control: bump build-deps:
  + require talloc >= 2.1.16
  + require tdb >= 1.3.18
  + require tevent >= 0.9.39
- d/libldb1.install: added libldb-tdb-{err-map,int}.so
  * d/rules: use Makefile targets instead of direct WAF calls
  * Add python3 packages (LP: #1440381):
- d/control: add python3 packages
- d/rules: clean extra paths in the clean target
- d/python3-ldb*.install: install files for the new python3 packages.
- d/control, d/python3-ldb-dev.install, d/rules: use dh-exec and
  install the python header file in a version-dependent include dir.
- d/python3-ldb.symbols.*: add per-architecture symbols files
- d/rules: dh_makeshlibs for python3-ldb
- d/rules: exclude "ldb." from symbols check/generation, as to match
  the python3 extension name.
- d/rules: fix tevent globbing used in its removal
  * d/control, d/python-ldb*, d/rules: drop python2 packages and support

 -- Andreas Hasenack   Fri, 08 Mar 2019 16:41:11
+

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in talloc package in Ubuntu:
  Fix Released
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

[Launchpad Bug Tracker]

This bug was fixed in the package talloc - 2.1.16-0ubuntu1

---
talloc (2.1.16-0ubuntu1) disco; urgency=medium

  * New upstream version: 2.1.16 (LP: #1818522):
- d/rules: cleanup more directories and pyc files waf is leaving behind
- d/rules: fix globbing for talloc static library creation
- d/libtalloc2.symbols: updated symbols for 2.1.16
- d/control, d/rules, d/python3-talloc{,-dev}.install: new python3 packages
  (LP: #1440381)
- d/s/lintian-overrides: change old PY2 variable override to the PY3
  one we are using.
- d/python3-talloc.symbols.{common,amd64,armhf,arm64,s390x,ppc64el,
  i386}: use per-arch symbols file
- d/rules: check python3-talloc symbols
- d/rules: remove change to keep python2 from desktop images, no longer
  needed
- d/control, d/python-talloc*, d/rules: remove python2 packages

 -- Andreas Hasenack   Sat, 09 Mar 2019 16:40:52
+

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

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

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

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in talloc package in Ubuntu:
  Fix Released
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[name_w]

** Information type changed from Public to Public Security

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

Title:
  cannot view wifi networks after re-enabling wifi

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

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1819354] [NEW] package linux-image-extra-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Frank Sellmer]

Public bug reported:

error messages came

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-142-generic 4.4.0-142.168
ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
Uname: Linux 3.13.0-165-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  frank  2392 F pulseaudio
Date: Sun Mar 10 16:01:39 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=f31508f4-4397-447a-85ef-478e83bfb618
InstallationDate: Installed on 2018-11-13 (116 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
MachineType: Dell Inc. Inspiron 15-3552
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-165-generic.efi.signed 
root=UUID=cbc0956d-ff90-45b2-a0cc-f5c8081575d7 ro recovery nomodeset 
locale=de_DE
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
StagingDrivers: rts5139
Title: package linux-image-extra-4.4.0-142-generic 4.4.0-142.168 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 4.3.0
dmi.board.name: 0M08DC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr4.3.0:bd02/01/2018:svnDellInc.:pnInspiron15-3552:pvr4.3.0:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 15-3552
dmi.product.version: 4.3.0
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package staging xenial

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

Title:
  package linux-image-extra-4.4.0-142-generic 4.4.0-142.168 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  error messages came

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-165-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frank  2392 F pulseaudio
  Date: Sun Mar 10 16:01:39 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=f31508f4-4397-447a-85ef-478e83bfb618
  InstallationDate: Installed on 2018-11-13 (116 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-165-generic.efi.signed 
root=UUID=cbc0956d-ff90-45b2-a0cc-f5c8081575d7 ro recovery nomodeset 
locale=de_DE
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  StagingDrivers: rts5139
  Title: package linux-image-extra-4.4.0-142-generic 4.4.0-142.168 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.3.0
  dmi.board.name: 0M08DC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.3.0:bd02/01/2018:svnDellInc.:pnInspiron15-3552:pvr4.3.0:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.3.0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://la

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

[Launchpad Bug Tracker]

This bug was fixed in the package samba - 2:4.10.0~rc4+dfsg-0ubuntu1

---
samba (2:4.10.0~rc4+dfsg-0ubuntu1) disco; urgency=medium

  * New upstream version 4.10.0rc4 (LP: #1818518):
- Removed patches already applied upstream:
  + d/p/nsswitch-Add-try_authtok-option-to-pam_winbind.patch
  + d/p/s3-auth-ignore-create_builtin_guests-failing-without.patch
- d/p/add-so-version-to-private-libraries: refreshed to remove fuzz
- d/control: Updated build dependencies:
  + tdb >= 1.3.17
  + talloc >= 2.1.15
  + tevent >= 0.9.38
  + ldb >= 1.5.3
- d/samba-common.docs: README is now README.md
- d/libsmbclient.symbols: update symbols for this version
- d/libwbclient0.symbols: update symbols for this version
- d/ctdb.install: new binary ctdb_local_daemons
- d/samba-dev.install: use globbing for the header files with
  exceptions for wbclient.h and libsmbclient.h, which belong in
 other packages.
- d/rules: fix globbing used to move the dckeytab python module to the
  samba package, and add a comment explaining why this is being done.
  * Switch to python3:
- d/rules: calculate the ldb version using python3, and drop the
  "really" bit since the real 1.5.x series is being used now.
- d/rules: make sure python3 is used for the build
- d/rules: adjust globbing to remove the python3 version of tevent.so
- d/rules: drop PYVERS, unused
- d/control: adjust dependencies (build and runtime) for python3
- d/python3-samba.install, d/control: new python3-samba package
  (LP: #1440381)
- d/control, d/python-samba.install: get rid of python-samba, which is py2
- d/python3-samba.lintian-overrides: use the same overrides we had for
  python-samba, now deleted.
- d/samba-dev.install, d/samba-libs.install: update file list
- d/t/control, d/t/python-smoke: use python3
- d/control: use ${python3:Depends} now instead of the python 2
  counterpart for samba and samba-common-bin.
  * d/control: drop suggests for python-gpgme, it's no longer available.

 -- Andreas Hasenack   Sat, 09 Mar 2019 12:45:25
+

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

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in talloc package in Ubuntu:
  Fix Released
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1819354] Re: package linux-image-extra-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1819354

Title:
  package linux-image-extra-4.4.0-142-generic 4.4.0-142.168 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  error messages came

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-165-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frank  2392 F pulseaudio
  Date: Sun Mar 10 16:01:39 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=f31508f4-4397-447a-85ef-478e83bfb618
  InstallationDate: Installed on 2018-11-13 (116 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-165-generic.efi.signed 
root=UUID=cbc0956d-ff90-45b2-a0cc-f5c8081575d7 ro recovery nomodeset 
locale=de_DE
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  StagingDrivers: rts5139
  Title: package linux-image-extra-4.4.0-142-generic 4.4.0-142.168 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.3.0
  dmi.board.name: 0M08DC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.3.0:bd02/01/2018:svnDellInc.:pnInspiron15-3552:pvr4.3.0:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.3.0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install

[Jeremy Bicha]

amano, please open a new bug for new issues instead of commenting on old
closed bugs.

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

Title:
  UIFe: Drop imagemagick-display from the default install

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in imagemagick package in Debian:
  New

Bug description:
  Impact
  ==
  I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.

  It is visible in the Show Applications view of the Activities Overview
  so this could impact screenshots.

  Justification
  =
  imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things and will still be 
installed by default.

  Bundled with imagemagick is the "display" app, which is an app with an
  unusual, difficult-to-use UI. It was not intentionally included in the
  default Ubuntu install but was only there because it was packaged
  together.

  I am proposing splitting the display app to a separate binary package
  so that it is available for install for the few who do want to use the
  app.

  I tried proposing this to Debian. See comment #60 on the attached
  Debian bug but the Debian maintainer doesn't seem interested in
  accepting my proposal any time soon. (I emailed him directly a few
  months ago too.)

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

  Other Info
  ==
  I will be attaching a patch for review by the Desktop Team here soon.

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

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

[Touch-packages] [Bug 1819359] [NEW] [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all

[Yorick Meulenbelt]

Public bug reported:

Internal speakers work, only having trouble with the headphone output,
(I have had this problem in every distrobution I´ve tried)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC2D0c:   yoyo   1917 F...m pulseaudio
 /dev/snd/pcmC0D1p:   yoyo   1917 F...m pulseaudio
 /dev/snd/controlC0:  yoyo   1917 F pulseaudio
 /dev/snd/controlC1:  yoyo   1917 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 10 18:44:38 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-03-10 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac 
(20160803)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, N/A
Symptom_Type: No sound at all
Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all
UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago)
dmi.bios.date: 09/25/2018
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 82.0.0.0.0
dmi.board.name: Mac-942B5BF58194151B
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-942B5BF58194151B
dmi.modalias: 
dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
dmi.product.family: iMac
dmi.product.name: iMac12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal speakers work, only having trouble with the headphone output,
  (I have had this problem in every distrobution I´ve tried)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0c:   yoyo   1917 F...m pulseaudio
   /dev/snd/pcmC0D1p:   yoyo   1917 F...m pulseaudio
   /dev/snd/controlC0:  yoyo   1917 F pulseaudio
   /dev/snd/controlC1:  yoyo   1917 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 10 18:44:38 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-03-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac 
(20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, N/A
  Symptom_Type: No sound at all
  Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at 
all
  UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago)
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 82.0.0.0.0
  dmi.board.name: Mac-942B5BF58194151B
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B5BF58194151B
  dmi.modalias: 
dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1819358] [NEW] [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all

[Yorick Meulenbelt]

Public bug reported:

Internal speakers work, only having trouble with the headphone output,
(I have had this problem in every distrobution I´ve tried)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC2D0c:   yoyo   1917 F...m pulseaudio
 /dev/snd/pcmC0D1p:   yoyo   1917 F...m pulseaudio
 /dev/snd/controlC0:  yoyo   1917 F pulseaudio
 /dev/snd/controlC1:  yoyo   1917 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 10 18:44:38 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-03-10 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac 
(20160803)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, N/A
Symptom_Type: No sound at all
Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all
UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago)
dmi.bios.date: 09/25/2018
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 82.0.0.0.0
dmi.board.name: Mac-942B5BF58194151B
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-942B5BF58194151B
dmi.modalias: 
dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
dmi.product.family: iMac
dmi.product.name: iMac12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal speakers work, only having trouble with the headphone output,
  (I have had this problem in every distrobution I´ve tried)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0c:   yoyo   1917 F...m pulseaudio
   /dev/snd/pcmC0D1p:   yoyo   1917 F...m pulseaudio
   /dev/snd/controlC0:  yoyo   1917 F pulseaudio
   /dev/snd/controlC1:  yoyo   1917 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 10 18:44:38 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-03-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac 
(20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, N/A
  Symptom_Type: No sound at all
  Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at 
all
  UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago)
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 82.0.0.0.0
  dmi.board.name: Mac-942B5BF58194151B
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B5BF58194151B
  dmi.modalias: 
dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1819359] Re: [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all

[El jinete sin cabeza]

Thanks for helping build a better Ubuntu. Could you run the following
command in the terminal?

$ sudo apt-get install --install-recommends linux-generic-hwe-18.04
xserver-xorg-hwe-18.04

Restart your computer, and tell us if it works now.

Thanks.

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

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

Title:
  [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Internal speakers work, only having trouble with the headphone output,
  (I have had this problem in every distrobution I´ve tried)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0c:   yoyo   1917 F...m pulseaudio
   /dev/snd/pcmC0D1p:   yoyo   1917 F...m pulseaudio
   /dev/snd/controlC0:  yoyo   1917 F pulseaudio
   /dev/snd/controlC1:  yoyo   1917 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 10 18:44:38 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-03-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac 
(20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, N/A
  Symptom_Type: No sound at all
  Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at 
all
  UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago)
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 82.0.0.0.0
  dmi.board.name: Mac-942B5BF58194151B
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B5BF58194151B
  dmi.modalias: 
dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1819255] Re: Ubuntu 18.04 suspends intermittently

[Mukund Varadarajan]

** Package changed: pm-utils (Ubuntu) => linux (Ubuntu)

** Attachment added: "dmesg log file"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819255/+attachment/5245200/+files/dmesg.txt

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

Title:
  Ubuntu 18.04 suspends intermittently

Status in linux package in Ubuntu:
  New

Bug description:
  I am using Lenovo Thinkpad E450 with Ubuntu 18.04.2 and kernel version
  is Linux 4.14.105-0414105-generic.

  I am currently not able to suspend my laptop properly.
  I first experienced this when I was using the kernel 4.15.46.

  Expected behavior when commanded to suspend:
  Display goes black, the CPU fan is switched off, the power LED pulsates 
showing that the computer is in suspend mode. This should happen whenever the 
PC is suspended using the command 'sudo systemctl suspend' or closing the lid 
or choosing suspend in the menu options by long-pressing the power button.

  What actually happens:
  If any of the above methods is used to suspend the PC, the display goes 
black, the PC goes to suspend state after a few seconds, but remains in suspend 
only for a maximum of 7-10 seconds. After that it automatically resumes, with 
the display trying to show the lockscreen if lid is not closed. If lid is 
closed, then I know it has resumed as the power LED stays on and the fan runs. 
As time goes, it intermittently goes to suspend for a few seconds and resumes 
back. There is no unnatural behavior according to 'journalctl' or 'dmesg'. The 
system supposedly goes to suspend "only for a few seconds" and resumes back.

  To resolve this issue I tried using 4.18 kernel and still the issue 
persisted.(Original kernel version was 4.15)
  In another forum, I was suggested to use 4.14 kernel and even now the issue 
persists.

  I don't know if this information would be helpful but during boot, I got 
these errors:
  ACPI Error: Needed type [Reference], found [Integer] (ptrval) 
(20180531/exresop-69)
  ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] 
(20180531/dswexec-427)
  ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE 
(20180531/psparse-516)

  I also did a 'cat /sys/kernel/debug/suspend_stats' which returned 5
  successes and 0 failures of any type.

  PS: I don't think this is a bug based on a particular application/package, so 
I didn't include any.
  Thanks in advance

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

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

[Touch-packages] [Bug 917231] Re: Mutual exclusion for cronjobs

[Markus Ueberall]

For the record: There's https://github.com/poeml/withlock which can
simply be put "between" cron and the applications in question…

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

Title:
  Mutual exclusion for cronjobs

Status in cron package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 12.04 dev with cron 3.0pl1-120ubuntu2. I encountered
  in the past a problem which can be solved with a new feature. Here is
  an example of the problem:

  0 0 * * * root /usr/local/share/python/backup_to_media.py
  0 0 1 * * root /usr/local/share/python/backup_to_internet.py

  These cronjobs do backup some data every day to a media and one time a
  month to the internet. The problem is on the first day of every month
  both backups are running at the same time. This can cause some
  problems like the backuped data to the internet is one day older as it
  should be or there are maybe exceptions because both jobs are
  accessing the files at the same time.

  Maybe there could be a priority column which controls this:

  0 0 * * * root 0 /usr/local/share/python/backup_to_media.py
  0 0 1 * * root 1 /usr/local/share/python/backup_to_internet.py

  The priority column ensures that jobs which are running at the same
  time are excuted sequentially (if the priority of every job is the
  same number we will have the current behaviour). On the first day of
  every month /usr/local/share/python/backup_to_media.py is executed
  first because it has a lower number and if it finishes
  /usr/local/share/python/backup_to_internet.py is executed.

  This would prevent complicated entries in the crontab or own complex
  mutual exclusion to solve this problem.

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

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

[Touch-packages] [Bug 1819369] [NEW] When specifying minute, hour, day-of-month, month, day-of-week values/ranges, given day-of-month range is *ignored*

[Markus Ueberall]

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd'
# lsb_release -rd
Description:Ubuntu 16.04.6 LTS
Release:16.04

2) The version of the package you are using, via 'apt-cache policy pkgname'
# apt-cache policy cron
cron:
  Installed: 3.0pl1-128ubuntu2
  Candidate: 3.0pl1-128ubuntu2
  Version table:
 *** 3.0pl1-128ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

3) What you expected to happen
/etc/crontab contains the following entries (each line lives on a separate host 
with identical setup, system clocks are in sync):
# m h dom mon dow user  command
00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4

The expectation was that none of the entries is executed in parallel at
any given point in time due to column three (date of month range).
(Note: All other (default) entries work as expected, syntax of all
crontab files has been checked using
https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)

4) What happened instead
Yesterday (Saturday, March 9th), the same script was executed in parallel on 
all four hosts.

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

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd'
  # lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04
  
- 
  2) The version of the package you are using, via 'apt-cache policy pkgname'
  # apt-cache policy cron
  cron:
-   Installed: 3.0pl1-128ubuntu2
-   Candidate: 3.0pl1-128ubuntu2
-   Version table:
-  *** 3.0pl1-128ubuntu2 500
- 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
- 
+   Installed: 3.0pl1-128ubuntu2
+   Candidate: 3.0pl1-128ubuntu2
+   Version table:
+  *** 3.0pl1-128ubuntu2 500
+ 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  3) What you expected to happen
  /etc/crontab contains the following entries (each line lives on a separate 
host with identical setup, system clocks are in sync):
  # m h dom mon dow user  command
  00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
  00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
  00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
  00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4
  
  The expectation was that none of the entries is executed in parallel at
  any given point in time due to column three (date of month range).
  (Note: All other (default) entries work as expected, syntax of all
- crontab files have been checked using
+ crontab files has been checked using
  https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)
- 
  
  4) What happened instead
  Yesterday (Saturday, March 9th), the same script was executed in parallel on 
all four hosts.

** Summary changed:

- When specifying specific minute,hour,day-of-month,month,day-of-week 
values/ranges, given day-of-month range is *ignored*
+ When specifying minute,hour,day-of-month,month,day-of-week values/ranges, 
given day-of-month range is *ignored*

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

Title:
  When specifying minute,hour,day-of-month,month,day-of-week
  values/ranges, given day-of-month range is *ignored*

Status in cron package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd'
  # lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname'
  # apt-cache policy cron
  cron:
    Installed: 3.0pl1-128ubuntu2
    Candidate: 3.0pl1-128ubuntu2
    Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /etc/crontab contains the following entries (each line lives on a separate 
host with identical setup, system clocks are in sync):
  # m h dom mon dow user  command
  00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
  00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
  00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
  00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4

  The expectation was that none of the entries is executed in parallel
  at any given point in time du

[Touch-packages] [Bug 1819369] Re: When specifying minute, hour, day-of-month, month, day-of-week values/ranges, given day-of-month range is *ignored*

[Markus Ueberall]

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd'
  # lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname'
  # apt-cache policy cron
  cron:
    Installed: 3.0pl1-128ubuntu2
    Candidate: 3.0pl1-128ubuntu2
    Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  
  3) What you expected to happen
  /etc/crontab contains the following entries (each line lives on a separate 
host with identical setup, system clocks are in sync):
  # m h dom mon dow user  command
  00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
  00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
  00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
  00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4
  
  The expectation was that none of the entries is executed in parallel at
- any given point in time due to column three (date of month range).
- (Note: All other (default) entries work as expected, syntax of all
- crontab files has been checked using
+ any given point in time due to column three (day-of-month range). (Note:
+ All other (default) entries work as expected, syntax of all crontab
+ files has been checked using
  https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)
  
  4) What happened instead
  Yesterday (Saturday, March 9th), the same script was executed in parallel on 
all four hosts.

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

Title:
  When specifying minute,hour,day-of-month,month,day-of-week
  values/ranges, given day-of-month range is *ignored*

Status in cron package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd'
  # lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname'
  # apt-cache policy cron
  cron:
    Installed: 3.0pl1-128ubuntu2
    Candidate: 3.0pl1-128ubuntu2
    Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /etc/crontab contains the following entries (each line lives on a separate 
host with identical setup, system clocks are in sync):
  # m h dom mon dow user  command
  00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
  00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
  00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
  00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4

  The expectation was that none of the entries is executed in parallel
  at any given point in time due to column three (day-of-month range).
  (Note: All other (default) entries work as expected, syntax of all
  crontab files has been checked using
  https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)

  4) What happened instead
  Yesterday (Saturday, March 9th), the same script was executed in parallel on 
all four hosts.

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

-- 
Mailing list: https://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 1819369] Re: When specifying minute, hour, day-of-month, month, day-of-week values/ranges, given day-of-month range is *ignored*

[Christian Kastner]

On 10.03.19 21:05, Markus Ueberall wrote:
>   # m h dom mon dow user  command
>   00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   
> #host1
>   00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   
> #host2
>   00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   
> #host3
>   00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   
> #host4

> The expectation was that none of the entries is executed in parallel
> at any given point in time due to column three> (day-of-month range)

This frequently occurring mistake is an unfortunate result of the
crontab(5) specification.

Quoting the man page:
> Note: The day of a command's execution can be specified by two fields —
> day of month, and day of week. If both fields are restricted (i.e.,
> aren't *), the command will be run when either field matches the current
> time. For example, ``30 4 1,15 * 5'' would cause a command to be run at
> 4:30 am on the 1st and 15th of each month, plus  every Friday.

In short: it's not dom AND dow, but dom OR dow.

Consequently, your specification of SAT in column 5 trumps your
specification of column 3.

The man page contains an example for how to work around this.

-- 
Christian Kastner


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

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

Title:
  When specifying minute,hour,day-of-month,month,day-of-week
  values/ranges, given day-of-month range is *ignored*

Status in cron package in Ubuntu:
  Invalid

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd'
  # lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname'
  # apt-cache policy cron
  cron:
    Installed: 3.0pl1-128ubuntu2
    Candidate: 3.0pl1-128ubuntu2
    Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /etc/crontab contains the following entries (each line lives on a separate 
host with identical setup, system clocks are in sync):
  # m h dom mon dow user  command
  00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
  00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
  00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
  00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4

  The expectation was that none of the entries is executed in parallel
  at any given point in time due to column three (day-of-month range).
  (Note: All other (default) entries work as expected, syntax of all
  crontab files has been checked using
  https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)

  4) What happened instead
  Yesterday (Saturday, March 9th), the same script was executed in parallel on 
all four hosts.

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

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

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

[Dr. Uwe Meyer-Gruhl]

Hi,

good idea in theory, but I want to add my 2cents: Please coordinate this
update with ALL affected packages, like apache2 and nginx.

My reason is:

I just tried the PPA and found that nginx works with TLS 1.3 after that
right out of the box.

HOWEVER, there is a problem: openssl 1.1.1 has changed the way the
cipher suites are configured - the ones for TLS 1.3 are configured
separately, see here:

https://github.com/openssl/openssl/commit/f865b08143b453962ad4afccd69e698d13c60f77

Nginx on the other hand has chosen to not support that new configuration
at all, see:

https://trac.nginx.org/nginx/ticket/1529

That means that the predefined order of TLS 1.3 is:

TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256

and cannot be changed - it took me hours to find that out since the
Nginx 1.15 documentation does not tell you that the TLS 1.3 ciphers
cannot be changed by ssl_ciphers, but are silently ignored.


The default set and order of ciphersuites may suit your needs or not -
matter-of-fact it makes my SSLLabs score worse because of the AES128
cipher used. I have tried to apply othe defaults in
/etc/ssl/openssl.conf but they do not seem to work for nginx. Neither
could I just disable TLS 1.3 in order to restore the old behaviour other
than to restore OpenSSL 1.1.0 by using "ppa-purge ppa:ci-train-ppa-
service/3473".


King regards,


Uwe


** Bug watch added: trac.nginx.org/nginx/ #1529
   http://trac.nginx.org/nginx/ticket/1529

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  In Progress
Status in libio-socket-ssl-perl source package in Bionic:
  New
Status in libnet-ssleay-perl source package in Bionic:
  New
Status in nova source package in Bionic:
  New
Status in openssl source package in Bionic:
  New
Status in python-cryptography source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in r-cran-openssl source package in Bionic:
  Fix Committed
Status in ruby-openssl source package in Bionic:
  Fix Committed
Status in ruby2.5 source package in Bionic:
  New

Bug description:
  [Impact]

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

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

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

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

  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

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

   * Backport TLS v1.3 support patches, where applicable

  [Regression Potential]

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

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

   * Notable changes are listed here
  https://wiki.openssl.org/index.php/TLS1.3

   * Most common connectivity issues so far:
     - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. 
Solution is client change to set hostname, or to clamp down the client to 
TLSv1.2.

     - session negotiation is different in TLSv1.3, existing client code
  may fail to create/negotiate/resume session. Clients need to learn how
  to use session callback.

   * This update bundles python 3.6 and 3.7 point releases

  [Other Info]

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

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

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

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

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

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

[Touch-packages] [Bug 1819183] Re: FFe: Update pygobject to 3.32

[Jeremy Bicha]

** Description changed:

  Feature Freeze exception request
  
  Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.
  
- 3.31.4-1 is in Debian experimental ready to be synced over once this FFe
- is approved. 3.32.0 is expected next week.
+ 3.32.0-1 is in Debian experimental ready to be synced over once this FFe
+ is approved.
  
  https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
- https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes 
several commits that were already included in the current 3.30.4 version)
+ https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes 
several commits that were already included in the current 3.30.4 version)
  
  Justification for lateness
  --
  Sorry, we've been a bit busy and this wasn't a high priority.

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

Title:
  FFe: Update pygobject to 3.32

Status in pygobject package in Ubuntu:
  New

Bug description:
  Feature Freeze exception request
  
  Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.

  3.32.0-1 is in Debian experimental ready to be synced over once this
  FFe is approved.

  https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
  https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes 
several commits that were already included in the current 3.30.4 version)

  Justification for lateness
  --
  Sorry, we've been a bit busy and this wasn't a high priority.

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

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

[Touch-packages] [Bug 1819359] Re: [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1819358
   [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all

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

Title:
  [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Internal speakers work, only having trouble with the headphone output,
  (I have had this problem in every distrobution I´ve tried)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0c:   yoyo   1917 F...m pulseaudio
   /dev/snd/pcmC0D1p:   yoyo   1917 F...m pulseaudio
   /dev/snd/controlC0:  yoyo   1917 F pulseaudio
   /dev/snd/controlC1:  yoyo   1917 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 10 18:44:38 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-03-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac 
(20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, N/A
  Symptom_Type: No sound at all
  Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at 
all
  UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago)
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 82.0.0.0.0
  dmi.board.name: Mac-942B5BF58194151B
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B5BF58194151B
  dmi.modalias: 
dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1819183] Re: FFe: Update pygobject to 3.32

[Jeremy Bicha]

** Tags added: upgrade-software-version

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

Title:
  FFe: Update pygobject to 3.32

Status in pygobject package in Ubuntu:
  New

Bug description:
  Feature Freeze exception request
  
  Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.

  3.32.0-1 is in Debian experimental ready to be synced over once this
  FFe is approved.

  https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
  https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes 
several commits that were already included in the current 3.30.4 version)

  Justification for lateness
  --
  Sorry, we've been a bit busy and this wasn't a high priority.

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

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

[Touch-packages] [Bug 1817338] Re: HDMI sound output not available in 19.04 (but works in 18.10)

[Daniel van Vugt]

Thanks. This bug has been reassigned to gnome-control-center.

** Summary changed:

- HDMI sound output not available
+ HDMI sound output not available in 19.04 (but works in 18.10)

** Summary changed:

- HDMI sound output not available in 19.04 (but works in 18.10)
+ HDMI sound output not selectable in 19.04 (but works in 18.10)

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  HDMI sound output not selectable in 19.04 (but works in 18.10)

Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  In 19.04, HDMI sound stopped working after some upgrade.

  The sink is somehow availalbe, but cannot be selected.
  In gnome-control-center, HDMI output device is listed, but if I choose it, no 
configuration list appears (see screen capture attached).

  aplay -l gives me:
  ~$ aplay -l
   Liste des Périphériques Matériels PLAYBACK 
  carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC 
Analog]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  pavucontrol shows HDMI as unplugged.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franck 5998 F pulseaudio
   /dev/snd/pcmC1D0c:   franck 5998 F...m pulseaudio
   /dev/snd/controlC0:  franck 5998 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 22 16:16:56 2019
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-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: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2353CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2353CTO
  dmi.product.sku: LENOVO_MT_2353
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)

[Robert Ancell]

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => High

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

Title:
  HDMI sound output not selectable in 19.04 (but works in 18.10)

Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  In 19.04, HDMI sound stopped working after some upgrade.

  The sink is somehow availalbe, but cannot be selected.
  In gnome-control-center, HDMI output device is listed, but if I choose it, no 
configuration list appears (see screen capture attached).

  aplay -l gives me:
  ~$ aplay -l
   Liste des Périphériques Matériels PLAYBACK 
  carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC 
Analog]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  pavucontrol shows HDMI as unplugged.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franck 5998 F pulseaudio
   /dev/snd/pcmC1D0c:   franck 5998 F...m pulseaudio
   /dev/snd/controlC0:  franck 5998 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 22 16:16:56 2019
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-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: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2353CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2353CTO
  dmi.product.sku: LENOVO_MT_2353
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40%

[Daniel van Vugt]

I wonder if 'tlp' or similar is at play...

Can you please run this command:

  dpkg -l > allpackages.txt

and then send us the resulting file 'allpackages.txt'?

** Summary changed:

- [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a 
while
+ [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or 
the battery % is above 20 - 40%

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged
  in or the battery % is above 20 - 40%

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

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  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/linux/+bug/1818802/+subscriptions

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

[Touch-packages] [Bug 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)

[Tim Lunn]

I had the same issue a few weeks ago, now however with 3.31.92 (on
Disco) I do get the configuration dropdown when selecting my HDMI Audio
device. It came up blank initially, but appears to have saved the
correct setting since.

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

Title:
  HDMI sound output not selectable in 19.04 (but works in 18.10)

Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  In 19.04, HDMI sound stopped working after some upgrade.

  The sink is somehow availalbe, but cannot be selected.
  In gnome-control-center, HDMI output device is listed, but if I choose it, no 
configuration list appears (see screen capture attached).

  aplay -l gives me:
  ~$ aplay -l
   Liste des Périphériques Matériels PLAYBACK 
  carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC 
Analog]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  pavucontrol shows HDMI as unplugged.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franck 5998 F pulseaudio
   /dev/snd/pcmC1D0c:   franck 5998 F...m pulseaudio
   /dev/snd/controlC0:  franck 5998 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 22 16:16:56 2019
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-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: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2353CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2353CTO
  dmi.product.sku: LENOVO_MT_2353
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1819277] Re: I see stripes plomas in full screen mode

[Daniel van Vugt]

Fixed upstream in Mesa:
https://gitlab.freedesktop.org/mesa/mesa/merge_requests/252

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

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Triaged

** Description changed:

- https://gitlab.gnome.org/GNOME/totem/issues/307
+ https://gitlab.freedesktop.org/mesa/mesa/merge_requests/252
  
  ---
  
  When I open a movie in totem, it looks like a window. But then I enlarge
  it to full screen. It is seen in the lower part, a strip of lead.
  
  Attached screenshot image.
  
  The problem occurs with wayland, in Xorg it looks good.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  9 12:12:52 2019
  InstallationDate: Installed on 2018-12-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: totem
  UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago)

** Description changed:

- https://gitlab.freedesktop.org/mesa/mesa/merge_requests/252
- 
- ---
- 
  When I open a movie in totem, it looks like a window. But then I enlarge
  it to full screen. It is seen in the lower part, a strip of lead.
  
  Attached screenshot image.
  
  The problem occurs with wayland, in Xorg it looks good.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  9 12:12:52 2019
  InstallationDate: Installed on 2018-12-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: totem
  UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago)

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

Title:
  I see stripes plomas in full screen mode

Status in mesa package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  When I open a movie in totem, it looks like a window. But then I
  enlarge it to full screen. It is seen in the lower part, a strip of
  lead.

  Attached screenshot image.

  The problem occurs with wayland, in Xorg it looks good.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  9 12:12:52 2019
  InstallationDate: Installed on 2018-12-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: totem
  UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago)

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

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

[Touch-packages] [Bug 1819264] Re: Graphis problem

[Daniel van Vugt]

You already have the right graphics driver built-in and working.

What problem are you trying to solve?

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

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

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

Title:
  Graphis problem

Status in Ubuntu:
  Incomplete

Bug description:
  How can i install graphis in dell inspiron 3442.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  9 18:33:36 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 3442
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=950331ed-5458-421a-be4b-05d38ca12e30 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0486K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0486K1:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1819359] Re: [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1819358
   [iMac12,1, Cirrus Logic CS4206] Internal speakers work, only having trouble 
with the headphone output
** This bug has been marked a duplicate of bug 1003039
   No sound in headphones on imac 2011[workaround]

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

Title:
  [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Internal speakers work, only having trouble with the headphone output,
  (I have had this problem in every distrobution I´ve tried)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0c:   yoyo   1917 F...m pulseaudio
   /dev/snd/pcmC0D1p:   yoyo   1917 F...m pulseaudio
   /dev/snd/controlC0:  yoyo   1917 F pulseaudio
   /dev/snd/controlC1:  yoyo   1917 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 10 18:44:38 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-03-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac 
(20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, N/A
  Symptom_Type: No sound at all
  Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at 
all
  UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago)
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 82.0.0.0.0
  dmi.board.name: Mac-942B5BF58194151B
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B5BF58194151B
  dmi.modalias: 
dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1754933] Re: Headphones no audio output at all

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1003039
   No sound in headphones on imac 2011[workaround]

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

Title:
  Headphones no audio output at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Went to use headphones for the first time and got no audio output. I
  use Ubuntu on an iMac and the speakers work ok and the headphones work
  when in osx.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   brent  2112 F...m pulseaudio
   /dev/snd/controlC0:  brent  2112 F pulseaudio
   /dev/snd/controlC1:  brent  2112 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 11 18:20:29 2018
  InstallationDate: Installed on 2018-03-07 (3 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   brent  2112 F...m pulseaudio
   /dev/snd/controlC0:  brent  2112 F pulseaudio
   /dev/snd/controlC1:  brent  2112 F pulseaudio
  Symptom_Jack: Green Headphone Out, N/A
  Symptom_Type: No sound at all
  Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM121.88Z.004D.B00.1708080012
  dmi.board.name: Mac-942B5BF58194151B
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B5BF58194151B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM121.88Z.004D.B00.1708080012:bd08/08/17:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1819358] Re: [iMac12, 1, Cirrus Logic CS4206] Internal speakers work, only having trouble with the headphone output

[Daniel van Vugt]

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

** Summary changed:

- [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all
+ [iMac12,1, Cirrus Logic CS4206] Internal speakers work, only having trouble 
with the headphone output

** This bug has been marked a duplicate of bug 1003039
   No sound in headphones on imac 2011[workaround]

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

Title:
  [iMac12,1, Cirrus Logic CS4206] Internal speakers work, only having
  trouble with the headphone output

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal speakers work, only having trouble with the headphone output,
  (I have had this problem in every distrobution I´ve tried)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0c:   yoyo   1917 F...m pulseaudio
   /dev/snd/pcmC0D1p:   yoyo   1917 F...m pulseaudio
   /dev/snd/controlC0:  yoyo   1917 F pulseaudio
   /dev/snd/controlC1:  yoyo   1917 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 10 18:44:38 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-03-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac 
(20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, N/A
  Symptom_Type: No sound at all
  Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at 
all
  UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago)
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 82.0.0.0.0
  dmi.board.name: Mac-942B5BF58194151B
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B5BF58194151B
  dmi.modalias: 
dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1003039] Re: No sound in headphones on imac 2011[workaround]

[Daniel van Vugt]

** Tags removed: precise
** Tags added: bionic xenial

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

Title:
  No sound in headphones on imac 2011[workaround]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Using ubuntu 12.04 mac specific amd64 in a 2011 imac 21,5. Sound works
  on the built-in speakers if no headphone is connected. This is not a
  audio devide switch mute issue; the sound is activated, but no sound
  is coming from a regular headphone when it is connected. System is
  updated and no changes had been made to it.

  It also looks to be an ancient bug, which affect macbooks also for example. 
Let me know which information you need to fix that, and how to obtain that 
information.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lunarts1804 F pulseaudio
   /dev/snd/controlC0:  lunarts1804 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xa890 irq 49'
 Mixer name : 'Cirrus Logic CS4206'
 Components : 'HDA:10134206,106b0900,00100302'
 Controls  : 24
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xa884 irq 50'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=9f77fbde-008f-4cdf-9e13-d1512cbd6abf
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64+mac 
(20120425.1)
  MachineType: Apple Inc. iMac12,1
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=c816adec-8dcc-4344-a56e-2fdc23f632b7 ro quiet splash
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  SourcePackage: linux
  StagingDrivers: mei
  Tags:  precise staging precise staging
  Uname: Linux 3.2.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM121.88Z.0047.B1F.1201241648
  dmi.board.name: Mac-942B5BF58194151B
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B5BF58194151B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM121.88Z.0047.B1F.1201241648:bd01/24/12:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
  dmi.product.name: iMac12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1819402] Re: package unattended-upgrades 1.5ubuntu3.18.10.2 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex

[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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1819402

Title:
  package unattended-upgrades 1.5ubuntu3.18.10.2 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 10

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  having system problem

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: unattended-upgrades 1.5ubuntu3.18.10.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Mon Mar 11 08:59:24 2019
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-02-22 (16 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.5ubuntu3.18.10.2 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1819402] [NEW] package unattended-upgrades 1.5ubuntu3.18.10.2 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error

[Manish]

Public bug reported:

having system problem

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: unattended-upgrades 1.5ubuntu3.18.10.2
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Mon Mar 11 08:59:24 2019
ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2019-02-22 (16 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, unpackaged
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.2
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 1.5ubuntu3.18.10.2 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package cosmic

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

Title:
  package unattended-upgrades 1.5ubuntu3.18.10.2 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 10

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  having system problem

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: unattended-upgrades 1.5ubuntu3.18.10.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Mon Mar 11 08:59:24 2019
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-02-22 (16 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.5ubuntu3.18.10.2 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1806399] Re: package python3-minimal 3.6.7-1~18.04 failed to install/upgrade: installed python3-minimal package post-installation script subprocess returned error exit status 127

[Launchpad Bug Tracker]

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

** Changed in: python3-defaults (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python3-minimal 3.6.7-1~18.04 failed to install/upgrade:
  installed python3-minimal package post-installation script subprocess
  returned error exit status 127

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  lkjhgfdsazASDERTYUIOP'/;.LKJHGFDSZ

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-minimal 3.6.7-1~18.04
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   python3-minimal:amd64: Configure
   python3:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Dec  3 23:48:46 2018
  DpkgTerminalLog:
   Setting up python3-minimal (3.6.7-1~18.04) ...
   /var/lib/dpkg/info/python3-minimal.postinst: 5: 
/var/lib/dpkg/info/python3-minimal.postinst: py3compile: not found
   dpkg: error processing package python3-minimal (--configure):
installed python3-minimal package post-installation script subprocess 
returned error exit status 127
  DuplicateSignature:
   package:python3-minimal:3.6.7-1~18.04
   Setting up python3-minimal (3.6.7-1~18.04) ...
   /var/lib/dpkg/info/python3-minimal.postinst: 5: 
/var/lib/dpkg/info/python3-minimal.postinst: py3compile: not found
   dpkg: error processing package python3-minimal (--configure):
installed python3-minimal package post-installation script subprocess 
returned error exit status 127
  ErrorMessage: installed python3-minimal package post-installation script 
subprocess returned error exit status 127
  InstallationDate: Installed on 2018-01-05 (332 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6m, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: python3-defaults
  Title: package python3-minimal 3.6.7-1~18.04 failed to install/upgrade: 
installed python3-minimal package post-installation script subprocess returned 
error exit status 127
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (67 days ago)

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

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

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

[Christian Ehrhardt ]

Hi,
it has been released for Cosmic already.
Some tests were blocking it for Bionic but I resolved those already.
It should be released the next time an SRU member will look at this.

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

Title:
  backport statx syscall whitelist fix

Status in docker.io package in Ubuntu:
  Invalid
Status in libseccomp package in Ubuntu:
  Fix Released
Status in docker.io source package in Bionic:
  Invalid
Status in libseccomp source package in Bionic:
  Fix Committed
Status in docker.io source package in Cosmic:
  Invalid
Status in libseccomp source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Some newer workloads fail due to libseccomp as in Bionic lacking
  statx support

   * This backports the syscall definitions for statx to Bionic to allow
  to manage those

  [Test Case]

  # Note: I took a KVM image of Bionic to not spoil my system with Docker 
config for this test too much
  $ sudo apt install docker.io
  $ sudo usermod -a -G docker ubuntu
  $ cat > test-statx/Dockerfile << EOF
  FROM ubuntu:18.04
  RUN apt-get update && apt-get install -y wget gcc
  WORKDIR /tmp
  RUN wget -q 
https://raw.githubusercontent.com/torvalds/linux/master/samples/statx/test-statx.c
  RUN gcc test-statx.c -o test-statx
  RUN touch test-file
  RUN chmod +x ./test-statx
  RUN ./test-statx test-file
  EOF
  $ docker build test-statx

  With the bug and current docker 18.06.1-0ubuntu1~18.04.1 in Bionic
  that yields

  [...]
  Step 8/8 : RUN ./test-statx test-file
   ---> Running in 6e60a82409e6
  test-file: Operation not permitted
  statx(test-file) = -1
  The command '/bin/sh -c ./test-statx test-file' returned a non-zero code: 1

  With the fix applied it would work and look like:
  Step 8/8 : RUN ./test-statx test-file
   ---> Running in a83bc043e7bd
  statx(test-file) = 0
  results=fff
Size: 0   Blocks: 0  IO Block: 4096regular file
  Device: 00:32   Inode: 261994  Links: 1
  Access: (0644/-rw-r--r--)  Uid: 0   Gid: 0
  Access: 2019-02-08 07:57:42.0+
  Modify: 2019-02-08 07:57:42.0+
  Change: 2019-02-08 07:57:43.076507007+
   Birth: 2019-02-08 07:57:43.076507007+
  Attributes:  (     
 -... .---.-..)
  Removing intermediate container a83bc043e7bd
   ---> d428d14cbc57
  Successfully built d428d14cbc57

  
  [Regression Potential] 

   * This "only" defines a new syscall number for all the architectures.
  It does not make any other changes, thereby it should be rather safe.
  If anything software could now manage statx through libseccomp and
  behavior that was formerly failing (like the reported docker case)
  would not succeed and due to that be a change in behavior - but I
  think it is a wanted change.

  [Other Info]
   
   * n/a

  ---

  
  Hello maintainer,

  The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall 
which is needed to build qt >=5.10 applications:
  https://github.com/docker/for-linux/issues/208#issuecomment-372400859

  Could this fix be backported in the ubuntu package ?
  https://github.com/moby/moby/pull/36417

  regards,
  xan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+subscriptions

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