[Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

[Andrew Conway]

The same problem occurs on 24.04, but the workaround of setting the
ubuntu priority to a negative number seems to be working.

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

Title:
  Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

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


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

[Bug 2063456] Re: package cephadm: dependency "cephadmlib" missing

[Andrew Beeman]

I can confirm this is still an issue.

I could not get #4 to work; there were dependency errors on some of the
commands.

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

Title:
  package cephadm: dependency "cephadmlib" missing

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


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

Re: [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

[Andrew Reis]

Confirmed. And it also looks like the fix made it into the 6.8 kernel
for noble.


From: nore...@launchpad.net  on behalf of ku4eto 
<2048...@bugs.launchpad.net>
Date: Friday, May 3, 2024 at 15:20
To: Drew Reis 
Subject: [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to 
kernel 6.5
Issue seems to have been fixed, with the bug report not being mentioned in the 
changelog.
Tested on Ubuntu 22.04, with 6.5.0-28-generic, vSphere 6.5, ESXi 6.5, IDE 
CD/DVD as Client Device.
I guess this can be closed.

@areis422 Can you test and confirm on your side as well?

--
You received this bug notification because you are subscribed to the bug
report.
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F2048945=05%7C02%7Cdrew_reis%40gensler.com%7Caa2ee77f19b24bd7689908dc6bae78e8%7C94a74758f2ff413c9f705725701b8d02%7C0%7C0%7C638503644324869373%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=5SEDThTBhEDUa%2BPxcBjVPk9Y0Oh9x6R49qET%2FIqA%2BxA%3D=0

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws-6.5 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Possibly related to 
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flkml.kernel.org%2Flinux-=05%7C02%7Cdrew_reis%40gensler.com%7Caa2ee77f19b24bd7689908dc6bae78e8%7C94a74758f2ff413c9f705725701b8d02%7C0%7C0%7C638503644324879127%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=PkMnglOHo3q9hgHMSOyDsJug1rM0HJJO2YW%2FgtRUtW0%3D=0
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fus.archive.ubuntu.com%2Fubuntu=05%7C02%7Cdrew_reis%40gensler.com%7Caa2ee77f19b24bd7689908dc6bae78e8%7C94a74758f2ff413c9f705725701b8d02%7C0%7C0%7C638503644324885309%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=gPrK1nNfbsxG84ZwqwLBYjT0SO5pehjcA78j5U3IPSE%3D=0
 jammy-updates/main amd64 Packages
  500 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsecurity.ubuntu.com%2Fubuntu=05%7C02%7Cdrew_reis%40gensler.com%7Caa2ee77f19b24bd7689908dc6bae78e8%7C94a74758f2ff413c9f705725701b8d02%7C0%7C0%7C638503644324888966%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=OmDdYEQ6WlEFtwTyVrFV%2BZSqMFfkCU%2BO7XZCVJXRc2o%3D=0
 jammy-security/main amd64 Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fus.archive.ubuntu.com%2Fubuntu=05%7C02%7Cdrew_reis%40gensler.com%7Caa2ee77f19b24bd7689908dc6bae78e8%7C94a74758f2ff413c9f705725701b8d02%7C0%7C0%7C638503644324893922%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=JR3G%2Fag6CELAWOxKRrHAZC7DF4HzQaZc6TbgfAoOBnc%3D=0
 jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no 

[Bug 2064147] Re: OneDrive integration causes sigfault after entering My Files

[Andrew Baker]

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #732
   https://gitlab.gnome.org/GNOME/gvfs/-/issues/732

** Also affects: gvfs via
   https://gitlab.gnome.org/GNOME/gvfs/-/issues/732
   Importance: Unknown
   Status: Unknown

** Summary changed:

- OneDrive integration causes sigfault after entering My Files
+ Unable to browse My Files using OneDrive integration

** Information type changed from Public to Private

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

Title:
  Unable to browse My Files using OneDrive integration

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


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

[Bug 2064147] Re: OneDrive integration causes sigfault after entering My Files

[Andrew Baker]

Captured gvfsd debug log of entering My Files

** Attachment added: "gvfs debug log"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2064147/+attachment/5772565/+files/gvfsd.log

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

Title:
  Unable to browse My Files using OneDrive integration

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


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

[Bug 2064147] [NEW] Unable to browse My Files using OneDrive integration

[Andrew Baker]

Private bug reported:

The new OneDrive integration is causing a sigfault when opening the My
Files folder.

Release information:
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04

Apt Cache:
gvfs:
  Installed: 1.54.0-1ubuntu2
  Candidate: 1.54.0-1ubuntu2
  Version table:
 *** 1.54.0-1ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status

Expected result:

1. Sign in to Microsoft 365 using personal account
2. Open Nautilus
3. Mount OneDrive storage
4. Enter My Files
5. Nautilus displays files in OneDrive

Actual result:

1. Sign in to Microsoft 365 using personal account
2. Open Nautilus
3. Mount OneDrive storage
4. Enter My Files
5. Nautilus shows "This location could not be displayed. Sorry, could not 
display all the contents of "My Files": The connection is closed"

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gvfs 1.54.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 29 18:03:59 2024
InstallationDate: Installed on 2024-04-26 (3 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gvfs
 Importance: Unknown
 Status: Unknown

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


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

** Attachment added: "Screencast of fault"
   
https://bugs.launchpad.net/bugs/2064147/+attachment/5772559/+files/Screencast%20from%202024-04-29%2018-09-30.webm

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

Title:
  Unable to browse My Files using OneDrive integration

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


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

[Bug 2018425] Re: apt install ubuntu-desktop takes forever

[Andrew N]

Hi, I’ve run into this issue many times and today tracked down the cause
to this open bug: https://bugs.launchpad.net/netplan/+bug/1999178

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

Title:
  apt install ubuntu-desktop takes forever

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


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

[Bug 794098] Re: [Regression] linux: 2.6.32-33.66 -proposed tracker

[Andrew Foran]

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

i have also facing the same type of issue on my client's site kindly
visit: https://www.pikashowgeeks.com/pikashow-for-ios/

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

Title:
  [Regression] linux: 2.6.32-33.66 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/794098/+subscriptions


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

[Bug 2063325] Re: postgis no longer works after dist-upgrade

[Andrew Gallagher]

This error went away on restart, so it's probably safe to close.

** Description changed:

  After dist-upgrading from focal to jammy, postgis no longer works due to
- an undeclared dependency on glibc 3.4.29:
+ an undeclared dependency on glibc++ 3.4.29:
  
  ```
  Apr 24 10:55:14 tiles2 renderd[1761]:reason: Postgis Plugin: ERROR:  
could not load library "/usr/lib/postgresql/12/lib/postgis-3.so": 
/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29'
  not found (required by /lib/x86_64-linux-gnu/libSFCGAL.so.1)#012LINE 16: )
  ```
  
  This makes it both impossible to use postgis, and impossible to migrate
  to postgresql 14, since for a postgres upgrade both versions must be
  operational simultaneously.
  
  See also https://bugs.launchpad.net/ubuntu/+source/update-
  manager/+bug/1907652?comments=all and
  https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/1950772 .
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: postgis 3.2.0+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-177.197-generic 5.4.268
  Uname: Linux 5.4.0-177-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 24 10:59:04 2024
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: postgis
  UpgradeStatus: Upgraded to jammy on 2024-04-23 (0 days ago)

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

Title:
  postgis no longer works after dist-upgrade

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


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

[Bug 2063325] [NEW] postgis no longer works after dist-upgrade

[Andrew Gallagher]

Public bug reported:

After dist-upgrading from focal to jammy, postgis no longer works due to
an undeclared dependency on glibc 3.4.29:

```
Apr 24 10:55:14 tiles2 renderd[1761]:reason: Postgis Plugin: ERROR:  could 
not load library "/usr/lib/postgresql/12/lib/postgis-3.so": 
/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29'
not found (required by /lib/x86_64-linux-gnu/libSFCGAL.so.1)#012LINE 16: )
```

This makes it both impossible to use postgis, and impossible to migrate
to postgresql 14, since for a postgres upgrade both versions must be
operational simultaneously.

See also https://bugs.launchpad.net/ubuntu/+source/update-
manager/+bug/1907652?comments=all and
https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/1950772 .

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: postgis 3.2.0+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-177.197-generic 5.4.268
Uname: Linux 5.4.0-177-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr 24 10:59:04 2024
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: postgis
UpgradeStatus: Upgraded to jammy on 2024-04-23 (0 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  postgis no longer works after dist-upgrade

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


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

[Bug 2045708] Re: [SRU] Improve debian/99-gce.rules to set schedulers based on disk

[Andrew Cloke]

As outlined in the [Test Case] for focal:

 * Images have been built with these packages from the -proposed pocket and
   published in the `ubuntu-os-cloud-image-proposed` project
 * The images have gone through CPC's own CTF framework and testing has been 
successful
 * The images have been shared with the Google team and their testing has also 
been successful


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

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

Title:
  [SRU] Improve debian/99-gce.rules to set schedulers based on disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2045708/+subscriptions


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

[Bug 2052438] Re: Update d/control file with a dependency on google-guest-agent

[Andrew Cloke]

As outlined in the [Test Case] for focal:

 * Images have been built with these packages from the -proposed pocket and
   published in the `ubuntu-os-cloud-image-proposed` project
 * The images have gone through CPC's own CTF framework and testing has been 
successful
 * The images have been shared with the Google team and their testing has also 
been successful


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

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

Title:
  Update d/control file with a dependency on google-guest-agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2052438/+subscriptions


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

[Bug 2061599] [NEW] cant download apache

[Andrew Cambron]

Public bug reported:

error code in subprocess usr/bin/dpkg

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: gitweb 1:2.34.1-1ubuntu1.10
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
 apache2:amd64: Install
 apache2-bin:amd64: Install
 apache2-data:amd64: Install
 apache2-utils:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Apr 15 13:33:35 2024
ErrorMessage: installed gitweb package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2024-02-21 (54 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt  2.4.12
SourcePackage: git
Title: package gitweb 1:2.34.1-1ubuntu1.10 failed to install/upgrade: installed 
gitweb package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apache2.conf-available.gitweb.conf: [deleted]

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  cant download apache

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


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

[Bug 2045708] Re: [SRU] Improve debian/99-gce.rules to set schedulers based on disk

[Andrew Cloke]

As outlined in the [Test Case] for mantic and jammy:

 * Images have been built with these packages from the -proposed pocket and
   published in the `ubuntu-os-cloud-image-proposed` project
 * The images have gone through CPC's own CTF framework and testing has been 
successful
 * The images have been shared with the Google team and their testing has also 
been successful

The Google's team testing of the focal images is still ongoing.

** Tags removed: verification-needed-jammy verification-needed-mantic
** Tags added: verification-done-jammy verification-done-mantic

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

Title:
  [SRU] Improve debian/99-gce.rules to set schedulers based on disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2045708/+subscriptions


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

[Bug 2052438] Re: Update d/control file with a dependency on google-guest-agent

[Andrew Cloke]

As outlined in the [Test Case] for mantic and jammy:

 * Images have been built with these packages from the -proposed pocket and
   published in the `ubuntu-os-cloud-image-proposed` project
 * The images have gone through CPC's own CTF framework and testing has been 
successful
 * The images have been shared with the Google team and their testing has also 
been successful

The Google's team testing of the focal images is still ongoing.


** Tags removed: verification-needed-jammy verification-needed-mantic
** Tags added: verification-done-jammy verification-done-mantic

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

Title:
  Update d/control file with a dependency on google-guest-agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2052438/+subscriptions


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

[Bug 2045708] Re: [SRU] Improve debian/99-gce.rules to set schedulers based on disk

[Andrew Cloke]

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

Title:
  [SRU] Improve debian/99-gce.rules to set schedulers based on disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2045708/+subscriptions


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

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

[Andrew Fernandes]

Daniel (@vanvugt) Thank you very much for your hard work, out-of-band
patch (the ppa!), and speed addressing this extremely subtle, yet
annoying bug... much appreciated!

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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


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

[Bug 2058411] Re: Builds with gcc -fsanitize=address crashing on startup

[Andrew Burnard]

Also affects me, using Uname: Linux 6.5.0-26-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/2058411

Title:
  Builds with gcc -fsanitize=address crashing on startup

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


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

[Bug 2058307] [NEW] package libjurt-java 1:6.4.7-0ubuntu0.20.04.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Andrew Ken Bell]

Public bug reported:

issue arose while installing first updates after install of ubuntu 20.04
operating system

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libjurt-java 1:6.4.7-0ubuntu0.20.04.9
ProcVersionSignature: Ubuntu 5.15.0-101.111~20.04.1-generic 5.15.143
Uname: Linux 5.15.0-101-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Mar 19 09:52:18 2024
DuplicateSignature:
 package:libjurt-java:1:6.4.7-0ubuntu0.20.04.9
 Setting up uno-libs-private (1:6.4.7-0ubuntu0.20.04.9) ...
 dpkg: error processing package libjurt-java (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2024-03-18 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.10
SourcePackage: libreoffice
Title: package libjurt-java 1:6.4.7-0ubuntu0.20.04.9 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal 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/2058307

Title:
  package libjurt-java 1:6.4.7-0ubuntu0.20.04.9 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

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


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

[Bug 2051876] Re: tpm2_nvwrite using an offset causes a TPM error

[Andrew Oswald]

With the advent of 22.04.4, this issue seems to have been resolved.

Thanks again for looking into it, Sudip!  =)

** Changed in: tpm2-tools (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  tpm2_nvwrite using an offset causes a TPM error

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


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

[Bug 2051876] Re: tpm2_nvwrite using an offset causes a TPM error

[Andrew Oswald]

Hello again, Sudip, hope this message finds you well!

I attempted to recreate the issue using a cert whose footprint exceeds
the 1,024 byte TPM data bus by using two tpm2_nvwrite commands (the
second of which specifying --offset=1024) and I'm happy to report that
it's working!

However, we were experiencing the issue on HP gear and this is a Dell
laptop.. so I still need to test it on HP.

thanks again!
-andy

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

Title:
  tpm2_nvwrite using an offset causes a TPM error

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


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

[Bug 2051876] Re: tpm2_nvwrite using an offset causes a TPM error

[Andrew Oswald]

Thanks for looking into this, Sudip!  I will need to write up explicit
instructions, but the issue only shows up when you attempt to write to
an offset, which (I would presume) is why your test didn't produce any
issues.  My usecase is storing a DER encoded x509 certificate whose
footprint exceeds the TPM data bus size, thus requiring multiple
tpm2_nvwrite calls, with any call other than the initial, requiring the
--offset flag and the appropriate offset starting point.

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

Title:
  tpm2_nvwrite using an offset causes a TPM error

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


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

[Bug 2048876] Re: Allow server and pool sources to be overridden through a conf.d or sources.d configuration

[Andrew Cloke]

Many thanks for that feedback and guidance. In parallel with working on
the suggested changes, I wanted to understand the right approach we
should take to fixing this bug.

From your comment in #1 "It can't hurt to discuss with Debian but it's
highly doubtful they'll take our delta", would it be reasonable to
assume that, as Ubuntu has already branched the chrony config associated
with NTP pools away from Debian, we should attempt to land this bug fix
to the NTP pools config directly into Ubuntu?

Thanks again for your help, Andy.

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

Title:
  Allow server and pool sources to be overridden through a conf.d or
  sources.d configuration

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


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

[Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

[Andrew Reis]

Bump. Is anyone looking at this at all?

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

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


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

[Bug 1884299] Re: Chromium snap won't run with nfs home drive

[Andrew Conway]

Matthieu, more recently a more likely problem has been characterized by Alberto 
Mardegan and found the line in question in
https://bugs.launchpad.net/snapd/+bug/1973321

In particular, restarting snapd doesn't help at all for me, so having
the directory mounted before snapd starts doesn't help, and the same
problem occurs with other file systems. However _starting_ outside the
home directory does help. This is the situation for me with Kerberos
authenticated NFS, and others with sshfs. I don't know whether it is
relevant for people using NFS without authentication. It is easy to test
for yourself - restart snapd and see if that helps.

So I think there is progress in understanding the problem, even if not
working out how to fix it.

FYI: I initially tried a work around where I used the debian repository
for firefox instead of the snap version, but despite giving it a higher
priority (confirmed via "sudo apt policy firefox") I found the debian
package twice over a week uninstalled and replaced by the snap version
that then would not start. I can manually revert it but it is
inconvenient. Any suggestions on how to make that work reliably would be
appreciated.

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

Title:
  Chromium snap won't run with nfs home drive

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


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

[Bug 1964763] Re: QtChooser doesn't support qt6

[Andrew Hayzen]

I was going to request this change into Debian as well, but appears that
has already been attempted and was rejected due to "qtchooser is dead
upstream". https://salsa.debian.org/qt-kde-
team/qt/qtchooser/-/merge_requests/2

I wonder if the situation can be improved though as if you are trying to
use Qt 6 tooling in a container image then you need workarounds :-/

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

Title:
  QtChooser doesn't support qt6

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


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

[Bug 1973114] Re: Key trust verification fails on Ubuntu 22.04

[Andrew Cloke]

Thanks Fabio. Adjusted tags accordingly.

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

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

Title:
   Key trust verification fails on Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1973114/+subscriptions


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

[Bug 1966773] Re: [FFe] remove zfs option from the installer

[Andrew L. Moore]

Why would Ubuntu want to remove ZFS support?  I use both Ubuntu and
Fedora but would have no reason to continue with Ubuntu without ZFS.

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

Title:
  [FFe] remove zfs option from the installer

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


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

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

[Andrew Conway]

Thanks Alberto. I tried running "hello" in a different directory, and
you were correct:

arc@andrewfairfield:~$ hello
cannot open path of the current working directory: Permission denied
arc@andrewfairfield:~$ cd /
arc@andrewfairfield:/$ hello
Hello, world!
arc@andrewfairfield:/$ 

[ This is in 20.04, not 22.04 ]

Yay! that is the first time I have seen a snap actually work with my
normal user account.

This feels like significant progress in working out what is going on!

Of course firefox needs access to the home directory to load the profile
and store downloads. Is the whole process run as some other user (a la
sudo) or is there just some starting stub running as some other user
doing something that returns to the actual user after doing something
that thinks it needs access to the current directory but could get by
without it?

Actually, I can sort of answer that - I tried running "musescore" as a snap, 
starting from /
It successfully ran. I tried saving something, and it sort of did... but in a 
new, empty "home" directory in a /home/arc/snap/musescore/216/ that the save 
file dialog went to when I pressed the home button. Is this normal behaviour 
for a snap? Regardless of the inconvenience of the subdirectory, that is 
running over nfs successfully. I can close Musescore and load it again. But not 
with cwd=/home/arc.

So that is fairly strong evidence supporting your idea that it is the
same root cause as https://bugs.launchpad.net/bugs/1973321 . I will add
a comment there.

Thanks for the insight Alberto!

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

Title:
  snapd is not autofs aware and fails with nfs home dir

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


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

[Bug 1884299] Re: Chromium snap won't run with nfs home drive

[Andrew Conway]

I (using Kerberos) don't the get apparmor DENIED messages that Eric (not
using Kerberos) did, but I get exactly the same "cannot open path of the
current working directory: Permission denied" error.

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

Title:
  Chromium snap won't run with nfs home drive

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


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

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

[Andrew Conway]

Using NVFv4, kerberos authenticated, mounted by autofs:

arc@andrewshoreham:~$ hello
cannot open path of the current working directory: Permission denied

[ Then as user with sudo privs, sudo systemctl restart snapd ]

arc@andrewshoreham:~$ hello
cannot open path of the current working directory: Permission denied


Logs since just before restarting snapd

syslog
--
May 15 14:54:09 andrewshoreham kernel: [12319.195323] audit: type=1400 
audit(1652590449.676:183): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/sssd" name="/proc/24886/cmdline" pid=910 comm="sssd_nss" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
May 15 14:54:09 andrewshoreham systemd[1]: Stopping Snap Daemon...
May 15 14:54:09 andrewshoreham snapd[726]: main.go:155: Exiting on terminated 
signal.
May 15 14:54:09 andrewshoreham snapd[726]: overlord.go:504: Released state lock 
file
May 15 14:54:09 andrewshoreham systemd[1]: snapd.service: Deactivated 
successfully.
May 15 14:54:09 andrewshoreham systemd[1]: Stopped Snap Daemon.
May 15 14:54:09 andrewshoreham systemd[1]: snapd.service: Consumed 2.753s CPU 
time.
May 15 14:54:09 andrewshoreham systemd[1]: Starting Snap Daemon...
May 15 14:54:09 andrewshoreham snapd[24890]: AppArmor status: apparmor is 
enabled and all features are available
May 15 14:54:09 andrewshoreham snapd[24890]: overlord.go:263: Acquiring state 
lock file
May 15 14:54:09 andrewshoreham snapd[24890]: overlord.go:268: Acquired state 
lock file
May 15 14:54:09 andrewshoreham snapd[24890]: daemon.go:247: started 
snapd/2.55.3+22.04 (series 16; classic) ubuntu/22.04 (amd64) 
linux/5.15.0-25-generic.
May 15 14:54:09 andrewshoreham kernel: [12319.270748] loop11: detected capacity 
change from 0 to 8
May 15 14:54:09 andrewshoreham snapd[24890]: daemon.go:340: adjusting startup 
timeout by 1m10s (pessimistic estimate of 30s plus 5s per snap)
May 15 14:54:09 andrewshoreham systemd[1]: 
tmp-sanity\x2dmountpoint\x2d2760788470.mount: Deactivated successfully.
May 15 14:54:09 andrewshoreham snapd[24890]: backend.go:133: snapd enabled NFS 
support, additional implicit network permissions granted
May 15 14:54:10 andrewshoreham kernel: [12319.549118] audit: type=1400 
audit(1652590450.028:184): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=24926 
comm="apparmor_parser"
May 15 14:54:10 andrewshoreham kernel: [12319.578896] audit: type=1400 
audit(1652590450.060:185): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=24926 
comm="apparmor_parser"
May 15 14:54:10 andrewshoreham kernel: [12319.969313] audit: type=1400 
audit(1652590450.448:186): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/snap/snapd/15534/usr/lib/snapd/snap-confine" 
pid=24946 comm="apparmor_parser"
May 15 14:54:10 andrewshoreham kernel: [12319.983029] audit: type=1400 
audit(1652590450.464:187): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/snap/snapd/15534/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
 pid=24946 comm="apparmor_parser"
May 15 14:54:10 andrewshoreham kernel: [12320.165228] audit: type=1400 
audit(1652590450.644:188): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.snapd-desktop-integration.hook.configure" 
pid=24950 comm="apparmor_parser"
May 15 14:54:10 andrewshoreham kernel: [12320.341043] audit: type=1400 
audit(1652590450.820:189): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="snap.snapd-desktop-integration.snapd-desktop-integration" pid=24951 
comm="apparmor_parser"
May 15 14:54:11 andrewshoreham kernel: [12320.633250] audit: type=1400 
audit(1652590451.112:190): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap-update-ns.snap-store" pid=24948 comm="apparmor_parser"
May 15 14:54:11 andrewshoreham kernel: [12320.721431] audit: type=1400 
audit(1652590451.200:191): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap-update-ns.snapd-desktop-integration" pid=24949 comm="apparmor_parser"
May 15 14:54:11 andrewshoreham kernel: [12320.727129] audit: type=1400 
audit(1652590451.208:192): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap-update-ns.hello" pid=24954 comm="apparmor_parser"
May 15 14:54:11 andrewshoreham systemd[1]: Started Snap Daemon.
May 15 14:54:11 andrewshoreham dbus-daemon[693]: [system] Activating via 
systemd: service name='org.freedesktop.timedate1' 
unit='dbus-org.freedesktop.timedate1.service' requested by ':1.166' (uid=0 
pid=24890 comm="/usr/lib/snapd/snapd " label="unconfined")
May 15 14:54:11 andrewshoreham systemd[1]: Starting Time & Date Service...
May 15 14:54:11 andrewshoreham dbus-daemon[693]: [system] Successfully 

[Bug 1643706] Re: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs

[Andrew Aitchison]

> The whole issue also raises the silly question: what is so security-
sensitive about /tmp?

Another, non-privileged, user can write to it, so could leave a trojan
(malware) in there ...

Ubuntu has /tmp/user/uid which I assume exists to work around that issue,
but chromium wont let me see /tmp/user// or file:///tmp/user//

One workaround would be to consistently use a directory you can access
through snap, such as /home/USER/tmp, instead of /tmp. (Globally)
setting TMP, TEMP, TMPDIR and/or TEMPDIR may help with this ...

https://www.the-art-of-web.com/php/where-is-tmp/ describes some other
"solutions" to this problem that have caused problems.

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

Title:
  snap apps need to be able to browse outside of user $HOME dir. for
  Desktop installs

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


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

[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

[Andrew Byrd]

I encountered this last week installing Ubuntu 22.04. I booted from USB
install media and installed to a second attached USB storage device. I
created an EFI system partition on the install target device, and
specifically selected this EFI system partition in the GUI as the place
to install the bootloader. However the bootloader was instead installed
to the EFI system partition of the machine's internal SSD.

I reproduced the process running ubiquity from a terminal with the debug
flag. The section of the logs that appears relevant is reproduced below.
The logs show it fetching the debconf value and running "grub-install
/dev/sdd1", which correctly reflects the partition I selected in the UI.

Based on documentation and various forum discussions I'm reading, my
impression is that the device is specified as a parameter to the grub-
install command (as Ubiquity seems to be doing here) for MBR installs
and EFI installs work differently, requiring the target EFI system
partition to be mounted on /boot/efi. Is this correct, and it possible
Ubiquity is missing some unmount/remount steps here?


debconf (developer): <-- METAGET grub-installer/progress/step_bootdev 
description
debconf (developer): --> 1 Determining GRUB boot device...
May  7 21:22:29 debconf (filter): --> 0 OK
May  7 21:22:29 debconf (filter): <-- FGET grub-installer/bootdev seen
debconf (developer): <-- FGET grub-installer/bootdev seen
debconf (developer): --> 0 true
May  7 21:22:29 debconf (filter): <-- GET grub-installer/bootdev
debconf (developer): <-- GET grub-installer/bootdev
debconf (developer): --> 1 /dev/sdd1
May  7 21:22:29 debconf (filter): <-- PROGRESS STEP 1
May  7 21:22:29 debconf (filter): widget found for grub-installer/progress/title
May  7 21:22:29 debconf (filter): --> 0 OK
May  7 21:22:29 debconf (filter): <-- SUBST 
grub-installer/progress/step_install_loader BOOTDEV /dev/sdd1
debconf (developer): <-- SUBST grub-installer/progress/step_install_loader 
BOOTDEV /dev/sdd1
debconf (developer): --> 0
May  7 21:22:29 debconf (filter): <-- PROGRESS INFO 
grub-installer/progress/step_install_loader
May  7 21:22:29 debconf (filter): widget found for grub-installer/progress/title
debconf (developer): <-- METAGET grub-installer/progress/step_install_loader 
description
debconf (developer): --> 1 Running "grub-install /dev/sdd1"...
May  7 21:22:29 debconf (filter): --> 0 OK
May  7 21:22:29 debconf (filter): <-- INPUT low 
grub-installer/force-efi-extra-removable
debconf (developer): <-- METAGET grub-installer/force-efi-extra-removable Type
debconf (developer): --> 1 boolean
debconf (developer): <-- INPUT low grub-installer/force-efi-extra-removable
debconf (developer): --> 30 question skipped
May  7 21:22:29 debconf (filter): <-- GO 
debconf (developer): <-- GO 
debconf (developer): --> 0 ok
May  7 21:22:29 debconf (filter): <-- GET 
grub-installer/force-efi-extra-removable
debconf (developer): <-- GET grub-installer/force-efi-extra-removable
debconf (developer): --> 1 false
May  7 21:22:32 debconf (filter): <-- GET grub-installer/make_active
debconf (developer): <-- GET grub-installer/make_active
debconf (developer): --> 1 true
May  7 21:22:32 debconf (filter): <-- PROGRESS STEP 1
May  7 21:22:32 debconf (filter): widget found for grub-installer/progress/title
May  7 21:22:32 debconf (filter): --> 0 OK
May  7 21:22:32 debconf (filter): <-- PROGRESS INFO 
grub-installer/progress/step_config_loader
May  7 21:22:32 debconf (filter): widget found for grub-installer/progress/title
debconf (developer): <-- METAGET grub-installer/progress/step_config_loader 
description
debconf (developer): --> 1 Running "update-grub"...

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

Title:
  installer uses first EFI system partition found even when directed
  otherwise

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


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

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

[Andrew Conway]

I got exactly the same errors as Miles above; a simple permission denied
error stopping things before AppArmor got involved.

I.e., the answer to Markus Kuhn's question is no, in fact even in
enforce mode there are no denied apparmor complaints.

I don't know whether this is because the gating problem is not being
able to read the ticket in /tmp, or whether being in the kernel solves
some of the apparmor issues, but the greater pickiness of kerberos user
definition is an issue. Do snaps run as a different uid?

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

Title:
  snapd is not autofs aware and fails with nfs home dir

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


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

[Bug 1884299] Re: Chromium snap won't run with nfs home drive

[Andrew Conway]

Firefox also doesn't work now it is a snap in 22.04.

I think there are still multiple issues here. The original poster seems
to be using NVSv3 I believe based on the RPC errors (NFSv3 uses multiple
ports, one of which is called something like RPC, but I am not an expert
in this as I have only used NFSv4, which uses a single port). Is this
correct tylerecouture?

NFSv3 has no user authentication; NFSv4 uses Kerberos for authentication
(and privacy and tamper resistance). I think this brings in additional
problems as snaps don't appear to work with Kerberos

e.g.

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346

https://bugzilla.mozilla.org/show_bug.cgi?id=1734791

I get a very different error - a simple permission denied error rather
than an AppArmor problem.



** Bug watch added: Mozilla Bugzilla #1734791
   https://bugzilla.mozilla.org/show_bug.cgi?id=1734791

** Also affects: firefox (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/1884299

Title:
  Chromium snap won't run with nfs home drive

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


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

[Bug 1971895] [NEW] Warning messages from stat printed on installation with no user crontabs

[Andrew Ruthven]

Public bug reported:

On installation of cron on a new system, or (I expect) an upgrade with
no user crontab files the following is printed:

Setting up cron (3.0pl1-128.1ubuntu1.1) ...
stat: cannot stat '*': No such file or directory
stat: cannot stat '*': No such file or directory
stat: cannot stat '*': No such file or directory
Warning: * is not a regular file!

This is related to the fix for CVE-2017-9525 introduced in
3.0pl1-128.1ubuntu1.1. The for loop at line 66 of cron.postinst needs to
have a guard like the following added to it:

[ "$tab_name" = "*" ] && continue

We have observed this with Bionic, I haven't checked any other Ubuntu
releases.

Cheers,
Andrew

** Affects: cron (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/1971895

Title:
  Warning messages from stat printed on installation with no user
  crontabs

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


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

[Bug 1662552] Re: snaps don't work with NFS home

[Andrew Conway]

I am pretty sure this is at least partly a problem with snaps not
working with Kerberos, which is the authentication mechanism for NFS.
The Kerberos credentials are (with good reason) not stored in the home
directory.

I described this in more detail in bug 1784774.

This means that firefox and lxd don't work in 22.04 with authenticated
NFS home directories.

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

Title:
  snaps don't work with NFS home

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


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

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

[Andrew Conway]

I did some more investigating, and I think there are two independent problems 
here:
(1) The problem as believed so far, network access permissions
(2) New insight: Kerberos doesn't work with snaps.
This explains why fixing (1) didn't help me (or Adam).

Background: Kerberos is the authentication mechanism used for NFS.
Assuming you are using authentication (as almost everyone does), then
when you access NFS contents, you need to provide kerberos credentials.
These are stored outside of your home directory (after all, home
directories are one of the most common reasons to use NFS, so you can't
store them there). I believe snaps restrict access to just your home
directory, so you can't access the Kerberos key and therefore can't
access your home directory.

This is supported by various bugs like
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346
(unresolved) which is a different but relevant issue - people who don't
use NFS but do use Kerberos features in Firefox found they don't work
post snap conversion.

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

Title:
  snapd is not autofs aware and fails with nfs home dir

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


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

[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded

[Andrew Robbins]

ah whoops-please undo

** Changed in: snapd (Ubuntu)
   Status: Fix Committed => 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/1969162

Title:
  bad interaction between snapd and update-notifier when snapd package
  is being upgraded

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


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

[Bug 1662552] Re: snaps don't work with NFS home

[Andrew Conway]

This still doesn't work with 22.04, which is a problem for firefox,
which is now installed as a snap. This seems somewhat strange as firefox
obviously needs network access, so it is not just the network access
that causes problems.

Running firefox from the command line produces an error complaining that
it doesn't have read access to the current working directory (which
would be true if it were as a different user as a different user doesn't
have access to the kerberos ticket).

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

Title:
  snaps don't work with NFS home

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


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

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

[Andrew Conway]

I never got it to work in 20.04, so I don't know whether your fix ever
made it in.

I have just installed Jammy Jellyfish (22.04), and can confirm snaps
don't work in it when using autofs and nfs mounted home directories.

The prior work around was just never use any snap applications, which
was OK as nothing important was in snaps prior to 22.04.

This is harder in 22.04 as firefox is distributed as a snap, and so
firefox doesn't work in 22.04 if you have autofs NFS home directories.

Work around is to use a different source for firefox,
https://ubuntuhandbook.org/index.php/2022/04/install-firefox-deb-
ubuntu-22-04/ but I don't know whether that will get security updates as
quickly, so this is a serious problem.

** Also affects: firefox (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/1784774

Title:
  snapd is not autofs aware and fails with nfs home dir

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


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

[Bug 1956243] Re: Ping give socket error initially if IPv6 is disabled

[Andrew Welham]

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

Title:
  Ping give socket  error initially if IPv6 is disabled

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


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

[Bug 1969211] Re: Out of date driver with no capabilities for 2.5Gb full duplex

[Andrew Welham]

I got it working, and confirmed the bug, only problem is it will get
overwritten with the next patch, and others cant use the fix.

Hopefully this is a quick fix for a proc dev.

This is how i did it


 When you try to compile the drivers you get

./r8152-2.15.0/r8152.c:18530:25: error: initialization of ‘int (*)(struct 
net_device *, struct ethtool_coalesce *, struct kernel_ethtool_coalesce *, 
struct netlink_ext_ack *)’ from incompatible pointer type ‘int (*)(struct 
net_device *, struct ethtool_coalesce *)’ [-Werror=incompatible-pointer-types]
18530 | .get_coalesce = rtl8152_get_coalesce,
  | ^~~~
./r8152-2.15.0/r8152.c:18530:25: note: (near initialization for 
‘ops.get_coalesce’)
./r8152-2.15.0/r8152.c:18531:25: error: initialization of ‘int (*)(struct 
net_device *, struct ethtool_coalesce *, struct kernel_ethtool_coalesce *, 
struct netlink_ext_ack *)’ from incompatible pointer type ‘int (*)(struct 
net_device *, struct ethtool_coalesce *)’ [-Werror=incompatible-pointer-types]
18531 | .set_coalesce = rtl8152_set_coalesce,

I had a look at the code and googled  (i cant code in C or C++ btw)
This site had similar code
https://sbexr.rabexc.org/latest/sources/26/53bfa290b96570.html#e00100031001

so i made the following changes to the realtek code. not sure if it
right or performant, but it now compiles


# diff ./r8152.c ../r8152-2.15.0/r8152.c
18339,18341c18339
<   struct ethtool_coalesce *coalesce,
<   struct kernel_ethtool_coalesce *,
<   struct netlink_ext_ack *)
---
>   struct ethtool_coalesce *coalesce)
18360,18363c18358
<   struct ethtool_coalesce *coalesce,
< struct kernel_ethtool_coalesce *,
< struct netlink_ext_ack *)
<
---
>   struct ethtool_coalesce *coalesce)

make install copied the code , but throws the following error, looks to
do with code signing ??? Any way i ignored it

At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: 
../crypto/bio/bss_file.c:69
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: 
../crypto/bio/bss_file.c:76
sign-file: certs/signing_key.pem: No such file or directory


I ran

# sudo depmod -a
# sudo update-initramfs -u

as requested by the drivers readme file

 rebooted

 ethtool -s enx5c857e38e9b7 autoneg on advertise 0x802f

now works

 ethtool enx5c857e38e9b7
Settings for enx5c857e38e9b7:
Supported ports: [ MII ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
2500baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
2500baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes:  10baseT/Half 10baseT/Full
 100baseT/Half 100baseT/Full
 1000baseT/Full
 2500baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 2500Mb/s
Duplex: Full
Auto-negotiation: on
Port: MII
PHYAD: 32
Transceiver: internal
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x7fff (32767)
   drv probe link timer ifdown ifup rx_err tx_err 
tx_queued intr tx_done rx_status pktdata hw wol
Link detected: yes


checking the version

# modinfo /lib/modules/5.15.0-25-generic/kernel/drivers/net/usb/r8152.ko
filename:   /lib/modules/5.15.0-25-generic/kernel/drivers/net/usb/r8152.ko
version:v2.15.0 (2021/04/15)
license:GPL

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

Title:
  Out of date driver with no capabilities for 2.5Gb full duplex

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


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

[Bug 1969211] [NEW] Out of date driver with no capabilities for 2.5Gb full duplex

[Andrew Welham]

Public bug reported:

Running on the latest release of ubuntu 22.04, with a usb-2.5gb ethernet
dongle containing the 8156b chip.

This chip is supported 8156b  by the R5182 driver.

see https://www.realtek.com/en/component/zoo/category/network-interface-
controllers-10-100-1000m-gigabit-ethernet-usb-3-0-software

The repository states the driver is not required above kernel 5.6, but the 
driver in this release of ubuntu looks to be out of date 
# modinfo r8152.ko
filename:   /lib/modules/5.15.0-25-generic/kernel/drivers/net/usb/r8152.ko
version:v1.12.12

and v 2.15.0 int he realtek repository


The driver only allows the max speed is 2500 / half

ethtool enx5c857e38e9b7

Settings for enx5c857e38e9b7:
Supported ports: [  ]
Supported link modes:   Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes:  Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 2500Mb/s
Duplex: Half
Auto-negotiation: off
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
MDI-X: Unknown
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

and the command to increase the speed

ethtool -s enx5c857e38e9b7 autoneg on advertise 0x802f

responds with 
netlink error: Operation not supported


I tried to build the driver, but it fails to build on ubuntu 22.04, but builds 
fine on older released ( in know not much help)

/home/andrew/r8152-2.15.0/r8152.c:18530:25: note: (near initialization for 
‘ops.get_coalesce’)
/home/andrew/r8152-2.15.0/r8152.c:18531:25: error: initialization of ‘int 
(*)(struct net_device *, struct ethtool_coalesce *, struct 
kernel_ethtool_coalesce *, struct netlink_ext_ack *)’ from incompatible pointer 
type ‘int (*)(struct net_device *, struct ethtool_coalesce *)’ 
[-Werror=incompatible-pointer-types]
18531 | .set_coalesce = rtl8152_set_coalesce,

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-modules-extra-5.15.0-25-generic 5.15.0-25.25 [modified: 
lib/modules/5.15.0-25-generic/kernel/drivers/net/usb/r8152.ko]
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-25-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', 
'/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card2.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card2.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
Date: Fri Apr 15 11:22:22 2022
InstallationDate: Installed on 2022-04-14 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220330)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-25-generic N/A
 linux-backports-modules-5.15.0-25-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1405
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X570-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.

[Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce

[Andrew Cloke]

** Changed in: kunpeng920/ubuntu-22.04
   Status: Fix Committed => Fix Released

** Changed in: kunpeng920
   Status: Fix Committed => 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/1933301

Title:
  [uacc-0623] hisi_sec2  fail to alloc uacce

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


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

[Bug 1967924] Re: One overlayfs fix has not been backported to the 5.13 branch

[Andrew Vagin]

Any update?

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

Title:
  One overlayfs fix has not been backported to the 5.13 branch

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


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

[Bug 1967924] [NEW] One overlayfs fix has not been backported to the 5.13 bracnh

[Andrew Vagin]

Public bug reported:

The next patch has not been ported to the the 5.13 branch:

$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn 
Date:   Mon Apr 26 10:11:00 2021 +0200

UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from 
map_files

BugLink: https://bugs.launchpad.net/bugs/1857257

...

Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")


But it isn't in the 5.13 branch:

$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c 
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying fs 
doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-bug

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

Title:
  One overlayfs fix has not been backported to the 5.13 bracnh

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


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

[Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container

[Andrew Vagin]

** Also affects: linux-azure (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/1857257

Title:
  linux-image-5.0.0-35-generic breaks checkpointing of container

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


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

[Bug 1966980] [NEW] GIMP crashes as soon as text tool is used

[Andrew Packer]

Public bug reported:

```
GNU Image Manipulation Program version 2.10.18
git-describe: GIMP_2_10_16-38-gde7f04567d
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
9.3.0-8ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib 
--with-tune=generic --enable-offload-targets=nvptx-none,hsa 
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) 

# Libraries #
using babl version 0.1.74 (compiled against version 0.1.74)
using GEGL version 0.4.22 (compiled against version 0.4.22)
using GLib version 2.64.6 (compiled against version 2.64.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.44.7 (compiled against version 1.44.7)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> GIMP-CRITICAL: gimp_tool_key_press: assertion 'gimp_tool_control_is_active 
> (tool->control) == FALSE' failed

Stack trace:
```

# Stack traces obtained from PID 28234 - Thread 28234 #

[New LWP 28236]
[New LWP 28237]
[New LWP 28238]
[New LWP 28250]
[New LWP 28251]
[New LWP 28259]
[New LWP 28297]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffd6d110d10, fd=15) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame 
* 1Thread 0x7f9d8c631340 (LWP 28234) "gimp-2.10"   __libc_read (nbytes=256, 
buf=0x7ffd6d110d10, fd=15) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f9d8beca700 (LWP 28236) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f9d8b6c9700 (LWP 28237) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f9d8aec8700 (LWP 28238) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f9d5a7e8700 (LWP 28250) "gmain"   0x7f9d8d46c9cf in 
__GI___poll (fds=0x5634fef2c370, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7f9d5cfe9700 (LWP 28251) "gdbus"   0x7f9d8d46c9cf in 
__GI___poll (fds=0x5634fef444b0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7f9d896c5700 (LWP 28259) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f9d7bfff700 (LWP 28297) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 8 (Thread 0x7f9d7bfff700 (LWP 28297)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f9d8d765623 in g_cond_wait () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7f9d8dc65aad in ?? () from /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3  0x7f9d8d741ad1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7f9d8d554609 in start_thread (arg=) at 
pthread_create.c:477
ret = 
pd = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140314366965504, 
3992424551288561243, 140726433284430, 140726433284431, 140726433284576, 
140314366961792, -4009040371817750949, -4009071936541270437}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 0
#5  0x7f9d8d479163 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.

Thread 7 (Thread 0x7f9d896c5700 (LWP 28259)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f9d8d765623 in g_cond_wait () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x5634fe290d84 in ?? ()
No symbol table info available.

[Bug 1961425] Re: 22.04: FTBFS due to test failure

[Andrew Cloke]

As 0.8.0-2ubuntu2 has fixed the build issue, marking this bug as "Fix Released".
Please feel free to revert if the issue is persisting.

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

** Changed in: ubuntu-power-systems
   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/1961425

Title:
  22.04: FTBFS due to test failure

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


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

[Bug 1957053] Re: BleachBit shows Errors trying to update

[Andrew Ziem]

This was fixed two years ago for BleachBit 4.0.0
https://github.com/bleachbit/bleachbit/issues/819

The latest BleachBit 4.4.0 is here https://www.bleachbit.org/

Ubuntu has a "no rolling release" policy, so the version in the Ubuntu
repository may be rather old.

** Bug watch added: github.com/bleachbit/bleachbit/issues #819
   https://github.com/bleachbit/bleachbit/issues/819

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

Title:
  BleachBit shows Errors trying to update

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


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

[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console

[Andrew Lee]

I've fixed this in https://github.com/canonical/cloud-
init/pull/1340/files (sadly blocked on getting the CLA signed)

I'm interested that you've hit this too @tony-casanova-nc-33-2017.

FWIW, I'm using:
- cloud-init 22.1
- I'm on a Microsoft OS called 'Mariner'
- I'm on VMware vSphere V7 -> I've only ever seen this bug on VMware. 

Are you using similar versions?

I'm fairly sure there's a corresponding VMware bug here (causing the
kernel to incorrectly set up the /dev/ttyS0 serial device).

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

Title:
  module ssh-authkey-fingerprints fails Input/output error: /dev/console

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


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

[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console

[Andrew Lee]

I've also hit this (on VMware), and while I suspect that may be due to
some particular funnies of the OS I am on, I agree a defensive fix in
cloud-init to not raise an Exception if you can't write to /dev/console
and fall back to writing to stdout would be welcomed.

Any objections if I raise a PR to do that?

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

Title:
  module ssh-authkey-fingerprints fails Input/output error: /dev/console

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


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

[Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot

[Andrew Purtell]

Running 5.13.0-xx on Parallels Desktop on M1 Macbook. 5.13.0-12-generic
is the last kernel that will boot. -13 and -14 have been withdrawn,
apparently. -15 and -16 just hang as soon as control is given to the
kernel back from the EFI loader. Some fail code was backported post -12
from more recent kernels it seems.

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

Title:
  Kernel 5.14.X / 5.13.14 fails to boot

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


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

[Bug 1957716] Re: Update for CVE-2021-43860 and CVE-2022-21682

[Andrew Hayzen]

@alexmurray, hey, I believe that commit was reverted later as it caused
a behavioural regression? The Github advisory
(https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx)
was changed to point to a different commit
(https://github.com/flatpak/flatpak/commit/5709f1aaed6579f0136976e14e7f3cae399134ca).

When creating that debdiff, if i recall correctly I went though the
commits in this branch
https://github.com/flatpak/flatpak/commits/flatpak-1.10.x combined with
referring to the github advisories and then skipped the "Make
--nofilesystem=host/home remove access to subdirs of those"
(307ee18dd62f65c1319594501d01bbdb10f88ab8) as it was reverted later with
"Revert "Make --nofilesystem=host/home remove access to subdirs of
those"" (ed91bba615d4e50ccd7de53ca9861e367175bbfb).

Please correct me if you think i've missed something :-)

In the github advisory
(https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx)
there are two commits for flatpak-builder so this could also be done.

Also note I tried looking at focal/bionic but there are a large amount
of merge conflicts due to substantial change in the codebase and I'm not
familiar enough with GObject/GLib etc to rewrite that code.

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

Title:
  Update for CVE-2021-43860 and CVE-2022-21682

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


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

[Bug 1962304] [NEW] package ubuntustudio-branding-common 20.04.1 failed to install/upgrade: installed ubuntustudio-branding-common package post-installation script subprocess returned error exit statu

[Andrew]

Public bug reported:

I'm on a Raspberry Pi 4 Cannakit build. I have had some troubles with a
lot of various packages. I'm not sure if there's a way around this. I
thought I read somewhere you have to use curl for everything, but I had
trouble with that too. I'll keep playing around with it and see what I
can find.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: ubuntustudio-branding-common 20.04.1
ProcVersionSignature: Ubuntu 5.4.0-1052.58-raspi 5.4.162
Uname: Linux 5.4.0-1052-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: arm64
CasperMD5CheckResult: skip
Date: Fri Feb 25 11:20:23 2022
DuplicateSignature:
 package:ubuntustudio-branding-common:20.04.1
 Setting up ubuntustudio-branding-common (20.04.1) ...
 /var/lib/dpkg/info/ubuntustudio-branding-common.postinst: 22: update-grub: not 
found
 dpkg: error processing package ubuntustudio-branding-common (--configure):
  installed ubuntustudio-branding-common package post-installation script 
subprocess returned error exit status 127
ErrorMessage: installed ubuntustudio-branding-common package post-installation 
script subprocess returned error exit status 127
ImageMediaBuild: 20210819.1
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.1
 apt  2.0.6
SourcePackage: ubuntustudio-look
Title: package ubuntustudio-branding-common 20.04.1 failed to install/upgrade: 
installed ubuntustudio-branding-common package post-installation script 
subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntustudio-look (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 arm64-image focal need-duplicate-check 
raspi-image uec-images

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

Title:
  package ubuntustudio-branding-common 20.04.1 failed to
  install/upgrade: installed ubuntustudio-branding-common package post-
  installation script subprocess returned error exit status 127

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


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

[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])

[Andrew Cloke]

Marking as "incomplete" while waiting for input from Power MMU experts.

** Changed in: ubuntu-power-systems
   Status: Confirmed => Incomplete

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

Title:
  IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash
  P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])

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


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

[Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce

[Andrew Cloke]

** Changed in: kunpeng920/ubuntu-21.10
   Status: Fix Committed => 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/1933301

Title:
  [uacc-0623] hisi_sec2  fail to alloc uacce

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


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

[Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32

[Andrew Cloke]

** Changed in: kunpeng920
   Importance: Undecided => Low

** Changed in: kunpeng920
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25
  report incorrect sched domain for cpu#32

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


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

[Bug 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

https://github.com/OSGeo/gdal/issues/5324 is a result of this and the
upstream https://github.com/libexpat/libexpat/issues/501

** Bug watch added: github.com/OSGeo/gdal/issues #5324
   https://github.com/OSGeo/gdal/issues/5324

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

Title:
  `libexpat1-dev` CMake configuration error

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


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

[Bug 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

** Bug watch added: github.com/libexpat/libexpat/issues #501
   https://github.com/libexpat/libexpat/issues/501

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

Title:
  `libexpat1-dev` CMake configuration error

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


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

[Bug 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

** Also affects: expat via
   https://github.com/libexpat/libexpat/issues/501
   Importance: Unknown
   Status: Unknown

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

Title:
  `libexpat1-dev` CMake configuration error

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


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

[Bug 1751954] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously

[Andrew-Q]

It says above fix released in August, however I still have the bad
wording and it has caught me out today.  I'm running Ubuntu 20.04.03
gnome 3.36.8.  Why has the fix not reached me yet please?

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

Title:
  Bluetooth and Wi-Fi items in Power are worded ambiguously

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


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

[Bug 1953386] Re: hisi_sas driver may oops in prep_ssp_v3_hw()

[Andrew Cloke]

** Changed in: kunpeng920/ubuntu-18.04
   Status: Fix Committed => Fix Released

** Changed in: kunpeng920
   Status: Fix Committed => 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/1953386

Title:
  hisi_sas driver may oops in prep_ssp_v3_hw()

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


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

[Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

[Andrew Platt]

Having a similar issue on my ASUS Zenbook UX434, also using the ALC294
as above, Kernel: 5.13.0-28-generic.

In my case after a reboot from my Windows 10 dual boot the audio out is
fine, but the microphone has very loud crackling which makes it
unusable. The problem isn't fixed by a reboot but after a full shutdown
and restart the problem seems to go away. Thanks to Hilikus for the
workaround!

Had an identical problem on Kubuntu 20.04 and now ZorinOS 16 - clearly
this issue isn't entirely fixed even with more recent kernel patches.

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

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


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

[Bug 1959926] [NEW] Version v1.9 has compiler bug when reading from 64-bit BAR

[Andrew]

Public bug reported:

There's a known issue in nvme-cli where the compiler optimizes out BAR
accesses into a single 64B read rather than 2 32-bits. This causes some
devices to hang and reboot the system. This bug was fixed in version
v1.14. The ubuntu supported version should be >= v1.14.

** Affects: nvme-cli (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/1959926

Title:
  Version v1.9 has compiler bug when reading from 64-bit BAR

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


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

[Bug 1959872] [NEW] Printer LJ1018 not printing

[Andrew Ohis]

Public bug reported:

it doesn't report any error message, the printer doesnt just print

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  3 10:01:03 2022
InstallationDate: Installed on 2021-11-22 (72 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Lpstat: device for HP-LaserJet-1018: hp:/usb/HP_LaserJet_1018?serial=KP218R3
MachineType: LENOVO 20AL008YUS
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-LaserJet-1018.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-LaserJet-1018.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-43-generic 
root=UUID=9ccd4b52-6d4c-404c-8cc0-4c9c00f3045e ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/10/2016
dmi.bios.release: 2.35
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET85WW (2.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AL008YUS
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.17
dmi.modalias: 
dmi:bvnLENOVO:bvrGIET85WW(2.35):bd03/10/2016:br2.35:efr1.17:svnLENOVO:pn20AL008YUS:pvrThinkPadX240:skuLENOVO_MT_20AL_BU_Think_FM_ThinkPadX240:rvnLENOVO:rn20AL008YUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AL008YUS
dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Printer LJ1018 not printing

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


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

[Bug 1959513] [NEW] image crashes image viewer

[andrew g]

Public bug reported:

when viewing pixie02.jpg image crashes the image viewer

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: eog 3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 30 10:57:16 2022
ExecutablePath: /usr/bin/eog
InstallationDate: Installed on 2022-01-30 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: eog
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "pixie02.jpg"
   
https://bugs.launchpad.net/bugs/1959513/+attachment/5558270/+files/pixie02.jpg

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

Title:
  image crashes image viewer

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


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

[Bug 1959512] [NEW] playing a video cause the video player to crash

[andrew g]

Public bug reported:

when attempting to play the vp8.webm file causes the Videos file to
crash

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgstreamer1.0-0 1.16.2-2
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 30 10:36:31 2022
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2022-01-30 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


** Tags: amd64 apport-bug focal

** Attachment added: "vp8.webm"
   https://bugs.launchpad.net/bugs/1959512/+attachment/5558263/+files/vp8.webm

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

Title:
   playing a video cause the video player to crash

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


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

[Bug 1957716] Re: Update for CVE-2021-43860 and CVE-2022-21682

[Andrew Hayzen]

Please find attached the debdiff for Ubuntu 21.10 impish. I have
performed some testing in a VM and built in a PPA.

** Attachment added: "Impish CVE debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1957716/+attachment/5557881/+files/flatpak_impish_lp1957716.debdiff.gz

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

Title:
  Update for CVE-2021-43860 and CVE-2022-21682

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


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

[Bug 1957716] Re: Update for CVE-2021-43860 and CVE-2022-21682

[Andrew Hayzen]

** Changed in: flatpak (Ubuntu Impish)
   Status: New => In Progress

** Changed in: flatpak (Ubuntu Impish)
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

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

Title:
  Update for CVE-2021-43860 and CVE-2022-21682

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


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

[Bug 1958880] [NEW] keytool error: java.io.IOException: keystore password was incorrect

[Andrew Welham]

Public bug reported:

I've trying the following commands (passwords are fake) to convert lets
encrypt certs for tp-link omada.

openssl pkcs12 -export -in fullchain.pem -inkey privkey.pem -name eap -out 
keystore.p12 -password pass:myeapc
keytool -storetype jks -importkeystore -destkeypass tplink -deststorepass 
tplink -destkeystore eap.keystore -srckeystore keystore.p12 -srcstoretype 
PKCS12 -srcstorepass myeapc

This works on focal, but on jammy I get keytool error:
java.io.IOException: keystore password was incorrect

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: openjdk-8-jre-headless 8u312-b07-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Jan 24 14:29:12 2022
InstallationDate: Installed on 2022-01-03 (20 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211029)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: openjdk-8
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openjdk-8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages uec-images

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

Title:
  keytool error: java.io.IOException: keystore password was incorrect

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


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

[Bug 1957716] Re: Update for CVE-2021-43860 and CVE-2022-21682

[Andrew Hayzen]

** Description changed:

  [Links]
  https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j ( 
CVE-2021-43860 )
  https://security-tracker.debian.org/tracker/CVE-2021-43860
  
  https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx ( 
CVE-2022-21682 )
  https://security-tracker.debian.org/tracker/CVE-2022-21682
  
  [Impact]
  Versions in Ubuntu right now:
  Jammy: 1.12.2-2
  Impish: 1.10.2-3ubuntu0.1
  Focal: 1.6.5-0ubuntu0.4
  Bionic: 1.0.9-0ubuntu0.4
  
  Affected versions:
  all
  
  Patched versions:
- 1.12.3, 1.10.6
+ 1.12.4, 1.10.7
  
  [Test Case]
  Unknown
  
  [Regression Potential]
  Flatpak has a test suite, which is run on build across all relevant 
architectures and passes.
  
  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
  
  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .
  
  Regression potential is low, and upstream is very responsive to any
  issues raised.
  
  [Patches]
  The first CVE has 4 patches (+ 1 test patch), the second CVE has 1 patch (+ 6 
doc/test patches).
  
  [Other Information]
  
  For the first advisory with the CVE:
  
  Ryan Gonzalez discovered that Flatpak doesn't properly validate that the
  permissions displayed to the user for an app at install time match the
  actual permissions granted to the app at runtime, in the case that
  there's a null byte in the metadata file of an app. Therefore apps can
  grant themselves permissions without the consent of the user.
  
  Flatpak shows permissions to the user during install by reading them
  from the "xa.metadata" key in the commit metadata. This cannot contain a
  null terminator, because it is an untrusted GVariant. Flatpak compares
  these permissions to the actual metadata, from the "metadata" file to
  ensure it wasn't lied to.
  
  However, the actual metadata contents are loaded in several places where
  they are read as simple C-style strings. That means that, if the
  metadata file includes a null terminator, only the content of the file
  from before the terminator gets compared to xa.metadata. Thus, any
  permissions that appear in the metadata file after a null terminator are
  applied at runtime but not shown to the user. Maliciously crafted apps
  can use this to give themselves hidden permissions.
  
  In addition, a similar weakness was discovered, where if the permissions
  in the summary metadata are invalid, they would not be displayed to the
  user, but the the actual permissions would be granted, even though it
  didn't match the invalid version.
  
- 
  For the second advisory:
  
  flatpak-builder applies finish-args last in the build. At this point the
  build directory will have the full access that is specified in the
  manifest, so running flatpak build against it will gain that
  permissions. Normally this will not be done, so this is not problem.
  However, if --mirror-screenshots-url is specified, then flatpak-builder
  will launch flatpak build --nofilesystem=host appstream-utils mirror-
  screenshots after finalization, which can lead to issues even with the
  --nofilesystem=host protection.
  
  There are two issues:
  
- --nofilesystem=host only overrides the access to the full host. The app 
can still request access to a specific directory, like --filesystem=~/some-dir, 
which is not affected by this.
- If a filesystem is specified like --filesystem=~/foobar:create, then that 
directory will be created before running the command.
+ --nofilesystem=host only overrides the access to the full host. The app 
can still request access to a specific directory, like --filesystem=~/some-dir, 
which is not affected by this.
+ If a filesystem is specified like --filesystem=~/foobar:create, then that 
directory will be created before running the command.
  
  In normal use the only issue is that these empty directories can be
  created wherever the user has write permissions. However, a malicious
  application could replace the appstream-util binary and potentially do
  something more hostile.

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

Title:
  Update for CVE-2021-43860 and CVE-2022-21682

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


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

[Bug 1957716] Re: Update for CVE-2021-43860 and CVE-2022-21682

[Andrew Hayzen]

** Description changed:

  [Links]
  https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j ( 
CVE-2021-43860 )
  https://security-tracker.debian.org/tracker/CVE-2021-43860
  
  https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx ( 
CVE-2022-21682 )
  https://security-tracker.debian.org/tracker/CVE-2022-21682
- 
  
  [Impact]
  Versions in Ubuntu right now:
  Jammy: 1.12.2-2
  Impish: 1.10.2-3ubuntu0.1
  Focal: 1.6.5-0ubuntu0.4
  Bionic: 1.0.9-0ubuntu0.4
  
  Affected versions:
  all
  
  Patched versions:
  1.12.3, 1.10.6
  
  [Test Case]
  Unknown
  
  [Regression Potential]
  Flatpak has a test suite, which is run on build across all relevant 
architectures and passes.
  
  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
  
  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .
  
  Regression potential is low, and upstream is very responsive to any
  issues raised.
  
  [Patches]
- There are two separate github advisories but only one of them has a CVE.
- 
- The advisory with the CVE has 5 patches, the other has 2 patches.
+ The first CVE has 4 patches (+ 1 test patch), the second CVE has 1 patch (+ 6 
doc/test patches).
  
  [Other Information]
  
  For the first advisory with the CVE:
  
  Ryan Gonzalez discovered that Flatpak doesn't properly validate that the
  permissions displayed to the user for an app at install time match the
  actual permissions granted to the app at runtime, in the case that
  there's a null byte in the metadata file of an app. Therefore apps can
  grant themselves permissions without the consent of the user.
  
  Flatpak shows permissions to the user during install by reading them
  from the "xa.metadata" key in the commit metadata. This cannot contain a
  null terminator, because it is an untrusted GVariant. Flatpak compares
  these permissions to the actual metadata, from the "metadata" file to
  ensure it wasn't lied to.
  
  However, the actual metadata contents are loaded in several places where
  they are read as simple C-style strings. That means that, if the
  metadata file includes a null terminator, only the content of the file
  from before the terminator gets compared to xa.metadata. Thus, any
  permissions that appear in the metadata file after a null terminator are
  applied at runtime but not shown to the user. Maliciously crafted apps
  can use this to give themselves hidden permissions.
  
  In addition, a similar weakness was discovered, where if the permissions
  in the summary metadata are invalid, they would not be displayed to the
  user, but the the actual permissions would be granted, even though it
  didn't match the invalid version.
  
+ 
  For the second advisory:
  
  flatpak-builder applies finish-args last in the build. At this point the
  build directory will have the full access that is specified in the
  manifest, so running flatpak build against it will gain that
  permissions. Normally this will not be done, so this is not problem.
  However, if --mirror-screenshots-url is specified, then flatpak-builder
  will launch flatpak build --nofilesystem=host appstream-utils mirror-
  screenshots after finalization, which can lead to issues even with the
  --nofilesystem=host protection.
  
- These changes result in a behaviour change as debian have noted in their
- changelog:
+ There are two issues:
  
-   * Behaviour changes, as a result of how GHSA-8ch7-5j3h-g4fx was fixed:
- - --nofilesystem=host is now special-cased to negate all --filesystem
-   permissions. Previously, it would cancel out --filesystem=host but
-   not --filesystem=/some/dir.
- - --nofilesystem=home is now special-cased to negate several
-   home-directory-related filesystem permssions such as
-   --filesystem=xdg-config/foo, not just --filesystem=host.
+ --nofilesystem=host only overrides the access to the full host. The app 
can still request access to a specific directory, like --filesystem=~/some-dir, 
which is not affected by this.
+ If a filesystem is specified like --filesystem=~/foobar:create, then that 
directory will be created before running the command.
+ 
+ In normal use the only issue is that these empty directories can be
+ created wherever the user has write permissions. However, a malicious
+ application could replace the appstream-util binary and potentially do
+ something more hostile.

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

Title:
  Update for CVE-2021-43860 and CVE-2022-21682

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


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

[Bug 1957716] Re: Update for CVE-2021-43860 and CVE-2022-21682

[Andrew Hayzen]

Note that Jammy now has 1.12.3-1 so is fixed.

** Summary changed:

- Update for CVE-2021-43860 and second github advisory
+ Update for CVE-2021-43860 and CVE-2022-21682

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

** Description changed:

  [Links]
- https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j
- https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx
+ https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j ( 
CVE-2021-43860 )
  https://security-tracker.debian.org/tracker/CVE-2021-43860
+ 
+ https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx ( 
CVE-2022-21682 )
+ https://security-tracker.debian.org/tracker/CVE-2022-21682
+ 
  
  [Impact]
  Versions in Ubuntu right now:
  Jammy: 1.12.2-2
  Impish: 1.10.2-3ubuntu0.1
  Focal: 1.6.5-0ubuntu0.4
  Bionic: 1.0.9-0ubuntu0.4
  
  Affected versions:
- all
+ all
  
  Patched versions:
- 1.12.3, 1.10.6
+ 1.12.3, 1.10.6
  
  [Test Case]
  Unknown
  
  [Regression Potential]
  Flatpak has a test suite, which is run on build across all relevant 
architectures and passes.
  
  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
  
  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .
  
  Regression potential is low, and upstream is very responsive to any
  issues raised.
  
  [Patches]
  There are two separate github advisories but only one of them has a CVE.
  
  The advisory with the CVE has 5 patches, the other has 2 patches.
- 
  
  [Other Information]
  
  For the first advisory with the CVE:
  
  Ryan Gonzalez discovered that Flatpak doesn't properly validate that the
  permissions displayed to the user for an app at install time match the
  actual permissions granted to the app at runtime, in the case that
  there's a null byte in the metadata file of an app. Therefore apps can
  grant themselves permissions without the consent of the user.
  
  Flatpak shows permissions to the user during install by reading them
  from the "xa.metadata" key in the commit metadata. This cannot contain a
  null terminator, because it is an untrusted GVariant. Flatpak compares
  these permissions to the actual metadata, from the "metadata" file to
  ensure it wasn't lied to.
  
  However, the actual metadata contents are loaded in several places where
  they are read as simple C-style strings. That means that, if the
  metadata file includes a null terminator, only the content of the file
  from before the terminator gets compared to xa.metadata. Thus, any
  permissions that appear in the metadata file after a null terminator are
  applied at runtime but not shown to the user. Maliciously crafted apps
  can use this to give themselves hidden permissions.
  
  In addition, a similar weakness was discovered, where if the permissions
  in the summary metadata are invalid, they would not be displayed to the
  user, but the the actual permissions would be granted, even though it
  didn't match the invalid version.
  
- 
  For the second advisory:
  
  flatpak-builder applies finish-args last in the build. At this point the
  build directory will have the full access that is specified in the
  manifest, so running flatpak build against it will gain that
  permissions. Normally this will not be done, so this is not problem.
  However, if --mirror-screenshots-url is specified, then flatpak-builder
  will launch flatpak build --nofilesystem=host appstream-utils mirror-
  screenshots after finalization, which can lead to issues even with the
  --nofilesystem=host protection.
  
- 
  These changes result in a behaviour change as debian have noted in their
  changelog:
  
-   * Behaviour changes, as a result of how GHSA-8ch7-5j3h-g4fx was fixed:
- - --nofilesystem=host is now special-cased to negate all --filesystem
-   permissions. Previously, it would cancel out --filesystem=host but
-   not --filesystem=/some/dir.
- - --nofilesystem=home is now special-cased to negate several
-   home-directory-related filesystem permssions such as
-   --filesystem=xdg-config/foo, not just --filesystem=host.
+   * Behaviour changes, as a result of how GHSA-8ch7-5j3h-g4fx was fixed:
+ - --nofilesystem=host is now special-cased to negate all --filesystem
+   permissions. Previously, it would cancel out --filesystem=host but
+   not --filesystem=/some/dir.
+ - --nofilesystem=home is now special-cased to negate several
+   home-directory-related filesystem permssions such as
+   --filesystem=xdg-config/foo, not just --filesystem=host.

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

Title:
  Update for CVE-2021-43860 and CVE-2022-21682

To manage notifications about this bug go to:

[Bug 1798089] Re: libclamunrar needs updated to 0.103.x to match clamav

[Andrew Aitchison]

Should be updated in sync with
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1957996
to either 0.103.5 or 0.104.2

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

Title:
  libclamunrar needs updated to 0.103.x to match clamav

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


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

[Bug 1957996] Re: CVE-2022-20698 ClamAV update

[Andrew Aitchison]

libclamunrar should ideally be updated in sync with this, see
https://bugs.launchpad.net/ubuntu/+source/libclamunrar/+bug/1798089

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

Title:
  CVE-2022-20698 ClamAV update

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


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

[Bug 1957996] Re: CVE-2022-20698 ClamAV update

[Andrew Aitchison]

** Information type changed from Private Security to Public Security

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

Title:
  CVE-2022-20698 ClamAV update

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


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

[Bug 1957716] Re: Update for CVE-2021-43860 and second github advisory

[Andrew Hayzen]

** Changed in: flatpak (Ubuntu)
   Status: New => 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/1957716

Title:
  Update for CVE-2021-43860 and second github advisory

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


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

[Bug 1957716] Re: Update for CVE-2021-43860 and second github advisory

[Andrew Hayzen]

Can someone with permission add impish, focal, bionic as affected
series? (hirsute i assume we can skip as it's about to EOL).

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

Title:
  Update for CVE-2021-43860 and second github advisory

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


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

[Bug 1957716] [NEW] Update for CVE-2021-43860 and second github advisory

[Andrew Hayzen]

*** This bug is a security vulnerability ***

Public security bug reported:

[Links]
https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j
https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx
https://security-tracker.debian.org/tracker/CVE-2021-43860

[Impact]
Versions in Ubuntu right now:
Jammy: 1.12.2-2
Impish: 1.10.2-3ubuntu0.1
Focal: 1.6.5-0ubuntu0.4
Bionic: 1.0.9-0ubuntu0.4

Affected versions:
all

Patched versions:
1.12.3, 1.10.6

[Test Case]
Unknown

[Regression Potential]
Flatpak has a test suite, which is run on build across all relevant 
architectures and passes.

There is also a manual test plan
https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .

Flatpak has autopkgtests enabled
http://autopkgtest.ubuntu.com/packages/f/flatpak .

Regression potential is low, and upstream is very responsive to any
issues raised.

[Patches]
There are two separate github advisories but only one of them has a CVE.

The advisory with the CVE has 5 patches, the other has 2 patches.


[Other Information]

For the first advisory with the CVE:

Ryan Gonzalez discovered that Flatpak doesn't properly validate that the
permissions displayed to the user for an app at install time match the
actual permissions granted to the app at runtime, in the case that
there's a null byte in the metadata file of an app. Therefore apps can
grant themselves permissions without the consent of the user.

Flatpak shows permissions to the user during install by reading them
from the "xa.metadata" key in the commit metadata. This cannot contain a
null terminator, because it is an untrusted GVariant. Flatpak compares
these permissions to the actual metadata, from the "metadata" file to
ensure it wasn't lied to.

However, the actual metadata contents are loaded in several places where
they are read as simple C-style strings. That means that, if the
metadata file includes a null terminator, only the content of the file
from before the terminator gets compared to xa.metadata. Thus, any
permissions that appear in the metadata file after a null terminator are
applied at runtime but not shown to the user. Maliciously crafted apps
can use this to give themselves hidden permissions.

In addition, a similar weakness was discovered, where if the permissions
in the summary metadata are invalid, they would not be displayed to the
user, but the the actual permissions would be granted, even though it
didn't match the invalid version.


For the second advisory:

flatpak-builder applies finish-args last in the build. At this point the
build directory will have the full access that is specified in the
manifest, so running flatpak build against it will gain that
permissions. Normally this will not be done, so this is not problem.
However, if --mirror-screenshots-url is specified, then flatpak-builder
will launch flatpak build --nofilesystem=host appstream-utils mirror-
screenshots after finalization, which can lead to issues even with the
--nofilesystem=host protection.


These changes result in a behaviour change as debian have noted in their
changelog:

  * Behaviour changes, as a result of how GHSA-8ch7-5j3h-g4fx was fixed:
- --nofilesystem=host is now special-cased to negate all --filesystem
  permissions. Previously, it would cancel out --filesystem=host but
  not --filesystem=/some/dir.
- --nofilesystem=home is now special-cased to negate several
  home-directory-related filesystem permssions such as
  --filesystem=xdg-config/foo, not just --filesystem=host.

** Affects: flatpak (Ubuntu)
 Importance: Undecided
 Assignee: Andrew Hayzen (ahayzen)
 Status: In Progress

** Information type changed from Public to Public Security

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

** Changed in: flatpak (Ubuntu)
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

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

Title:
  Update for CVE-2021-43860 and second github advisory

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


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

[Bug 1957024] Re: pam-mkhomedir does not honor private home directories

[Andrew Lowther]

Here is a demonstration as requested in Discourse.  These steps were run
on a stock image of Ubuntu Impish taken from https://cloud-
images.ubuntu.com/impish/current/.

Showing the inconsistent behavior of the default settings if the goal is
private home directories.  Both adduser and useradd create a home
directory that is private but pam_mkhomedir.so does not.

# enable pam_mkhomedir.so configuration
pam-auth-update --enable mkhomedir
# create a user with adduser that creates the home directory
adduser --disabled-password --gecos adduser homemadebyadduser
# create a user with useradd that creates the home directory
useradd --create-home homemadebyuseradd
# create a user with useradd that does *not* create the home directory so that 
pam_mkhomedir.so can create it
useradd --no-create-home homemadebymkhomedir
# trigger pam_mkhomedir.so to create the home directory
su - homemadebymkhomedir -c exit

The result is inconsistent permissions on the home directories.
root@ubuntu:~# ls -al /home
total 24
drwxr-xr-x  6 rootroot4096 Jan 11 03:27 .
drwxr-xr-x 19 rootroot4096 Jan 11 03:13 ..
drwxr-x---  2 homemadebyadduser   homemadebyadduser   4096 Jan 11 03:20 
homemadebyadduser
drwxr-xr-x  2 homemadebymkhomedir homemadebymkhomedir 4096 Jan 11 03:27 
homemadebymkhomedir
drwxr-x---  2 homemadebyuseradd   homemadebyuseradd   4096 Jan 11 03:23 
homemadebyuseradd
drwxr-x---  4 ubuntu  ubuntu  4096 Jan 11 03:15 ubuntu


Configuring pam_mkhomedir.so to be consistent with the other tools.

# update pam_mkhomedir.so configuration
sed -i -e "s/pam_mkhomedir.so$/pam_mkhomedir.so umask=0027/" 
/usr/share/pam-configs/mkhomedir
# enable mkhomedir again
pam-auth-update --enable mkhomedir
# create a user with useradd that does *not* create the home directory so that 
pam_mkhomedir.so can create it
useradd --no-create-home homemadebymkhomedirpatch
# trigger pam_mkhomedir.so to create the home directory
su - homemadebymkhomedirpatch -c exit

The result is the permissions are consistent with the other tools.
root@ubuntu:~# ls -l /home/
total 20
drwxr-x--- 2 homemadebyadduserhomemadebyadduser4096 Jan 11 
03:20 homemadebyadduser
drwxr-xr-x 2 homemadebymkhomedir  homemadebymkhomedir  4096 Jan 11 
03:27 homemadebymkhomedir
drwxr-x--- 2 homemadebymkhomedirpatch homemadebymkhomedirpatch 4096 Jan 11 
03:36 homemadebymkhomedirpatch
drwxr-x--- 2 homemadebyuseraddhomemadebyuseradd4096 Jan 11 
03:23 homemadebyuseradd
drwxr-x--- 4 ubuntu   ubuntu   4096 Jan 11 
03:15 ubuntu

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

Title:
  pam-mkhomedir does not honor private home directories

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


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

[Bug 124406] Re: Keyboard keys get stuck and repeat

[Andrew Yakovlev]

I have a keyboard a4tech KV-300h and the bug reproduce on windows too. I have 
already tried to replace to another a new keyboard. The problem isn't gone.
I found out if I use embedded USB port of keyboard to connect a mouse then the 
problem reproduce very often.
Also I tested my keyboard on macbook pro. There is everything works fine. 

System:
  Host: adrug-X470-AORUS-ULTRA-GAMING Kernel: 5.13.0-23-generic x86_64 
  bits: 64 compiler: N/A Desktop: Cinnamon 5.0.7 Distro: Linux Mint 20.2 Uma 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: Gigabyte product: X470 AORUS ULTRA GAMING v: N/A 
  serial: N/A 
  Mobo: Gigabyte model: X470 AORUS ULTRA GAMING-CF v: x.x serial: N/A 
  UEFI: American Megatrends LLC. v: F61 date: 07/13/2021 
CPU:
  Topology: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 
  L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 86394 
  Speed: 2200 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 2200 2: 2189 
  3: 2199 4: 2200 5: 2199 6: 2199 7: 2199 8: 2200 9: 2249 10: 2198 11: 2200 
  12: 2199 
Graphics:
  Device-1: AMD vendor: Gigabyte driver: amdgpu v: kernel bus ID: 0c:00.0 
  Display: server: X.Org 1.20.13 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,radeon,vesa resolution: 2560x1080~60Hz 
  OpenGL: renderer: AMD Radeon RX 6600 XT (DIMGREY_CAVEFISH DRM 3.41.0 
  5.13.0-23-generic LLVM 12.0.1) 
  v: 4.6 Mesa 21.3.0-devel direct render: Yes

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

Title:
  Keyboard keys get stuck and repeat

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


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

[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time

[Andrew Enderson]

Same issues here on Kubuntu 21.10 after upgrade to 5.13.0-23-generic:
  amdgpu: failed to write reg  wait reg 

AMD Ryzen 7 3700U w/ Radeon Vega 10 Mobile graphics

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

Title:
  amdgpu hangs for 90 seconds at a time

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


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

[Bug 1956243] [NEW] Ping give socket error initially if IPv6 is disabled

[Andrew Welham]

Public bug reported:

With IpV6 enabled everything works well. However if you disable ipv6 by editing 
/etc/default/grub with the following entry
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
 then when you ping there is an initial socket error 

ping localhost
ping: socket: Address family not supported by protocol
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms


however ping -4 works

ping -4 localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms

so it looks like ping is trying ipv6 first and not detecting that its
disabled.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: iputils-ping 3:20210202-1build1
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Jan  3 17:42:07 2022
InstallationDate: Installed on 2022-01-03 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211029)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy third-party-packages uec-images

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

Title:
  Ping give socket  error initially if IPv6 is disabled

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


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

[Bug 1923007] Re: graphite-carbon 1.1.4-2 crashes

[Steven ANDREW Spring]

if you need the fix for now, I temp added Hirsute to sources.list and
issued,  sudo apt-get --only-upgrade true install graphite-carbon, of
course removing the hirsute repo's after. I will report everything
remained stable and has worked properly since. If you would like I can
post an exact guide of what I did, and the resulting output for proof.

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

Title:
  graphite-carbon 1.1.4-2 crashes

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


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

[Bug 1955361] [NEW] [Jammy] steam-installer doesn't appear in software centres due to appdata changes

[Andrew Hayzen]

Public bug reported:

Since the appdata changes in the recent upload, steam-installer doesn't
appear in the software stores.

Lets revert back to our downstream changes for now as this was an
experiment.

** Affects: steam (Ubuntu)
 Importance: Undecided
 Assignee: Andrew Hayzen (ahayzen)
 Status: In Progress

** Changed in: steam (Ubuntu)
   Status: New => In Progress

** Changed in: steam (Ubuntu)
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

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

Title:
  [Jammy] steam-installer doesn't appear in software centres due to
  appdata changes

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


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

[Bug 1951894] Re: Merge steam 1.0.0.74-1 from debian sid to ubuntu jammy

[Andrew Hayzen]

** Summary changed:

- Merge steam 1.0.0.73-1 from debian sid to ubuntu jammy
+ Merge steam 1.0.0.74-1 from debian sid to ubuntu jammy

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

Title:
  Merge steam 1.0.0.74-1 from debian sid to ubuntu jammy

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


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

[Bug 1946578] Re: Update for CVE-2021-41133

[Andrew Hayzen]

I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Impish VM and things are working normally.

$ apt policy flatpak
flatpak:
  Installed: 1.10.2-3ubuntu0.1
  Candidate: 1.10.2-3ubuntu0.1
  Version table:
 *** 1.10.2-3ubuntu0.1 500
500 http://ppa.launchpad.net/ubuntu-security-proposed/ppa/ubuntu 
impish/main amd64 Packages
100 /var/lib/dpkg/status
 1.10.2-3 500
500 http://gb.archive.ubuntu.com/ubuntu impish/universe amd64 Packages

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

Title:
  Update for CVE-2021-41133

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


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

[Bug 1946578] Re: Update for CVE-2021-41133

[Andrew Hayzen]

I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Hirsute VM and things are working normally.

$ apt policy flatpak
flatpak:
  Installed: 1.10.2-1ubuntu1.1
  Candidate: 1.10.2-1ubuntu1.1
  Version table:
 *** 1.10.2-1ubuntu1.1 500
500 http://ppa.launchpad.net/ubuntu-security-proposed/ppa/ubuntu 
hirsute/main amd64 Packages
100 /var/lib/dpkg/status
 1.10.2-1ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages

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

Title:
  Update for CVE-2021-41133

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


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

[Bug 1946578] Re: Update for CVE-2021-41133

[Andrew Hayzen]

I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Bionic VM and things are working normally.

$ apt policy flatpak
flatpak:
  Installed: 1.0.9-0ubuntu0.4
  Candidate: 1.0.9-0ubuntu0.4
  Version table:
 *** 1.0.9-0ubuntu0.4 500
500 http://ppa.launchpad.net/ubuntu-security-proposed/ppa/ubuntu 
bionic/main amd64 Packages
100 /var/lib/dpkg/status
 1.0.9-0ubuntu0.3 500
500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages
 0.11.3-3 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

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

Title:
  Update for CVE-2021-41133

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


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

[Bug 1946578] Re: Update for CVE-2021-41133

[Andrew Hayzen]

I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Focal VM and things are working normally.

$ apt policy flatpak
flatpak:
  Installed: 1.6.5-0ubuntu0.4
  Candidate: 1.6.5-0ubuntu0.4
  Version table:
 *** 1.6.5-0ubuntu0.4 500
500 http://ppa.launchpad.net/ubuntu-security-proposed/ppa/ubuntu 
focal/main amd64 Packages
100 /var/lib/dpkg/status
 1.6.5-0ubuntu0.3 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 
Packages
 1.6.3-1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

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

Title:
  Update for CVE-2021-41133

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


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

[Bug 1946578] Re: Update for CVE-2021-41133

[Andrew Hayzen]

Sorry, I somehow missed comment 11 and was thinking we were still
waiting for the libseccomp decision. I'll check the packages now!

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

Title:
  Update for CVE-2021-41133

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


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

[Bug 1951696] Re: kernel: general protection fault

[Andrew Heninger]

Happened again, with associated stuff making it into syslog. File
crashlog2 attached.

** Attachment added: "crashlog2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951696/+attachment/5546513/+files/crashlog2

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

Title:
  kernel:  general protection fault

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


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

[Bug 1951894] Re: Merge steam 1.0.0.73-1 from debian sid to ubuntu jammy

[Andrew Hayzen]

** Summary changed:

-  Merge steam 1.0.0.72-2 from debian sid to ubuntu jammy
+ Merge steam 1.0.0.73-1 from debian sid to ubuntu jammy

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

Title:
  Merge steam 1.0.0.73-1 from debian sid to ubuntu jammy

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


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

[Bug 1953339] Re: Failure to install ceph client on ARM64

[Andrew Cloke]

** Changed in: ceph (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
(unassigned)

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

Title:
  Failure to install ceph client on ARM64

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


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

[Bug 1953116] [NEW] Mouse not staying powered

[Andrew]

Public bug reported:

Mouse receives power via USB when plugged in, immediately loses it.
Mouse on other devices, USB port provides power to other mice.

Manufacturer: Microsoft  
Model: Microsoft Ergonomic Mouse (Wired)
Connection: USB
Mechanism: Optical
Buttons: 4 Buttons + 1 Scrollwheel

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151
Uname: Linux 5.4.0-91-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  3 00:14:13 2021
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:0810]
InstallationDate: Installed on 2021-11-01 (32 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic 
root=UUID=e3adb636-cdf3-436a-8963-358dfa8e0a4e ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 05/15/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 0D65FD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0D65FD:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Mouse not staying powered

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


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

[Bug 371221] Re: [pbuilder-dist] Use packages from ~/pbuilder/dist_result to satisfy deps

[Andrew Bate]

I am currently working around this bug also.

The suggested workaround to generate a local repository of the packages
that are built in ~/pbuilder/dist_result is a good one, but it is
fragile because we are forced to assume the location of
~/pbuilder/dist_result when writing our ~/.pbuilderrc and hooks.

This is because pbuilder-dist does not export an environment variable
with the build result directory.

Thus if someone were to call pbuilder-dist with the --buildresult option
then everything will break.

If pbuilder-dist exported the build result directory as an environment
variable that would be an improvement because it could be used to write
a more robust ~/.pbuilderrc.

However, the real fix here is to accept the patch by Benjamin Drung.
With that patch there would be no need for workarounds or hacks.

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

Title:
  [pbuilder-dist] Use packages from ~/pbuilder/dist_result to satisfy
  deps

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


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

[Bug 1004579] Re: [pbuilder-dist] overwrite OTHERMIRROR set in ~/.pbuilderrc

[Andrew Bate]

Adding to my previous comment, I can also see that the documentation is
wrong.

The page https://wiki.ubuntu.com/PbuilderHowto#Differences_with_pbuilder
says that:

[QUOTE]
pbuilder-dist does apparently not yet support all kinds of operations. The 
following doesn't work correctly for example:

sudo pbuilder-dist eoan i386 update --override-config --othermirror "deb
http://ppa.launchpad.net/cae-team/ppa/ubuntu eoan main"

So if you want to add a repository, you will have to use "OTHERMIRROR"
in ~/.pbuilderrc as follows:

OTHERMIRROR="deb http://ppa.launchpad.net/cae-team/ppa/ubuntu eoan main"
[/QUOTE]

But adding OTHERMIRROR to ~/.pbuilderrc has no effect, as was originally
reported.

Basic tracing shows that this is still the case in focal (20.04).

My workaround has been to add a hook directory ~/.pbuilderrc by adding the line:
HOOKDIR="$HOME/.pbuilder-hooks/"

Then in $HOME/.pbuilder-hooks/ create a file D10addsource which contains the 
lines:
echo "deb [your-source-here]" >> /etc/apt/sources.list
apt-get update

However, if setting OTHERMIRROR inside of ~/.pbuilderrc worked as documented, 
then all I would have needed to do would be to add the following line to 
~/.pbuilderrc and no hook required:
OTHERMIRROR="deb [your-source-here]"

If my workaround is wrong, please tell me.

So in summary, this bug still exists. If the bug is not going to be
fixed, then at least the documentation needs to be updated.

This bug is somewhat related to
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/371221,
because if packages from ~/pbuilder/dist_result could satisfy
dependencies then I wouldn't need to use OTHERMIRROR. But really
OTHERMIRROR should still work regardless.

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

Title:
  [pbuilder-dist] overwrite OTHERMIRROR set in ~/.pbuilderrc

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


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

[Bug 1004579] Re: [pbuilder-dist] overwrite OTHERMIRROR set in ~/.pbuilderrc

[Andrew Bate]

This bug still exists in focal 20.04. It should not have been closed.

When using pbuilder-dist the value of OTHERMIRROR is ignored, as is the
value of --othermirror passed as argument to pbuilder-dist.

To work around this I need to manually add a mirror to
/etc/apt/sources.list from within a hook file, which is a bit of a hack
and shouldn't be necessary.

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

Title:
  [pbuilder-dist] overwrite OTHERMIRROR set in ~/.pbuilderrc

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


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