[Bug 1926819] Re: Empty MOTD on up-to-date systems (includes fix)

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-apt_check.py-Fix-empty-output-in-the-no-ESM-up-to-
da.patch" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926819

Title:
  Empty MOTD on up-to-date systems (includes fix)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917167] Re: Can't install 18.04, 20.04, 21.10 on the desktop. 16.04 installation is OK.

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917167

Title:
  Can't install 18.04, 20.04, 21.10 on the desktop. 16.04 installation
  is OK.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926633] Re: Ramdom Stuck in activities after pressing super key

[dev]

** Summary changed:

- Stuck in activities after pressing super key
+ Ramdom Stuck in activities after pressing super key

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926633

Title:
  Ramdom Stuck in activities after pressing super key

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926822] [NEW] Updating from 18.04 LTS to 20.04 LTS fails with no hints on what to do

[Dustin]

Public bug reported:

Trying to upgrade results in a error with no help hints.

> Calculating the changes
>
> Could not calculate the upgrade
>
> An unresolvable problem occurred while calculating the upgrade.
>
> If none of this applies, then please report this bug using the
> command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If
> you want to investigate this yourself the log files in
> '/var/log/dist-upgrade' will contain details about the upgrade.
> Specifically, look at 'main.log' and 'apt.log'.

apt.log contains a long list of broken packages, none of which I
remember installing, save for one or two.

I'm running Ubuntu MATE 18.04.5 LTS, with 'ubuntu-release-upgrader-core'
version '1:18.04.44'

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.44
ProcVersionSignature: Ubuntu 5.4.0-72.80~18.04.1-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: MATE
Date: Fri Apr 30 21:47:08 2021
InstallationDate: Installed on 2020-03-12 (414 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-05-01 (0 days ago)
mtime.conffile..etc.update-manager.release-upgrades: 2020-08-29T13:08:00.600669

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


** Tags: amd64 apport-bug bionic dist-upgrade

** Description changed:

  Trying to upgrade results in a error with no help hints.
  
  > Calculating the changes
- > 
- > Could not calculate the upgrade 
- > 
- > An unresolvable problem occurred while calculating the upgrade. 
- > 
- > If none of this applies, then please report this bug using the 
- > command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If 
- > you want to investigate this yourself the log files in 
- > '/var/log/dist-upgrade' will contain details about the upgrade. 
- > Specifically, look at 'main.log' and 'apt.log'. 
+ >
+ > Could not calculate the upgrade
+ >
+ > An unresolvable problem occurred while calculating the upgrade.
+ >
+ > If none of this applies, then please report this bug using the
+ > command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If
+ > you want to investigate this yourself the log files in
+ > '/var/log/dist-upgrade' will contain details about the upgrade.
+ > Specifically, look at 'main.log' and 'apt.log'.
  
  apt.log contains a long list of broken packages, none of which I
- remember installing, save for one or two. If apt.log doesn't get
- attached, you can download it here:
- 
https://cdn.discordapp.com/attachments/796094282279813150/837891646757535754/apt.log
+ remember installing, save for one or two.
  
  I'm running Ubuntu MATE 18.04.5 LTS, with 'ubuntu-release-upgrader-core'
  version '1:18.04.44'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.44
  ProcVersionSignature: Ubuntu 5.4.0-72.80~18.04.1-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Apr 30 21:47:08 2021
  InstallationDate: Installed on 2020-03-12 (414 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to bionic on 2021-05-01 (0 days ago)
  mtime.conffile..etc.update-manager.release-upgrades: 
2020-08-29T13:08:00.600669

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926822

Title:
  Updating from 18.04 LTS to 20.04 LTS fails with no hints on what to do

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925421] Re: arm64 support

[Khaled El Mously]

** Changed in: linux-oracle (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925421

Title:
  arm64 support

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926819] Re: Empty MOTD on up-to-date focal systems (includes fix)

[Aaron Thompson]

** Summary changed:

- Empty MOTD on update-to-date focal systems (includes fix)
+ Empty MOTD on up-to-date focal systems (includes fix)

** Summary changed:

- Empty MOTD on up-to-date focal systems (includes fix)
+ Empty MOTD on up-to-date systems (includes fix)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926819

Title:
  Empty MOTD on up-to-date systems (includes fix)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 106737]

[Bugzilla2007]

*** Bug 1708164 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/106737

Title:
  Renaming folder to same name but different case not allowed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912652] Re: Upgrading libc6-lse breaks on systems it is in use

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-release-upgrader (Ubuntu Groovy)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912652

Title:
  Upgrading libc6-lse breaks on systems it is in use

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912652] Re: Upgrading libc6-lse breaks on systems it is in use

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912652

Title:
  Upgrading libc6-lse breaks on systems it is in use

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912652] Re: Upgrading libc6-lse breaks on systems it is in use

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912652

Title:
  Upgrading libc6-lse breaks on systems it is in use

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912652] Re: Upgrading libc6-lse breaks on systems it is in use

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912652

Title:
  Upgrading libc6-lse breaks on systems it is in use

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926183] Re: 'ua fix' tells me to reboot with inaccurate message

[Chad Smith]

Bionic Focal, Groovy and Hirsute test runs:

Test procedure: 
1. install u-a-tools from -proposed pocket using cloud-init
2. touch external reboot-required flag file to simulate a system which already 
needs a reboot from an unrelated package install.
3. run ua fix on an issue that will not install any packages
4. confirm ua tooling doesn't report reboot required.
5. Expect SUCCESS if no reboot suggested FAILURE otherwise

TLDR: All SUCCESS msgs, no reboot required messaging if ua fix hasn't
installing debs.


 test script ==

#!/bin/bash
set -e


for release in bionic focal groovy hirsute; do 
  echo "=== START $release "

  name=test-sru-1926183-$release
  case "${release}" in
  hirsute) lxc exec $name apt install samba; issue="CVE-2021-20254";;
  *) issue="CVE-2020-8285";;
  esac
  lxc stop $name || true
  lxc delete $name || true
  lxc launch ubuntu-daily:$release $name -c user.user-data="$( cat 
proposed-$release.yaml )"
  sleep 3;
  lxc exec $name -- cloud-init status --wait --long
  lxc exec $name -- ua version
  echo "== Check ua tools 27.0 ="
  lxc exec $name -- apt policy ubuntu-advantage-tools
  lxc exec $name -- apt install ${downgrade}
  lxc exec $name -- touch /var/run/reboot-required
  echo "== Check no reboot required message on NOOP "
  MSG=`lxc exec $name -- ua fix $issue`
  echo $MSG
  echo $MSG| grep -q reboot && echo "FAILURE: reboot required message found 
when no pkg changes made" || echo "SUCCESS: no reboot required message"
  echo "=== END $release "
done



=== START bionic 
Creating test-sru-1926183-bionic
Starting test-sru-1926183-bionic
..
status: done
time: Fri, 30 Apr 2021 23:26:23 +
detail:
DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]
27.0~18.04.1
== Check ua tools 27.0 =
ubuntu-advantage-tools:
  Installed: 27.0~18.04.1
  Candidate: 27.0~18.04.1
  Version table:
 *** 27.0~18.04.1 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 17 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
== Check no reboot required message on NOOP 
CVE-2020-8285: curl vulnerabilities https://ubuntu.com/security/CVE-2020-8285 1 
affected package is installed: curl (1/1) curl: A fix is available in Ubuntu 
standard updates. The update is already installed. ✔ CVE-2020-8285 is resolved.
SUCCESS: no reboot required message
=== END bionic 
=== START focal 
Creating test-sru-1926183-focal
Starting test-sru-1926183-focal

status: done
time: Fri, 30 Apr 2021 23:27:07 +
detail:
DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]
27.0~20.04.1
== Check ua tools 27.0 =
ubuntu-advantage-tools:
  Installed: 27.0~20.04.1
  Candidate: 27.0~20.04.1
  Version table:
 *** 27.0~20.04.1 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 20.3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 22 not upgraded.
== Check no reboot required message on NOOP 
CVE-2020-8285: curl vulnerabilities https://ubuntu.com/security/CVE-2020-8285 1 
affected package is installed: curl (1/1) curl: A fix is available in Ubuntu 
standard updates. The update is already installed. ✔ CVE-2020-8285 is resolved.
SUCCESS: no reboot required message
=== END focal 
=== START groovy 
Creating test-sru-1926183-groovy
Starting test-sru-1926183-groovy
.
status: done
time: Fri, 30 Apr 2021 23:27:48 +
detail:
DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]
27.0~20.10.1
== Check ua tools 27.0 =
ubuntu-advantage-tools:
  Installed: 27.0~20.10.1
  Candidate: 27.0~20.10.1
  Version table:
 *** 27.0~20.10.1 500
500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 24.4 500
500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
Reading package lists... Done
Building dependency tree   
Reading state 

[Bug 1926183] Re: 'ua fix' tells me to reboot with inaccurate message

[Chad Smith]

sample cloud-config setting up proposed-bionic.yaml

** Attachment added: "proposed-bionic.yaml"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926183/+attachment/5494004/+files/proposed-bionic.yaml

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926183

Title:
  'ua fix' tells me to reboot with inaccurate message

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926184

Title:
  locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926184

Title:
  locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926184

Title:
  locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926184

Title:
  locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926184

Title:
  locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926184

Title:
  locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924809] Re: apt 2.0.5 in focal causes autopkgtest failures for update-manager

[Launchpad Bug Tracker]

This bug was fixed in the package update-manager - 1:21.10.1

---
update-manager (1:21.10.1) impish; urgency=medium

  * UpdateManager/Core/MetaRelease.py: use -proposed in the variable which
corresponds to it.
  * debian/control: drop the build-dep on apt-clone which was missed during
the separtion of u-r-u and update-manager.

 -- Brian Murray   Wed, 28 Apr 2021 12:37:49 -0700

** Changed in: update-manager (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924809

Title:
  apt 2.0.5 in focal causes autopkgtest failures for update-manager

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs

[Seth Arnold]

Hello Dan and Matthew, thanks for working on this. I gave the debdiffs a
look, skimmed through openssl changes, and don't see any reason to not
do this. There *are* larger changes to that function in
https://github.com/openssl/openssl/commit/1e41dadfa7b9f792ed0f4714a3d3d36f070cf30e
-- but it's a fairly invasive change, and I'm not recommending or
suggesting we take it instead. It'd be nice though if someone could
double-check the certs in question against a build that uses this newer
commit and make sure that we're not backporting a very short-lived
functional change.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926254

Title:
  x509 Certificate verification fails when
  basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922439] Re: X hangs after wake on Mobility Radeon x1400

[Boris Gjenero]

Wake worked with kernel 5.11.0-16-generic. So, I guess this is fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922439

Title:
  X hangs after wake on Mobility Radeon x1400

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922443] Re: Lxdm black screen after Ubuntu 21.04 upgrade

[Boris Gjenero]

The problem seems to be /usr/lib/lxdm/lxdm-greeter-gtk crashing at
g_key_file_load_from_file(). Also, lxappearance crashes similarly. This
may be related: https://gitlab.gnome.org/GNOME/glib/-/issues/2361 . But
the crash seems to be triggered by plasma.desktop and twm.desktop in
/usr/share/xsessions. In both of those, the Name[whatever]= and
Comment[whatever]= lines cause the crash. Yet xfce.desktop works with
such lines.

/usr/lib/lxdm/lxdm-greeter-gdk does work but seems lacking in features.

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2361
   https://gitlab.gnome.org/GNOME/glib/-/issues/2361

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922443

Title:
  Lxdm black screen after Ubuntu 21.04 upgrade

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913851] Re: pam_winbind should reject disabled users

[John Runyon]

Hi,

My concern specifically centers around SSH key auth, but in more general
terms, Ubuntu makes a distinction between an account being locked, and a
password being locked. So far as I can tell, Samba/AD do not make that
distinction, but in any case the operation 'samba-tool user disable
' is described as disabling a "user". However, it does not
disable a user in the same sense as other tools do. For example, 'passwd
-l ' will disable password login, but not other ways to log in
to a user account. 'usermod -e 1 ' however will disable other
methods:

$ ssh test@foo echo yay
yay

# passwd -l test
$ ssh test@foo echo yay
yay

# usermod -e 1 test
$ ssh t...@private.simplynuc.com echo yay
Your account has expired; please contact your system administrator
Connection closed by ...

(This last case is rejected by pam_unix at the account stage:
"pam_unix(sshd:account): account test has expired (account expired)")

IMHO, the account stage of pam_winbind should do the same for disabled
users.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1913851

Title:
  pam_winbind should reject disabled users

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913851] Re: pam_winbind should reject disabled users

[John Runyon]

(To clarify my first paragraph: 'samba-tool user disable' has a similar
effect to 'passwd -l', but the phraseology and description from --help,
as well as the phraseology in the Microsoft AD Users & Computers tool,
imply that it should have a similar effect to 'usermod -e 1')

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1913851

Title:
  pam_winbind should reject disabled users

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926819] [NEW] Empty MOTD on update-to-date focal systems (includes fix)

[Aaron Thompson]

Public bug reported:

Starting with update-notifier-common 3.192.30.7 (focal), my up-to-date
systems are showing this MOTD on login:

Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-72-generic x86_64)


user@host:~$


I've attached a patch that fixes this issue and adds more test cases.

** Affects: update-notifier (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: 
"0001-apt_check.py-Fix-empty-output-in-the-no-ESM-up-to-da.patch"
   
https://bugs.launchpad.net/bugs/1926819/+attachment/5493997/+files/0001-apt_check.py-Fix-empty-output-in-the-no-ESM-up-to-da.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926819

Title:
  Empty MOTD on update-to-date focal systems (includes fix)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926527] Re: "Power off" dialog appears when any three keyboard keys are pressed quickly

[Alex Hung]

It is possible udev rules are broken. You might be able to identify
source of this power button events by checking keyboard scancode (with
evtest) and/or workaround this by removing the power button assignment
or assigning it to something else

== get scancode ==
 * run "sudo apt install evtes"
 * run "evtest" and select your keyboard
 * try to duplicate your issue
  * identify the trigger of the power button

== Modify keymap ==
 * cd /lib/udev/hwdb.d/
 * edit keymap file (60-keyboard.hwdb)
 * add a change, ex KEYBOARD_KEY_81=f20 # mic mute
 * run "sudo udevadm hwdb --update"
 * reboot


There are some online examples for modifying hwdb files such as 
https://askubuntu.com/questions/499252/my-custom-udev-hwdb-rule-doesnt-work

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926527

Title:
  "Power off" dialog appears when any three keyboard keys are pressed
  quickly

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04

[Daniel Mulholland]

** Description changed:

- This morning I upgraded to Ubuntu 21.04.
+ This morning I upgraded to Kubuntu 21.04.
  
  I use two external monitors connected to my Dell XPS laptop via a Dell
  WD19 dock.
  
  Post-upgrade the monitors and also network functionality through the
  dock appear to have completely stopped functioning.
  
  When the dock is plugged in and the computer is booted the monitors do not 
enable.
  When the dock is not plugged in the computer boots normally.
  
  When I look at the dmesg output there appears to be some notable errors
  when I plug the dock in:
  
  [  516.173451] xhci_hcd :39:00.0: xHCI host controller not responding, 
assume dead
  [  516.207480] xhci_hcd :39:00.0: HC died; cleaning up
  [  521.313422] pcieport :02:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
  [  555.140320] xhci_hcd :39:00.0: xHCI host controller not responding, 
assume dead
  [  555.140343] xhci_hcd :39:00.0: HC died; cleaning up
  [  560.291086] pcieport :02:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
  [  850.385934] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  850.499763] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  851.717630] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  851.815190] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  856.231021] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  856.301269] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  856.320487] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  856.343208] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun
  [  856.382831] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  860.704920] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  860.765138] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  860.894454] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  860.965337] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  861.115198] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  861.182111] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  866.232326] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  866.351715] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  866.454536] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  866.473097] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  866.534697] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  
  With the dock plugged in:
  
  * neither monitor displays although they are present under display 
configuration
  * since my laptop screen is not usually on if both monitors are present on 
the dock the immediate result was no display at all under the dock was detached
  * network connectivity is not established although the network device appears 
under networks
  
  Unfortunately I lack the skills to diagnose this further without
  assistance or to install a more recent kernel to see if it is resolved
  there.
  
  It appears that communications between the laptop and the Dock are not
  going well to my eyes (is this what link training is on Thunderbolt)
  
  I'm happy to provide further information... although in a few days the
  lack of Dock and monitors will be a bit of an issue and I may have to
  roll something back.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  mulhollandd   1940 F pulseaudio
-  /dev/snd/controlC1:  mulhollandd   1940 F pulseaudio
-  /dev/snd/controlC0:  mulhollandd   1940 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  mulhollandd   1940 F pulseaudio
+  /dev/snd/controlC1:  mulhollandd   1940 F pulseaudio
+  /dev/snd/controlC0:  mulhollandd   1940 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat May  1 08:57:26 2021
  InstallationDate: Installed on 2020-06-13 (321 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash 

[Bug 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)

[Harrison Chen]

Update: still affects 21.04 and the above Reddit solution no longer
works for me

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895422

Title:
  Sound card not detected on Dell Latitude 9510 (Realtek ALC711)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926817] [NEW] kube-controller-manager crashes due to 5 duplicate certs in ca.crt

[Alex Zero]

Public bug reported:

On Kubernetes deployments with cert_manager_api enabled, the certificate
container fails to come up because there are five duplicate public
certificates in /etc/kubernetes/certs/ca.crt, this causes the service to
crash:

Apr 30 23:44:21 k8s-prod-24e2ug52zqb4-master-0 bash[153677]: I0430 
23:44:21.416326   1 job_controller.go:144] Starting job controller
Apr 30 23:44:21 k8s-prod-24e2ug52zqb4-master-0 bash[153677]: I0430 
23:44:21.416470   1 shared_informer.go:223] Waiting for caches to sync for 
job
Apr 30 23:44:21 k8s-prod-24e2ug52zqb4-master-0 bash[153677]: I0430 
23:44:21.429543   1 dynamic_serving_content.go:111] Loaded a new cert/key 
pair for 
"csr-controller::/etc/kubernetes/certs/ca.crt::/etc/kubernetes/certs/ca.key"
Apr 30 23:44:21 k8s-prod-24e2ug52zqb4-master-0 bash[153677]: E0430 
23:44:21.430347   1 controllermanager.go:521] Error starting "csrsigning"
Apr 30 23:44:21 k8s-prod-24e2ug52zqb4-master-0 bash[153677]: F0430 
23:44:21.430532   1 controllermanager.go:235] error starting controllers: 
failed to start certificate controller: error reading CA cert file 
"csr-controller::/etc/kubernetes/certs/ca.crt::/etc/kubernetes/certs/ca.key": 
expected 1 certificate, found 5
Apr 30 23:44:21 k8s-prod-24e2ug52zqb4-master-0 podman[153677]: 2021-04-30 
23:44:21.470875534 + UTC m=+49.221008858 container died 
df7295074c1b7cbef19a79e6c8741b9dfbcb4fd608863978fb5924de8946ba05 
(image=k8s.gcr.io/hyperkube:v1.18.2, name=kube-controller-manager)
Apr 30 23:44:21 k8s-prod-24e2ug52zqb4-master-0 systemd[1]: 
kube-controller-manager.service: Main process exited, code=exited, 
status=255/EXCEPTION
Apr 30 23:44:21 k8s-prod-24e2ug52zqb4-master-0 systemd[1]: 
kube-controller-manager.service: Failed with result 'exit-code'.
Apr 30 23:44:31 k8s-prod-24e2ug52zqb4-master-0 systemd[1]: 
kube-controller-manager.service: Scheduled restart job, restart counter is at 
456.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926817

Title:
  kube-controller-manager crashes due to 5 duplicate certs in ca.crt

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926011] Re: groovy / focal fwupd sbat support

[Dimitri John Ledkov]

dbxupdate got published on uefi.org website. I would be happy to sponsor
the fwupd debdiff for groovy now. To unblock roll-outs of the new shim.

The split to have standalone fwupd-efi should happen as it is a good
idea - it will enable shipping newer fwupd user-space tooling in the
snap / OEM archives / PPAs at an accelerated pace without impacting
signed UEFI binary. But at least we don't need to rush the split.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926011

Title:
  groovy / focal fwupd sbat support

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924685] Re: No sound output/input available after installing 21.04

[Herczeg Zsolt]

Haven't try the headset microphone input, but I believe it may be a
separate bug cause i've seen error reports for that on 20.04/20.10
versions with DKMS drivees. I'll try the headset input as soon as I get
my hands on a 4-wire headset and check the status on my machine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924685

Title:
  No sound output/input available after installing 21.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926816] [NEW] Computer does not shut down

[PJSingh5000]

Public bug reported:

In Ubuntu 21.04, when I shut down, my laptop never actually shuts down.

I see a black screen, the laptop stays on, and the fans spin up.

The computer will stay in this state all night.

I then have to press and hold the power button to shut down the device.

I am using the default kernel, 5.11.0-16-generic.
I am also using the Nvidia driver (nvidia-driver-460, version 
460.73.01-0ubuntu1) with XOrg.

This was not an issue for prior releases of Ubuntu on this machine. For
example, Ubuntu 20.04 does not have this problem.

I see the following messages in the journalctl log (attached) for
gdm.service, which I think may be contributing to this issue:

gdm.service: Main process exited, code=exited, status=1/FAILURE
gdm.service: Failed with result 'exit-code'.
Stopped GNOME Display Manager.
gdm.service: Triggering OnFailure= dependencies.
Requested transaction contradicts existing jobs: Transaction for 
plymouth-quit.service/start is destructive (umount.target has 'start' job 
queued, but 'stop' is included in transaction).
gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for 
plymouth-quit.service/start is destructive (umount.target has 'start' job 
queued, but 'stop' is included in transaction).

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gdm3 3.38.2.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME
Date: Fri Apr 30 19:09:43 2021
InstallationDate: Installed on 2021-04-28 (2 days ago)
InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" 
(20210427)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute

** Attachment added: "Journalctl log from prior unsuccessful shutdown."
   
https://bugs.launchpad.net/bugs/1926816/+attachment/5493993/+files/journal_ctl_2021-04-30-02.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926816

Title:
  Computer does not shut down

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926686] Re: lightdm segfaults

[Gunnar Hjalmarsson]

OTOH... If you haven't enabled the guest session feature, the difference
between the lightdm versions in focal-release and focal-proposed can't
possibly cause the segfault.

Did you possibly install everything from focal-proposed? In that case
you may be actually 'testing' this upload:

https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.3

After all the error message includes "error 4 in libc-2.31.so".

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926686

Title:
  lightdm segfaults

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926815] Re: gdb 'call' / 'print' commands don't work properly when attaching to R

[Kevin Ushey]

** Summary changed:

- gdb doesn't work properly when attaching to R
+ gdb 'call' / 'print' commands don't work properly when attaching to R

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926815

Title:
  gdb 'call' / 'print' commands don't work properly when attaching to R

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925010] Re: shim-signed 15.4 does not boot on EFI 1.10 systems

[MikeMecanic]

This new shim package fixes secure boot when booting an unsigned Kernel.
Impish Indru Kubuntu 21.10. Thanks for the fix

2021-04-30 18:34:28 upgrade shim-signed:amd64 1.46+15.4-0ubuntu1
1.47+15.4-0ubuntu2

mokutil --sb
SecureBoot enabled
SecureBoot validation is disabled in shim
uname -srm
Linux 5.12.0-051200daily20210430-generic x86_64

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010

Title:
  shim-signed 15.4 does not boot on EFI 1.10 systems

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913851] Re: pam_winbind should reject disabled users

[Sergio Durigan Junior]

Thanks for the bug report and apologies for the delay in getting back to
you.

I configured a Bionic VM acting as an AD member, joined the AD, and then
disabled one of the users in the AD DC.  I noticed that issuing a "login
inva...@ad1.example.com" correctly displays the following message:

# login inva...@ad1.example.com
Password: 
Your account has been locked. Please contact your System administrator

Login incorrect
#

I'm afraid I don't fully understand what you meant by "which means that
they can still be logged into through other credentials."  What
credentials are you referring to here?  If you could provide steps to
reproduce what you meant, that would be very helpful.

Thank you.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1913851

Title:
  pam_winbind should reject disabled users

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926686] Re: lightdm segfaults

[Gunnar Hjalmarsson]

On 2021-04-30 23:59, Robert Dinse wrote:
> I was under the impression that the purpose of proposed was to test
> and get feedback and fix such things before it entered mainstream.

It is, but such testing happens normally via dedicated bug reports. As
regards the current lightdm version in -proposed that is bug #1921655.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926686

Title:
  lightdm segfaults

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926815] Re: gdb doesn't work properly when attaching to R

[Kevin Ushey]

In addition, I get a segfault if I use a single-quoted string rather
than a double-quoted string. (My understanding is that single-quoted
strings are normally used to reference symbols, so this should be an
error but not a crash)

$ /usr/bin/gdb -batch -p $(pgrep -nx R) -ex "print (char*) getenv('oops')"
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f69b4c870da in select () from /usr/lib/x86_64-linux-gnu/libc.so.6
Aborted (core dumped)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926815

Title:
  gdb doesn't work properly when attaching to R

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926815] [NEW] gdb doesn't work properly when attaching to R

[Kevin Ushey]

Public bug reported:

Sorry for the somewhat weird / vague title; hopefully the rest of this
issue will make it more concrete ...

First, to set the stage; gdb and R both installed from apt repositories:

$ /usr/bin/gdb --version
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

$ /usr/bin/R --version
R version 4.0.5 (2021-03-31) -- "Shake and Throw"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under the terms of the
GNU General Public License versions 2 or 3.
For more information about these matters see
https://www.gnu.org/licenses/.

Now, I can use gdb in batch mode to introspect a bash process; e.g.
print the SHELL environment variable:

$ /usr/bin/gdb -batch -p $(pgrep -nx bash) -ex 'print (char*) getenv("SHELL")'
0x7f5623d8c1db in __pselect (nfds=1, readfds=0x7ffdaeda52f0, writefds=0x0, 
exceptfds=0x0, timeout=, sigmask=0x5615fe778140 
<_rl_orig_sigset>) at ../sysdeps/unix/sysv/linux/pselect.c:48
48  ../sysdeps/unix/sysv/linux/pselect.c: No such file or directory.
$1 = 0x5615ffc825d0 "/bin/bash"
[Inferior 1 (process 640102) detached]


But, if I try to do the same with a running R process, I see:

$ R -s -e "Sys.sleep(100)" &
[1] 643585

$ /usr/bin/gdb -batch -p $(pgrep -nx R) -ex 'print (char*) getenv("SHELL")'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f47944050da in select () from /usr/lib/x86_64-linux-gnu/libc.so.6
Invalid character '"' in expression.
[Inferior 1 (process 643585) detached]


Note the very confusing 'Invalid character '"' in expression.' error, implying 
that gdb was for some reason unable to handle the double-quoted string passed 
to getenv().

I cannot reproduce this in a version of gdb 9.2 built from sources
locally; e.g.

$ gdb --version
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

$ gdb -batch -p $(pgrep -nx R) -ex 'print (char*) getenv("SHELL")'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fba31ad60da in select () from /usr/lib/x86_64-linux-gnu/libc.so.6
$1 = 0x7fff4dc9adfe "/bin/bash"
[Inferior 1 (process 701827) detached]

So it seems like something specifically is broken in the version of GDB
packaged for Ubuntu 20.04.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926815

Title:
  gdb doesn't work properly when attaching to R

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847479] Re: update-manager window expands off-screen (which effectively stops distribution upgrade)

[arQon]

Just happened with 21.04 (on a pi4), albeit with a minor variation: this time, 
the suggestion was "change the home directory of user irc?" (the pi was a 
server install originally, with the desktop packages added later).
When I clicked "Help" it resized the window to fill the desktop, and I can JUST 
see what I'm guessing is the top of a "Close" button at the very bottom of the 
screen.

Once again, the window CANNOT be moved, and CANNOT be resized vertically
(although it CAN be resized horizontally). IDK what toolkit the
installer is using and how it manages to apparently default to being
this broken, but the fix is the same as it was 18 months ago: if the
layout is going to keep breaking like this - and empirically, it
obviously is - then we need to stop disabling basic functionality like
resize so the user can at least work around it!

Cheers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847479

Title:
  update-manager window expands off-screen (which effectively stops
  distribution upgrade)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le

[Kelsey Skunberg]

** Tags added: sru-20210412

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867570

Title:
  reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on
  ppc64le

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881643] Re: pmtu.sh net selftest fail with PMTU dst likely leaked (can't delete veth device in a timely manner, PMTU dst likely leaked)

[Kelsey Skunberg]

** Tags added: sru-20210412

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881643

Title:
  pmtu.sh net selftest fail with PMTU dst likely leaked (can't delete
  veth device in a timely manner, PMTU dst likely leaked)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881643/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926298] Re: Segfault added in the recent changes

[Dan Bungert]

Requesting sponsorship for SRU of hirsute-update-
notifier-2-3.192.40.2.debdiff

** Patch added: "hirsute-update-notifier-2-3.192.40.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1926298/+attachment/5493992/+files/hirsute-update-notifier-2-3.192.40.2.debdiff

** Changed in: update-notifier (Ubuntu Hirsute)
   Status: New => Confirmed

** Tags added: patch

** Changed in: update-notifier (Ubuntu Hirsute)
 Assignee: Dan Bungert (dbungert) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926298

Title:
  Segfault added in the recent changes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926298] Re: Segfault added in the recent changes

[Dan Bungert]

** Description changed:

  [Impact]
  
  On hirsute/impish, update-notifier can crash when attempting to run hooks.
  This issue is the #2 crash on update-notifier in hirsute, presently (and
  maybe some of the others).  I would call this a severe regression.
+ 
+ In the crash cases, cleanup steps are running on an uninitialized
+ variable.  The fix resolves this by ensuring the relevant variable is
+ initialized.
  
  [Test Case]
  
  Create a file 'bug'
  
  'Name: bug
  Priority: Low
  Command: "/bin/true"
  DisplayIf: /bin/true
  Description: update notifier bug'
  
  and copy it to /var/lib/update-notifier/user.d
  
  [Where problems could occur]
  
  This is not the most absolute minimal version of this fix.
  If the minimal version of the fix is desired, I can provide that, which
  should be a +2/-2 diff.  (I don't want to confuse the current proposal.)
  The fix changeset being proposed includes other glib usage improvements
  which sound really good from a maintainability perspective and may even
  close other yet unknown bugs but add their own risk of regressions if
  said maintainability was not done correctly.
  
  The original idea was to address a problem where we offer to run a
  command, and the user would click the button to do so, but then nothing
  would happen because the command wasn't on the system.  If the parsing
  of this command is invalid, then valid hooks may be filtered.
  
  It's possible for the command to contain arguments, and to be quoted (or
  not), or to not be the full command path.  Variables for such testing
  include:
  * rely on path lookup or fully qualified path supplied in command
  * quoted or unquoted or mixed quotes (quote the command and args
-   outside of the quotes)
+   outside of the quotes)
  * arguments or no
  * presence or absence of actual command
  See attached tarball for the resulting 20 tests (4 redundant tests pruned).
  All the 'present' hooks are valid, 'absent' hooks should be skipped.
  
  In an attempt to stave off further memory safety problems I've analyzed
  this version with valgrind.  valgrind is able to observe several
  problems in the unfixed version, whereas the fixed version only
  complains about some items in glib that appear to be unrelated to this
  change.
  
  I've got some unit test code as well but haven't integrated that yet to
  the update-notifier codebase.
  
  [Original Bug Report Description]
  
  The issue is new using
  
https://code.launchpad.net/~dbungert/update-notifier/+git/update-notifier/+merge/397367
  , the previous revision didn't have the issue
  
  * Create a file 'bug'
  
  'Name: bug
  Priority: Low
  Command: "/bin/true"
  DisplayIf: /bin/true
  Description: update notifier bug'
  
  and copy it to /var/lib/update-notifier/user.d
  
  ->  update-notifier segfaults
  
  (gdb) bt
  #0  0x7718c769 in __GI___libc_free (mem=0x555aa7f9) at 
malloc.c:3288
  #1  0x77365215 in g_strfreev (str_array=) at 
../../../glib/gstrfuncs.c:2553
  #2  g_strfreev (str_array=0x555d9e00) at ../../../glib/gstrfuncs.c:2546
  #3  0xdd2d in hook_command_exists (cmd=0x55702600 
"\"/usr/bin/eog\"") at hooks.c:137
  #4  0xfd6e in is_hook_relevant (hook_file=0x55829e7b 
"apt-file.update-notifier")
  at hooks.c:717
  #5  0xffb1 in check_update_hooks (ta=0x556c9a20) at 
hooks.c:781
  #6  0x55560715 in hook_tray_icon_init (ta=0x556c9a20) at 
hooks.c:969
  #7  0xcd77 in tray_icons_init (un=0x5562c3e0,
  
  It seems likely to be the error on top of the weekly report for hirsute
  but that's missing a stacktrace
  
  One comment in addition on the change there, was the env split + iterate
  over pathdirs basically a re-implementation of
  
https://developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-find-program-in-path
  ? If there is particular reason to do that I would recommend just using
  the glib function instead (which might also fix the issue as a side
  effect, I didn't check)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926298

Title:
  Segfault added in the recent changes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926811] [NEW] After upgrading to 20.04 applications no longer launch from overview

[Gabriel]

Public bug reported:

System info:

$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

$ apt-cache policy gnome
gnome:
  Installed: (none)
  Candidate: 1:3.30+2
  Version table:
 1:3.30+2 500
500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/universe amd64 
Packages

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.36.7-0ubuntu0.20.04.1
  Candidate: 3.36.7-0ubuntu0.20.04.1
  Version table:
 *** 3.36.7-0ubuntu0.20.04.1 500
500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.36.4-1ubuntu1~20.04.2 500
500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-security/main amd64 
Packages
 3.36.1-5ubuntu1 500
500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/main amd64 Packages

$ apt-cache policy ubuntu-desktop
ubuntu-desktop:
  Installed: 1.450.2
  Candidate: 1.450.2
  Version table:
 *** 1.450.2 500
500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.450 500
500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/main amd64 Packages


I upgraded my system from 19.10/Eoan to 20.04 and when I go to the
overview (Activities menu/hotspot), search an application and click on
it it no longer launches. If I right click on it and select "Add to
favorites" and then go to the dock and click on it it launches fine.

I have not been able to find how to debug this issue but it is very
annoying. Someone said it may have to do with the way .desktop files are
handled now.

Can someone please help?

Thank you!

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

** Package changed: gnome-shell-extension-desktop-icons (Ubuntu) =>
gnome-shell (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926811

Title:
  After upgrading to 20.04 applications no longer launch from overview

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835644] Re: CRL files are not accessible for the Verify CRL options

[Shuhao]

This seems to also happen when you specify any cert inline in an
imported openvpn config.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835644

Title:
  CRL files are not accessible for the Verify CRL options

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926298] Re: Segfault added in the recent changes

[Dan Bungert]

** Description changed:

  [Impact]
  
- On Hirsute/Impish, update-notifier can crash when attempting to run
- hooks.
+ On hirsute/impish, update-notifier can crash when attempting to run hooks.
+ This issue is the #2 crash on update-notifier in hirsute, presently (and
+ maybe some of the others).  I would call this a severe regression.
  
  [Test Case]
  
  Create a file 'bug'
  
  'Name: bug
  Priority: Low
  Command: "/bin/true"
  DisplayIf: /bin/true
  Description: update notifier bug'
  
  and copy it to /var/lib/update-notifier/user.d
  
  [Where problems could occur]
  
  This is not the most absolute minimal version of this fix.
- If the minimal version of the fix is desired, I can provide that, which 
should be a +2/-2 diff.
- The fix changeset includes other glib usage improvements which sound good 
from a maintainability perspective and may even close other yet unknown bugs 
but add their own risk of regressions if said maintainability was not done 
correctly.
+ If the minimal version of the fix is desired, I can provide that, which
+ should be a +2/-2 diff.  (I don't want to confuse the current proposal.)
+ The fix changeset being proposed includes other glib usage improvements
+ which sound really good from a maintainability perspective and may even
+ close other yet unknown bugs but add their own risk of regressions if
+ said maintainability was not done correctly.
+ 
+ The original idea was to address a problem where we offer to run a
+ command, and the user would click the button to do so, but then nothing
+ would happen because the command wasn't on the system.  If the parsing
+ of this command is invalid, then valid hooks may be filtered.
+ 
+ It's possible for the command to contain arguments, and to be quoted (or
+ not), or to not be the full command path.  Variables for such testing
+ include:
+ * rely on path lookup or fully qualified path supplied in command
+ * quoted or unquoted or mixed quotes (quote the command and args
+   outside of the quotes)
+ * arguments or no
+ * presence or absence of actual command
+ See attached tarball for the resulting 20 tests (4 redundant tests pruned).
+ All the 'present' hooks are valid, 'absent' hooks should be skipped.
+ 
+ In an attempt to stave off further memory safety problems I've analyzed
+ this version with valgrind.  valgrind is able to observe several
+ problems in the unfixed version, whereas the fixed version only
+ complains about some items in glib that appear to be unrelated to this
+ change.
+ 
+ I've got some unit test code as well but haven't integrated that yet to
+ the update-notifier codebase.
  
  [Original Bug Report Description]
  
- The issue is new using https://code.launchpad.net/~dbungert/update-
- notifier/+git/update-notifier/+merge/397367 , the previous revision
- didn't have the issue
+ The issue is new using
+ 
https://code.launchpad.net/~dbungert/update-notifier/+git/update-notifier/+merge/397367
+ , the previous revision didn't have the issue
  
  * Create a file 'bug'
  
  'Name: bug
  Priority: Low
  Command: "/bin/true"
  DisplayIf: /bin/true
  Description: update notifier bug'
  
  and copy it to /var/lib/update-notifier/user.d
  
  ->  update-notifier segfaults
  
  (gdb) bt
  #0  0x7718c769 in __GI___libc_free (mem=0x555aa7f9) at 
malloc.c:3288
  #1  0x77365215 in g_strfreev (str_array=) at 
../../../glib/gstrfuncs.c:2553
  #2  g_strfreev (str_array=0x555d9e00) at ../../../glib/gstrfuncs.c:2546
  #3  0xdd2d in hook_command_exists (cmd=0x55702600 
"\"/usr/bin/eog\"") at hooks.c:137
  #4  0xfd6e in is_hook_relevant (hook_file=0x55829e7b 
"apt-file.update-notifier")
  at hooks.c:717
  #5  0xffb1 in check_update_hooks (ta=0x556c9a20) at 
hooks.c:781
  #6  0x55560715 in hook_tray_icon_init (ta=0x556c9a20) at 
hooks.c:969
  #7  0xcd77 in tray_icons_init (un=0x5562c3e0,
  
  It seems likely to be the error on top of the weekly report for hirsute
  but that's missing a stacktrace
  
  One comment in addition on the change there, was the env split + iterate
  over pathdirs basically a re-implementation of
- https://developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-
- Functions.html#g-find-program-in-path ? If there is particular reason to
- do that I would recommend just using the glib function instead (which
- might also fix the issue as a side effect, I didn't check)
+ 
https://developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-find-program-in-path
+ ? If there is particular reason to do that I would recommend just using
+ the glib function instead (which might also fix the issue as a side
+ effect, I didn't check)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926298

Title:
  Segfault added in the recent changes

To manage notifications about this bug go to:

[Bug 1914279] Re: linux from security may force reboots without complete dkms modules

[Dimitri John Ledkov]

debdiffs are on https://bileto.ubuntu.com/#/ticket/4543

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914279] Re: linux from security may force reboots without complete dkms modules

[Dimitri John Ledkov]

I've rebuilt all the packages mentioned above in bileto ppa against
security pocket and pushed them to focal-proposed queue, ready for sru
review and accept.

All, but openafs which ftbfs now, and will need to be fixed up for v5.11
anyway. So it will be rebuild in security pocket with v5.11 fixes later.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926298] Re: Segfault added in the recent changes

[Dan Bungert]

Test hooks to cover the cases introduced by the original change.

** Attachment added: "tests.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1926298/+attachment/5493991/+files/tests.tgz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926298

Title:
  Segfault added in the recent changes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926686] Re: lightdm segfaults

[Robert Dinse]

Ok, I've installed the old version to see if this occurs, this was not a
frequent problem with this version so I'm unlikely to have an answer
overnight.  However, I was under the impression that the purpose of
proposed was to test and get feedback and fix such things before it
entered mainstream.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926686

Title:
  lightdm segfaults

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923684] Re: Parallel builds for monero are running out of memory

[William Wilson]

Seb, The builds were failing in the launchpad build farm. The official
package builds are failing on multiple architectures with various "out
of memory" errors, and preventing this package from migrating out of
-proposed. Debian builds don't seem to be affected, so I would think
they wouldn't want to slow down their builds. If you think they would
accept the patch anyway I would be happy to forward it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923684

Title:
  Parallel builds for monero are running out of memory

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926809] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926809

Title:
  WD19 dock stops working in Ubuntu 21.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04

[Daniel Mulholland]

It may be that this (fixed) bug is related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903969

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926809

Title:
  WD19 dock stops working in Ubuntu 21.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04

[Daniel Mulholland]

When I boot to use an older kernel, initially things appear no better --
no monitors except the laptop and after logging into Kubuntu no monitors
at all.

After removing the USB-C connection and plugging it back in again both
monitors come back, headphones work but the wired network connection
does not work.

Here's some dmesg output for this:

mulhollandd@mulhollandd-XPS-13-9360:~$ sudo dmesg --level=err
[   95.459529] xhci_hcd :39:00.0: xHCI host controller not responding, 
assume dead
[   95.459573] xhci_hcd :39:00.0: HC died; cleaning up
[  100.553294] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[  100.553301] pcieport :00:1c.0: AER:   device [8086:9d10] error 
status/mask=0001/2000
[  100.553306] pcieport :00:1c.0: AER:[ 0] RxErr 
[  100.630562] pcieport :02:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
mulhollandd@mulhollandd-XPS-13-9360:~$ # no monitors but when I unplug and 
replug both monitors come back
mulhollandd@mulhollandd-XPS-13-9360:~$ # now a new dmesg output
mulhollandd@mulhollandd-XPS-13-9360:~$ sudo dmesg --level=err
[   95.459529] xhci_hcd :39:00.0: xHCI host controller not responding, 
assume dead
[   95.459573] xhci_hcd :39:00.0: HC died; cleaning up
[  100.553294] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[  100.553301] pcieport :00:1c.0: AER:   device [8086:9d10] error 
status/mask=0001/2000
[  100.553306] pcieport :00:1c.0: AER:[ 0] RxErr 
[  100.630562] pcieport :02:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
[  158.228726] pcieport :00:1c.4: AER: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, (Transmitter ID)
[  158.228734] pcieport :00:1c.4: AER:   device [8086:9d14] error 
status/mask=1000/2000
[  158.228739] pcieport :00:1c.4: AER:[12] Timeout   
mulhollandd@mulhollandd-XPS-13-9360:~$ # we are on an older kernel now
mulhollandd@mulhollandd-XPS-13-9360:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 21.04
Release:21.04
Codename:   hirsute
mulhollandd@mulhollandd-XPS-13-9360:~$ uname -a
Linux mulhollandd-XPS-13-9360 5.8.0-50-generic #56-Ubuntu SMP Mon Apr 12 
17:18:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
mulhollandd@mulhollandd-XPS-13-9360:~$ 

I should note that the AER PCIe Bus Errors have been present I think for
many years and versions of Ubuntu so I think they are unrelated. However
the power state transition from "D3cold to D0 (config space
inaccessible)" is I think new.

Happy to provide further information.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926809

Title:
  WD19 dock stops working in Ubuntu 21.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926809] [NEW] WD19 dock stops working in Ubuntu 21.04

[Daniel Mulholland]

Public bug reported:

This morning I upgraded to Ubuntu 21.04.

I use two external monitors connected to my Dell XPS laptop via a Dell
WD19 dock.

Post-upgrade the monitors and also network functionality through the
dock appear to have completely stopped functioning.

When the dock is plugged in and the computer is booted the monitors do not 
enable.
When the dock is not plugged in the computer boots normally.

When I look at the dmesg output there appears to be some notable errors
when I plug the dock in:

[  516.173451] xhci_hcd :39:00.0: xHCI host controller not responding, 
assume dead
[  516.207480] xhci_hcd :39:00.0: HC died; cleaning up
[  521.313422] pcieport :02:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
[  555.140320] xhci_hcd :39:00.0: xHCI host controller not responding, 
assume dead
[  555.140343] xhci_hcd :39:00.0: HC died; cleaning up
[  560.291086] pcieport :02:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
[  850.385934] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
[  850.499763] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
[  851.717630] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  851.815190] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  856.231021] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
[  856.301269] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
[  856.320487] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  856.343208] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun
[  856.382831] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  860.704920] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  860.765138] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  860.894454] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  860.965337] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  861.115198] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  861.182111] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  866.232326] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
[  866.351715] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  866.454536] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
[  866.473097] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  866.534697] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful

With the dock plugged in:

* neither monitor displays although they are present under display configuration
* since my laptop screen is not usually on if both monitors are present on the 
dock the immediate result was no display at all under the dock was detached
* network connectivity is not established although the network device appears 
under networks

Unfortunately I lack the skills to diagnose this further without
assistance or to install a more recent kernel to see if it is resolved
there.

It appears that communications between the laptop and the Dock are not
going well to my eyes (is this what link training is on Thunderbolt)

I'm happy to provide further information... although in a few days the
lack of Dock and monitors will be a bit of an issue and I may have to
roll something back.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-16-generic 5.11.0-16.17
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  mulhollandd   1940 F pulseaudio
 /dev/snd/controlC1:  mulhollandd   1940 F pulseaudio
 /dev/snd/controlC0:  mulhollandd   1940 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat May  1 08:57:26 2021
InstallationDate: Installed on 2020-06-13 (321 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. XPS 13 9360
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-16-generic N/A
 linux-backports-modules-5.11.0-16-generic  N/A
 linux-firmware 1.197
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-04-30 (0 days ago)
dmi.bios.date: 03/09/2021
dmi.bios.release: 2.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.15.1
dmi.board.name: 0115N5
dmi.board.vendor: Dell Inc.

[Bug 1926661] Re: i think gpu driver isn't working well.

[Shoyayeb Hasan Shafin]

anyone know how to fix this shit?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926661

Title:
  i think gpu driver isn't working well.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04

[Daniel Mulholland]

Some functionality still appears to work correctly -- headphones plugged
into the Dock appear to function.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926809

Title:
  WD19 dock stops working in Ubuntu 21.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921518] Re: OpenSSL "double free" error

[Mahantesh Salimath]

** Attachment added: "Core dump file"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+attachment/5493968/+files/core-curl.32878.localhost.localdomain.1619816112

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921518

Title:
  OpenSSL "double free" error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926808] [NEW] Bionic update: upstream stable patchset 2021-04-30

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2021-04-30

Ported from the following upstream stable releases:
v4.14.228, v4.19.184
v4.14.229, v4.19.185
v4.14.230, v4.19.186
   v4.19.187
v4.14.231, v4.19.188

   from git://git.kernel.org/

net: fec: ptp: avoid register access when ipg clock is disabled
powerpc/4xx: Fix build errors from mfdcr()
atm: eni: dont release is never initialized
atm: lanai: dont run lanai_dev_close if not open
Revert "r8152: adjust the settings about MAC clock speed down for RTL8153"
ixgbe: Fix memleak in ixgbe_configure_clsu32
net: tehuti: fix error return code in bdx_probe()
sun/niu: fix wrong RXMAC_BC_FRM_CNT_COUNT count
gpiolib: acpi: Add missing IRQF_ONESHOT
nfs: fix PNFS_FLEXFILE_LAYOUT Kconfig default
NFS: Correct size calculation for create reply length
net: hisilicon: hns: fix error return code of hns_nic_clear_all_rx_fetch()
net: wan: fix error return code of uhdlc_init()
atm: uPD98402: fix incorrect allocation
atm: idt77252: fix null-ptr-dereference
sparc64: Fix opcode filtering in handling of no fault loads
u64_stats,lockdep: Fix u64_stats_init() vs lockdep
drm/radeon: fix AGP dependency
nfs: we don't support removing system.nfs4_acl
ia64: fix ia64_syscall_get_set_arguments() for break-based syscalls
ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign
squashfs: fix inode lookup sanity checks
squashfs: fix xattr id and id lookup sanity checks
arm64: dts: ls1046a: mark crypto engine dma coherent
arm64: dts: ls1012a: mark crypto engine dma coherent
arm64: dts: ls1043a: mark crypto engine dma coherent
ARM: dts: at91-sama5d27_som1: fix phy address to 7
dm ioctl: fix out of bounds array access when no devices
bus: omap_l3_noc: mark l3 irqs as IRQF_NO_THREAD
libbpf: Fix INSTALL flag order
macvlan: macvlan_count_rx() needs to be aware of preemption
net: dsa: bcm_sf2: Qualify phydev->dev_flags based on port
e1000e: add rtnl_lock() to e1000_reset_task
e1000e: Fix error handling in e1000_set_d0_lplu_state_82571
net/qlcnic: Fix a use after free in qlcnic_83xx_get_minidump_template
ftgmac100: Restart MAC HW once
can: peak_usb: add forgotten supported devices
can: c_can_pci: c_can_pci_remove(): fix use-after-free
can: c_can: move runtime PM enable/disable to c_can_platform
can: m_can: m_can_do_rx_poll(): fix extraneous msg loss warning
mac80211: fix rate mask reset
net: cdc-phonet: fix data-interface release on probe failure
net: stmmac: dwmac-sun8i: Provide TX and RX fifo sizes
drm/msm: fix shutdown hook in case GPU components failed to bind
arm64: kdump: update ppos when reading elfcorehdr
net/mlx5e: Fix error path for ethtool set-priv-flag
RDMA/cxgb4: Fix adapter LE hash errors while destroying ipv6 listening server
ACPI: scan: Rearrange memory allocation in acpi_device_add()
ACPI: scan: Use unique number for instance_no
perf auxtrace: Fix auxtrace queue conflict
scsi: qedi: Fix error return code of qedi_alloc_global_queues()
scsi: mpt3sas: Fix error return code of mpt3sas_base_attach()
locking/mutex: Fix non debug version of mutex_lock_io_nested()
can: dev: Move device back to init netns on owning netns delete
net: sched: validate stab values
net: qrtr: fix a kernel-infoleak in qrtr_recvmsg()
mac80211: fix double free in ibss_leave
ext4: add reclaim checks to xattr code
can: peak_usb: Revert "can: peak_usb: add forgotten supported devices"
block: Suppress uevent for hidden device when removed
netsec: restore phy power state after controller reset
can: flexcan: flexcan_chip_freeze(): fix chip freeze for missing bitrate
dm verity: add root hash pkcs#7 signature verification
x86/mem_encrypt: Correct physical address calculation in __set_clr_pte_enc()
UBUNTU: upstream stable to v4.14.228, v4.19.184
selinux: vsock: Set SID for socket returned by accept()
ipv6: weaken the v4mapped source check
ext4: fix bh ref count on error paths
rpc: fix NULL dereference on kmalloc failure
ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10
ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10
ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on probe
ASoC: es8316: Simplify adc_pga_gain_tlv table
ASoC: cs42l42: Fix mixer volume control
ASoC: cs42l42: Always wait at least 3ms after reset
vhost: Fix vhost_vq_reset()
scsi: st: Fix a use after free in st_open()
scsi: qla2xxx: Fix broken #endif placement
staging: comedi: cb_pcidas: fix request_irq() warn

[Bug 1909830] Re: [USB-Audio - Razer Kraken 7.1 V2, playback] Playback problem | VLC Player works correctly

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909830

Title:
  [USB-Audio - Razer Kraken 7.1 V2, playback] Playback problem | VLC
  Player works correctly

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926802] Re: qt5-default package is missed in 21.04

[Dmitry Shachnev]

Qt 4 was removed, Qt 5 is now default, so that package is no longer
needed.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926802

Title:
  qt5-default package is missed in 21.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1926802/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926799] Re: Multiple issues with zoom in accessibility

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1926799/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926799

Title:
  Multiple issues with zoom in accessibility

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926801] Re: BCM2835 SPI chipselect limit - kernel/driver panic

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1926801/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926801

Title:
   BCM2835 SPI chipselect limit - kernel/driver panic

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926794] Re: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 11.0957:dependency problems - leaving triggers unprocessed

[Ubuntu Foundations Team Bug Bot]

** Attachment removed: "VarLogDistupgradeTermlog.gz"
   
https://bugs.launchpad.net/bugs/1926794/+attachment/5493933/+files/VarLogDistupgradeTermlog.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926794

Title:
  package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade:
  11.0957:dependency problems - leaving triggers unprocessed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926794] Re: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 11.0957:dependency problems - leaving triggers unprocessed

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926794

Title:
  package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade:
  11.0957:dependency problems - leaving triggers unprocessed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920837] Re: apport bugs from official raspi or riscv images are not identified

[William Wilson]

The verification passed for groovy:

ubuntu@ubuntu:~$ apt-cache policy apport
apport:
  Installed: 2.20.11-0ubuntu50.5
  Candidate: 2.20.11-0ubuntu50.6
  Version table:
 2.20.11-0ubuntu50.6 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/main arm64 
Packages
 *** 2.20.11-0ubuntu50.5 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 
Packages
500 http://ports.ubuntu.com/ubuntu-ports groovy-security/main arm64 
Packages
100 /var/lib/dpkg/status
 2.20.11-0ubuntu50 500
500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages

`ubuntu-bug apport` shows 
== Tags =
 groovy uec-images

ubuntu@ubuntu:~$ sudo apt install apport
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  python3-apport
Suggested packages:
  apport-gtk | apport-kde
The following packages will be upgraded:
  apport python3-apport
2 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
Need to get 214 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/main arm64 
python3-apport all 2.20.11-0ubuntu50.6 [85.2 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/main arm64 apport 
all 2.20.11-0ubuntu50.6 [129 kB]
Fetched 214 kB in 1s (258 kB/s)
(Reading database ... 101926 files and directories currently installed.)
Preparing to unpack .../python3-apport_2.20.11-0ubuntu50.6_all.deb ...
Unpacking python3-apport (2.20.11-0ubuntu50.6) over (2.20.11-0ubuntu50.5) ...
Preparing to unpack .../apport_2.20.11-0ubuntu50.6_all.deb ...
Unpacking apport (2.20.11-0ubuntu50.6) over (2.20.11-0ubuntu50.5) ...
Setting up python3-apport (2.20.11-0ubuntu50.6) ...
Setting up apport (2.20.11-0ubuntu50.6) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for systemd (246.6-1ubuntu1.3) ...

`ubuntu-bug apport` shows
== Tags =
 arm64-image raspi-image groovy uec-images package-from-proposed

** Tags removed: verification-needed verification-needed-focal 
verification-needed-groovy
** Tags added: verification-done verification-done-focal 
verification-done-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920837

Title:
  apport bugs from official raspi or riscv images are not identified

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1704870] Re: Keys can't be grabbed under Wayland

[Esokrates]

No longer a problem in Ubuntu 21.04. In gnome settings go to
"Applications", select Remmina and toggle "Inhibit system keyboard
shortcuts". That gives the application permission to grab the keyboard.

** Changed in: remmina (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704870

Title:
  Keys can't be grabbed under Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926806] ProcEnviron.txt

[peace_corpse]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1926806/+attachment/5493967/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926806

Title:
  pipx terminates with "TypeError: __init__() got an unexpected keyword
  argument 'encoding'"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926806] ProcCpuinfoMinimal.txt

[peace_corpse]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1926806/+attachment/5493966/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926806

Title:
  pipx terminates with "TypeError: __init__() got an unexpected keyword
  argument 'encoding'"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926806] [NEW] pipx terminates with "TypeError: __init__() got an unexpected keyword argument 'encoding'"

[peace_corpse]

Public bug reported:

Running `pipx` with any parameters except for help results in the
following error:

pipx uninstall-all
Traceback (most recent call last):
  File "/usr/bin/pipx", line 11, in 
load_entry_point('pipx==0.12.3.1', 'console_scripts', 'pipx')()
  File "/usr/lib/python3/dist-packages/pipx/main.py", line 496, in cli
exit(run_pipx_command(parsed_pipx_args, binary_args))
  File "/usr/lib/python3/dist-packages/pipx/main.py", line 191, in 
run_pipx_command
commands.uninstall_all(PIPX_LOCAL_VENVS, LOCAL_BIN_DIR, verbose)
  File "/usr/lib/python3/dist-packages/pipx/commands.py", line 432, in 
uninstall_all
uninstall(venv_dir, package, local_bin_dir, verbose)
  File "/usr/lib/python3/dist-packages/pipx/commands.py", line 409, in uninstall
metadata = venv.get_venv_metadata_for_package(package)
  File "/usr/lib/python3/dist-packages/pipx/Venv.py", line 65, in 
get_venv_metadata_for_package
data = json.loads(
  File "/usr/lib/python3.9/json/__init__.py", line 359, in loads
return cls(**kw).decode(s)
TypeError: __init__() got an unexpected keyword argument 'encoding'
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DistroRelease: Ubuntu 21.04
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: pipx 0.12.3.1-3ubuntu1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 5.11.0-16.17-lowlatency 5.11.12
Tags:  hirsute
Uname: Linux 5.11.0-16-lowlatency x86_64
UpgradeStatus: Upgraded to hirsute on 2020-12-28 (123 days ago)
UserGroups: adm audio cdrom dip docker floppy netdev plugdev scanner sudo sys 
systemd-journal tty video wireshark
_MarkForUpload: True

** Affects: python-pipx (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected hirsute

** Tags added: apport-collected hirsute

** Description changed:

  Running `pipx` with any parameters except for help results in the
  following error:
  
  pipx uninstall-all
  Traceback (most recent call last):
File "/usr/bin/pipx", line 11, in 
  load_entry_point('pipx==0.12.3.1', 'console_scripts', 'pipx')()
File "/usr/lib/python3/dist-packages/pipx/main.py", line 496, in cli
  exit(run_pipx_command(parsed_pipx_args, binary_args))
File "/usr/lib/python3/dist-packages/pipx/main.py", line 191, in 
run_pipx_command
  commands.uninstall_all(PIPX_LOCAL_VENVS, LOCAL_BIN_DIR, verbose)
File "/usr/lib/python3/dist-packages/pipx/commands.py", line 432, in 
uninstall_all
  uninstall(venv_dir, package, local_bin_dir, verbose)
File "/usr/lib/python3/dist-packages/pipx/commands.py", line 409, in 
uninstall
  metadata = venv.get_venv_metadata_for_package(package)
File "/usr/lib/python3/dist-packages/pipx/Venv.py", line 65, in 
get_venv_metadata_for_package
  data = json.loads(
File "/usr/lib/python3.9/json/__init__.py", line 359, in loads
  return cls(**kw).decode(s)
  TypeError: __init__() got an unexpected keyword argument 'encoding'
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu65
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 21.04
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: pipx 0.12.3.1-3ubuntu1
+ PackageArchitecture: all
+ ProcVersionSignature: Ubuntu 5.11.0-16.17-lowlatency 5.11.12
+ Tags:  hirsute
+ Uname: Linux 5.11.0-16-lowlatency x86_64
+ UpgradeStatus: Upgraded to hirsute on 2020-12-28 (123 days ago)
+ UserGroups: adm audio cdrom dip docker floppy netdev plugdev scanner sudo sys 
systemd-journal tty video wireshark
+ _MarkForUpload: True

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926806

Title:
  pipx terminates with "TypeError: __init__() got an unexpected keyword
  argument 'encoding'"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926806] Dependencies.txt

[peace_corpse]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1926806/+attachment/5493965/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926806

Title:
  pipx terminates with "TypeError: __init__() got an unexpected keyword
  argument 'encoding'"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551949] Re: Printing to PDF file loses URLs/links

[Bug Watch Updater]

** Changed in: thunderbird
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551949

Title:
  Printing to PDF file loses URLs/links

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921518] Re: OpenSSL "double free" error

[Mahantesh Salimath]

** Description changed:

  "double free" error is seen when using curl utility. Error is from
  libcrypto.so which is part of the OpenSSL package. This happens only
  when OpenSSL is configured to use a dynamic engine.
  
  OpenSSL version is 1.1.1f
  
- This issue is not encountered if
+ The issue is not encountered if
  http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.
+ 
+ 
+ OpenSSL can be configured to use a dynamic engine by editing the default 
openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu 
systems.
+ 
+ On Bluefield systems, config diff to enable PKA dynamic engine, is as
+ below:
+ 
+ +openssl_conf = conf_section
+ +
+  # Extra OBJECT IDENTIFIER info:
+  #oid_file  = $ENV::HOME/.oid
+  oid_section= new_oids
+  
+ +[ conf_section ]
+ +engines = engine_section
+ +
+ +[ engine_section ]
+ +bf = bf_section
+ +
+ +[ bf_section ]
+ +engine_id=pka
+ +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
+ +init=0
+ +
+ 
+ engine_id above refers to dynamic engine name/identifier.
+ dynamic_path points to the .so file for the dynamic engine.
  
  # curl -O https://tpo.pe/pathogen.vim
  
  double free or corruption (out)
  
  Aborted (core dumped)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921518

Title:
  OpenSSL "double free" error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901286] Re: gnome-disk-image-mounter fails after upgrade to 20.10

[Tessa]

I'm actually running Arch on my desktops now, so I don't have a free
system to try this out with. if upstream says it's fixed, then it's
probably fine to close this for now and re-open it if the problem re-
appears for someone else.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901286

Title:
  gnome-disk-image-mounter fails after upgrade to 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1901286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs

[Dan Streetman]

added ubuntu-security to the bug, just for quick review to make sure
they don't object to the patch

I can sponsor this to -updates if there's no objection

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926254

Title:
  x509 Certificate verification fails when
  basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551949]

[Jfkthame]

Created attachment 9219175
Bug 454059 - Add a Link() method to DrawTarget, and implement it in 
DrawTargetCairo. r?jrmuizel


This provides a basic Link() API on DrawTarget, intended to generate a link
for a single rectangular area (which will be the rect of a frame corresponding
to a link element).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551949

Title:
  Printing to PDF file loses URLs/links

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551949]

[Jfkthame]

With the cairo update in bug 739096, the functions `cairo_tag_begin` and
`cairo_tag_end` become available, which can be used (with the "Link" tag
type) to generate links in PDF output.

There are two ways to use this. One approach is to issue
`cairo_tag_begin` with an associated URL, then do some drawing, and then
do `cairo_tag_end`; the PDF backend will collect the bounding rect of
whatever gets drawn in between the begin/end pair, and generate a link
for this area. The alternative is to explicitly pass a rect (or list of
rects) to `cairo_tag_begin`, rather than relying on the backend to
collect the affected area.

I've experimented with both options, and it seems to me that we get a
better result by explicitly passing the frame rect of whatever frame(s)
are associated with the link, rather than depending on cairo's
accumulation of the area between begin and end. This results in
clickable PDF links that better match the clickable areas of the HTML
document as viewed in the browser. (Which makes sense, as the active
area of an HTML link is determined by the frame's area, not by the
actual rendered ink.)

Currently, only the PDF backend supports generating links like this. On
macOS, our Save as PDF functionality actually goes via the cairo-quartz
backend and the macOS printing architecture, rather than cairo's PDF
backend. So to support links there, we'll need to add support for tag
begin/end to the quartz surface. Fortunately, we don't currently need to
implement everything that the PDF backend provides; just supporting
tag_begin with the Link type and an explicit rect will provide enough
functionality here.

(Eventually, it would be awesome to implement more Tagged PDF support --
e.g. to tag document structure, internal destinations, etc -- but that's
for another day, another bug.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551949

Title:
  Printing to PDF file loses URLs/links

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924850] Re: package usrmerge 24ubuntu3 failed to install/upgrade: installed usrmerge package post-installation script subprocess returned error exit status 1

[Carlos A.]

I have the same problem after updating to 21.04. The error is:

usrmerge (24ubuntu3)...

FATAL ERROR:
Both /bin/ksh and /usr/bin/ksh exist.
Sub-process /usr/bin/dpkg returned an error code (1)

$ sudo /usr/lib/usrmerge/convert-usrmerge

FATAL ERROR:
Both /bin/ksh and /usr/bin/ksh exist.

You can try correcting the errors reported and running again
/usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
Do not install or update other Debian packages until the program
has been run successfully.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924850

Title:
  package usrmerge 24ubuntu3 failed to install/upgrade: installed
  usrmerge package post-installation script subprocess returned error
  exit status 1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824136] Re: ubuntu_k8s_unit_tests failed with GCP (scheduler / master / spdy)

[Ian]

** Tags added: sru-20210412

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824136

Title:
  ubuntu_k8s_unit_tests failed with GCP (scheduler / master / spdy)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1824136/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 / 5.6 /5.8 / 5.10 kernels

[Ian]

focal/linux-gcp 5.8.0-1029.30~20.04.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844493

Title:
  ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 / 5.6 /5.8 / 5.10 kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1844493/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915536] Re: one grub

[Steve Langasek]

Hello Dimitri, or anyone else affected,

Accepted grub2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.32 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: grub2 (Ubuntu Xenial)
   Status: Fix Released => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915536

Title:
  one grub

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations

[Steve Langasek]

Hello Dimitri, or anyone else affected,

Accepted grub2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.32 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926748

Title:
  regression in xenial updates - grub2 cannot handle new arm64
  relocations

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919122] Re: net test from ubuntu_kernel_selftests / ubuntu_bpf failed to build on F-OEM-5.10

[Ian]

focal/gcp 5.8.0-1029.30~20.04.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919122

Title:
  net test from ubuntu_kernel_selftests / ubuntu_bpf failed to build on
  F-OEM-5.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1919122/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924907] Re: Sync bouncy 0.6.20071104-8 (universe) from Debian unstable (main)

[Hans Joachim Desserud]

https://bugs.launchpad.net/ubuntu/+source/bouncy/0.6.20071104-8

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924907

Title:
  Sync bouncy 0.6.20071104-8 (universe) from Debian unstable (main)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16

[Dominik Babic]

You're welcome!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925482

Title:
  Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920837] Re: apport bugs from official raspi or riscv images are not identified

[William Wilson]

The verification passed for focal:

ubuntu@ubuntu:~$ apt-cache policy apport
apport:
  Installed: 2.20.11-0ubuntu27.16
  Candidate: 2.20.11-0ubuntu27.17
  Version table:
 2.20.11-0ubuntu27.17 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf 
Packages
 *** 2.20.11-0ubuntu27.16 500
500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf 
Packages
500 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf 
Packages
100 /var/lib/dpkg/status
 2.20.11-0ubuntu27 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages

`ubuntu-bug apport` shows:
== Tags =
 focal uec-images

ubuntu@ubuntu:~$ sudo apt install apport
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  python3-apport
Suggested packages:
  apport-gtk | apport-kde
The following packages will be upgraded:
  apport python3-apport
2 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
Need to get 214 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf 
python3-apport all 2.20.11-0ubuntu27.17 [85.2 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf apport all 
2.20.11-0ubuntu27.17 [129 kB]
Fetched 214 kB in 1s (247 kB/s)
(Reading database ... 99636 files and directories currently installed.)
Preparing to unpack .../python3-apport_2.20.11-0ubuntu27.17_all.deb ...
Unpacking python3-apport (2.20.11-0ubuntu27.17) over (2.20.11-0ubuntu27.16) ...
Preparing to unpack .../apport_2.20.11-0ubuntu27.17_all.deb ...
Unpacking apport (2.20.11-0ubuntu27.17) over (2.20.11-0ubuntu27.16) ...
Setting up python3-apport (2.20.11-0ubuntu27.17) ...
Setting up apport (2.20.11-0ubuntu27.17) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for systemd (245.4-4ubuntu3.6) ...

`ubuntu-bug apport` shows
== Tags =
 armhf-image raspi-image focal uec-images package-from-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920837

Title:
  apport bugs from official raspi or riscv images are not identified

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926804] [NEW] Installer crashed saying unable to write grub to sda. Was a duel boot. Win10 and ubuntudde same version was already installed but was attempting to install clean over deepin

[John]

Public bug reported:

Recent clean installs. Windows 10 first using newest most recent ISO
then ParrotOS newest then UbuntuDDE. DDE install lost acess to ParrotOS.
Then tried to overight DDE with this newest ubuntu and install crashed
as mentioned obove. I have no idea if this is a bug but I assume when i
attempt reboot ill loose all access and I can't get out of the installer

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.19
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 30 11:32:10 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
RebootRequiredPkgs:
 linux-image-5.11.0-16-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute ubiquity-21.04.19 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926804

Title:
  Installer crashed saying unable to write grub to sda. Was a duel boot.
  Win10 and ubuntudde same version was already installed but was
  attempting to install clean over deepin

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833229] Re: `--extra-index-url` not working for PIP

[Stefano Rivera]

** Also affects: python-pip (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Description changed:

+ [Impact]
+ 
+  * The --extra-index-url feature is not working when an index doesn't
+ contain all the packages in the dependency set.
+ 
+ [Test Plan]
+ # apt install python3-venv
+ # python3 -m venv /tmp/test3env
+ # /tmp/test3env/bin/pip install wheel
+ # /tmp/test3env/bin/pip install --index-url https://test.pypi.org/simple/ 
--extra-index-url https://pypi.org/simple pytopo==1.6.1
+ 
+ A 404 error is the failure.
+ A successful install is success.
+ 
+ [Where problems could occur]
+ 
+  * Changes were cherry-picked from upstream trunk, where they are still 
present.
+  * It's entirely possible that other de-bundling bugs will be fixed by the 
same changes.
+ 
+ [Other Info]
+  
+ * https://github.com/pypa/pip/pull/6113 has a good explanation of the bug.
+ 
+ [Original Bug Report]
+ 
  I originally wrote this as a comment on
  https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1822842 , but I
  guess it makes sense to open a new separate bug since the other report was
  already closed. Pasting my comment contents below.
  
- ~$ lsb_release -rd
- Description:Ubuntu 18.04.2 LTS
- Release:18.04 
- 
- ~$ apt-cache policy python3-pip
- python3-pip:
-   Installed: 9.0.1-2.3~ubuntu1.18.04.1
-   Candidate: 9.0.1-2.3~ubuntu1.18.04.1
-   Version table:
-  *** 9.0.1-2.3~ubuntu1.19.04.1 500
- 500 http://se.archive.ubuntu.com/ubuntu bionic-updates/universe 
amd64 packages
- 500 http://se.archive.ubuntu.com/ubuntu bionic-updates/universe 
i386 packages
- 100 /var/lib/dpkg/status
-  9.0.1-2 500
- 500 http://se.archive.ubuntu.com/ubuntu bionic/universe amd64 
packages
- 500 http://se.archive.ubuntu.com/ubuntu bionic/universe i386 
packages
+ ~$ lsb_release -rd
+ Description:Ubuntu 18.04.2 LTS
+ Release:18.04
+ 
+ ~$ apt-cache policy python3-pip
+ python3-pip:
+   Installed: 9.0.1-2.3~ubuntu1.18.04.1
+   Candidate: 9.0.1-2.3~ubuntu1.18.04.1
+   Version table:
+  *** 9.0.1-2.3~ubuntu1.19.04.1 500
+ 500 http://se.archive.ubuntu.com/ubuntu bionic-updates/universe 
amd64 packages
+ 500 http://se.archive.ubuntu.com/ubuntu bionic-updates/universe 
i386 packages
+ 100 /var/lib/dpkg/status
+  9.0.1-2 500
+ 500 http://se.archive.ubuntu.com/ubuntu bionic/universe amd64 
packages
+ 500 http://se.archive.ubuntu.com/ubuntu bionic/universe i386 
packages
  
  ---
  
  It seems like `9.0.1-2.3~ubuntu1.18.04.1` breaks the `--extra-index-url`
  functionality of PIP.
  
  In my understanding, the idea is for `--extra-index-url` to provide a
  PyPI-compliant repository that offers a few additional packages, allowing PIP
  to fall back onto the instance configured as `--index-url` (defaults to
  upstream PyPI). This has been the case with earlier versions, allowing us to
  host an internal PyPI repository containing a subset of packages, as well as a
  generic local caching PyPI mirror.
  
  In `9.0.1-2.3~ubuntu1.18.04.1`, it seems like the fallback mechanisms do not
  work properly, instead failing if _either_ the `--index-url` _or_
  `--extra-index-url` instances lack the package.
  
  ---
  
  With `~/.config/pip/pip.conf` as:
  
- [global]
- index-url = 
https://:@artifactory.internal/artifactory/api/pypi/PyPI_mirror/simple
- extra-index-url = 
https://:@artifactory.internal/artifactory/api/pypi/PyPI_extra/simple
+ [global]
+ index-url = 
https://:@artifactory.internal/artifactory/api/pypi/PyPI_mirror/simple
+ extra-index-url = 
https://:@artifactory.internal/artifactory/api/pypi/PyPI_extra/simple
  
  With `python3-pip` version `9.0.1-2.3~ubuntu1.18.04.1`, I get a session
  like:
  
- ~$ python3 -m venv env/pip-latest
- ~$ . env/pip-latest/bin/activate
- (pip-latest) ~$ pip --version
- pip 9.0.1 from 
/home/dandersson/env/pip-latest/lib/python3.6/site-packages (python 3.6)
- (pip-latest) ~$ pip install hpt
- Collecting hpt
- Exception:
- Traceback (most recent call last):
-   File 
"/home/dandersson/env/pip-latest/lib/python3.6/site-packages/pip/basecommand.py",
 line 215, in main
- status = self.run(options, args)
-   File 
"/home/dandersson/env/pip-latest/lib/python3.6/site-packages/pip/commands/install.py",
 line 353, in run
- wb.build(autobuilding=True)
-   File 
"/home/dandersson/env/pip-latest/lib/python3.6/site-packages/pip/wheel.py", 
line 749, in build
- self.requirement_set.prepare_files(self.finder)
-   File 
"/home/dandersson/env/pip-latest/lib/python3.6/site-packages/pip/req/req_set.py",
 line 380, in prepare_files
- ignore_dependencies=self.ignore_dependencies))
-   File 
"/home/dandersson/env/pip-latest/lib/python3.6/site-packages/pip/req/req_set.py",
 line 554, in 

[Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

[JohnDoe_71Rus]

when we can wait for the update?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915870

Title:
  gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
  SIGSEGV in cso_destroy_context() [r300_dri.so]

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914239] Re: ubuntu-20.04 pip3 ignores /etc/pip.conf

[Stefano Rivera]

** Changed in: python-pip (Ubuntu Focal)
   Status: New => In Progress

** Changed in: python-pip (Ubuntu Focal)
 Assignee: (unassigned) => Stefano Rivera (stefanor)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914239

Title:
  ubuntu-20.04 pip3 ignores /etc/pip.conf

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926624] Re: failed to start commit a transient machine-id on disk

[Dan Streetman]

how did you install the system onto the usb stick? that service
shouldn't run during normal boots.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926624

Title:
  failed to start commit a transient machine-id on disk

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926803] [NEW] Copied Folders from Google Drive does not inherit the name of Folder

[John T]

Public bug reported:

When I tried to copy my folders from Google Drive after mounting it from
gnome-control-center it does not inherit the folder names and the file
names.

Description:Ubuntu 21.04 (Xubuntu)
Release:21.04

thunar:
  Installed: 4.16.6-0ubuntu1
  Candidate: 4.16.6-0ubuntu1
  Version table:
 *** 4.16.6-0ubuntu1 500

I expected that the file names and folders that were copied from Google
Drive kept the same name.

I got filenames and folder names that looks like this:
"1pk7M7JUKfE0h0OqGZbUWN0Yx9yKq_ZbX"

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: thunar 4.16.6-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Apr 30 14:31:38 2021
InstallationDate: Installed on 2021-04-24 (6 days ago)
InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: thunar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute

** Attachment added: "Screenshot_2021-04-27_20-10-54.png"
   
https://bugs.launchpad.net/bugs/1926803/+attachment/5493952/+files/Screenshot_2021-04-27_20-10-54.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926803

Title:
  Copied Folders from Google Drive does not inherit the name of Folder

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926802] [NEW] qt5-default package is missed in 21.04

[Norbert]

Public bug reported:

Previous 20.10 version has the qt5-default package in place (see
https://packages.ubuntu.com/groovy/qt5-default ).

Please upload the  qt5-default package for 21.04 Ubuntu version.

What is interesting - all its dependencies can be simply installed with
`sudo apt-get install qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools`
.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926802

Title:
  qt5-default package is missed in 21.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1926802/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876687] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on Focal

[Guilherme G. Piccoli]

** Tags added: sru-20210412

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876687

Title:
  function traceon/off triggers in ftace from ubuntu_kernel_selftests
  failed on Focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926799] [NEW] Multiple issues with zoom in accessibility

[Sai Madhan]

Public bug reported:

LSB Version:
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch

i have low vision so i need to use screen magnifiers and i am having a
lot of issues with the zoom feature in accessibility.

1. zoom focus shifts - lets assume a window in the center of the screen
and i am at 3x zoom and i try to point my mouse at something and try to
click that. 90% of the time zoom focus shifts away from the mouse
location to mostly top left corner of the screen.

2. mouse pointing away from the object - Similarly when i reach above
some zoom limit sets say 4x and now lets say i am in a browser trying to
click a link i point at the link cursor changes to hand and when i try
to click i couldnt. So i try to zoom out and i fid that the pointer was
not exactly placed on the link. To sum up when zoomed in it seems like i
am pointing at a link while the cursor is actually placed away from the
link

3. Compressing text - after reaching certain high zoom level as said 4x
or 5x the content on the screen becomes a bit compressed on the sides
texts and images and everything on screen becomes elongated

I actually tried using a combination of settings available within the
zoom settings but i had the same result no matter the setting i use I
love working with linux ubuntu especially but this makes it really
frustrating at times as i have to heavily rely on such features as
magnifiers and screen readers.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: accessibility

** Tags added: acceeeibility

** Tags removed: acceeeibility
** Tags added: accessibility

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926799

Title:
  Multiple issues with zoom in accessibility

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926800] [NEW] erased existing Ubuntu version 18.04, fatal error at the end of the installation process

[yodaanneaux]

Public bug reported:

>From a liveUsb I tried to erased the existing Ubuntu version (18.04). At
the end of the installation procees, I got an error about (on \dev\sd or
\dev\sb..). It may have a link with grub or the starying process? On
this computer there is also Windows 7.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 30 20:13:20 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926800

Title:
  erased existing Ubuntu version 18.04, fatal error at the end of the
  installation process

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926801] [NEW] BCM2835 SPI chipselect limit - kernel/driver panic

[Robert Stephens]

Public bug reported:

Bug fix was just committed by Phil Elwell , and
appears as response driver error reported for Raspberry Pi OS. I have
the same problem with driver in Ubuntu 21.04. My apology for not knowing
how driver fixes are coordinated across Pi OS and Ubuntu, so I am
providing the information here in hopes a fix will be made available in
Ubuntu 21.04. Please let me know if driver fix will be available for
21.04.

As background, my previous comment on github in discussion of problem with Mr. 
Elwell was:
A limit of 24 chipselects would work for me. -- This would likely solve problem 
seeing a kernel panic (bad kernel memory reference) in 5.11.0-1007-raspi after 
configuring 6 chipselects for for BCM2835 SPI via dtoverlay. Kernel panic is on 
shutdown/reboot, however, memory corruption for more than 4 chipselects likely 
has other runtime consequences.

---
Details on new driver commit for drivers/spi/spi-bcm2835.c from Mr. Elwell on 
4-30-2021:

https://github.com/raspberrypi/linux/commit/05f8d5826e28e9d82485c03b65c18d5013ba13bd

spi: bcm2835: Increase the CS limit to 24

Increase the maximum number of CS lines to 24, and ensure this limit is
not exceeded.

See: #4281 -- https://github.com/raspberrypi/linux/pull/4281

Suggested-by: Joe Burmeister 
Signed-off-by: Phil Elwell 

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926801

Title:
   BCM2835 SPI chipselect limit - kernel/driver panic

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16

[Guilherme G. Piccoli]

Thanks a lot Dominik, I'll investigate based on your attached files!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925482

Title:
  Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs