[Touch-packages] [Bug 1912030] Re: Crash unless ffmpeg direct rendering disabled with ATI X1400

2021-10-12 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Crash unless ffmpeg direct rendering disabled with ATI X1400

Status in mesa package in Ubuntu:
  Expired

Bug description:
  After upgrading to Ubuntu 20.10, VLC started crashing when I tried to
  play video. I tried changing to different video output methods, but
  none of them worked. In the past, I remember several methods working
  fine.

  In the ffmpeg advanced preferences page, disabling the direct
  rendering option made video playback work.

  I thought the vaapi errors VLC reports had something to do with it,
  but apparently not, because they still happen with successful
  playback. This is on a Dell Inspiron 6400 with ATI Mobility Radeon
  X1400, which doesn't support hardware decoding of the H.264 video I'm
  trying to play.

  Here's one backtrace:
  Thread 26 "vlc" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fff880df640 (LWP 11335)]
  __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104
  104 ../sysdeps/x86_64/multiarch/memcpy-ssse3.S: No such file or directory.
  (gdb) bt
  #0  __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104
  #1  0x77d03fc2 in picture_CopyPixels ()
  at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #2  0x77d04016 in picture_Copy ()
  at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #3  0x77cdf1ea in  () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #4  0x77ce1438 in  () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #5  0x77f67590 in start_thread (arg=0x7fff880df640)
  at pthread_create.c:463
  #6  0x77e87223 in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Also another:
  #0  __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104
  #1  0x7fffc7022bff in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #2  0x7fffc74f1d66 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #3  0x7fffc6b41317 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #4  0x7fffc6cb4b07 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #5  0x7fffc6cb7dcc in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #6  0x7fffc6cbd9d9 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #7  0x7fff885b2eee in  ()
  at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so
  #8  0x7fff885ad2c5 in  ()
  at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so
  #9  0x7fff885b3cee in  ()
  at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so
  #10 0x77cdf4e6 in  () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #11 0x77ce1438 in  () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #12 0x77f67590 in start_thread (arg=0x7fff886bb640)
  at pthread_create.c:463
  #13 0x77e87223 in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: vlc 3.0.11.1-2
  ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Jan 15 18:46:42 2021
  InstallationDate: Installed on 2012-01-19 (3284 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: vlc
  UpgradeStatus: Upgraded to groovy on 2020-10-21 (86 days ago)

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


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


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

2021-10-12 Thread Bryce Harrington
** Changed in: rsync (Ubuntu)
 Assignee: (unassigned) => Bryce Harrington (bryce)

-- 
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
Post to : touch-packages@lists.launchpad.net

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

2021-10-12 Thread Bryce Harrington
Public bug reported:

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

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


** Tags: needs-merge

-- 
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: 

[Touch-packages] [Bug 1946854] [NEW] Merge dnsmasq from Debian unstable for 22.04

2021-10-12 Thread Bryce Harrington
Public bug reported:

Scheduled-For: 23.01
Upstream: tbd
Debian:   2.86-1
Ubuntu:   2.85-1ubuntu2


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 ###

dnsmasq (2.86-1) unstable; urgency=low

   * Fix debian/changelog format error. (closes: #986626)

 -- Simon Kelley   Thu, 08 Apr 2021 22:39:00
+0100

dnsmasq (2.85-1) unstable; urgency=low

   * New upstream.
   * Includes fix to CVE-2021-3448.
   * Fix manpage typos. (closes: #986150)

 -- Simon Kelley   Sat, 03 Apr 2021 22:17:23
+0100

dnsmasq (2.84-1.2) unstable; urgency=medium

   * Non-maintainer upload.
   * Bump old-version in dpkg-maintscript-helper dir_to_symlink calls to also
 clean up after upgrades to an earlier version in testing.

 -- Andreas Beckmann   Thu, 01 Apr 2021 16:01:51 +0200

dnsmasq (2.84-1.1) unstable; urgency=medium

   * Non-maintainer upload.
   * Fix symlink to directory conversion for /usr/share/doc/dnsmasq.
 This is achieved by directly calling dpkg-maintscript-helper in the 
preinst,
 postinst, and postrm scripts, since the package does not use debhelper.
 (Closes: #985282)

 -- Sébastien Villemot   Sun, 28 Mar 2021 10:55:07
+0200

dnsmasq (2.84-1) unstable; urgency=low

   * New upstream.

 -- Simon Kelley   Sun, 24 Jan 2021 22:02:01
+

dnsmasq (2.83-1) unstable; urgency=high

   * New upstream.
   * Includes fixes to CVE-2020-25681 - CVE-2020-25687 inclusive.

 -- Simon Kelley   Fri, 15 Jan 2021 22:22:41
+

dnsmasq (2.82-1) unstable; urgency=low

   * New upstream.

 -- Simon Kelley   Fri, 26 Jun 2020 22:22:41
+

dnsmasq (2.81-4) unstable; urgency=low

   * Remove runit support when building for Ubuntu. (closes: #960401)

 -- Simon Kelley   Fri, 26 Jun 2020 21:52:44
+

dnsmasq (2.81-3) unstable; urgency=low

   * Fixes to control file for bug 958100

 -- Simon Kelley   Sun, 19 Apr 2020 21:44:12
+

dnsmasq (2.81-2) unstable; urgency=low

   * Fix FTBFS on kFreeBSD. (closes: #958100)

 -- Simon Kelley   Sat, 18 Apr 2020 18:34:15 +

dnsmasq (2.81-1) unstable; urgency=low

   * New upstream.
   * Fix nodocs/nodoc confusion in rules. (closes: #922758)
   * Add Vcs-* fields to control. (closes: #922422)
   * Add systemd support for multiple daemon instances. (closes: #914305)
   * Add note explaining that ENABLED is SYSV-init only. (closes: #914755)
   * Replace ash with dash in contrib/reverse-dns. (closes: #920224)
   * Move to libidn2. (closes: #932695)
   * Fix RA problem with two interfaces on same net, but RA service on
 only one of the interfaces. (closes: #949565)
   * Fix breakage of dig +trace. (closes: #942363)
   * Fix build faliure with newer Nettle libraries. (closes: #940985)
   * Support runscript init-system (closes: #929884)
   * Security fix for CVE-2019-14834 (closes: #948373)

 -- Simon Kelley   Wed, 8 Apr 2020 17:33:15 +

dnsmasq (2.80-1) unstable; urgency=low

   * New upstream. (closes: #837602) (closes: #794640) (closes: #794636)
   * Close old bugs, long agp fixed. (closes: #802845) (closes: #754299)
   * Provide usr/lib/tmpfiles.d/dnsmasq.conf. (closes: #872396)
   * Run restorecon on /run/dnsmasq for SE Linux. (closes: #872397)

 -- Simon Kelley   Mon, 17 Sep 2018 23:11:25
+

dnsmasq (2.79-1) unstable; urgency=low

   * New upstream. (closes: #888200)
   * Fix trust-anchor regex in init script. (closes: #884347)


### Old Ubuntu Delta ###

dnsmasq (2.85-1ubuntu2) impish; urgency=medium

  * Revert: 'src/radv.c: avoid leases to be issued forever when not set'
(LP 1894619) according to the bug and upstream discussion.

 -- Christian Ehrhardt   Tue, 22 Jun
2021 07:18:30 +0200

dnsmasq (2.85-1ubuntu1) impish; urgency=medium

  * Merge with Debian unstable. Remaining changes:
- src/radv.c: avoid leases to be issued forever when not set
  (LP 1894619)

 -- Christian Ehrhardt   Wed, 02 Jun
2021 09:34:26 +0200

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


** Tags: needs-merge

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

Title:
  Merge dnsmasq from Debian unstable for 22.04

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Scheduled-For: 23.01
  Upstream: tbd
  Debian:   2.86-1
  Ubuntu:   2.85-1ubuntu2


  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 ###

  dnsmasq (2.86-1) unstable; urgency=low

 * Fix debian/changelog format error. (closes: #986626)

   -- Simon Kelley   Thu, 08 Apr 2021 22:39:00
  +0100

  dnsmasq (2.85-1) unstable; urgency=low

 * New upstream.
 * Includes fix to CVE-2021-3448.
 * Fix manpage typos. (closes: #986150)

   -- 

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

2021-10-12 Thread Bryce Harrington
Public bug reported:

Scheduled-For: 22.12
Upstream: tbd
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 :-?

 -- 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.

 -- 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.

 -- 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.

 -- 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.

 -- 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.

 -- 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.

 -- Santiago Garcia Mantinan   Tue, 15 Jan 2019
13:18:33 +0100

bridge-utils (1.5-16) unstable; urgency=medium

  * Don't set dev globally at bridge-utils.sh. Closes: #873086.

 -- Santiago Garcia Mantinan   Sun, 08 Apr 2018
23:06:30 +0200

bridge-utils (1.5-15) unstable; urgency=medium

  * Fix substrings on interfaces. Closes: #873087.
  * Make it lintian clean sticking to 1.0 source format for now.
No time to properly comment all the patches right now.

 -- Santiago Garcia Mantinan   Fri, 02 Mar 2018
22:08:20 +0100

bridge-utils (1.5-14) unstable; urgency=low

  * Fix a problem with some vlan interfaces not being created.

 -- Santiago Garcia Mantinan   Mon, 26 Jun 2017
17:48:37 +0200

bridge-utils (1.5-13) unstable; urgency=low

  * Fix a hardcoded interface name on bridge-utils.sh. Closes: #854841.

 -- Santiago Garcia Mantinan   Sat, 11 Feb 2017
00:16:45 +0100

bridge-utils (1.5-12) unstable; urgency=medium

  * Add vlan support so that old setups using vlans as ports don't
break.

 -- Santiago Garcia Mantinan   Sun, 22 Jan 2017
00:23:50 +0100


### Old Ubuntu Delta ###

bridge-utils (1.7-1ubuntu2) impish; urgency=medium

  * No-change rebuild to build packages with zstd compression.

 -- Matthias Klose   Thu, 07 Oct 2021 12:09:41 +0200

bridge-utils (1.7-1ubuntu1) impish; urgency=low

  * Merge from Debian unstable. Remaining changes:
- Don't call ifup from bridge-network-interface, instead just call brctl
  and let udev/upstart bring the interface up.
- debian/ifupdown.sh: Handle bridge params which use port and value
- debian/bridge-utils-interface.5:
  + Update max, default value for path cost
  + Update unsettable gcint value for newer kernels

 -- Steve Langasek   Wed, 17 Mar 2021
12:32:22 -0700

** Affects: bridge-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: needs-merge

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

Title:
  Merge bridge-utils from Debian unstable for 22.04

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Scheduled-For: 22.12
  Upstream: tbd
  Debian:   1.7-1
  Ubuntu:   1.7-1ubuntu2


  Debian 

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

2021-10-12 Thread Bryce Harrington
Public bug reported:

Scheduled-For: 22.11
Upstream: tbd
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.

 -- 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.

 -- 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.

 -- 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)

 -- 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.

 -- 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.

 -- 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.

  [ 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

heimdal (7.4.0.dfsg.1-1) unstable; urgency=high

  * New upstream version.
  * Update standards version to 4.0.0.
  * CVE-2017-11103: Fix Orpheus' Lyre KDC-REP service name validation.
(Closes: #868208).

 -- Brian May   Sat, 15 Jul 2017 19:47:32 +1000

heimdal (7.1.0+dfsg-13) unstable; urgency=medium

  * Add missing symbols base64_decode and base64_encode back into
libroken. Closes: #848694.

 -- Brian May   Wed, 26 Apr 2017 19:38:20 +1000

heimdal (7.1.0+dfsg-12) unstable; urgency=high

  * Fix transit path validation CVE-2017-6594.

 -- Brian May   Mon, 10 Apr 2017 17:21:35 +1000

heimdal (7.1.0+dfsg-11) unstable; urgency=medium

  * Remove legacy provides/conflicts/replaces headers. Old daemons


### Old Ubuntu Delta ###

heimdal (7.7.0+dfsg-2ubuntu2) impish; urgency=medium

  * Remove symbol rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
(LP: #1945787) 

 -- Heinrich Schuchardt   Fri, 01 Oct
2021 15:03:02 +0200

heimdal (7.7.0+dfsg-2ubuntu1) impish; urgency=medium

  * Disable lto, to regain dep on roken, otherwise dependencies on amd64
are different to i386 resulting in different files on amd64 and
i386. LP: #1934936

 -- Dimitri John Ledkov   Tue, 20 Jul 2021
10:32:53 +0100

heimdal (7.7.0+dfsg-2build1) impish; urgency=medium

  * No-change rebuild due to OpenLDAP soname bump.

 -- Sergio Durigan Junior   Mon, 21 Jun
2021 17:48:49 -0400

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


** Tags: needs-merge

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

Title:
  Merge heimdal from Debian unstable for 22.04

Status in heimdal package in Ubuntu:
  New

Bug description:
  Scheduled-For: 22.11
  Upstream: tbd
  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.

   -- 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.

   

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

2021-10-12 Thread Bryce Harrington
Public bug reported:

Scheduled-For: 22.11
Upstream: tbd
Debian:   1.60+git20181103.0eebece-1
Ubuntu:   1.60+git20181103.0eebece-1ubuntu2


### 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.

 -- 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.

 -- 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.

 -- 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.

 -- 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.

 -- 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 Standards-Version, with no changes.

 -- Martín Ferrari   Mon, 26 Dec 2016 05:58:42 +

net-tools (1.60+git20150829.73cef8a-2.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Apply an additional fix for the previous FTBFS for some architectures.

 -- Andrey Rahmatullin   Thu, 01 Dec 2016 22:49:27
+0500

net-tools (1.60+git20150829.73cef8a-2.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Fix FTBFS by applying the upstream patch (Closes: #844073).

 -- Andrey Rahmatullin   Sun, 20 Nov 2016 15:23:12
+0500

net-tools (1.60+git20150829.73cef8a-2) unstable; urgency=medium

  [ Laurent Bigonville ]
  * Enable SELinux support. Closes: #666204.

  [ Martín Ferrari ]
  * Mark the package 'Multi-Arch: foreign', thanks to Frédéric Brière
. Closes: #752584.
  * Fix bug in Portuguese man page, thanks to julianofisc...@gmail.com.
Closes: #805377.

 -- Martín Ferrari   Thu, 19 Nov 2015 14:48:47 +

net-tools (1.60+git20150829.73cef8a-1) unstable; urgency=medium


### Old Ubuntu Delta ###

net-tools (1.60+git20181103.0eebece-1ubuntu2) hirsute; urgency=medium

  * No change rebuild with fixed ownership.

 -- Dimitri John Ledkov   Tue, 16 Feb 2021 15:18:30
+

net-tools (1.60+git20181103.0eebece-1ubuntu1) hirsute; urgency=low

  * Merge from Debian unstable.  Remaining changes:
- Ubuntu_unit_conversion.patch:
  + Ubuntu Policy: output using standard SI unit multiples:
KB (10^3), MB (10^6), GB (10^9), TB (10^12) and PB (10^15).
Includes manpage update to remove comment about IEC units.

 -- Dimitri John Ledkov   Mon, 15 Feb 2021 12:36:42
+

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


** Tags: needs-merge

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

Title:
  Merge net-tools from Debian unstable for 22.04

Status in net-tools package in Ubuntu:
  New

Bug description:
  Scheduled-For: 22.11
  Upstream: tbd
  Debian:   1.60+git20181103.0eebece-1
  Ubuntu:   1.60+git20181103.0eebece-1ubuntu2


  
  ### New Debian Changes ###

  net-tools 

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

2021-10-12 Thread Bryce Harrington
Public bug reported:

Scheduled-For: 22.12
Upstream: tbd
Debian:   2.4.59+dfsg-12.5.7+dfsg-1~exp1
Ubuntu:   2.5.6+dfsg-1~exp1ubuntu1


Debian new has 2.5.7+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.

 -- 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)

 -- 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)

 -- 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)

 -- 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)

 -- Ryan Tandy   Wed, 11 Nov 2020 09:13:56 -0800

openldap (2.4.55+dfsg-1) unstable; urgency=medium

  * New upstream release.
- Fixed slapd normalization handling with modrdn
  (ITS#9370) (CVE-2020-25692)

 -- Ryan Tandy   Tue, 27 Oct 2020 21:07:29 -0700

openldap (2.4.54+dfsg-1) unstable; urgency=medium

  * New upstream release.
  * Change upstream Homepage and get-orig-source URLs to HTTPS.
  * Create debian/gbp.conf.

 -- Ryan Tandy   Sun, 18 Oct 2020 16:03:46 +

openldap (2.4.53+dfsg-1) unstable; urgency=medium

  * New upstream release.

 -- Ryan Tandy   Mon, 07 Sep 2020 09:47:28 -0700

openldap (2.4.51+dfsg-1) unstable; urgency=medium

  * New upstream release.
- Add ldap_parse_password_expiring_control to libldap-2.4-2.symbols.
  * Merge some changes from Ubuntu:
- slapd.default, slapd.README.Debian: update to refer to slapd.d instead
  of slapd.conf.
- debian/slapd.scripts-common: dump_databases: make slapcat_opts a local
  variable.
  * Drop paragraph about patch gnutls-altname-nulterminated (#465197) from
slapd.README.Debian. The patch referred to was dropped in 2.4.7-6.
  * debian/patches/set-maintainer-name: Extract maintainer address dynamically
from debian/control. (Closes: #960448)
  * Fix Torsten's email address in a historic debian/changelog entry to
resolve a Lintian error (bogus-mail-host-in-debian-changelog).


### Old Ubuntu Delta ###

openldap (2.5.6+dfsg-1~exp1ubuntu1) impish; urgency=medium

  * Merge with Debian unstable. Remaining changes:
- Enable AppArmor support:
  + d/apparmor-profile: add AppArmor profile
  + d/rules: use dh_apparmor
  + d/control: Build-Depends on dh-apparmor
  + d/slapd.README.Debian: add note about AppArmor
- Enable ufw support:
  + d/control: suggest ufw.
  + d/rules: install ufw profile.
  + d/slapd.ufw.profile: add ufw profile.
- d/{rules,slapd.py}: Add apport hook.
- d/rules: better regexp to match the Maintainer tag in d/control,
  needed in the Ubuntu case because of XSBC-Original-Maintainer
  (Closes #960448, LP #1875697)

 -- Sergio Durigan Junior   Tue, 17 Aug
2021 14:06:00 -0400

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


** Tags: needs-merge

-- 
You received this bug notification 

[Touch-packages] [Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.

2021-10-12 Thread Jerry Lee
Hi Sebastien,

I verified this new package from impish-proposed :

* The version of the packages tested:
   ModemManager: 1.16.6-2‌ubuntu1

* The test report is attached as "TestReport_impish-
proposed_1946096.pdf".


Besides, I ave not found the packages are ready in hirsute-proposed and 
focal-proposed yet.
Can you help to check it?

Thanks

** Attachment added: "TestReport_impish-proposed_1946096.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946096/+attachment/5532306/+files/TestReport_impish-proposed_1946096.pdf

** Tags added: verification-done-impish

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

Title:
  Apply upstream patches to fix problems for Foxconn and Quectel modems.

Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

  The following 2 modems need the ModemManager v1.16.6 suite to be patched from 
v1.18.2 to fix some problems(LP#1943774, LP#1943780):
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 

  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
 
  * for Foxconn T99W175
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9

**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware 
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot 
  7. Verify if the upgraded modem firmware is still working

  
  [Where problems could occur]

  The requested upstream patches are for these 2 specific modems and the status 
information.
  This should not affect existing generic functions and other modems.

  
  [Other Info]

  The firmware and the upgrading application can be downloaded from the 
following link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions


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


[Touch-packages] [Bug 1946691] Re: using xorg driver for graphics card prevents suspend

2021-10-12 Thread Daniel van Vugt
Thanks for the bug report.

While the broken Xorg driver is installed and the problem is happening
again, please run:

  lspci -kv > lspci.txt
  journalctl -b0 > journal.txt

and attach the resulting text files here.

To save time in future, please report graphical bugs by running:

  ubuntu-bug xorg


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Tags added: nouveau

** Also affects: xserver-xorg-video-nouveau (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Incomplete

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

Title:
  using xorg driver for graphics card prevents suspend

Status in xorg-server package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 20.04.3 LTS

  Not sure what package this belongs to, but this has to do with trying
  to suspend the computer.

  What I expect: 
  selecting power off->suspend suspends my computer e.g. turns off screen, 
turns off fans, etc.

  What happens:
  In "Software & Updates" Additional Drivers tab, for my GeForce GT 745M, if I 
select the "Using X.Org X server" open source driver and then I try to suspend, 
the computer will log off, and the screen will turn black except for blinking 
cursor in the top left corner. The computer will never power down.

  The workaround:
  I work around this by selecting "Using NVIDIA driver metapackage" from 
nvidia-driver-470 (proprietary, tested)
  After this, my computer properly suspends.

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


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


[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2021-10-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the hirsute Pi desktop, under a wayland session with the "full" KMS
  overlay enabled, and "kms-modifiers" present in the
  org.gnome.mutter/experimental-features, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

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


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


[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2021-10-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the hirsute Pi desktop, under a wayland session with the "full" KMS
  overlay enabled, and "kms-modifiers" present in the
  org.gnome.mutter/experimental-features, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

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


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


[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2021-10-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the hirsute Pi desktop, under a wayland session with the "full" KMS
  overlay enabled, and "kms-modifiers" present in the
  org.gnome.mutter/experimental-features, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

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


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


[Touch-packages] [Bug 1946664] Re: [raspi] screen corruption on online accounts webviews

2021-10-12 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1924251 ***
https://bugs.launchpad.net/bugs/1924251

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


** This bug has been marked a duplicate of bug 1924251
   Embedded browser display corruption under Wayland on Pi desktop

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

Title:
  [raspi] screen corruption on online accounts webviews

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I installed ubuntu desktop on my Raspberrypi 4b. I set up the ubuntu
  sign-one account, but to set up the Google and Microsoft account, the
  window to enter the account data gets misconfigured on the screen and
  does not read the fields to enter the data and set up access to my
  accounts.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22
  Uname: Linux 5.11.0-1019-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: arm64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 11 12:12:33 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  GraphicsCard:
   
  ImageMediaBuild: 20210421
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:BB:4B:64 
vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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


[Touch-packages] [Bug 1946541] Re: Changed the language to India(malayalam) and calender doesnt show up correctly.

2021-10-12 Thread Daniel van Vugt
Here it is again.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Attachment added: "8k7GskX8.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946541/+attachment/5532289/+files/8k7GskX8.png

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => 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/1946541

Title:
  Changed the language to India(malayalam) and calender doesnt show up
  correctly.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  
https://www.dropbox.com/s/usw3j54x5jek3i2/%E0%B4%A4%E0%B4%B2%E0%B4%95%E0%B5%8D%E0%B4%95%E0%B5%86%E0%B4%9F%E0%B5%8D%E0%B4%9F%E0%B4%BF%E0%B4%B2%E0%B5%8D%E0%B4%B2%E0%B4%BE%E0%B4%A4%E0%B5%8D%E0%B4%A4%E0%B4%A4%E0%B5%8D.png?dl=0

  I've uploaded the picture in dropbox (above link). I changed my system
  language to Malayalam (India) And the calendar doesnot show the dates
  properly. I guess this might be an issue with missing keys in the
  language or may be not having a fallback language. This might not be a
  priority bug but I would like to contribute if this is a beginner-
  fixable bug & if you could point out the right place to start(docs or
  repo).

  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: Sat Oct  9 12:56:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86c8]
  InstallationDate: Installed on 2020-11-23 (319 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 30c9:0013 DJKCVA1RSE0WKF HP TrueVision HD Camera
   Bus 001 Device 002: ID 17ef:609f Lenovo Lenovo Wireless KB_Mouse KN100 WW
   Bus 001 Device 004: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 14s-dr1xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=c3de697a-52cc-438a-9247-24c4655390fa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2021
  dmi.bios.release: 15.21
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86C8
  dmi.board.vendor: HP
  dmi.board.version: 56.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 56.33
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd07/21/2021:br15.21:efr56.33:svnHP:pnHPLaptop14s-dr1xxx:pvr:sku227U3PA#ACJ:rvnHP:rn86C8:rvr56.33:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14s-dr1xxx
  dmi.product.sku: 227U3PA#ACJ
  dmi.sys.vendor: HP
  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.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.2
  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/gnome-shell/+bug/1946541/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-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

2021-10-12 Thread Gunnar Hjalmarsson
Probably not. The hirsute version of vte2.91 does not even build on
impish.

For gdebi-gtk to keep working, somebody probably needs to

* rewrite 91_keep_fds.patch, or

* fix gdebi so it works without that patch.

Also I can't stop wondering why gdebi-gtk works on Debian testing
without 91_keep_fds.patch.

-- 
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:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

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 force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


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

[Touch-packages] [Bug 1945227] Re: drm/amdgpu: Add support for Yellow Carp

2021-10-12 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 21.0.3-0ubuntu0.3~20.04.3

---
mesa (21.0.3-0ubuntu0.3~20.04.3) focal; urgency=medium

  * patches: Backport support for AMD Yellow Carp. (LP: #1945227)

 -- Timo Aaltonen   Mon, 27 Sep 2021 20:48:12 +0300

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

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

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


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


[Touch-packages] [Bug 1945227] Re: drm/amdgpu: Add support for Yellow Carp

2021-10-12 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware - 1.187.19

---
linux-firmware (1.187.19) focal; urgency=medium

  * Add Intel WiFi/Bluetooth firmware for ADL-S/ADL-P (LP: #1933938)
- iwlwifi: add FWs for new So device types with multiple RF modules
- linux-firmware: Update firmware file for Intel Bluetooth AX211
- linux-firmware: Update firmware file for Intel Bluetooth 9560
- linux-firmware: Update firmware file for Intel Bluetooth AX201
- linux-firmware: Update firmware file for Intel Bluetooth AX211
- linux-firmware: Update firmware file for Intel Bluetooth 9462
  * Revert "amdgpu: update renoir firmware from 21.20" (LP: #1945565)
  * [Packaging] Add close-release helper script and debian rule
  * i915: Update ADLP DMC v2.12 (LP: #1945438)
  * amdgpu: add initial firmware for Yellow Carp (LP: #1945227)

 -- Timo Aaltonen   Thu, 30 Sep 2021 16:29:46 +0300

** Changed in: linux-firmware (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: mesa (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

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


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


[Touch-packages] [Bug 1945227] Update Released

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

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

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

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


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


[Touch-packages] [Bug 1946804] Re: ufw breaks boot on network root filesystem

2021-10-12 Thread Mauricio Faria de Oliveira
** Description changed:

  [Impact]
  
  A system with rootfs on iSCSI stops booting when ufw.service starts.
  The kernel logs iSCSI command/reset timeout until I/O fails and the
  root filesystem/journal break.
  
  The issue is that ufw_start() sets the default policy _first_, then
  adds rules _later_.
  
  So, a default INPUT policy of DROP (default setting in ufw) prevents
  further access to the root filesystem (blocks incoming iSCSI traffic)
  thus any rules that could help are not loaded (nor anything else.)
  
- 
  [Fix]
  
  The fix is to set default policy after loading rules in ufw_start().
  That seems to be OK as `ip[6]tables-restore -n/--noflush` is used,
  and per iptables source, that only sets the chain policy.
  
+ This allows the system to boot due to the RELATED,ESTABLISHED rule,
+ that is introduced by before.rules in INPUT/ufw-before-input chain.
+ 
  The comparison of `iptables -L` before/after shows no differences
  (verified on a local rootfs); `run_tests.sh` has 0 skipped/errors.
+ 
  
  
  Functional tests summary
  
  Attempted:   22 (3339 individual tests)
  Skipped: 0
  Errors:  0
- 
  
  [ufw info]
  
  # ufw --version
  ufw 0.36
  Copyright 2008-2015 Canonical Ltd.
  
  # lsb_release -cs
  focal
  
- 
  [Boot Log]
  
  [ 232.168355] iBFT detected.
  Begin: Running /scripts/init-premount ... done.
- Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
+ Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
  Setting up software interface enp45s0f0np0
  ...
  [ 254.644505] Loading iSCSI transport class v2.0-870.
  [ 254.714938] iscsi: registered transport (tcp)
  [ 254.780129] scsi host12: iSCSI Initiator over TCP/IP
  ...
  [ 255.433491] sd 12:0:0:1: [sda] 251658240 512-byte logical blocks: (129 
GB/120 GiB)
  ...
  [ 256.379550] EXT4-fs (sda1): mounted filesystem with ordered data mode. 
Opts: (null)
  ...
  [ 266.620860] systemd[1]: Starting Uncomplicated firewall...
  Starting Uncomplicated firewall...
  ...
  [ 298.491560] session1: iscsi_eh_cmd_timed_out scsi cmd 310a6696 
timedout
  [ 298.580803] session1: iscsi_eh_cmd_timed_out return shutdown or nh
  [ 298.656262] session1: iscsi_eh_cmd_timed_out scsi cmd 94ad9246 
timedout
  [ 298.745237] session1: iscsi_eh_cmd_timed_out return shutdown or nh
  [ 298.745270] session1: iscsi_eh_abort aborting sc 310a6696
  [ 298.899644] session1: iscsi_eh_abort aborting [sc 310a6696 itt 0x13]
  [ 298.985788] session1: iscsi_exec_task_mgmt_fn tmf set timeout
  [ 302.075554] session1: iscsi_eh_cmd_timed_out scsi cmd 1a9458b5 
timedout
  [ 302.164786] session1: iscsi_eh_cmd_timed_out return shutdown or nh
  [ 314.107541] session1: iscsi_tmf_timedout tmf timedout
  [ 314.169797] connection1:0: detected conn error (1021)
  [ 314.232266] session1: iscsi_eh_abort abort failed [sc 310a6696 itt 
0x13]
  [ 314.323531] session1: iscsi_eh_abort aborting sc 94ad9246
  [ 314.399640] session1: iscsi_eh_abort sc never reached iscsi layer or it 
completed.
  [ 314.495578] session1: iscsi_eh_abort aborting sc 1a9458b5
  [ 314.571554] session1: iscsi_eh_abort sc never reached iscsi layer or it 
completed.
  [ 314.664050] session1: iscsi_eh_device_reset LU Reset [sc 310a6696 
lun 1]
  [ 314.755773] session1: iscsi_eh_device_reset dev reset result = FAILED
  [ 314.834736] session1: iscsi_eh_target_reset tgt Reset [sc 310a6696 
tgt <...>]
  [ 314.954144] session1: iscsi_eh_target_reset tgt <...> reset result = FAILED
  [ 315.063456] connection1:0: detected conn error (1021)
  [ 315.125743] session1: iscsi_eh_session_reset wait for relogin
  [ 398.843556] INFO: task systemd:1 blocked for more than 120 seconds.
  ...
  [ 401.039006] INFO: task jbd2/sda1-8:2522 blocked for more than 123 seconds.
  ...
  [ 402.483917] INFO: task iptables-restor:2648 blocked for more than 124 
seconds.
  ...
  [ 435.707549] session1: session recovery timed out after 120 secs
  [ 435.780058] session1: iscsi_eh_session_reset failing session reset: Could 
not log back into <...> [age 0]
  [ 435.920710] sd 12:0:0:1: Device offlined - not ready after error recovery
  [ 436.003563] sd 12:0:0:1: [sda] tag#105 FAILED Result: 
hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK cmd_age=169s
  [ 436.015520] sd 12:0:0:1: rejecting I/O to offline device
  [ 436.134354] sd 12:0:0:1: [sda] tag#105 CDB: Read(10) 28 00 00 05 8d d8 00 
00 08 00
  [ 436.198807] blk_update_request: I/O error, dev sda, sector 360816 op 
0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
  [ 436.198818] blk_update_request: I/O error, dev sda, sector 2324480 op 
0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
  [ 436.198852] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1004: 
inode #1398: lblock 0: comm systemd: error -5 reading directory block
  [ 436.290259] blk_update_request: I/O error, dev sda, 

[Touch-packages] [Bug 1946804] Re: ufw breaks boot on network root filesystem

2021-10-12 Thread Mauricio Faria de Oliveira
Merge Proposal submitted:
https://code.launchpad.net/~mfo/ufw/+git/ufw/+merge/410091

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

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

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

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

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

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

Title:
  ufw breaks boot on network root filesystem

Status in ufw:
  New
Status in ufw package in Ubuntu:
  New
Status in ufw source package in Bionic:
  New
Status in ufw source package in Focal:
  New
Status in ufw source package in Hirsute:
  New
Status in ufw source package in Impish:
  New

Bug description:
  [Impact]

  A system with rootfs on iSCSI stops booting when ufw.service starts.
  The kernel logs iSCSI command/reset timeout until I/O fails and the
  root filesystem/journal break.

  The issue is that ufw_start() sets the default policy _first_, then
  adds rules _later_.

  So, a default INPUT policy of DROP (default setting in ufw) prevents
  further access to the root filesystem (blocks incoming iSCSI traffic)
  thus any rules that could help are not loaded (nor anything else.)

  
  [Fix]

  The fix is to set default policy after loading rules in ufw_start().
  That seems to be OK as `ip[6]tables-restore -n/--noflush` is used,
  and per iptables source, that only sets the chain policy.

  The comparison of `iptables -L` before/after shows no differences
  (verified on a local rootfs); `run_tests.sh` has 0 skipped/errors.

  
  Functional tests summary
  
  Attempted:   22 (3339 individual tests)
  Skipped: 0
  Errors:  0

  
  [ufw info]

  # ufw --version
  ufw 0.36
  Copyright 2008-2015 Canonical Ltd.

  # lsb_release -cs
  focal

  
  [Boot Log]

  [ 232.168355] iBFT detected.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
  Setting up software interface enp45s0f0np0
  ...
  [ 254.644505] Loading iSCSI transport class v2.0-870.
  [ 254.714938] iscsi: registered transport (tcp)
  [ 254.780129] scsi host12: iSCSI Initiator over TCP/IP
  ...
  [ 255.433491] sd 12:0:0:1: [sda] 251658240 512-byte logical blocks: (129 
GB/120 GiB)
  ...
  [ 256.379550] EXT4-fs (sda1): mounted filesystem with ordered data mode. 
Opts: (null)
  ...
  [ 266.620860] systemd[1]: Starting Uncomplicated firewall...
  Starting Uncomplicated firewall...
  ...
  [ 298.491560] session1: iscsi_eh_cmd_timed_out scsi cmd 310a6696 
timedout
  [ 298.580803] session1: iscsi_eh_cmd_timed_out return shutdown or nh
  [ 298.656262] session1: iscsi_eh_cmd_timed_out scsi cmd 94ad9246 
timedout
  [ 298.745237] session1: iscsi_eh_cmd_timed_out return shutdown or nh
  [ 298.745270] session1: iscsi_eh_abort aborting sc 310a6696
  [ 298.899644] session1: iscsi_eh_abort aborting [sc 310a6696 itt 0x13]
  [ 298.985788] session1: iscsi_exec_task_mgmt_fn tmf set timeout
  [ 302.075554] session1: iscsi_eh_cmd_timed_out scsi cmd 1a9458b5 
timedout
  [ 302.164786] session1: iscsi_eh_cmd_timed_out return shutdown or nh
  [ 314.107541] session1: iscsi_tmf_timedout tmf timedout
  [ 314.169797] connection1:0: detected conn error (1021)
  [ 314.232266] session1: iscsi_eh_abort abort failed [sc 310a6696 itt 
0x13]
  [ 314.323531] session1: iscsi_eh_abort aborting sc 94ad9246
  [ 314.399640] session1: iscsi_eh_abort sc never reached iscsi layer or it 
completed.
  [ 314.495578] session1: iscsi_eh_abort aborting sc 1a9458b5
  [ 314.571554] session1: iscsi_eh_abort sc never reached iscsi layer or it 
completed.
  [ 314.664050] session1: iscsi_eh_device_reset LU Reset [sc 310a6696 
lun 1]
  [ 314.755773] session1: iscsi_eh_device_reset dev reset result = FAILED
  [ 314.834736] session1: iscsi_eh_target_reset tgt Reset [sc 310a6696 
tgt <...>]
  [ 314.954144] session1: iscsi_eh_target_reset tgt <...> reset result = FAILED
  [ 315.063456] connection1:0: detected conn error (1021)
  [ 315.125743] session1: iscsi_eh_session_reset wait for relogin
  [ 398.843556] INFO: task systemd:1 blocked for more than 120 seconds.
  ...
  [ 401.039006] INFO: task jbd2/sda1-8:2522 blocked for more than 123 seconds.
  ...
  [ 402.483917] INFO: task iptables-restor:2648 blocked for more than 124 
seconds.
  ...
  [ 435.707549] session1: session recovery timed out after 120 secs
  [ 435.780058] session1: iscsi_eh_session_reset failing session reset: Could 
not log back into <...> [age 0]
  [ 435.920710] sd 12:0:0:1: Device offlined - not ready after error recovery
  [ 436.003563] sd 

[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

2021-10-12 Thread Brian Murray
I booted an Ubuntu desktop ISO with the new version of glib2.0 and pkmon
now indicates that "network status=online".

 $ bsdtar -x -f impish-desktop-amd64.iso -O \./.disk/info
Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)%

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Impish:
  Fix Released

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


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


[Touch-packages] [Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

2021-10-12 Thread aliengotithard
ALSO AFFECTS DOCKER VPS - Is there a definitive solution? Im going to
try @jasdenty solution. Im not that technical user.

It affects my VPS after "apt upgrade". Suddenly resolving domains from
docker containers stopped - from what i understand docker defaultly
inherits /etc/resolv.conf.  Completly revisiting my docker networks
didn't help.

So this comment is for you guys whose dockers stopped working after
update.

Thanks

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

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When using nslookup for local machine names, the local DNS was being
  ignored (not queried) and none of the local machines could be found.

  After much research and digging, it was discovered that the cause was
  the incorrect symbolic link /etc/resolv.conf file.

  The default install caused systemd-resolve to configure the link to point to 
the stub file:
  /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

  Reomving that link and pointing it to the correct file solved the DNS lookup 
issue. The correct link looks like this:
  /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

  
  Steps used to test the bug before fixing the link is to perform an nslookup 
on a local (non FQDN) machine that is in your local DNS (my router is my DNS 
server for this case) Here is an example of the incorrect output:

  $ nslookup web1

  Server: 127.0.0.53
  Address:127.0.0.53#53

  ** server can't find web1: SERVFAIL

  
  Switching the symbolic link solves the problem. Here is my solution:

  $ sudo rm -f /etc/resolv.conf
  $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

  
  After switching the symbolic link, the nslookup functions properly.

  $ nslookup web1

  Server: 192.168.1.1
  Address:192.168.1.1#53

  Name:   web1
  Address: 192.168.1.107

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  1 05:28:41 2018
  InstallationDate: Installed on 2018-01-20 (131 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5755
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=7fe151d3-4033-4903-b356-341d9f16e124 ro acpi=force
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (33 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0VY15F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/27/2015:svnDellInc.:pnInspiron5755:pvrA08:rvnDellInc.:rn0VY15F:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 5755
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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


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


[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

2021-10-12 Thread Launchpad Bug Tracker
This bug was fixed in the package glib2.0 - 2.68.4-1ubuntu1

---
glib2.0 (2.68.4-1ubuntu1) impish; urgency=medium

  * Cherry-pick merge request 2291 to fix network monitoring with latest
NetworkManager (LP: #1946196)

 -- Julian Andres Klode   Tue, 12 Oct 2021 14:39:07
+0200

** Changed in: glib2.0 (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Impish:
  Fix Released

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


-- 
Mailing list: https://launchpad.net/~touch-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

2021-10-12 Thread Norbert
Downgrading VTE to hirsute's version solves the issue. Could anyone
downgrade it for Impish?

-- 
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:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

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 force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


-- 
Mailing list: https://launchpad.net/~touch-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

2021-10-12 Thread Gunnar Hjalmarsson
A related comment in #ubuntu-desktop:

https://irclogs.ubuntu.com/2021/10/12/%23ubuntu-desktop.html#t15:12

** Changed in: vte2.91 (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

-- 
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:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

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 force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


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

Re: [Touch-packages] [Bug 1946664] Re: account setup window becomes unconfigured

2021-10-12 Thread Luis Augusto Xavier Cruz
Sebastian,
I have not noticed any similar problem in any other application that I have
used on the system.
I am sorry but I am new to using the system and I did not understand if the
rendering problems you mentioned refer to any application that I need to
test? (...rendering problems in yelp , devhelp or epiphany-browser?)

Em ter., 12 de out. de 2021 às 11:35, Sebastien Bacher <
1946...@bugs.launchpad.net> escreveu:

> Thank you for your bug report, it seems corruption in webkitgtk views.
> Do you get similar rendering problems in yelp , devhelp or epiphany-
> browser?
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> ** Summary changed:
>
> - account setup window becomes unconfigured
> + [raspi] screen correct on online accounts webviews
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946664
>
> Title:
>   [raspi] screen correct on online accounts webviews
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I installed ubuntu desktop on my Raspberrypi 4b. I set up the ubuntu
>   sign-one account, but to set up the Google and Microsoft account, the
>   window to enter the account data gets misconfigured on the screen and
>   does not read the fields to enter the data and set up access to my
>   accounts.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: xorg 1:7.7+22ubuntu1
>   ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22
>   Uname: Linux 5.11.0-1019-raspi aarch64
>   ApportVersion: 2.20.11-0ubuntu65.3
>   Architecture: arm64
>   BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
>   CasperMD5CheckResult: unknown
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Oct 11 12:12:33 2021
>   DistUpgraded: Fresh install
>   DistroCodename: hirsute
>   DistroVariant: ubuntu
>   GraphicsCard:
>
>   ImageMediaBuild: 20210421
>   Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805
> USB 3.0 Host Controller
>   ProcEnviron:
>LANGUAGE=pt_BR:pt:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=pt_BR.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0
> snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1
> video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:BB:4B:64
> vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0
> console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait
> fixrtc quiet splash
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   acpidump:
>
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.105-3~21.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1946664/+subscriptions
>
>

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

Title:
  [raspi] screen corruption on online accounts webviews

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I installed ubuntu desktop on my Raspberrypi 4b. I set up the ubuntu
  sign-one account, but to set up the Google and Microsoft account, the
  window to enter the account data gets misconfigured on the screen and
  does not read the fields to enter the data and set up access to my
  accounts.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22
  Uname: Linux 5.11.0-1019-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: arm64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 11 12:12:33 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  GraphicsCard:
   
  ImageMediaBuild: 20210421
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:BB:4B:64 
vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 
console=tty1 

[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

2021-10-12 Thread Brian Murray
** Tags removed: rls-ii-incoming

** Also affects: glib2.0 (Ubuntu Impish)
   Importance: High
 Assignee: Julian Andres Klode (juliank)
   Status: Fix Committed

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in glib2.0 source package in Impish:
  Fix Committed

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


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


[Touch-packages] [Bug 1946481] Re: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"

2021-10-12 Thread Sebastien Bacher
** Package changed: dbus (Ubuntu) => modemmanager (Ubuntu)

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

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

Title:
  NetworkManager cannot connect to ModemManager with
  "org.freedesktop.DBus.Error.AccessDenied"

Status in modemmanager package in Ubuntu:
  New

Bug description:
  Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get 
access to Modem Manager fails with:
  > error: couldn't create manager: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied

  This was working on 21.04.

  STR:
   - Open Settings, go to "Network"
  OR
   - mmcli -m 0

  Running mmcli as root workaround the problem, but I'm not able to use
  network applet to connect my modem.

  > $ id
  uid=1000(alex) gid=1000(alex) 
groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker)

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


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


[Touch-packages] [Bug 1946664] Re: [raspi] screen corruption on online accounts webviews

2021-10-12 Thread Sebastien Bacher
** Summary changed:

- [raspi] screen correct on online accounts webviews
+ [raspi] screen corruption on online accounts webviews

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

Title:
  [raspi] screen corruption on online accounts webviews

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I installed ubuntu desktop on my Raspberrypi 4b. I set up the ubuntu
  sign-one account, but to set up the Google and Microsoft account, the
  window to enter the account data gets misconfigured on the screen and
  does not read the fields to enter the data and set up access to my
  accounts.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22
  Uname: Linux 5.11.0-1019-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: arm64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 11 12:12:33 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  GraphicsCard:
   
  ImageMediaBuild: 20210421
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:BB:4B:64 
vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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


[Touch-packages] [Bug 1945969] Re: Update to 0.52.6 in impish

2021-10-12 Thread Sebastien Bacher
I see an upload in the queue for libunity so setting as fix commited

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

Title:
  Update to 0.52.6 in impish

Status in libunity package in Ubuntu:
  Fix Committed
Status in vala package in Ubuntu:
  Fix Released

Bug description:
  The 0.52.x series is receiving further bug fix releases for GNOME 40.x.
  See https://wiki.gnome.org/Projects/Vala

  Upstream changes since 0.52.5:

  Vala 0.52.6
  ===
   * Various improvements and bug fixes:
- codegen:
  + Fix property access inside opaque compact class
  + Add type declaration for implicit temporary local variable
- vala:
  + Warn about unsupported cast to void and drop it [#1070]
  + Don't restrict element type of GLib.Array [#1227]
  + Multi-dimensional params-array not allowed [#1230]
  + Accept NullType as generic type argument
  + Set source references of created DataType instances in OCE
- valadoc: Correctly format background of inline @link's [#1226]

   * Bindings:
- gio-2.0: Unhide a few usable symbols which are marked not introspectable 
[#1222]
- gio-2.0: Backport fixes from 0.54.2
- glib-2.0: Current constants in GLib.Math are part of glib.h [#1220]
- glib-2.0: Add RefString since 2.58 [#723]
- gtk4: Backport fixes from 0.54.2

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


-- 
Mailing list: https://launchpad.net/~touch-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"

2021-10-12 Thread Lukas Märdian
Thank you! You changes LGTM.
The first patch resembles the upstream commit, the 2nd patch (that touches the 
translation files) is not yet merged upstream, but makes sense.

With all builds passing in a PPA and a successful autopkgtest run, I'll
stage this to be a 0-day SRU, as discussed with the release team.

$ dput ubuntu ../util-linux_2.36.1-8ubuntu2_source.changes 
D: Setting host argument.
Checking signature on .changes
gpg: ../util-linux_2.36.1-8ubuntu2_source.changes: Valid signature from 
5889C17AB1C8D890
Checking signature on .dsc
gpg: ../util-linux_2.36.1-8ubuntu2.dsc: Valid signature from 5889C17AB1C8D890
Uploading to ubuntu (via sftp to upload.ubuntu.com):
  Uploading util-linux_2.36.1-8ubuntu2.dsc: done.
  Uploading util-linux_2.36.1-8ubuntu2.debian.tar.xz: done.
  Uploading util-linux_2.36.1-8ubuntu2_source.buildinfo: done. 
  Uploading util-linux_2.36.1-8ubuntu2_source.changes: done.
Successfully uploaded packages.

-- 
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:
  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, 

[Touch-packages] [Bug 1945969] Re: Update to 0.52.6 in impish

2021-10-12 Thread Sebastien Bacher
I see an upload in the queue for libunity so setting as fix commited

** Changed in: libunity (Ubuntu)
   Status: New => Fix Committed

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

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

Title:
  Update to 0.52.6 in impish

Status in libunity package in Ubuntu:
  Fix Committed
Status in vala package in Ubuntu:
  Fix Released

Bug description:
  The 0.52.x series is receiving further bug fix releases for GNOME 40.x.
  See https://wiki.gnome.org/Projects/Vala

  Upstream changes since 0.52.5:

  Vala 0.52.6
  ===
   * Various improvements and bug fixes:
- codegen:
  + Fix property access inside opaque compact class
  + Add type declaration for implicit temporary local variable
- vala:
  + Warn about unsupported cast to void and drop it [#1070]
  + Don't restrict element type of GLib.Array [#1227]
  + Multi-dimensional params-array not allowed [#1230]
  + Accept NullType as generic type argument
  + Set source references of created DataType instances in OCE
- valadoc: Correctly format background of inline @link's [#1226]

   * Bindings:
- gio-2.0: Unhide a few usable symbols which are marked not introspectable 
[#1222]
- gio-2.0: Backport fixes from 0.54.2
- glib-2.0: Current constants in GLib.Math are part of glib.h [#1220]
- glib-2.0: Add RefString since 2.58 [#723]
- gtk4: Backport fixes from 0.54.2

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


-- 
Mailing list: https://launchpad.net/~touch-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

2021-10-12 Thread Gunnar Hjalmarsson
This is an attempt at a fix which does not work:

https://launchpad.net/~gunnarhj/+archive/ubuntu/vte2.91/+packages

-- 
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:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

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 force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


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


[Touch-packages] [Bug 1946664] Re: account setup window becomes unconfigured

2021-10-12 Thread Sebastien Bacher
Thank you for your bug report, it seems corruption in webkitgtk views.
Do you get similar rendering problems in yelp , devhelp or epiphany-
browser?

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

** Summary changed:

- account setup window becomes unconfigured
+ [raspi] screen correct on online accounts webviews

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

Title:
  [raspi] screen correct on online accounts webviews

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I installed ubuntu desktop on my Raspberrypi 4b. I set up the ubuntu
  sign-one account, but to set up the Google and Microsoft account, the
  window to enter the account data gets misconfigured on the screen and
  does not read the fields to enter the data and set up access to my
  accounts.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22
  Uname: Linux 5.11.0-1019-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: arm64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 11 12:12:33 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  GraphicsCard:
   
  ImageMediaBuild: 20210421
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:BB:4B:64 
vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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


[Touch-packages] [Bug 1946691] Re: using xorg driver for graphics card prevents suspend

2021-10-12 Thread Brian Murray
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  using xorg driver for graphics card prevents suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu 20.04.3 LTS

  Not sure what package this belongs to, but this has to do with trying
  to suspend the computer.

  What I expect: 
  selecting power off->suspend suspends my computer e.g. turns off screen, 
turns off fans, etc.

  What happens:
  In "Software & Updates" Additional Drivers tab, for my GeForce GT 745M, if I 
select the "Using X.Org X server" open source driver and then I try to suspend, 
the computer will log off, and the screen will turn black except for blinking 
cursor in the top left corner. The computer will never power down.

  The workaround:
  I work around this by selecting "Using NVIDIA driver metapackage" from 
nvidia-driver-470 (proprietary, tested)
  After this, my computer properly suspends.

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


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


[Touch-packages] [Bug 1946691] [NEW] using xorg driver for graphics card prevents suspend

2021-10-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

ubuntu 20.04.3 LTS

Not sure what package this belongs to, but this has to do with trying to
suspend the computer.

What I expect: 
selecting power off->suspend suspends my computer e.g. turns off screen, turns 
off fans, etc.

What happens:
In "Software & Updates" Additional Drivers tab, for my GeForce GT 745M, if I 
select the "Using X.Org X server" open source driver and then I try to suspend, 
the computer will log off, and the screen will turn black except for blinking 
cursor in the top left corner. The computer will never power down.

The workaround:
I work around this by selecting "Using NVIDIA driver metapackage" from 
nvidia-driver-470 (proprietary, tested)
After this, my computer properly suspends.

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


** Tags: bot-comment
-- 
using xorg driver for graphics card prevents suspend
https://bugs.launchpad.net/bugs/1946691
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


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

2021-10-12 Thread Alexandre Ghiti
** Description changed:

- 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'.
- 
- Fix that by removing the 'Unleashed' part of the current name so that it
- fits both.
- 
- The attached debdiff contains the patch that was merged upstream
- (https://github.com/karelzak/util-
- linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07).
+ [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
   
+ /dev/vda13 34 2081 20481M HiFive FSBL 
   
+ 

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

2021-10-12 Thread Gunnar Hjalmarsson
Confirmed that gdebi-gtk works on Debian testing (without
91_keep_fds.patch). So the need for that patch is Ubuntu specific
somehow. (Not sure how that helps, but I thought it was worth checking.)

-- 
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:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

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 force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


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

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

2021-10-12 Thread Daniel Manrique
** Changed in: canonical-identity-provider
   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/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 1944741] Re: HiFive Unmatched partitions are named "Unleashed"

2021-10-12 Thread Alexandre Ghiti
I actually missed the translation files that contain the translation of
the partition names I changed. Attached the corresponding debdiff that
contains all the changes.

** Patch added: "util_linux_debdiff.patch"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+attachment/5532128/+files/util_linux_debdiff.patch

-- 
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:
  New
Status in util-linux package in Debian:
  Confirmed

Bug description:
  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'.
  
  Fix that by removing the 'Unleashed' part of the current name so that it
  fits both.

  The attached debdiff contains the patch that was merged upstream
  (https://github.com/karelzak/util-
  linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07).

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


-- 
Mailing list: https://launchpad.net/~touch-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

2021-10-12 Thread Gunnar Hjalmarsson
Hi!

I can confirm the problem with gdebi-gtk, as already described by
Norbert.

The patch is apparently a workaround since nobody has had the time to
adapt gdebi. My refresh in the latest Ubuntu upload of vte2.91 was a
minimum change to make it still apply after upstream had made changes.
Maybe I did a mistake when doing so.

Wonder if gdebi-gtk works on Debian (which does not have
91_keep_fds.patch.

-- 
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:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

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 force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

To manage notifications about this bug go to:

[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

2021-10-12 Thread Julian Andres Klode
** Changed in: glib2.0 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


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


[Touch-packages] [Bug 1946481] Re: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"

2021-10-12 Thread Pirouette Cacahuète
Attached journal taken after following the previously documented STR:
 - Open Settings,
 - Go to Network tab

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

Title:
  NetworkManager cannot connect to ModemManager with
  "org.freedesktop.DBus.Error.AccessDenied"

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get 
access to Modem Manager fails with:
  > error: couldn't create manager: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied

  This was working on 21.04.

  STR:
   - Open Settings, go to "Network"
  OR
   - mmcli -m 0

  Running mmcli as root workaround the problem, but I'm not able to use
  network applet to connect my modem.

  > $ id
  uid=1000(alex) gid=1000(alex) 
groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker)

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


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


[Touch-packages] [Bug 1946481] Re: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"

2021-10-12 Thread Pirouette Cacahuète
** Attachment added: "journal.log"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1946481/+attachment/5532127/+files/journal.log

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

Title:
  NetworkManager cannot connect to ModemManager with
  "org.freedesktop.DBus.Error.AccessDenied"

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get 
access to Modem Manager fails with:
  > error: couldn't create manager: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied

  This was working on 21.04.

  STR:
   - Open Settings, go to "Network"
  OR
   - mmcli -m 0

  Running mmcli as root workaround the problem, but I'm not able to use
  network applet to connect my modem.

  > $ id
  uid=1000(alex) gid=1000(alex) 
groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker)

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


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


[Touch-packages] [Bug 1946481] Re: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"

2021-10-12 Thread Pirouette Cacahuète
The output of `mmcli -L` was already provided above:
> $ mmcli -L
> error: couldn't create manager: 
> GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 5 
> matched rules; type="method_call", sender=":1.269" (uid=1000 pid=48173 
> comm="mmcli -L " label="unconfined") 
> interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
> error name="(unset)" requested_reply="0" destination=":1.17" (uid=0 pid=1702 
> comm="/usr/sbin/ModemManager " label="unconfined")

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

Title:
  NetworkManager cannot connect to ModemManager with
  "org.freedesktop.DBus.Error.AccessDenied"

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get 
access to Modem Manager fails with:
  > error: couldn't create manager: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied

  This was working on 21.04.

  STR:
   - Open Settings, go to "Network"
  OR
   - mmcli -m 0

  Running mmcli as root workaround the problem, but I'm not able to use
  network applet to connect my modem.

  > $ id
  uid=1000(alex) gid=1000(alex) 
groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker)

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


-- 
Mailing list: https://launchpad.net/~touch-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

2021-10-12 Thread Norbert
It fails, see screen-cast, this is with latest gdebi and latest VTE from 
Impish. 
Proposed is not enabled (if this matters).

```
$ dpkg -l | grep -E "vte|gdebi"
ii  gdebi0.9.5.7+nmu5ubuntu1
all  simple tool to view and install deb files - GNOME GUI
ii  gdebi-core   0.9.5.7+nmu5ubuntu1
all  simple tool to install deb files
ii  gir1.2-vte-2.91:amd640.64.2-1ubuntu1
amd64GObject introspection data for the VTE library
ii  libvte-2.91-0:amd64  0.64.2-1ubuntu1
amd64Terminal emulator widget for GTK+ 3.0 - runtime files
ii  libvte-2.91-common   0.64.2-1ubuntu1
amd64Terminal emulator widget for GTK+ 3.0 - common files
```


** Attachment added: "gdebi-gtk.gif"
   
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1946499/+attachment/5532126/+files/gdebi-gtk.gif

-- 
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:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

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 

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

2021-10-12 Thread Martin Wimpress 
The only difference in 91_keep_fds.patch between vte2.91
(0.62.3-1ubuntu1) and vte2.91 (0.64.2-1ubuntu1) is this:

164,165c164,165
<  auto op = new vte::base::SpawnOperation{spawn_context_from_args(pty,
<  
working_directory,
---
>  auto op = std::make_unique
>  (spawn_context_from_args(pty,

-- 
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:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

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 force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

To manage notifications about this bug go to:

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

2021-10-12 Thread Martin Wimpress 
From the recent changelog I see 91_keep_fds.patch in vte2.91 was
refreshed.

vte2.91 (0.64.2-1ubuntu1) impish; urgency=medium

  * Merge with debian experimental. Remaining changes:
- Add 91_keep_fds.patch since gdebi still requires it (LP: #1756238)
- Breaks/Replaces with libvte-2.91-0 (<= 0.60.0-2ubuntu1)
- Ubuntu gbp.conf and debian/control VCS information
  * Refresh 91_keep_fds.patch


gunnarhj can you confirm that gdebi fail to install debs?


** Changed in: vte2.91 (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
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:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

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 force_start=1
   

[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

2021-10-12 Thread Julian Andres Klode
Fix proposed in
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2291

** Changed in: packagekit (Ubuntu)
Milestone: None => ubuntu-21.10

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

** Package changed: packagekit (Ubuntu) => glib2.0 (Ubuntu)

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


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


[Touch-packages] [Bug 1943189] Re: [SRU] "cannot refresh whilst network offline"in plasma-discover

2021-10-12 Thread Julian Andres Klode
So it turns out that yes, this fix was not helpful, and we are dealing
with the underlying glib issue in bug 1946196 directly - it needs an
update for NetworkManager DBus API break.

** Changed in: packagekit (Ubuntu Hirsute)
   Status: Confirmed => Invalid

** Changed in: packagekit (Ubuntu Focal)
   Status: Confirmed => Invalid

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

Title:
  [SRU] "cannot refresh whilst network offline"in plasma-discover

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Focal:
  Invalid
Status in packagekit source package in Hirsute:
  Invalid
Status in packagekit source package in Impish:
  Fix Released

Bug description:
  [Impact]

  In Ubuntu Impish, an issue has been noted in regards to refreshing
  packages in Plasma Discover for upgrade or installation. An error
  appears upon initialization of the Discover interface:

  "cannot refresh whilst network offline"

  This will happen regardless of if a system is online or not.

  I identified a race condition in which this is occurring on systems
  where packagekitd is initialized before the network service is online.
  This was a relatively easy fix and required adding one line to the
  packagekit.service file:

  Wants=network-online.target

  This ensures that packagekitd is not initialized prior to being
  online. If the 90 second deadline isn't met, then packagekitd will
  simply not start as a background process until the user connects to
  the network and initializes it via a graphical utility, such as with
  GNOME Software or Plasma Discover, both of which initialize
  packagekitd on a user level.

  The attached patch will easily apply the fix via normal Debian
  packaging methods.

  [Test Plan]

   * Install Kubuntu or Ubuntu Studio

   * While connected to network, Run Discover

   * Discover will complain about "cannot refresh whilst offline", which
  is being communicated from PackageKit. All functionality in Discover
  is hindered from this point forward. This is due to a hung packagekitd
  process which sees the network offline, even though this is false.

  [Where problems could occur]

   * packagekitd's systemd service will time-out after 90 seconds if
  systemd finds no network, which means any update notifications will
  not automatically start until packagekitd is manually started.
  Luckily, Discover and GNOME Software both attempt to start packagekitd
  for the user when run. I'd consider this to be expected behavior for
  an offline system. The fix is mostly to prevent the false-negative of
  the system being offline when it's really not.

  [Other Info]

   * This fix has been accepted upstream by the PackageKit maintainers
  as a sane workaround for when gio misbehaves or otherwise. It's a
  decent safety net. https://github.com/PackageKit/PackageKit/pull/506

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: packagekit 1.2.2-2ubuntu1 [modified: 
lib/systemd/system/packagekit.service]
  ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
  Uname: Linux 5.13.0-14-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Sep  9 16:34:12 2021
  InstallationDate: Installed on 2021-03-20 (172 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago)

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


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


[Touch-packages] [Bug 1946481] Re: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"

2021-10-12 Thread Sebastien Bacher
Thank you for your bug report. Could you add the 'journalctl - b 0' from a 
session where you got the issue? What's the output of
$ mmcli -L
?

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

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

Title:
  NetworkManager cannot connect to ModemManager with
  "org.freedesktop.DBus.Error.AccessDenied"

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get 
access to Modem Manager fails with:
  > error: couldn't create manager: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied

  This was working on 21.04.

  STR:
   - Open Settings, go to "Network"
  OR
   - mmcli -m 0

  Running mmcli as root workaround the problem, but I'm not able to use
  network applet to connect my modem.

  > $ id
  uid=1000(alex) gid=1000(alex) 
groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker)

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


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


[Touch-packages] [Bug 1946561] Re: tracker causes 0 bytes free in /home

2021-10-12 Thread UlfZibis
** Changed in: tracker (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  tracker causes 0 bytes free in /home

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  This is what I have:
  Partition Ubuntu mounted in / :  20 GiB, 12 GiB in use
  Partition home   mounted in /home :   8 GiB, 3.1 GiB in use
  Partition Data   mounted in /mnt/Data : 120 GiB, 35 GiB in use
  Symlink /home/me/Download  -> /mnt/Data/Users/me/Download
  Symlink /home/me/Documents -> /mnt/Data/Users/me/Documents
  Symlink /home/me/Pictures  -> /mnt/Data/Users/me/Pictures
  Symlink /home/me/Music -> /mnt/Data/Users/me/Music
  Symlink /home/me/Videos-> /mnt/Data/Users/me/Videos

  /home had 4.6 GB free.
  After I copied 8 GB of *.epub files to /home/me/Documents/eBooks/, I got 0 
byte free on /home after 10 minutes, caused by tracker files in 
/home/user/.cache/tracker/
  gsettings set org.freedesktop.Tracker.Miner.Files low-disk-space-limit 10
  did not help.

  It seems, that tracker estimates more space than 4.6 GB because of the
  symlinks to /mnt/Data/...

  Suggestions:
  - tracker should not try to index DRM encrypted epub files and similars
  - all tracker components, not only tracker-miner*.service, should respect 
low-disk-space-limit
  - tracker components should never create situations with 0 bytes free, even 
if low-disk-space-limit is -1
  - tracker components anyway should estimate free space correctly (not include 
space from symlinks to other file systems)

  Workaround:
  Add '*.epub' to org.freedesktop.Tracker.Miner.Files ignored-files.

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


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


[Touch-packages] [Bug 1946714] [NEW] Unable to locally verify the issuer's authority.

2021-10-12 Thread robin
Public bug reported:

In a terminal, when I run the following:
wget https://www.linz.govt.nz/sites/default/files/media/ntm/bsb/BSB_UPDATE.zip  


I get an error message about certificates, as follows.
ERROR: cannot verify www.linz.govt.nz's certificate, issued by ‘CN=Thawte RSA 
CA 2018,OU=www.digicert.com,O=DigiCert Inc,C=US’:

The file is not downloaded. I contacted the maintainers of the site,
they declared there is no problem with the certificate.

Of course, this probably isn't a problem with wget, or with curl which gives a 
similar error and the advice to go to this page:
https://curl.se/docs/sslcerts.html

Unfortunately that's way over my head, so I'm hoping someone helpful
here can shed some light on the matter.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: wget 1.20.3-1ubuntu1
Uname: Linux 5.14.11-051411-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Flashback:GNOME
Date: Tue Oct 12 19:19:54 2021
InstallationDate: Installed on 2019-05-26 (869 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: wget
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  Unable to locally verify the issuer's authority.

Status in wget package in Ubuntu:
  New

Bug description:
  In a terminal, when I run the following:
  wget 
https://www.linz.govt.nz/sites/default/files/media/ntm/bsb/BSB_UPDATE.zip   
   

  I get an error message about certificates, as follows.
  ERROR: cannot verify www.linz.govt.nz's certificate, issued by ‘CN=Thawte RSA 
CA 2018,OU=www.digicert.com,O=DigiCert Inc,C=US’:

  The file is not downloaded. I contacted the maintainers of the site,
  they declared there is no problem with the certificate.

  Of course, this probably isn't a problem with wget, or with curl which gives 
a similar error and the advice to go to this page:
  https://curl.se/docs/sslcerts.html

  Unfortunately that's way over my head, so I'm hoping someone helpful
  here can shed some light on the matter.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wget 1.20.3-1ubuntu1
  Uname: Linux 5.14.11-051411-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue Oct 12 19:19:54 2021
  InstallationDate: Installed on 2019-05-26 (869 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: wget
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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