[Touch-packages] [Bug 1946898] Re: Merge rsync from Debian unstable for 22.04

[Bryce Harrington]

** Changed in: rsync (Ubuntu)
Milestone: None => ubuntu-22.01

** Changed in: rsync (Ubuntu)
Milestone: ubuntu-22.01 => ubuntu-21.11

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

Title:
  Merge rsync from Debian unstable for 22.04

Status in rsync package in Ubuntu:
  New

Bug description:
  Scheduled-For: 23.01
  Upstream: tbd
  Debian:   3.2.3-8
  Ubuntu:   3.2.3-4ubuntu1


  Debian does new releases regularly, so it's likely there will be newer
  versions available before FF that we can pick up if this merge is done
  later in the cycle.

  
  ### New Debian Changes ###

  rsync (3.2.3-8) unstable; urgency=medium

* debian/patches:
  - manpage_upstream_fixes.patch: Import multiple upstream patches to fix
manpage.
  - copy-devices.diff: Add missing manpage changes to patch
  - CVE-2020-14387.patch: Add Forwarded DEP3 field to point to upstream 
patch
  - fix_delay_updates.patch: Refresh patch
  - fix_mkpath.patch: New upstream patch to fix an edge case on --mkpath
  - fix_rsync-ssl_RSYNC_SSL_CERT_feature.patch: New upstream patch
  - fix_sparse_inplace.patch: New upstream patch to fix --sparse + --inplace
options
  - update_rrsync_options.patch: New upstream patch to update rrsync options

   -- Samuel Henrique   Sat, 25 Sep 2021 17:38:16
  +0100

  rsync (3.2.3-7) unstable; urgency=medium

* Bump Standards-Version to 4.6.0
* d/p/workaround_glibc_lchmod_regression.patch: New patch from upstream
  (closes: #994543)
* debian/rsync.NEWS: Fix typo in last entry

   -- Samuel Henrique   Sat, 18 Sep 2021 00:25:13
  +0100

  rsync (3.2.3-6) unstable; urgency=medium

* d/t/upstream-tests: Suppress stderr warnings from the build
  process

   -- Samuel Henrique   Sun, 12 Sep 2021 18:22:57
  +0100

  rsync (3.2.3-5) unstable; urgency=medium

[ 刘建强 ]
* Set the rsync.service not to start automatically after installation,
  the rsyncd.conf configuration file needs to be configured by the user
  before the service can start

[ Samuel Henrique ]
* Re-add upstream patch for --copy-devices, the --write-devices option is
  not fully equivalent (closes: #992215)
* d/rsync.docs: Add NEWS.md file (previously named NEWS) (closes: #993697)
* d/p/fix_delay_updates.patch: New patch from upstream (closes: #992231)

   -- Samuel Henrique   Sun, 12 Sep 2021 17:25:37
  +0100

  rsync (3.2.3-4) unstable; urgency=medium

[ Helmut Grohne ]
* d/p/fix_ftcbfs_configure.patch: New patch to fix FTCBFS (closes: #971285)

[ Samuel Henrique ]
* Bump Standards-Version to 4.5.1

   -- Samuel Henrique   Tue, 02 Feb 2021 23:08:54
  +

  rsync (3.2.3-3) unstable; urgency=high

* d/p/CVE-2020-14387.patch: New patch to fix an openssl related CVE
  (closes: #969530, CVE-2020-14387)

   -- Samuel Henrique   Sat, 19 Dec 2020 12:48:33
  +

  rsync (3.2.3-2) unstable; urgency=medium

[ Sergio Durigan Junior ]
* Make the autopkgtests cross-friendly.
  Thanks to Steve Langasek 

   -- Samuel Henrique   Wed, 26 Aug 2020 21:23:57
  +0100

  rsync (3.2.3-1) unstable; urgency=medium

* New upstream version 3.2.3
* debian/patches:
  - time-limit.diff: Remove patch, applied upstream now
  - disable_reconfigure_req.diff: Refresh patch and dep3 headers
  - perl_shebang.patch: Update patch
  - fix_bwlimit_0.patch: Remove patch, applied upstream

   -- Samuel Henrique   Sun, 09 Aug 2020 13:41:10
  +0100

  rsync (3.2.2-2) unstable; urgency=medium

* d/p/fix_bwlimit_0.patch: New upstream patch to fix bwlimit=0
  (closes: #964587)

   -- Samuel Henrique   Fri, 10 Jul 2020 18:35:21
  +0100

  rsync (3.2.2-1) unstable; urgency=medium

* New upstream version 3.2.2
* d/rsync.install: Install rsync-no-vanished (closes: #353697)

   -- Samuel Henrique   Mon, 06 Jul 2020 19:01:52
  +0100

  rsync (3.2.1-1) unstable; urgency=medium

* New upstream version 3.2.1
* Remove patches applied upstream:


  ### Old Ubuntu Delta ###

  rsync (3.2.3-4ubuntu1) impish; urgency=low

* Merge from Debian unstable. Remaining changes:
  - debian/rules: add --disable-asm configure flag. The only asm
implementation is available for md5 on x86_64, however it is no-op,
because we built with OpenSSL which has optimized md5
implementation. Furthermore, linking noop md5 asm on x86_64 results in
rsync binary not getting marked as CET compatible, because the noop
md5 asm is not marked as CET compatible. Thus building without noop
md5 asm, results in rsync gaining CET.

   -- Julian Andres Klode   Mon, 10 May 2021
  11:27:26 +0200

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


-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1946883] Re: Merge openldap from Debian unstable for 22.04

[Bryce Harrington]

** Description changed:

- Scheduled-For: 22.12
- Upstream: tbd
- Debian:   2.4.59+dfsg-12.5.7+dfsg-1~exp1
+ Upstream: 2.5.8
+ Debian:   2.4.59+dfsg-12.5.8+dfsg-1~exp1
  Ubuntu:   2.5.6+dfsg-1~exp1ubuntu1
  
- 
- Debian new has 2.5.7+dfsg-1~exp1
- 
+ Debian experimental has 2.5.8+dfsg-1~exp1
  
  ### New Debian Changes ###
  
  openldap (2.4.59+dfsg-1) unstable; urgency=medium
  
-   * New upstream release.
-   * Fix FTBFS with autoconf 2.71 (Closes: #993032):
- - Backport upstream changes to support Autoconf 2.69 instead of simply
-   disabling automake in debian/rules. Fixes FTBFS due to autoreconf
-   thinking files required by Automake are missing, even though Automake is
-   not actually used.
- - Stop running autoreconf in contrib/ldapc++ since we don't build it.
- - Drop custom config.{guess,sub} handling. dh_update_autotools_config does
-   the right thing for us.
-   * Update Standards-Version to 4.6.0; no changes required.
-   * Add a superficial autopkgtest for smbk5pwd.
-   * Stop disabling test060-mt-hot on ppc64el. The underlying kernel bug
- (#866122) is fixed in all relevant suites by now.
+   * New upstream release.
+   * Fix FTBFS with autoconf 2.71 (Closes: #993032):
+ - Backport upstream changes to support Autoconf 2.69 instead of simply
+   disabling automake in debian/rules. Fixes FTBFS due to autoreconf
+   thinking files required by Automake are missing, even though Automake is
+   not actually used.
+ - Stop running autoreconf in contrib/ldapc++ since we don't build it.
+ - Drop custom config.{guess,sub} handling. dh_update_autotools_config does
+   the right thing for us.
+   * Update Standards-Version to 4.6.0; no changes required.
+   * Add a superficial autopkgtest for smbk5pwd.
+   * Stop disabling test060-mt-hot on ppc64el. The underlying kernel bug
+ (#866122) is fixed in all relevant suites by now.
  
-  -- Ryan Tandy   Fri, 27 Aug 2021 09:42:31 -0700
+  -- Ryan Tandy   Fri, 27 Aug 2021 09:42:31 -0700
  
  openldap (2.4.57+dfsg-3) unstable; urgency=medium
  
-   * Link smbk5pwd with -lkrb5. (Closes: #988565)
+   * Link smbk5pwd with -lkrb5. (Closes: #988565)
  
-  -- Ryan Tandy   Sat, 15 May 2021 16:03:34 -0700
+  -- Ryan Tandy   Sat, 15 May 2021 16:03:34 -0700
  
  openldap (2.4.57+dfsg-2) unstable; urgency=medium
  
-   * Fix slapd assertion failure in Certificate List Exact Assertion validation
- (ITS#9454) (CVE-2021-27212)
+   * Fix slapd assertion failure in Certificate List Exact Assertion validation
+ (ITS#9454) (CVE-2021-27212)
  
-  -- Ryan Tandy   Sun, 14 Feb 2021 09:26:41 -0800
+  -- Ryan Tandy   Sun, 14 Feb 2021 09:26:41 -0800
  
  openldap (2.4.57+dfsg-1) unstable; urgency=medium
  
-   * New upstream release.
- - Fixed slapd crashes in Certificate Exact Assertion processing
-   (ITS#9404, ITS#9424) (CVE-2020-36221)
- - Fixed slapd assertion failures in saslAuthzTo validation
-   (ITS#9406, ITS#9407) (CVE-2020-36222)
- - Fixed slapd crash in Values Return Filter control handling
-   (ITS#9408) (CVE-2020-36223)
- - Fixed slapd crashes in saslAuthzTo processing
-   (ITS#9409, ITS#9412, ITS#9413)
-   (CVE-2020-36224, CVE-2020-36225, CVE-2020-36226)
- - Fixed slapd assertion failure in X.509 DN parsing
-   (ITS#9423) (CVE-2020-36230)
- - Fixed slapd crash in X.509 DN parsing (ITS#9425) (CVE-2020-36229)
- - Fixed slapd crash in Certificate List Exact Assertion processing
-   (ITS#9427) (CVE-2020-36228)
- - Fixed slapd infinite loop with Cancel operation
-   (ITS#9428) (CVE-2020-36227)
+   * New upstream release.
+ - Fixed slapd crashes in Certificate Exact Assertion processing
+   (ITS#9404, ITS#9424) (CVE-2020-36221)
+ - Fixed slapd assertion failures in saslAuthzTo validation
+   (ITS#9406, ITS#9407) (CVE-2020-36222)
+ - Fixed slapd crash in Values Return Filter control handling
+   (ITS#9408) (CVE-2020-36223)
+ - Fixed slapd crashes in saslAuthzTo processing
+   (ITS#9409, ITS#9412, ITS#9413)
+   (CVE-2020-36224, CVE-2020-36225, CVE-2020-36226)
+ - Fixed slapd assertion failure in X.509 DN parsing
+   (ITS#9423) (CVE-2020-36230)
+ - Fixed slapd crash in X.509 DN parsing (ITS#9425) (CVE-2020-36229)
+ - Fixed slapd crash in Certificate List Exact Assertion processing
+   (ITS#9427) (CVE-2020-36228)
+ - Fixed slapd infinite loop with Cancel operation
+   (ITS#9428) (CVE-2020-36227)
  
-  -- Ryan Tandy   Sat, 23 Jan 2021 08:57:07 -0800
+  -- Ryan Tandy   Sat, 23 Jan 2021 08:57:07 -0800
  
  openldap (2.4.56+dfsg-1) unstable; urgency=medium
  
-   * New upstream release.
- - Fixed slapd abort due to assertion failure in Certificate List syntax
-   validation (ITS#9383) (CVE-2020-25709)
- - Fixed slapd abort due to assertion failure in CSN normalization with
-   invalid input (ITS#9384) (CVE-2020-25710)
+   * New upstream release.
+ - Fixed 

[Touch-packages] [Bug 1946878] Re: Merge net-tools from Debian unstable for 22.04

[Bryce Harrington]

** Description changed:

- Scheduled-For: 22.11
- Upstream: tbd
- Debian:   1.60+git20181103.0eebece-1
+ Upstream: 1.60+git20210422.dfc41e0
+ Debian:   1.60+git20181103.0eebece-1
  Ubuntu:   1.60+git20181103.0eebece-1ubuntu2
  
- 
+ Debian updates this package infrequently, and last updated it 20.10.
+ There is a new upstream version, however, so may be worth going ahead of 
debian and/or updating it in Debian and syncing it.
  
  ### New Debian Changes ###
  
  net-tools (1.60+git20181103.0eebece-1) unstable; urgency=medium
  
-   * New upstream version 1.60+git20181103.0eebece
- - Fix nstrcmp() to prevent ifconfig from showing
-   duplicate interfaces. (Closes: #812886)
-   * Fix d/watch to point to upstream git repository
-   * Add patch to fix decoding of MII vendor ids. (Closes: #549397)
- - Thanks, Ben Hutchings, for the patch.
-   * Add patch to fix Japanese translation which uses a wrong
- Kanji character. (Closes: #621752)
- - Thanks, Takeshi Hamasaki, for the patch.
-   * Add patch to fix wrong indentation of 'collisions' in  the
- Japanese translation. (Closes: #653117)
- - Thanks, NODA, Kai, for the patch.
-   * Fix Uploaders' field.
- - Add myself as an uploader.
- - Fix Tina's details.
+   * New upstream version 1.60+git20181103.0eebece
+ - Fix nstrcmp() to prevent ifconfig from showing
+   duplicate interfaces. (Closes: #812886)
+   * Fix d/watch to point to upstream git repository
+   * Add patch to fix decoding of MII vendor ids. (Closes: #549397)
+ - Thanks, Ben Hutchings, for the patch.
+   * Add patch to fix Japanese translation which uses a wrong
+ Kanji character. (Closes: #621752)
+ - Thanks, Takeshi Hamasaki, for the patch.
+   * Add patch to fix wrong indentation of 'collisions' in  the
+ Japanese translation. (Closes: #653117)
+ - Thanks, NODA, Kai, for the patch.
+   * Fix Uploaders' field.
+ - Add myself as an uploader.
+ - Fix Tina's details.
  
-  -- Utkarsh Gupta   Fri, 02 Oct 2020 15:01:04 +0530
+  -- Utkarsh Gupta   Fri, 02 Oct 2020 15:01:04 +0530
  
  net-tools (1.60+git20180626.aebd88e-1) unstable; urgency=medium
  
-   * New upstream snapshot
-   * Refresh patches.
-   * Fix typos in German manpages. Thanks to Prof. Dr. Steffen Wendzel and
- Dr. Tobias Quathamer for the patch. Closes: #900962.
+   * New upstream snapshot
+   * Refresh patches.
+   * Fix typos in German manpages. Thanks to Prof. Dr. Steffen Wendzel and
+ Dr. Tobias Quathamer for the patch. Closes: #900962.
  
-  -- Martín Ferrari   Mon, 24 Sep 2018 19:08:57 +
+  -- Martín Ferrari   Mon, 24 Sep 2018 19:08:57 +
  
  net-tools (1.60+git20161116.90da8a0-4) unstable; urgency=medium
  
-   * Update maintainer email address. Closes: #899617.
-   * Update Standards-Version with no changes.
+   * Update maintainer email address. Closes: #899617.
+   * Update Standards-Version with no changes.
  
-  -- Martín Ferrari   Mon, 24 Sep 2018 17:16:31 +
+  -- Martín Ferrari   Mon, 24 Sep 2018 17:16:31 +
  
  net-tools (1.60+git20161116.90da8a0-3) unstable; urgency=medium
  
-   * debian/control: Update Vcs-* and Standards-Version.
-   * debian/control: remove references to ancient package ja-trans.
-   * debian/gbp.conf: Update repo layout.
+   * debian/control: Update Vcs-* and Standards-Version.
+   * debian/control: remove references to ancient package ja-trans.
+   * debian/gbp.conf: Update repo layout.
  
-  -- Martín Ferrari   Tue, 31 Jul 2018 19:09:00 +
+  -- Martín Ferrari   Tue, 31 Jul 2018 19:09:00 +
  
  net-tools (1.60+git20161116.90da8a0-2) unstable; urgency=medium
  
-   * Fix typo in French manpage. Thanks to  Michel Grigaut for the patch.
-   * Add manpage for iptunnel, thanks to Sergio Durigan Junior.
- Closes: #88910
-   * Rename patches so CME does not choke on them.
-   * Automated cme fixes; packaging improvements.
-   * Remove unused and ancient patch.
+   * Fix typo in French manpage. Thanks to  Michel Grigaut for the patch.
+   * Add manpage for iptunnel, thanks to Sergio Durigan Junior.
+ Closes: #88910
+   * Rename patches so CME does not choke on them.
+   * Automated cme fixes; packaging improvements.
+   * Remove unused and ancient patch.
  
-  -- Martín Ferrari   Sun, 11 Feb 2018 17:29:24 +
+  -- Martín Ferrari   Sun, 11 Feb 2018 17:29:24 +
  
  net-tools (1.60+git20161116.90da8a0-1) unstable; urgency=medium
  
-   * New upstream snapshot.
-   * Re-synced translations.patch.
-   * Acknowledge NMUs. Thanks a lot to Andrey Rahmatullin for the
- fixes and uploads. Closes: 846509.
-   * Fix FTCBFS, thanks to Helmut Grohne for the patch. Closes: #811561.
- + Really assign CC for cross compilation.
- + Use triplet prefixed pkg-config.
-   * Add debian/NEWS warning about changing output in net-tools commands.
- Closing bugs that reported problems in 3rd-party scripts arising from 
these
- changes.  Closes: #845153, #843892, #820212.
-   * Update 

[Touch-packages] [Bug 1946847] Re: Merge bridge-utils from Debian unstable for 22.04

[Bryce Harrington]

** Description changed:

- Scheduled-For: 22.12
  Upstream: tbd
- Debian:   1.7-1
+ Debian:   1.7-1
  Ubuntu:   1.7-1ubuntu2
- 
  
  Debian typically updates bridge-utils every 4 months on average, but it
  was last updated 21.02 and looks overdue.  Check back in on this
  monthly.
  
  No release expected for bridge-utils this cycle
  
- 
  ### New Debian Changes ###
  
  bridge-utils (1.7-1) unstable; urgency=medium
  
-   * New upstream version.
- Only messages related changes and compilation fixes.
-   * Remove preserve_gcc_flags patch (in upstream now).
-   * Bump standards, no change needed.
-   * Clarify portprio and fix example.
-   * Update upstream url.
-   * Fix NEWS versioning of last entry :-?
+   * New upstream version.
+ Only messages related changes and compilation fixes.
+   * Remove preserve_gcc_flags patch (in upstream now).
+   * Bump standards, no change needed.
+   * Clarify portprio and fix example.
+   * Update upstream url.
+   * Fix NEWS versioning of last entry :-?
  
-  -- Santiago Garcia Mantinan   Wed, 24 Feb 2021
+  -- Santiago Garcia Mantinan   Wed, 24 Feb 2021
  12:34:03 +0100
  
  bridge-utils (1.6-6) unstable; urgency=medium
  
-   * Fix IPv6 address getting assigned on hotplug devices.
- Closes: #980752.
-   * Fix waiting so that DAD works again. Closes: #982943.
-   * Move mac setting before brctl addif to ensure mac setting.
- Closes: #980856.
-   * Update documentation and add examples. Closes: #765098.
-   * Update manpages. Closes: #981253.
-   * Add a note on MTU settings. Closes: #292088.
-   * Hook also on down to recreate the bridge so that multiple
- stanzas work Ok on ifdown. Closes: #319832.
+   * Fix IPv6 address getting assigned on hotplug devices.
+ Closes: #980752.
+   * Fix waiting so that DAD works again. Closes: #982943.
+   * Move mac setting before brctl addif to ensure mac setting.
+ Closes: #980856.
+   * Update documentation and add examples. Closes: #765098.
+   * Update manpages. Closes: #981253.
+   * Add a note on MTU settings. Closes: #292088.
+   * Hook also on down to recreate the bridge so that multiple
+ stanzas work Ok on ifdown. Closes: #319832.
  
-  -- Santiago Garcia Mantinan   Tue, 16 Feb 2021
+  -- Santiago Garcia Mantinan   Tue, 16 Feb 2021
  13:29:04 +0100
  
  bridge-utils (1.6-5) unstable; urgency=low
  
-   * Overload bridge_hw to allow do specify an interface as well as the
- MAC address. Closes: #966244.
-   * Change man page for bridge-utils-interfaces and news fileto document
- this overloading.
+   * Overload bridge_hw to allow do specify an interface as well as the
+ MAC address. Closes: #966244.
+   * Change man page for bridge-utils-interfaces and news fileto document
+ this overloading.
  
-  -- Santiago Garcia Mantinan   Fri, 22 Jan 2021
+  -- Santiago Garcia Mantinan   Fri, 22 Jan 2021
  11:08:47 +0100
  
  bridge-utils (1.6-4) unstable; urgency=low
  
-   * Add en* to the device regex so that all catches them. Closes: #966319.
-   * Document MAC address changes on news. Closes: #980505.
+   * Add en* to the device regex so that all catches them. Closes: #966319.
+   * Document MAC address changes on news. Closes: #980505.
  
-  -- Santiago Garcia Mantinan   Thu, 21 Jan 2021
+  -- Santiago Garcia Mantinan   Thu, 21 Jan 2021
  10:51:31 +0100
  
  bridge-utils (1.6-3) unstable; urgency=medium
  
-   * Support VLAN aware setups where we need vlan filtering.
- Thanks Benedikt Spranger for the patch. Closes: #950879.
-   * Clarify on manual page that stp will get IPv6 lost. Closes: #736336.
-   * Add a 1 second sleep if hw address needs to be changed. Closes: #945466.
+   * Support VLAN aware setups where we need vlan filtering.
+ Thanks Benedikt Spranger for the patch. Closes: #950879.
+   * Clarify on manual page that stp will get IPv6 lost. Closes: #736336.
+   * Add a 1 second sleep if hw address needs to be changed. Closes: #945466.
  
-  -- Santiago Garcia Mantinan   Thu, 30 Apr 2020
+  -- Santiago Garcia Mantinan   Thu, 30 Apr 2020
  10:06:38 +0200
  
  bridge-utils (1.6-2) unstable; urgency=medium
  
-   * Bump Standards-Version.
-   * Preserve gcc flags set when building the lib.
+   * Bump Standards-Version.
+   * Preserve gcc flags set when building the lib.
  
-  -- Santiago Garcia Mantinan   Mon, 28 Jan 2019
+  -- Santiago Garcia Mantinan   Mon, 28 Jan 2019
  00:25:14 +0100
  
  bridge-utils (1.6-1) unstable; urgency=low
  
-   * New upstream version.
-   * Change default back to not hotplug. Closes: #892277.
-   * Allow mtu to be set on the bridge by propagating it to the bridged
- interfaces. Closes: #661711.
-   * Remove kernel headers from the package.
+   * New upstream version.
+   * Change default back to not hotplug. Closes: #892277.
+   * Allow mtu to be set on the bridge by propagating it to the bridged
+ interfaces. Closes: #661711.
+   * Remove kernel headers from the package.
  
-  -- Santiago Garcia Mantinan   Tue, 15 Jan 2019

[Touch-packages] [Bug 1946860] Re: Merge heimdal from Debian unstable for 22.04

[Bryce Harrington]

** Description changed:

- Scheduled-For: 22.11
  Upstream: tbd
- Debian:   7.7.0+dfsg-2
+ Debian:   7.7.0+dfsg-2
  Ubuntu:   7.7.0+dfsg-2ubuntu2
- 
- 
  
  ### New Debian Changes ###
  
  heimdal (7.7.0+dfsg-2) unstable; urgency=medium
  
-   * Build using python3. Closes: #936695, #960032.
+   * Build using python3. Closes: #936695, #960032.
  
-  -- Brian May   Tue, 12 May 2020 06:56:04 +1000
+  -- Brian May   Tue, 12 May 2020 06:56:04 +1000
  
  heimdal (7.7.0+dfsg-1) unstable; urgency=medium
  
-   * New upstream version.
-   * Fix CVE-2019-14870: The DelegationNotAllowed Kerberos feature restriction
- was not being applied when processing protocol
- transition requests (S4U2Self), in the AD DC KDC. Closes: #946786.
+   * New upstream version.
+   * Fix CVE-2019-14870: The DelegationNotAllowed Kerberos feature restriction
+ was not being applied when processing protocol
+ transition requests (S4U2Self), in the AD DC KDC. Closes: #946786.
  
-  -- Brian May   Tue, 17 Dec 2019 20:23:41 +1100
+  -- Brian May   Tue, 17 Dec 2019 20:23:41 +1100
  
  heimdal (7.5.0+dfsg-3) unstable; urgency=high
  
-   * CVE-2018-16860: Samba AD DC S4U2Self/S4U2Proxy unkeyed checksum.
- Closes: #928966.
-   * CVE-2019-12098: Always confirm PA-PKINIT-KX for anon PKINIT.
- Closes: #929064.
-   * Update test certificates to pre 2038 expiry. Closes: #923930.
+   * CVE-2018-16860: Samba AD DC S4U2Self/S4U2Proxy unkeyed checksum.
+ Closes: #928966.
+   * CVE-2019-12098: Always confirm PA-PKINIT-KX for anon PKINIT.
+ Closes: #929064.
+   * Update test certificates to pre 2038 expiry. Closes: #923930.
  
-  -- Brian May   Tue, 21 May 2019 18:04:35 +1000
+  -- Brian May   Tue, 21 May 2019 18:04:35 +1000
  
  heimdal (7.5.0+dfsg-2.1) unstable; urgency=medium
  
-   * Non-maintainer upload
-   * Add patch to create headers before building (Closes: 906623)
+   * Non-maintainer upload
+   * Add patch to create headers before building (Closes: 906623)
  
-  -- Hilko Bengen   Sun, 28 Oct 2018 15:10:44 +0100
+  -- Hilko Bengen   Sun, 28 Oct 2018 15:10:44 +0100
  
  heimdal (7.5.0+dfsg-2) unstable; urgency=medium
  
-   * Replace 'MAXHOSTNAMELEN' with 'MaxHostNameLen' in kdc/kx509.c for The
- Hurd. Closes: #900079.
+   * Replace 'MAXHOSTNAMELEN' with 'MaxHostNameLen' in kdc/kx509.c for The
+ Hurd. Closes: #900079.
  
-  -- Brian May   Sat, 02 Jun 2018 10:01:46 +1000
+  -- Brian May   Sat, 02 Jun 2018 10:01:46 +1000
  
  heimdal (7.5.0+dfsg-1) unstable; urgency=high
  
-   * New upstream version. (Closes: #850723)
- + CVE-2017-17439: Remote unauthenticated DoS in Heimdal-KDC 7.4
-   (Closes: #878144, #868157)
- + Refresh patches.
-   * Bump Standards-Version to 4.1.2 and compat level to 10.
- + Remove explicit reference to dh-autoreconf.
-   * Use uscan to get orig source.
- + Refrain from mangling some bundled RFC texts;
-   just exclude the mas they are not installed into any binary anyway.
- + Update d/copyright to DEP-5.
- + Can now use standard uscan/gbp/pristine-tar workflow.
-   * Fix some lintian errors/warnings.
- + Strip trailing whitespace from changelog.
- + Fix some duplicate long descriptions.
- + Use optional priority everywhere.
- + Update/remove some overrides.
- + Enforce set -e in maintainer scripts.
- + Enable hardening.
-   * Migrate to -dbgsym.
-   * Add myself to uploaders.
+   * New upstream version. (Closes: #850723)
+ + CVE-2017-17439: Remote unauthenticated DoS in Heimdal-KDC 7.4
+   (Closes: #878144, #868157)
+ + Refresh patches.
+   * Bump Standards-Version to 4.1.2 and compat level to 10.
+ + Remove explicit reference to dh-autoreconf.
+   * Use uscan to get orig source.
+ + Refrain from mangling some bundled RFC texts;
+   just exclude the mas they are not installed into any binary anyway.
+ + Update d/copyright to DEP-5.
+ + Can now use standard uscan/gbp/pristine-tar workflow.
+   * Fix some lintian errors/warnings.
+ + Strip trailing whitespace from changelog.
+ + Fix some duplicate long descriptions.
+ + Use optional priority everywhere.
+ + Update/remove some overrides.
+ + Enforce set -e in maintainer scripts.
+ + Enable hardening.
+   * Migrate to -dbgsym.
+   * Add myself to uploaders.
  
-  -- Dominik George   Fri, 15 Dec 2017 01:13:04 +0100
+  -- Dominik George   Fri, 15 Dec 2017 01:13:04 +0100
  
  heimdal (7.4.0.dfsg.1-2) unstable; urgency=medium
  
-   [ Jelmer Vernooij ]
-   * Remove myself from uploaders.
+   [ Jelmer Vernooij ]
+   * Remove myself from uploaders.
  
-   [ Brian May ]
-   * Be explicit with heimdal.mkey filename in postinst. Closes: #868638.
-   * Tests should respect DEB_BUILD_OPTIONS=nocheck.  Closes: #868842.
+   [ Brian May ]
+   * Be explicit with heimdal.mkey filename in postinst. Closes: #868638.
+   * Tests should respect DEB_BUILD_OPTIONS=nocheck.  Closes: #868842.
  
-  -- Brian May   Sun, 23 Jul 2017 10:32:34 +1000
+  

[Touch-packages] [Bug 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[Daniel van Vugt]

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

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470
(Ubuntu)

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

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

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1892825] Re: update-locale not perform correctly sanity checks

[Michael Hudson-Doyle]

** Also affects: glibc (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: pam (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: pam (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: pam (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

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

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

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  New
Status in glibc source package in Bionic:
  New
Status in pam source package in Bionic:
  New
Status in glibc source package in Focal:
  New
Status in pam source package in Focal:
  New
Status in glibc source package in Hirsute:
  New
Status in pam source package in Hirsute:
  New
Status in glibc source package in Impish:
  New
Status in pam source package in Impish:
  New

Bug description:
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale 
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1892825] Re: update-locale not perform correctly sanity checks

[Gunnar Hjalmarsson]

@Michael: I could easily reproduce the issue at the time (a year ago).

Good that it's about to be fixed. As you can see in comment #2 I first
turned to Debian, but the response was a bit disappointing. Any chance
that you can handle this on the Debian side too?

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

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  New

Bug description:
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale 
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1947526] Re: can't run associated docker-compose

[Seth Arnold]

Hello Andrew, I don't understand what exactly is broken; your logs show
a lot of AppArmor profiles loading without trouble.

What are you trying to do? What's going wrong?

Thanks

** Changed in: apparmor (Ubuntu)
   Status: New => Incomplete

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

Title:
  can't run associated docker-compose

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  I can't seem to get apparmor to run at all, even sudo rm and sudo
  restart in the /etc/init.d/apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu5.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 17 17:56:59 2021
  InstallationDate: Installed on 2021-08-31 (47 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=ca77035a-d2b3-4803-a4e1-333e95d847fb ro quiet splash
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.abstractions.mysql: [deleted]
  modified.conffile..etc.apparmor.parser.conf: [deleted]

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


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

[Touch-packages] [Bug 1892825] Re: update-locale not perform correctly sanity checks

[Michael Hudson-Doyle]

Adding a pam task, pam_env does some sanity checking of the input (e.g.
%=1 in /etc/default/locale gets ignored) so I don't see why an empty
variable name should cause a total failure. But will fix the update-
locale script too.

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

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

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  New

Bug description:
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale 
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1943359] Re: Cherry-pick crypt_checksalt fix

[Jeremy Bicha]

** Changed in: pam (Ubuntu)
   Status: Incomplete => New

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

Title:
  Cherry-pick crypt_checksalt fix

Status in pam package in Ubuntu:
  New

Bug description:
  Please cherry-pick this commit (included in Debian's pam 1.4.0-10 or
  upstream 1.5.2)

  https://github.com/linux-pam/linux-pam/commit/980d90c9232fe5

  The pam upstream bug is
  https://github.com/linux-pam/linux-pam/issues/367

  I believe we need this fix before updating libxcrypt to 1:4.4.22-1

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


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

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

[Launchpad Bug Tracker]

This bug was fixed in the package gdebi - 0.9.5.7+nmu6

---
gdebi (0.9.5.7+nmu6) unstable; urgency=medium

  * Non-maintainer upload

  [ Christian Ehrhardt ]
  * GDebi/GDebiGtk.py:
- Don't call gio_copy_in_place if there is no path / uri being
  passed (LP: #1931394, closes: #989647).

  [ Dani Llewellyn ]
  * GDebi/GDebiGtk.py:
- Drop Ubuntu-specific changes - no-longer needed
  (LP: #1756238, LP: #1946499)

 -- Gunnar Hjalmarsson   Thu, 14 Oct 2021 23:45:16
+0200

** Changed in: gdebi (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 gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1946499

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Invalid
Status in gdebi package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Confirmed
Status in gdebi source package in Impish:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start 

[Touch-packages] [Bug 1947617] Re: Cannot configure suspend-then-hibernate

[Dan Streetman]

You have 16G of memory:

> [0.081527] Memory: 15609664K/16134968K available

But you only seem to have 2G of swap:

[2.770354] Adding 2097148k swap on /swapfile

There is no way hibernation is possible on your system with this setup.

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

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

Title:
  Cannot configure suspend-then-hibernate

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Configuring login to suspend-then-hiberrnate when the lid is off and
  configuring sleep so that hibernate happens 10 seconds after suspend,
  when trying to test with:

  sudo systemctl suspend-then-hibernate

  I get:

  Failed to suspend system, hibernate later via logind: Sleep verb
  "suspend-then-hibernate" not supported

  This could be a security vulnerability. If the user expects the system
  to suspend (and then lock) when the lid is off and it does not work,
  somebody could then just reopen the lid and get access.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: i3
  Date: Mon Oct 18 18:57:35 2021
  InstallationDate: Installed on 2021-10-14 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ENVY x360 Convertible 13-ay0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=e85d08c2-ae82-4f0f-a625-a5012616c934 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2021
  dmi.bios.release: 15.20
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 876E
  dmi.board.vendor: HP
  dmi.board.version: 12.52
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 12.52
  dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd07/30/2021:br15.20:efr12.52:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:sku3V693EA#ABF:rvnHP:rn876E:rvr12.52:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx
  dmi.product.sku: 3V693EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.logind.conf: 2021-10-18T18:51:43.976989
  mtime.conffile..etc.systemd.sleep.conf: 2021-10-18T18:52:04.283409

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


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

[Touch-packages] [Bug 1947617] [NEW] Cannot configure suspend-then-hibernate

[Larry Skywalker]

Public bug reported:

Configuring login to suspend-then-hiberrnate when the lid is off and
configuring sleep so that hibernate happens 10 seconds after suspend,
when trying to test with:

sudo systemctl suspend-then-hibernate

I get:

Failed to suspend system, hibernate later via logind: Sleep verb
"suspend-then-hibernate" not supported

This could be a security vulnerability. If the user expects the system
to suspend (and then lock) when the lid is off and it does not work,
somebody could then just reopen the lid and get access.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: systemd 248.3-1ubuntu8
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: i3
Date: Mon Oct 18 18:57:35 2021
InstallationDate: Installed on 2021-10-14 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: HP HP ENVY x360 Convertible 13-ay0xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=e85d08c2-ae82-4f0f-a625-a5012616c934 ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
 [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: 
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
 --
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: 
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2021
dmi.bios.release: 15.20
dmi.bios.vendor: Insyde
dmi.bios.version: F.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 876E
dmi.board.vendor: HP
dmi.board.version: 12.52
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 12.52
dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd07/30/2021:br15.20:efr12.52:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:sku3V693EA#ABF:rvnHP:rn876E:rvr12.52:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx
dmi.product.sku: 3V693EA#ABF
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
mtime.conffile..etc.systemd.logind.conf: 2021-10-18T18:51:43.976989
mtime.conffile..etc.systemd.sleep.conf: 2021-10-18T18:52:04.283409

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


** Tags: amd64 apport-bug impish

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

Title:
  Cannot configure suspend-then-hibernate

Status in systemd package in Ubuntu:
  New

Bug description:
  Configuring login to suspend-then-hiberrnate when the lid is off and
  configuring sleep so that hibernate happens 10 seconds after suspend,
  when trying to test with:

  sudo systemctl suspend-then-hibernate

  I get:

  Failed to suspend system, hibernate later via logind: Sleep verb
  "suspend-then-hibernate" not supported

  This could be a security vulnerability. If the user expects the system
  to suspend (and then lock) when the lid is off and it does not work,
  somebody could then just reopen the lid and get access.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: i3
  Date: Mon Oct 18 18:57:35 2021
  InstallationDate: Installed on 2021-10-14 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ENVY x360 Convertible 13-ay0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=e85d08c2-ae82-4f0f-a625-a5012616c934 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 

[Touch-packages] [Bug 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

[Olivier Tilloy]

Sam, I know this doesn't address your main grief (it is actively being
worked on and tracked in a separate place), but for support purposes,
the "Help > About Firefox" dialog will show you whether the application
is packaged as a snap. Alternatively opening "about:support" will also
reveal this information. That's probably a bit easier than asking users
to run commands in a terminal.

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

Title:
  [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Fix Released
Status in ubuntu-settings source package in Impish:
  Fix Released

Bug description:
  Per Canonical's distribution agreement with Mozilla, we're making the
  snap¹ the default installation of firefox on desktop ISOs starting
  with Ubuntu 21.10.

  The snap is built and published for amd64, armhf and arm64. It is
  jointly maintained by Mozilla and the Ubuntu desktop team, and
  published by Mozilla.

  This requires updating the desktop-minimal seed, as well as ubuntu-
  release-upgrader.

  ¹ https://snapcraft.io/firefox

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


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

[Touch-packages] [Bug 1947475] Re: PAM: pam_chroot.so not accessible after upgrade 21.04 > 21.10

[Steve Langasek]

This is a regression in the libpam-chroot package, which is installing
the module to the wrong path, not where libpam looks for it.

libpam-chroot is a separate source package in universe; reassigning.

** Package changed: pam (Ubuntu) => libpam-chroot (Ubuntu)

** Changed in: libpam-chroot (Ubuntu)
   Status: New => Triaged

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

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

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

Title:
  PAM: pam_chroot.so not accessible after upgrade 21.04 > 21.10

Status in libpam-chroot package in Ubuntu:
  Triaged
Status in libpam-chroot package in Debian:
  Unknown

Bug description:
  After upgrading Ubuntu server (AMD64) from 21.04 to 21.10 the module
  pam_chroot.so cannot be loaded by PAM anymore.

  21.10
  -
  auth.log:
  sshd: PAM unable to dlopen(pam_chroot.so): /lib/security/pam_chroot.so: 
cannot open shared object file: No such file or directory
  sshd: PAM adding faulty module: pam_chroot.so

  # find / -name 'pam_chroot.so'
  /usr/lib/x86_64-linux-gnu/pam_chroot.so

  21.04
  -
  # find / -type f -name 'pam_chroot.so'
  /usr/lib/security/pam_chroot.so

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-release-upgrader-core 1:21.10.8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Sat Oct 16 21:02:22 2021
  InstallationDate: Installed on 2020-12-07 (313 days ago)
  InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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


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

[Touch-packages] [Bug 1947475] Re: PAM: pam_chroot.so not accessible after upgrade 21.04 > 21.10

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => pam (Ubuntu)

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

Title:
  PAM: pam_chroot.so not accessible after upgrade 21.04 > 21.10

Status in libpam-chroot package in Ubuntu:
  Triaged
Status in libpam-chroot package in Debian:
  Unknown

Bug description:
  After upgrading Ubuntu server (AMD64) from 21.04 to 21.10 the module
  pam_chroot.so cannot be loaded by PAM anymore.

  21.10
  -
  auth.log:
  sshd: PAM unable to dlopen(pam_chroot.so): /lib/security/pam_chroot.so: 
cannot open shared object file: No such file or directory
  sshd: PAM adding faulty module: pam_chroot.so

  # find / -name 'pam_chroot.so'
  /usr/lib/x86_64-linux-gnu/pam_chroot.so

  21.04
  -
  # find / -type f -name 'pam_chroot.so'
  /usr/lib/security/pam_chroot.so

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-release-upgrader-core 1:21.10.8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Sat Oct 16 21:02:22 2021
  InstallationDate: Installed on 2020-12-07 (313 days ago)
  InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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


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

[Touch-packages] [Bug 1947475] [NEW] PAM: pam_chroot.so not accessible after upgrade 21.04 > 21.10

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrading Ubuntu server (AMD64) from 21.04 to 21.10 the module
pam_chroot.so cannot be loaded by PAM anymore.

21.10
-
auth.log:
sshd: PAM unable to dlopen(pam_chroot.so): /lib/security/pam_chroot.so: cannot 
open shared object file: No such file or directory
sshd: PAM adding faulty module: pam_chroot.so

# find / -name 'pam_chroot.so'
/usr/lib/x86_64-linux-gnu/pam_chroot.so

21.04
-
# find / -type f -name 'pam_chroot.so'
/usr/lib/security/pam_chroot.so

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: ubuntu-release-upgrader-core 1:21.10.8
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
Date: Sat Oct 16 21:02:22 2021
InstallationDate: Installed on 2020-12-07 (313 days ago)
InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting

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


** Tags: amd64 apport-bug dist-upgrade impish
-- 
PAM: pam_chroot.so not accessible after upgrade 21.04 > 21.10
https://bugs.launchpad.net/bugs/1947475
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pam 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 1006898] Re: [SRU] dnsmasq fails at leasing issues when using vlan mode

[Christian Parpart]

Many thanks Chris.

I just felt triggered by this closing because I remember how much pain
this bug caused me while working in a data center back in the days. :)

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

Title:
  [SRU] dnsmasq fails at leasing issues when using vlan mode

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Precise:
  Won't Fix

Bug description:
  ** Issue **

  There is an issue with the way nova uses dnsmasq in VLAN mode. It starts
  up a single copy of dnsmasq for each vlan on the network host (or on
  every host in multi_host mode). The problem is in the way that dnsmasq
  binds to an ip address and port[2]. Both copies can respond to broadcast
  packet, but unicast packets can only be answered by one of the copies.

  In nova this means that guests from only one project will get responses
  to their unicast dhcp renew requests. Unicast projects from guests in
  other projects get ignored. What happens next is different depending on
  the guest os. Linux generally will send a broadcast packet out after
  the unicast fails, and so the only effect is a small (tens of ms) hiccup
  while interface is reconfigured. It can be much worse than that,
  however. I have seen cases where Windows just gives up and ends up with
  a non-configured interface.

  This bug was first noticed by some users of openstack who rolled their
  own fix. Basically, on linux, if you set the SO_BINDTODEVICE socket
  option, it will allow different daemons to share the port and respond to
  unicast packets, as long as they listen on different interfaces. I
  managed to communicate with Simon Kelley, the maintainer of dnsmasq and
  he has integrated a fix[3] for the issue in the current version[1] of
  dnsmaq.

  [3]
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=9380ba70d67db6b69f817d8e318de5ba1e990b12

  ** Development Fix **

  This has been fixed in quantal with the newer version of dnmasq.

  ** Stable Fix **

  I have backported the patch which fixes this issue, I have attached
  the debdiff and the buildlog.

  ** Test Case **

  1. Install openstack with vlan mode.
  2. Watch instances loose their IP addresses.

  ** Regression Potential **

  Minimal, most installations dont use this type of networking.

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


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

[Touch-packages] [Bug 1899343] Re: tzdata sets /etc/timezone to `/UTC`, not `Etc/UTC`

[Launchpad Bug Tracker]

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

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

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

Title:
  tzdata sets /etc/timezone to `/UTC`, not `Etc/UTC`

Status in tzdata package in Ubuntu:
  Confirmed

Bug description:
  When installed within the `ubuntu` Docker container, `tzdata` sets
  `etc/timezone` to `/UTC`, not `Etc/UTC`, which breaks applications
  that are reading `etc/timezone` and expecting a valid timezone name.

  I'm guess that this wasn't noticed, since technically
  `/usr/share/zoneinfo//UTC` (double slash) still works.

  Here is a Dockerfile that reproduces the issue:

  ```dockerfile
  FROM ubuntu

  RUN apt-get update && \
  apt-get install -y tzdata
  ```

  Here is the output of `docker build`:

  ```
  test (master)$ docker build --no-cache -t tztest .
  Sending build context to Docker daemon   2.56kB
  Step 1/3 : FROM ubuntu
   ---> 9140108b62dc
  Step 2/3 : RUN apt-get update && apt install -y tzdata
   ---> Running in 03da406f73cb
  Get:1 http://archive.ubuntu.com/ubuntu focal InRelease [265 kB]
  Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB]
  Get:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB]
  Get:4 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 
Packages [75.9 kB]
  Get:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB]
  Get:6 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 
Packages [1169 B]
  Get:7 http://security.ubuntu.com/ubuntu focal-security/universe amd64 
Packages [626 kB]
  Get:8 http://archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [33.4 
kB]
  Get:9 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [177 
kB]
  Get:10 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [11.3 
MB]
  Get:11 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 
[406 kB]
  Get:12 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [1275 kB]
  Get:13 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 
[745 kB]
  Get:14 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 
[832 kB]
  Get:15 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 
Packages [88.7 kB]
  Get:16 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 
Packages [21.6 kB]
  Get:17 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 
Packages [4277 B]
  Fetched 16.2 MB in 4s (3919 kB/s)
  Reading package lists...

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following NEW packages will be installed:
    tzdata
  0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
  Need to get 293 kB of archives.
  After this operation, 4026 kB of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 tzdata all 
2020a-0ubuntu0.20.04 [293 kB]
  debconf: delaying package configuration, since apt-utils is not installed
  Fetched 293 kB in 1s (262 kB/s)
  Selecting previously unselected package tzdata.
  (Reading database ... 4121 files and directories currently installed.)
  Preparing to unpack .../tzdata_2020a-0ubuntu0.20.04_all.deb ...
  Unpacking tzdata (2020a-0ubuntu0.20.04) ...
  Setting up tzdata (2020a-0ubuntu0.20.04) ...
  debconf: unable to initialize frontend: Dialog
  debconf: (TERM is not set, so the dialog frontend is not usable.)
  debconf: falling back to frontend: Readline
  debconf: unable to initialize frontend: Readline
  debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the 
Term::ReadLine module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
  debconf: falling back to frontend: Teletype
  Configuring tzdata
  --

  Please select the geographic area in which you live. Subsequent configuration
  questions will narrow this down by presenting a list of cities, representing
  the time zones in which they are located.

    1. Africa  4. Australia  7. Atlantic  10. Pacific  13. Etc
    2. America 5. Arctic 8. Europe11. SystemV
    3. Antarctica  6. Asia   9. Indian12. US
  Geographic area:
  Use of uninitialized value $_[1] in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.

  Current default time zone: '/UTC'
  Local time is now:  Sun Oct 11 11:35:33 UTC 2020.
  Universal Time is now:  Sun Oct 11 11:35:33 

[Touch-packages] [Bug 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[rhi]

** Attachment added: "Photo of unlock screen after standby ("Ric i" should be 
"Ricki")"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947597/+attachment/5533870/+files/20211018_155933.jpg

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[rhi]

Additional info: If you log out from the Gnome session (you have to know
by heart where to click because there is no text) and log in again,
everything works again. So it's some kind of temporary screen
corruption.

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[rhi]

** Attachment added: "Screenshot of both screens after unlocking (Gnome desktop 
on right screen, the three dots are from the dock)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947597/+attachment/5533881/+files/Bildschirmfoto%20von%202021-10-18%2015-59-48.png

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[rhi]

Hardware: NVIDIA GeForce RTX 2070, two screens

Attached: screenshots of screen corruption (photo of unlock screen,
screenshot of Gnome UI after unlocking)

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1947597] [NEW] Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[rhi]

Public bug reported:

Steps to reproduce:

1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
2. Log into Gnome with Wayland.
3. Let the PC go into standby.
4. Wake it up again.
5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

(New windows seem to be OK.)

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.74  Mon Sep 13 23:09:15 
UTC 2021
 GCC version:
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 18 15:53:12 2021
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] [1458:37c2]
InstallationDate: Installed on 2021-10-15 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F32
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ULTRA
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570 AORUS ULTRA
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
nvidia-settings:
 ERROR: Unable to find display on any available system
 
 
 ERROR: Unable to find display on any available system
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug corruption impish ubuntu wayland-session

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  

[Touch-packages] [Bug 1946667] Re: resolved reports Failed to send hostname reply: Invalid argument

[Daniel Manrique]

I marked it invalid for Ubuntu One SSO because it is NOT an Ubuntu One
SSO issue. The systemd task is still filed/active, for that project's
bug triagers to look at.

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

Title:
  resolved reports Failed to send hostname reply: Invalid argument

Status in Canonical SSO provider:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  According to https://github.com/systemd/systemd/issues/11626 this is
  fixed in version 248 of systemd.

  Please make that version available to LTS 20.04.3

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-identity-provider/+bug/1946667/+subscriptions


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

[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)

[Rolf Leggewie]

There is no need for an SRU.  The problem does not affect focal as such. This 
is only an issue when moving from gir1.2-signon-1.0 to 
gir1.2-signon-2.0 which will only occur in groovy2hirsute and focal2jammy.  The 
Replaces-line can be dropped in jammy+1.

** Changed in: libsignon-glib (Ubuntu)
   Status: Incomplete => In Progress

** Summary changed:

- gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)
+ gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute 
and Focal2Jammy)

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute and Focal2Jammy)

Status in libsignon-glib package in Ubuntu:
  In Progress

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

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


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

[Touch-packages] [Bug 1947588] [NEW] Infinite Loop in OpenSSL s_server

[Matt Caswell]

Public bug reported:

Launching openssl s_server as follows:

$ openssl s_server -nocert -psk 01020304 -dtls1

And using openssl s_client to connect to it like this:

$ openssl s_client -dtls1 -psk 01020304

Results in s_server entering an infinite loop:


Using default temp DH parameters
ACCEPT
ERROR
140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
ERROR
140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
ERROR

...and so on...

I have confirmed that upstream OpenSSL does not have this issue in a
default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
with these commands (https://github.com/openssl/openssl/issues/16707)
and it was while working on the fix for that issue
(https://github.com/openssl/openssl/pull/16838) that I noticed this
problem in the Ubuntu packages.

$ lsb_release -rd
Description:Ubuntu 21.04
Release:21.04

$ apt-cache policy openssl
openssl:
  Installed: 1.1.1j-1ubuntu3.5
  Candidate: 1.1.1j-1ubuntu3.5
  Version table:
 *** 1.1.1j-1ubuntu3.5 500
500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
100 /var/lib/dpkg/status
 1.1.1j-1ubuntu3 500
500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

$ openssl version -a
OpenSSL 1.1.1j  16 Feb 2021
built on: Mon Aug 23 17:02:39 2021 UTC
platform: debian-amd64
options:  bn(64,64) rc4(16x,int) des(int) blowfish(ptr) 
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g 
-O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2
OPENSSLDIR: "/usr/lib/ssl"
ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1"
Seeding source: os-specific

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

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

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  New

Bug description:
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j  16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options:  bn(64,64) rc4(16x,int) des(int) blowfish(ptr) 
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2
  OPENSSLDIR: "/usr/lib/ssl"
 

[Touch-packages] [Bug 1947578] [NEW] broken RTL support in VTE-based terminal emulators.

[Danial Behzadi]

Public bug reported:

AFAIK Whiptail has a built-in RTL script support, which is awesome on
many environment with no RTL support such as text-based Debian installer
or TTYs. But recently VTE added support for RTL languages and now,
Whiptail is broken on GNOME Terminal, etc.


---


I reported this upstream too: https://pagure.io/newt/issue/20

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: whiptail 0.52.21-4ubuntu7
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 18 15:09:03 2021
InstallationDate: Installed on 2021-07-13 (97 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fa_IR
 SHELL=/bin/bash
SourcePackage: newt
UpgradeStatus: Upgraded to impish on 2021-10-16 (1 days ago)

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


** Tags: amd64 apport-bug impish wayland-session

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

Title:
  broken RTL support in VTE-based terminal emulators.

Status in newt package in Ubuntu:
  New

Bug description:
  AFAIK Whiptail has a built-in RTL script support, which is awesome on
  many environment with no RTL support such as text-based Debian
  installer or TTYs. But recently VTE added support for RTL languages
  and now, Whiptail is broken on GNOME Terminal, etc.

  
  ---

  
  I reported this upstream too: https://pagure.io/newt/issue/20

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: whiptail 0.52.21-4ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:09:03 2021
  InstallationDate: Installed on 2021-07-13 (97 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fa_IR
   SHELL=/bin/bash
  SourcePackage: newt
  UpgradeStatus: Upgraded to impish on 2021-10-16 (1 days ago)

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


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

[Touch-packages] [Bug 1671536] Re: Default initrd is LZMA compressed, yet rebuilt initramfs are gzip?

[Dimitri John Ledkov]

I believe livecd-rootfs and live-build have been fixed for this.

** Changed in: cloud-images
   Status: New => Fix Released

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Fix Released

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

Title:
  Default initrd is LZMA compressed, yet rebuilt initramfs are gzip?

Status in cloud-images:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  $ file ~/Downloads/xenial-server-cloudimg-amd64-initrd-generic
  /home/xnox/Downloads/xenial-server-cloudimg-amd64-initrd-generic: LZMA 
compressed data, streamed

  Yet, in the base image I don't see that initramfs config options set
  COMPRESS=lzma. Thus first boot is lzma, yet on package upgrades i
  guess initrd would be regenerated as gzip...

  Isn't the fact that all of our images use lzma and/or xz compression
  means we should switch Ubuntu default to lzma and/or xz as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1671536/+subscriptions


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

[Touch-packages] [Bug 1944082] Re: initramfs-tools: zstd uses too much memory in mkinitramfs

[Dimitri John Ledkov]

In general we optimize for bootspeed, at the expense of generation time.
It is often the case that we can complete the boot on systems smaller
than required to recreate files for such boot. I.e. impossible to
install/upgrade packages.

Are you experiencing failure to create initrd, where previously you
could? a 512MB instance should still be able to create zstd compressed
initrd and boot.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  initramfs-tools: zstd uses too much memory in mkinitramfs

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  Changing the default compression method of initramfs to zstd using
  hardcoded compression flag "-19 -T0" takes 200MB memory in return for
  40MB reduction of disk IO. I think it is too much memory usage for
  some fraction of seconds while booting.

  The default compression method of initramfs was changed in Bug #1931725 for 
impish but the runtime memory usage was not discussed well.
  the test results by modifying compression command in /usr/sbin/mkinitramfs on 
a small VM (amd64, 512MB RAM, 1vCPU, with 5.13.0-16-generic image) 
  | RSSmax | initrd size
  zstd -q -19 -T0 |  214MB |  64MB (+-0MB)
  zstd -q -3 -T1  |   44MB |  84MB (+20MB)
  lz4 -9 -l   |   15MB | 107MB (+43MB)

  Since the hardcoded flag uses "-T0", more memory will be used if more CPU 
threads are available.
  Please reconsider the default compression method or patch the hardcoded flag 
to "-3 -T1" (=zstd default).

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


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

[Touch-packages] [Bug 1941649] Re: switch to zstd by default breaks booting focal LTS kernel

[Dimitri John Ledkov]

partial upgrades are not supported, and during upgrades we generally do
not recreate initrds for old kernels.

Meaning one should have at least .old kernel+initrd pair bootable.

It is more of linux bug maybe that v5.4 does not support zstd compressed
initrd?

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

Title:
  switch to zstd by default breaks booting focal LTS kernel

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  While trying to track down a behavior difference between focal and
  impish, I installed focal's kernel in an impish userspace and
  attempted to boot it. The boot failed, unable to find root. While GRUB
  reported that it had loaded the initramfs, no initramfs messages were
  emitted during boot. I tracked this down to initramfs-tools having
  switched to use zstd compression by default. zstd decompression does
  not appear to be supported by the LTS 5.4 kernel - it appears to have
  been added upstream in v5.9. I imagine this is likely to cause
  problems with partial-upgrade scenarios.

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


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

[Touch-packages] [Bug 1944741] Re: HiFive Unmatched partitions are named "Unleashed"

[Lukas Märdian]

** Also affects: util-linux (Ubuntu Jammy)
   Importance: Low
   Status: New

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

Title:
  HiFive Unmatched partitions are named "Unleashed"

Status in util-linux package in Ubuntu:
  New
Status in util-linux source package in Impish:
  Fix Committed
Status in util-linux source package in Jammy:
  New
Status in util-linux package in Debian:
  Confirmed

Bug description:
  [Impact]  
   

   
  Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same  
   
  UUIDs to load the next stage bootloader: the current name makes partitions
   
  on Unmatched board appear as 'Unleashed'. 
   

   
  This issue gives the feeling that the Ubuntu RISC-V images made specifically  
   
  for those 2 boards were assembled in a rushed manner. 
   

   
  The attached patch fixes this by removing the 'Unleashed' part of the current 
   
  name so that it fits both, it was build againt all architectures here:
   
  
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12783067/+listing-archive-extra

   
  [Test Plan]   
   

   
  1. Download the SiFive Unmatched image here: 
https://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/pending/impish-preinstalled-server-riscv64+unmatched.img.xz
  2. Follow instructions here to launch a riscv64 VM: 
https://wiki.ubuntu.com/RISC-V
  3. Execute the following command: 
   
  ubuntu@ubuntu:~$ sudo fdisk -l
   
  Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors
   
  Units: sectors of 1 * 512 = 512 bytes 
   
  Sector size (logical/physical): 512 bytes / 512 bytes 
   
  I/O size (minimum/optimal): 512 bytes / 512 bytes 
   
  Disklabel type: gpt   
   
  Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 
   

   
  Device  Start  End  Sectors  Size Type
   
  /dev/vda1  235554 83886046 83650493 39.9G Linux filesystem
   
  /dev/vda12 227362   235553 81924M Linux filesystem
   
  /dev/vda13 34 2081 20481M HiFive Unleashed FSBL   
   
  /dev/vda14   208210273 81924M HiFive Unleashed BBL
   
  /dev/vda15  10274   227361   217088  106M EFI System  
   

   
  Partition table entries are not in disk order.
   
  4. Download and install the new packages that contain the fix here:   
   
  
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk1_2.36.1-8ubuntu4_riscv64.deb
  
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk-dev_2.36.1-8ubuntu4_riscv64.deb
  
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/fdisk_2.36.1-8ubuntu4_riscv64.deb
  5. Re-execute the same command as above:  
   
  ubuntu@ubuntu:~$ sudo fdisk -l
   
  Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors
   
  Units: sectors of 1 * 512 = 512 bytes 
   
  Sector size (logical/physical): 512 bytes / 512 bytes 
   
  I/O size (minimum/optimal): 512 bytes / 512 bytes 
   
  Disklabel type: gpt   
   
  Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 
   

   
  Device  Start  End  Sectors  Size Type
   
  /dev/vda1  235554 83886046 83650493 39.9G Linux filesystem
   
  /dev/vda12 227362   235553 81924M Linux filesystem
   
  

[Touch-packages] [Bug 1947558] Re: rfkill fails to turn on wifi card on Dell Latitude 5490

[Gilbert Fernandes]

Note : it might be a problem in the ilwifi driver. I am not sure.
Perhaps rf-kill does the block properly on suspend
But fails to unblock the card because the ilwifi driver does not bring it back 
from "hardware lock" to "available" on resume.
So I am not sure of where the problem is, but I tend to think that it's a 
ilwifi problem :/

https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
dkms/+bug/1947561

How can I make sure rfkill does ask properly to the kernel/module to
unlock the hardware wifi card, and confirm this is a ilwifi problem ?

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

Title:
  rfkill fails to turn on wifi card on Dell Latitude 5490

Status in util-linux package in Ubuntu:
  New

Bug description:
  Laptop is a Dell Latitude 5490
  Was using Windows 10 and installed Ubuntu 20.04
  All updates are installed, all firmwares are up to date.

  Machine was crashing on sleep : would go into sleep, then waking the
  machine up would do a full system restart. Edited the file
  /etc/systemd/sleep.conf to have a line "SuspendState=mem"

  The machine now suspends and wakes properly. But... Once the machine
  comes back from sleep, the wifi card is dead. Rebooting does not fix
  the issue, only a full shutdown then restart brings the wifi card
  back.

  When doing a tail -f on the /var/log/syslog I can see that rfkill is
  used to bring the Wifi card back.

  Here is what happens when laptop goes into sleep :

  Oct 18 09:53:29 alpha systemd[1]: Starting Suspend...
  Oct 18 09:53:29 alpha systemd-sleep[3046]: Suspending system...

  Oct 18 09:53:29 alpha kernel: [  136.204296] PM: suspend entry (deep)
  Oct 18 09:53:29 alpha systemd[1]: Starting GRUB failed boot detection...
  Oct 18 09:53:29 alpha kernel: [  136.228964] Filesystems sync: 0.024 seconds
  Oct 18 09:53:29 alpha systemd[1]: grub-initrd-fallback.service: Succeeded.
  Oct 18 09:53:29 alpha systemd[1]: Finished GRUB failed boot detection.
  Oct 18 09:55:40 alpha kernel: [  136.495878] Freezing user space processes 
... (elapsed 0.003 seconds) done.
  Oct 18 09:55:40 alpha kernel: [  136.499361] OOM killer disabled.
  Oct 18 09:55:40 alpha kernel: [  136.499363] Freezing remaining freezable 
tasks ... (elapsed 0.000 seconds) done.
  Oct 18 09:55:40 alpha kernel: [  136.500427] printk: Suspending console(s) 
(use no_console_suspend to debug)
  Oct 18 09:55:40 alpha kernel: [  136.529343] sd 2:0:0:0: [sda] Synchronizing 
SCSI cache
  Oct 18 09:55:40 alpha kernel: [  136.534871] sd 2:0:0:0: [sda] Stopping disk
  Oct 18 09:55:40 alpha kernel: [  136.580654] ACPI: EC: interrupt blocked
  Oct 18 09:55:40 alpha kernel: [  136.624750] ACPI: Preparing to enter system 
sleep state S3
  Oct 18 09:55:40 alpha kernel: [  136.635044] ACPI: EC: event blocked
  Oct 18 09:55:40 alpha kernel: [  136.635046] ACPI: EC: EC stopped
  Oct 18 09:55:40 alpha kernel: [  136.635047] PM: Saving platform NVS memory
  Oct 18 09:55:40 alpha kernel: [  136.635149] Disabling non-boot CPUs ...
  Oct 18 09:55:40 alpha kernel: [  136.636740] smpboot: CPU 1 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.639254] smpboot: CPU 2 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.641610] smpboot: CPU 3 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.643970] smpboot: CPU 4 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.645806] IRQ 122: no longer affine to CPU5
  Oct 18 09:55:40 alpha kernel: [  136.645815] IRQ 128: no longer affine to CPU5
  Oct 18 09:55:40 alpha kernel: [  136.646820] smpboot: CPU 5 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.647982] IRQ 124: no longer affine to CPU6
  Oct 18 09:55:40 alpha kernel: [  136.649021] smpboot: CPU 6 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.650373] IRQ 126: no longer affine to CPU7
  Oct 18 09:55:40 alpha kernel: [  136.650382] IRQ 129: no longer affine to CPU7
  Oct 18 09:55:40 alpha kernel: [  136.651394] smpboot: CPU 7 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.654659] ACPI: Low-level resume complete
  Oct 18 09:55:40 alpha kernel: [  136.654749] ACPI: EC: EC started
  Oct 18 09:55:40 alpha kernel: [  136.654750] PM: Restoring platform NVS memory
  Oct 18 09:55:40 alpha kernel: [  136.655504] Enabling non-boot CPUs ...
  Oct 18 09:55:40 alpha kernel: [  136.655548] x86: Booting SMP configuration:
  Oct 18 09:55:40 alpha kernel: [  136.655549] smpboot: Booting Node 0 
Processor 1 APIC 0x2
  Oct 18 09:55:40 alpha kernel: [  136.656533] CPU1 is up
  Oct 18 09:55:40 alpha kernel: [  136.656552] smpboot: Booting Node 0 
Processor 2 APIC 0x4
  Oct 18 09:55:40 alpha kernel: [  136.657153] CPU2 is up
  Oct 18 09:55:40 alpha kernel: [  136.657171] smpboot: Booting Node 0 
Processor 3 APIC 0x6
  Oct 18 09:55:40 alpha kernel: [  136.657774] CPU3 is up
  Oct 18 09:55:40 alpha kernel: [  136.657792] smpboot: Booting Node 0 
Processor 4 APIC 0x1
 

[Touch-packages] [Bug 1947558] Re: rfkill fails to turn on wifi card on Dell Latitude 5490

[Gilbert Fernandes]

tried to use rfkill to bring the wifi card back, fails :

after wake from suspend :

gilbert@alpha:~$ sudo rfkill list
1: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
4: hci0: Bluetooth
Soft blocked: no
Hard blocked: no


trying to turn on :

gilbert@alpha:~$ sudo rfkill unblock 3
gilbert@alpha:~$ sudo rfkill 
ID TYPE  DEVICE  SOFT  HARD
 1 wlan  dell-wifi  unblocked unblocked
 2 bluetooth dell-bluetooth unblocked unblocked
 3 wlan  phy0   unblocked   blocked
 4 bluetooth hci0   unblocked unblocked

The RF Kill is done on suspend
And it does not work to bring the Wifi card ON when resuming the laptop.

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

Title:
  rfkill fails to turn on wifi card on Dell Latitude 5490

Status in util-linux package in Ubuntu:
  New

Bug description:
  Laptop is a Dell Latitude 5490
  Was using Windows 10 and installed Ubuntu 20.04
  All updates are installed, all firmwares are up to date.

  Machine was crashing on sleep : would go into sleep, then waking the
  machine up would do a full system restart. Edited the file
  /etc/systemd/sleep.conf to have a line "SuspendState=mem"

  The machine now suspends and wakes properly. But... Once the machine
  comes back from sleep, the wifi card is dead. Rebooting does not fix
  the issue, only a full shutdown then restart brings the wifi card
  back.

  When doing a tail -f on the /var/log/syslog I can see that rfkill is
  used to bring the Wifi card back.

  Here is what happens when laptop goes into sleep :

  Oct 18 09:53:29 alpha systemd[1]: Starting Suspend...
  Oct 18 09:53:29 alpha systemd-sleep[3046]: Suspending system...

  Oct 18 09:53:29 alpha kernel: [  136.204296] PM: suspend entry (deep)
  Oct 18 09:53:29 alpha systemd[1]: Starting GRUB failed boot detection...
  Oct 18 09:53:29 alpha kernel: [  136.228964] Filesystems sync: 0.024 seconds
  Oct 18 09:53:29 alpha systemd[1]: grub-initrd-fallback.service: Succeeded.
  Oct 18 09:53:29 alpha systemd[1]: Finished GRUB failed boot detection.
  Oct 18 09:55:40 alpha kernel: [  136.495878] Freezing user space processes 
... (elapsed 0.003 seconds) done.
  Oct 18 09:55:40 alpha kernel: [  136.499361] OOM killer disabled.
  Oct 18 09:55:40 alpha kernel: [  136.499363] Freezing remaining freezable 
tasks ... (elapsed 0.000 seconds) done.
  Oct 18 09:55:40 alpha kernel: [  136.500427] printk: Suspending console(s) 
(use no_console_suspend to debug)
  Oct 18 09:55:40 alpha kernel: [  136.529343] sd 2:0:0:0: [sda] Synchronizing 
SCSI cache
  Oct 18 09:55:40 alpha kernel: [  136.534871] sd 2:0:0:0: [sda] Stopping disk
  Oct 18 09:55:40 alpha kernel: [  136.580654] ACPI: EC: interrupt blocked
  Oct 18 09:55:40 alpha kernel: [  136.624750] ACPI: Preparing to enter system 
sleep state S3
  Oct 18 09:55:40 alpha kernel: [  136.635044] ACPI: EC: event blocked
  Oct 18 09:55:40 alpha kernel: [  136.635046] ACPI: EC: EC stopped
  Oct 18 09:55:40 alpha kernel: [  136.635047] PM: Saving platform NVS memory
  Oct 18 09:55:40 alpha kernel: [  136.635149] Disabling non-boot CPUs ...
  Oct 18 09:55:40 alpha kernel: [  136.636740] smpboot: CPU 1 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.639254] smpboot: CPU 2 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.641610] smpboot: CPU 3 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.643970] smpboot: CPU 4 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.645806] IRQ 122: no longer affine to CPU5
  Oct 18 09:55:40 alpha kernel: [  136.645815] IRQ 128: no longer affine to CPU5
  Oct 18 09:55:40 alpha kernel: [  136.646820] smpboot: CPU 5 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.647982] IRQ 124: no longer affine to CPU6
  Oct 18 09:55:40 alpha kernel: [  136.649021] smpboot: CPU 6 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.650373] IRQ 126: no longer affine to CPU7
  Oct 18 09:55:40 alpha kernel: [  136.650382] IRQ 129: no longer affine to CPU7
  Oct 18 09:55:40 alpha kernel: [  136.651394] smpboot: CPU 7 is now offline
  Oct 18 09:55:40 alpha kernel: [  136.654659] ACPI: Low-level resume complete
  Oct 18 09:55:40 alpha kernel: [  136.654749] ACPI: EC: EC started
  Oct 18 09:55:40 alpha kernel: [  136.654750] PM: Restoring platform NVS memory
  Oct 18 09:55:40 alpha kernel: [  136.655504] Enabling non-boot CPUs ...
  Oct 18 09:55:40 alpha kernel: [  136.655548] x86: Booting SMP configuration:
  Oct 18 09:55:40 alpha kernel: [  136.655549] smpboot: Booting Node 0 
Processor 1 APIC 0x2
  Oct 18 09:55:40 alpha kernel: [  136.656533] CPU1 is up
  Oct 18 09:55:40 alpha kernel: [  136.656552] smpboot: Booting Node 0 
Processor 2 APIC 0x4
  

[Touch-packages] [Bug 1947558] [NEW] rfkill fails to turn on wifi card on Dell Latitude 5490

[Gilbert Fernandes]

Public bug reported:

Laptop is a Dell Latitude 5490
Was using Windows 10 and installed Ubuntu 20.04
All updates are installed, all firmwares are up to date.

Machine was crashing on sleep : would go into sleep, then waking the
machine up would do a full system restart. Edited the file
/etc/systemd/sleep.conf to have a line "SuspendState=mem"

The machine now suspends and wakes properly. But... Once the machine
comes back from sleep, the wifi card is dead. Rebooting does not fix the
issue, only a full shutdown then restart brings the wifi card back.

When doing a tail -f on the /var/log/syslog I can see that rfkill is
used to bring the Wifi card back.

Here is what happens when laptop goes into sleep :

Oct 18 09:53:29 alpha systemd[1]: Starting Suspend...
Oct 18 09:53:29 alpha systemd-sleep[3046]: Suspending system...

Oct 18 09:53:29 alpha kernel: [  136.204296] PM: suspend entry (deep)
Oct 18 09:53:29 alpha systemd[1]: Starting GRUB failed boot detection...
Oct 18 09:53:29 alpha kernel: [  136.228964] Filesystems sync: 0.024 seconds
Oct 18 09:53:29 alpha systemd[1]: grub-initrd-fallback.service: Succeeded.
Oct 18 09:53:29 alpha systemd[1]: Finished GRUB failed boot detection.
Oct 18 09:55:40 alpha kernel: [  136.495878] Freezing user space processes ... 
(elapsed 0.003 seconds) done.
Oct 18 09:55:40 alpha kernel: [  136.499361] OOM killer disabled.
Oct 18 09:55:40 alpha kernel: [  136.499363] Freezing remaining freezable tasks 
... (elapsed 0.000 seconds) done.
Oct 18 09:55:40 alpha kernel: [  136.500427] printk: Suspending console(s) (use 
no_console_suspend to debug)
Oct 18 09:55:40 alpha kernel: [  136.529343] sd 2:0:0:0: [sda] Synchronizing 
SCSI cache
Oct 18 09:55:40 alpha kernel: [  136.534871] sd 2:0:0:0: [sda] Stopping disk
Oct 18 09:55:40 alpha kernel: [  136.580654] ACPI: EC: interrupt blocked
Oct 18 09:55:40 alpha kernel: [  136.624750] ACPI: Preparing to enter system 
sleep state S3
Oct 18 09:55:40 alpha kernel: [  136.635044] ACPI: EC: event blocked
Oct 18 09:55:40 alpha kernel: [  136.635046] ACPI: EC: EC stopped
Oct 18 09:55:40 alpha kernel: [  136.635047] PM: Saving platform NVS memory
Oct 18 09:55:40 alpha kernel: [  136.635149] Disabling non-boot CPUs ...
Oct 18 09:55:40 alpha kernel: [  136.636740] smpboot: CPU 1 is now offline
Oct 18 09:55:40 alpha kernel: [  136.639254] smpboot: CPU 2 is now offline
Oct 18 09:55:40 alpha kernel: [  136.641610] smpboot: CPU 3 is now offline
Oct 18 09:55:40 alpha kernel: [  136.643970] smpboot: CPU 4 is now offline
Oct 18 09:55:40 alpha kernel: [  136.645806] IRQ 122: no longer affine to CPU5
Oct 18 09:55:40 alpha kernel: [  136.645815] IRQ 128: no longer affine to CPU5
Oct 18 09:55:40 alpha kernel: [  136.646820] smpboot: CPU 5 is now offline
Oct 18 09:55:40 alpha kernel: [  136.647982] IRQ 124: no longer affine to CPU6
Oct 18 09:55:40 alpha kernel: [  136.649021] smpboot: CPU 6 is now offline
Oct 18 09:55:40 alpha kernel: [  136.650373] IRQ 126: no longer affine to CPU7
Oct 18 09:55:40 alpha kernel: [  136.650382] IRQ 129: no longer affine to CPU7
Oct 18 09:55:40 alpha kernel: [  136.651394] smpboot: CPU 7 is now offline
Oct 18 09:55:40 alpha kernel: [  136.654659] ACPI: Low-level resume complete
Oct 18 09:55:40 alpha kernel: [  136.654749] ACPI: EC: EC started
Oct 18 09:55:40 alpha kernel: [  136.654750] PM: Restoring platform NVS memory
Oct 18 09:55:40 alpha kernel: [  136.655504] Enabling non-boot CPUs ...
Oct 18 09:55:40 alpha kernel: [  136.655548] x86: Booting SMP configuration:
Oct 18 09:55:40 alpha kernel: [  136.655549] smpboot: Booting Node 0 Processor 
1 APIC 0x2
Oct 18 09:55:40 alpha kernel: [  136.656533] CPU1 is up
Oct 18 09:55:40 alpha kernel: [  136.656552] smpboot: Booting Node 0 Processor 
2 APIC 0x4
Oct 18 09:55:40 alpha kernel: [  136.657153] CPU2 is up
Oct 18 09:55:40 alpha kernel: [  136.657171] smpboot: Booting Node 0 Processor 
3 APIC 0x6
Oct 18 09:55:40 alpha kernel: [  136.657774] CPU3 is up
Oct 18 09:55:40 alpha kernel: [  136.657792] smpboot: Booting Node 0 Processor 
4 APIC 0x1
Oct 18 09:55:40 alpha kernel: [  136.658525] CPU4 is up
Oct 18 09:55:40 alpha kernel: [  136.658547] smpboot: Booting Node 0 Processor 
5 APIC 0x3
Oct 18 09:55:40 alpha kernel: [  136.659182] CPU5 is up
Oct 18 09:55:40 alpha kernel: [  136.659201] smpboot: Booting Node 0 Processor 
6 APIC 0x5
Oct 18 09:55:40 alpha kernel: [  136.659849] CPU6 is up
Oct 18 09:55:40 alpha kernel: [  136.659868] smpboot: Booting Node 0 Processor 
7 APIC 0x7
Oct 18 09:55:40 alpha kernel: [  136.660511] CPU7 is up
Oct 18 09:55:40 alpha kernel: [  136.662946] ACPI: Waking up from system sleep 
state S3
Oct 18 09:55:40 alpha kernel: [  136.717996] ACPI: EC: interrupt unblocked
Oct 18 09:55:40 alpha kernel: [  136.801154] ACPI: EC: event unblocked
Oct 18 09:55:40 alpha kernel: [  136.803505] usb usb1: root hub lost power or 
was reset
Oct 18 09:55:40 alpha kernel: [  136.803619] usb usb2: root hub lost power or 
was reset
Oct 18 09:55:40 alpha kernel: [  136.803618] 

[Touch-packages] [Bug 494462] Re: Network manager connection stage icons incomplete, suggestion attached

[Adolfo Jayme]

** Project changed: openoffice.org-human-icons => ubuntu

** No longer affects: ubuntu

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

Title:
  Network manager connection stage icons incomplete, suggestion attached

Status in Humanity:
  Fix Released
Status in humanity-icon-theme package in Ubuntu:
  Fix Released

Bug description:
  When it's connecting, network manager shows three animation stages
  representing three different stages of handshaking. Currently, the
  Humanity theme uses the same animation for all stages, thus throwing
  away information that could be useful for the user.

  Attached is a small modification of the Humanity-Dark nm-applet icons
  that try to solve this issue. Basically, it's the current animation
  for the first stage, addition of a small circle for the second and
  filling of such circle for the third. It's inspired by Karl Lattimer's
  Tango-style icons for network manager [1].

  Making non-dark icons would be trivial. Please let me know what you
  think.

  [1] http://www.mail-archive.com/networkmanager-
  l...@gnome.org/msg10869.html

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


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

[Touch-packages] [Bug 1947545] Re: [nouveau] Ubuntu desktop screen and whole app screen started corrupting the display, I can't see the letters & display properly.

[Daniel van Vugt]

It appears this is a bug in the 'nouveau' driver. In most cases we would
recommend using the proprietary Nvidia driver instead, but for this
particular GPU that requires Nvidia driver version 304 which Ubuntu
doesn't ship anymore (usually because of limited support for particular
kernel versions by Nvidia).

The only suggestions I have are:

  * Use slow software graphics by adding a kernel boot parameter:
'nomodeset'; or

  * Use Ubuntu 16.04 on this machine
(https://releases.ubuntu.com/16.04/), where the nvidia-304 driver is
still supported; or

  * [EXPERT] Install an older kernel like v4.4 and then you should be
able to manually install
https://www.nvidia.com/Download/driverResults.aspx/123709/en-us or

  * Use Windows only.

I suggest the simplest solution for using Ubuntu on this machine is to
install https://releases.ubuntu.com/16.04/

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

** Summary changed:

- [nouveau] Ubuntu desktop screen and whole app screen started corrupting the 
display, I can't see the letters & display properly.
+ [nouveau] [Nvidia C61] Ubuntu desktop screen and whole app screen started 
corrupting the display, I can't see the letters & display properly.

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

Title:
  [nouveau] [Nvidia C61] Ubuntu desktop screen and whole app screen
  started corrupting the display, I can't see the letters & display
  properly.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (1)Description:   Ubuntu 20.04.3 LTS
 Release:   20.04

  (2)Ubuntu 20.04.3 LTS

  (3)I expected that after dual booting Ubuntu OS will be working
  properly and the display will be amazing.Simultaneously my Windows 10
  OS was working perfectly.

  (4)But what happened is my Ubuntu desktop screen and whole app screen
  started corrupting the display, I cant see the letters & display
  properly.When i am opening the application like Mozilla Firefox,
  terminal window, etc;then there is not corrupting. when I am logging
  into Ubuntu OS the Login Screen also corrupts.

  Please do something about this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 10:06:34 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
  InstallationDate: Installed on 2021-10-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 8086:0808 Intel Corp. USB PnP Sound Device
   Bus 002 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=19032621-4455-41db-85e6-c10e0d5b345e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: M68MT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-S2:pvr:sku:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: M68MT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1947545] Re: Ubuntu desktop screen and whole app screen started corrupting the display, I can't see the letters & display properly.

[Daniel van Vugt]

** Summary changed:

- Actually i had dualbooted ubuntu with windows.From beginning of my usage 
there was so much screen corupted in the OS. I cant able to see the letters 
correctly it was like lot of a hell. I did'nt expected this from ubuntu 
.Simultaneously my Windows 10 OS was working perfectly.PLease do something 
about this issue.
+ Ubuntu desktop screen and whole app screen started corrupting the display, I 
can't see the letters & display properly.

** Tags added: nouveau

** Summary changed:

- Ubuntu desktop screen and whole app screen started corrupting the display, I 
can't see the letters & display properly.
+ [nouveau] Ubuntu desktop screen and whole app screen started corrupting the 
display, I can't see the letters & display properly.

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

Title:
  [nouveau] Ubuntu desktop screen and whole app screen started
  corrupting the display, I can't see the letters & display properly.

Status in xorg package in Ubuntu:
  New

Bug description:
  (1)Description:   Ubuntu 20.04.3 LTS
 Release:   20.04

  (2)Ubuntu 20.04.3 LTS

  (3)I expected that after dual booting Ubuntu OS will be working
  properly and the display will be amazing.Simultaneously my Windows 10
  OS was working perfectly.

  (4)But what happened is my Ubuntu desktop screen and whole app screen
  started corrupting the display, I cant see the letters & display
  properly.When i am opening the application like Mozilla Firefox,
  terminal window, etc;then there is not corrupting. when I am logging
  into Ubuntu OS the Login Screen also corrupts.

  Please do something about this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 10:06:34 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
  InstallationDate: Installed on 2021-10-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 8086:0808 Intel Corp. USB PnP Sound Device
   Bus 002 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=19032621-4455-41db-85e6-c10e0d5b345e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: M68MT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-S2:pvr:sku:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: M68MT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1947452] Re: Please remove maliit from Ubuntu

[Adolfo Jayme]

https://github.com/maliit

The project doesn’t look dead to me…

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

Title:
  Please remove maliit from Ubuntu

Status in maliit-framework package in Ubuntu:
  New
Status in maliit-inputcontext-gtk package in Ubuntu:
  New

Bug description:
  Please remove maliit-framework & maliit-inputcontext-gtk from Ubuntu.

  They have no reverse dependencies.

  https://tracker.debian.org/pkg/maliit-framework was uploaded to Debian
  experimental once but was removed.

  I think the packages were added as part of the Unity 8 project and
  aren't actively maintained in Ubuntu since Canonical stopped work
  there.

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


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