[Touch-packages] [Bug 2019970] Re: OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

[Michael Baentsch]

Thanks for this explanation, Seth. Very good to know--from a security
perspective. A bit less satisfying from a functionality perspective,
particularly given the assurance by Matt from the OpenSSL team above.

I do understand though that you're aiming for "bug completeness" to
support those that rely on those bugs. The others then need to work
around them (using other distros or building packages from source).

Please feel free to close this report then.

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

Title:
  OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Full bug report at https://github.com/openssl/openssl/issues/20981

  No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any
  more.

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


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

[Touch-packages] [Bug 1991606] Autopkgtest regression report (distro-info/1.1ubuntu0.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted distro-info (1.1ubuntu0.1) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

devscripts/2.22.1ubuntu1 (amd64, arm64, armhf, ppc64el, s390x)
livecd-rootfs/2.765.20 (amd64)
vagrant-mutate/1.2.0-4.1 (arm64, ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#distro-info

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  

[Touch-packages] [Bug 1991606] Autopkgtest regression report (python-debian/0.1.46ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python-debian (0.1.46ubuntu1) for 
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

devscripts/2.22.2ubuntu3 (amd64, arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#python-debian

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The 

[Touch-packages] [Bug 1991606] Autopkgtest regression report (python-debian/0.1.43ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python-debian (0.1.43ubuntu1.1) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

devscripts/2.22.1ubuntu1 (amd64, arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#python-debian

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The 

[Touch-packages] [Bug 1991606] Autopkgtest regression report (python-debian/0.1.36ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python-debian (0.1.36ubuntu1.1) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

reprotest/0.7.14 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#python-debian

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools 

[Touch-packages] [Bug 2019970] Re: OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

[Seth Arnold]

Michael, Ubuntu backports specific fixes as they are identified; you can
check the status of our OpenSSL packages on our website:

All OpenSSL issues:

https://ubuntu.com/security/cves?q==openssl===

OpenSSL issues, restricted to just Jammy:

https://ubuntu.com/security/cves?q==openssl==jammy=

OpenSSL issues without a release, restricted to just Jammy:

https://ubuntu.com/security/cves?q==openssl==jammy=needed
https://ubuntu.com/security/cves?q==openssl==jammy=deferred
https://ubuntu.com/security/cves?q==openssl==jammy=ignored
https://ubuntu.com/security/cves?q==openssl==jammy=needs-triage

(Yeah, it's unfortunate that currently takes multiple pages to view.
Hopefully this will be addressed soon.)

Thanks

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

Title:
  OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Full bug report at https://github.com/openssl/openssl/issues/20981

  No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any
  more.

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


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

[Touch-packages] [Bug 1895486] Re: [media-keys] Media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards

[Cristiano Fraga G. Nunes]

Just for better bug tracking, I've added some links.

Related bugs (maybe duplicated):
- https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013255
- https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892747
- https://bugs.launchpad.net/gnome-shell/+bug/1895486
- 
https://askubuntu.com/questions/1242205/ubuntu-20-04-hangs-when-changing-brightness-level-with-keyboard
- 
https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on-ubuntu-gnome-17-04

Upstream issues:
- https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1821
- https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1279


** Summary changed:

- [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" 
keyboards
+ [media-keys] Media keys with lag slow/delay on Gnome with "Scroll Lock" 
keyboards

** Changed in: xkeyboard-config (Ubuntu)
 Assignee: Cristiano Fraga G. Nunes (cfgnunes) => (unassigned)

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

Title:
  [media-keys] Media keys with lag slow/delay on Gnome with "Scroll
  Lock" keyboards

Status in GNOME Shell:
  New
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  I use Ubuntu 20.04.1.

  After some use, I noticed a delay when using keyboard media controls
  (for example: increase volume audio).

  The first time I push these key Gnome hangs for a short time before
  display the action on the screen.

  (This problem is still happening in Ubuntu 18.04 too. Even worse some
  times, the system crashes when using media keys.)

  For some reason, my Gnome freezes when using Fn keys, or when I try to
  use two keyboards. A friend of mine pointed to me that it occurs when
  switching to a keyboard layout that has Scroll Lock enabled, so I
  disabled it in the X11 keyboard layout file for my language, and it
  solved the problem.

  
  A workaround to solve the problem is:

  1) Opened the keyboard layout file for my language, in my case:

  sudo nano /usr/share/X11/xkb/symbols/br

  2) Commented the line:

  modifier_map Mod3 { Scroll_Lock };

  3) Logged out and logged in again or run command setxkbmap.

  These steps are specific for the Brazilian Portuguese ABNT2 Layout and
  may not work for other layouts, but it can help you find a similar
  solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-xkb-utils 7.7+5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 13 21:52:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
  InstallationDate: Installed on 2020-08-15 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
  SourcePackage: x11-xkb-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.15
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.15
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  

[Touch-packages] [Bug 1971242] Please test proposed package

[Steve Langasek]

Hello dm, or anyone else affected,

Accepted cups into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/cups/2.4.1op1-1ubuntu4.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Fix Committed
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

  sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

  FiileDevice Yes

  and start CUPS again:

  sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

  lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Chcke whether it contains a line

  @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

  @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

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


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

[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

[Steve Langasek]

FiileDevice Yes


This is a typo for "FileDevice", correct?

** Description changed:

  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.
  
  [ Impact ]
  
  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).
  
  Only an ugly command-line-based workaround, running the command
  
- lpadmin -p PRINTER -o print-color-mode-default=color
+ lpadmin -p PRINTER -o print-color-mode-default=color
  
  makes the printer print in color.
  
  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers are
  affected.
  
  [ Test Plan ]
  
  Remove the workaround if you had applied it:
  
- lpadmin -p PRINTER -R print-color-mode-default
+ lpadmin -p PRINTER -R print-color-mode-default
  
  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do
  
- lp -d PRINTER -o ColorModel=CMYK FILE.pdf
+ lp -d PRINTER -o ColorModel=CMYK FILE.pdf
  
  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.
  
  To test without a printer:
  
  Stop CUPS:
  
- sudo systemctl stop cups
+ sudo systemctl stop cups
  
  Edit /etc/cups/cups-files.conf to have a line
  
- FiileDevice Yes
+ FiileDevice Yes
  
- ans start CUPS again:
+ and start CUPS again:
  
- sudo systemctl start cups
+ sudo systemctl start cups
  
  Then create a queue using the attached sample PPD file:
  
- lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-PDF_Printer-
+ lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-PDF_Printer-
  PDF.ppd
  
  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Chcke whether it contains a line
  
- @PJL SET RENDERMODE=COLOR
+ @PJL SET RENDERMODE=COLOR
  
  near its beginning, and NOT a line
  
- @PJL SET RENDERMODE=GRAYSCALE
+ @PJL SET RENDERMODE=GRAYSCALE
  
  [ Where problems could occur ]
  
  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints about
  color printing. So the regression potential is very low.

** Changed in: cups (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Fix Committed
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  

[Touch-packages] [Bug 1983359] Re: [SRU] hwrng drivers missing in initrd.img

[Steve Langasek]

Hello Heinrich, or anyone else affected,

Accepted initramfs-tools into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.140ubuntu13.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: initramfs-tools (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Title:
  [SRU] hwrng drivers missing in initrd.img

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Jammy:
  Fix Committed
Status in initramfs-tools source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  The initialization of the entropy buffer of the urandom device is
  critical for security.

  When booting Jammy 22.04.1 on QEMU riscv64 I see the following
  warnings:

  [   14.654546] random: lvm: uninitialized urandom read (4 bytes read)
  [   15.247995] random: lvm: uninitialized urandom read (2 bytes read)
  [   22.484719] random: lvm: uninitialized urandom read (4 bytes read)
  [   43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read)
  [   48.862281] random: lvm: uninitialized urandom read (4 bytes read)

  Module virtio-rng.ko is missing in initrd.img.
  Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings.

  Hardware RNG drivers should generally be included in the initrd to
  provide early entropy.

  [Test case]

  To reproduce the issue:

  Install the prerequisites:
  sudo apt-get update
  sudo apt-get install opensbi qemu-system-misc u-boot-qemu

  Download https://old-
  releases.ubuntu.com/releases/22.04.1/ubuntu-22.04.1-preinstalled-
  server-riscv64+unmatched.img.xz.

  Decompress it with
  xz -d ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img.xz

  Run it in QEMU with

  qemu-system-riscv64 \
  -machine virt -nographic -m 2048 -smp 4 \
  -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin \
  -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \
  -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \
  -device virtio-rng-pci \
  -drive 
file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio

  You can log into the system with user ubuntu, password ubuntu after
  seeing the message "Cloud-init v. 22.2-0ubuntu1~22.04.3 finished"

  Run 'sudo dmesg | grep 'uninitialized urandom'

  To test the fix:

  Update the initramfs-tools package.

  Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in
  /etc/initramfs-tools/initramfs.conf or in /etc/initramfs-
  tools/conf.d/*.conf)

  Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)'

  Check that [main/]lib/modules/$(uname
  -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules.
  When running on QEMU the relevant module is virtio-rng.ko.

  Reboot and check the kernel log by running 'sudo dmesg | grep
  'uninitialized urandom'.

  [Where problems could occur]

  Adding more drivers increases the size of the initrd. The larger
  initrd might not fit onto the boot partition. The total size of
  hw_random drivers on amd64 is less than 150 KiB so this seem
  improbable.

  [Other Info]

  n/a

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


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

[Touch-packages] [Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards

[Cristiano Fraga G. Nunes]

As the xkeyboard-config is not the cause of that bug, the Scroll Lock
key must return because many users use this key in some apps.

I've opened a Merge Request to return the Scroll Lock key:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/merge_requests/555

** Changed in: xkeyboard-config (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
  Lock" keyboards

Status in GNOME Shell:
  New
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  I use Ubuntu 20.04.1.

  After some use, I noticed a delay when using keyboard media controls
  (for example: increase volume audio).

  The first time I push these key Gnome hangs for a short time before
  display the action on the screen.

  (This problem is still happening in Ubuntu 18.04 too. Even worse some
  times, the system crashes when using media keys.)

  For some reason, my Gnome freezes when using Fn keys, or when I try to
  use two keyboards. A friend of mine pointed to me that it occurs when
  switching to a keyboard layout that has Scroll Lock enabled, so I
  disabled it in the X11 keyboard layout file for my language, and it
  solved the problem.

  
  A workaround to solve the problem is:

  1) Opened the keyboard layout file for my language, in my case:

  sudo nano /usr/share/X11/xkb/symbols/br

  2) Commented the line:

  modifier_map Mod3 { Scroll_Lock };

  3) Logged out and logged in again or run command setxkbmap.

  These steps are specific for the Brazilian Portuguese ABNT2 Layout and
  may not work for other layouts, but it can help you find a similar
  solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-xkb-utils 7.7+5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 13 21:52:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
  InstallationDate: Installed on 2020-08-15 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
  SourcePackage: x11-xkb-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.15
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.15
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


-- 
Mailing list: 

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Steve Langasek]

Hello wieczyk, or anyone else affected,

Accepted distro-info into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/distro-
info/1.1ubuntu0.1 in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: distro-info (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 

[Touch-packages] [Bug 1991606] Please test proposed package

[Steve Langasek]

Hello wieczyk, or anyone else affected,

Accepted python-debian into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
debian/0.1.36ubuntu1.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), 

[Touch-packages] [Bug 1991606] Please test proposed package

[Steve Langasek]

Hello wieczyk, or anyone else affected,

Accepted python-debian into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
debian/0.1.43ubuntu1.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: python-debian (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Steve Langasek]

Hello wieczyk, or anyone else affected,

Accepted python-debian into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
debian/0.1.46ubuntu1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Description changed:

  [ Impact ]
  
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources` module,
  can produce errors like this:
  
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'
  
  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .
  
  suffix 1build1 is invalid.
  
  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.
  
  Example: python poetry: Invalid PEP 440 version: '1.1build1'
  
  [ Test Plan ]
+ 1.
+ $ mkdir /tmp/lp.1991606
+ $ export HOME=/tmp/lp.1991606
+ $ sudo apt install dput python3-pip
+ $ pip3 install -U setuptools
+ $ sudo apt install 
+ $ dput
  
- 1. Install the affected package and pip plus python3-dev, gcc, libfuzzy-dev:
- ```
- sudo apt update
- sudo apt install python3-dev python3-pip python3-distro-info python3-debian 
libfuzzy-dev gcc -y
- ```
- 2. Install setuptools 67.5 **as normal user** using pip:
- ```
- python3 -m pip install setuptools==67.5.0
- ```
- 3. Then try to install ssdeep with pip using that setuptools version:
- ```
- python3 -m pip install ssdeep
- ```
+ This will produce a backtrace.
  
- The installation should succeed with the fixed package, but it will fail
- with InvalidVersion with the affected package versions installed.
+ 2. Enable -proposed
+ 3. Upgrade  from proposed
+ 4. dput
  
- Commands for Benjamin's local testing with schroot:
- ```
- schroot-wrapper -p 
python3-dev,python3-pip,python3-distro-info,python3-debian,libfuzzy-dev,gcc -c 
$distro
- python3 -m pip install setuptools==67.5.0
- python3 -m pip install ssdeep
- ```
+ This will succeed.
  
  [ Where problems could occur ]
  
  The fix touches only setup.py which is only used for installing the
  package. So there should be no effect on the installed package (except
  for exposing a different version). But there could be indirect effects
  (hidden bugs that trigger on package upgrade, etc).
  
  [ Other Info ]
  
  The 

[Touch-packages] [Bug 2021948] Re: New bugfix release 23.0.4

[Steve Langasek]

Hello Timo, or anyone else affected,

Accepted mesa into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~23.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-lunar

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

Title:
  New bugfix release 23.0.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  New
Status in mesa source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 23.0.x-series, we should put it
  in lunar so latest bugfixes would get there, and in jammy for 22.04.3
  image.

  We'll include an additional bugfix (a revert) to fix GPU hangs on some
  AMD gpu's running certain games.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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

[Touch-packages] [Bug 2021498] Re: Please merge 3.134 into mantic

[Benjamin Drung]

Thanks. There are some smaller points to address. Among other things:

* "extrausers support for adduser" adds "--encrypt-home" to the --help
output. That should be in the other commit.

Let us discuss/address that on Monday together.

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

Title:
  Please merge 3.134 into mantic

Status in adduser package in Ubuntu:
  In Progress

Bug description:
  The upstream version 3.134 should be merged into mantic. The current
  version is 3.129ubuntu1.

  See the merge conflict report:
  https://merges.ubuntu.com/a/adduser/REPORT

  Note: this is a tracking bug

  PPA for review: https://launchpad.net/~mateus-
  morais/+archive/ubuntu/adduser-merge-mantic-3.134-lp2021498

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


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

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Steve Langasek]

The evince upload to jammy still does:

+Recommends: default-dbus-session-bus | dbus-session-bus,
+   apparmor (>= 3.0.4-2ubuntu2.3),

with the explanation that:

+- debian/control.in: recommend apparmor version that includes the
+  snap_browsers abstraction, or else policy loads will fail.

But the use of #include if exists was supposed to make this unnecessary.
And downgrading the Depends to a Recommends doesn't change the default
behavior here; installing this version of evince will by default pull in
apparmor, even in contexts where apparmor was not previously installed.
(There are not many of those in Ubuntu, which means if apparmor was not
installed it was probably deliberate on the part of the admin!)

I'm rejecting this upload, as to my understanding this is not what we're
meant to have.

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Incomplete
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Touch-packages] [Bug 1794064] Proposed package upload rejected

[Steve Langasek]

An upload of evince to jammy-proposed has been rejected from the upload
queue for the following reason: "adds Recommends that shouldn't be
needed".

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Incomplete
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Touch-packages] [Bug 1794064] Please test proposed package

[Steve Langasek]

Hello Olivier, or anyone else affected,

Accepted apparmor into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apparmor/3.0.4-2ubuntu2.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Incomplete
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Touch-packages] [Bug 1794064] Please test proposed package

[Steve Langasek]

Hello Olivier, or anyone else affected,

Accepted evince into lunar-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/evince/44.1-1ubuntu0.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: apparmor (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Incomplete
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Steve Langasek]

I see that there is an apparmor upload for this bug in the lunar queue,
in addition to the evince upload.  The apparmor upload adds a line to
abstractions/snap_browsers.  This bug report does not explain that the
abstractions/snap_browsers was previously inadequate or that it should
be updated to fix this bug.  Please provide more information of why this
apparmor change is needed.

** Changed in: apparmor (Ubuntu Lunar)
   Status: In Progress => Incomplete

** Changed in: evince (Ubuntu Lunar)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-lunar

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Incomplete
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Touch-packages] [Bug 2024252] Re: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

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

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Unknown error occurred during auto-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Fri Jun 16 10:30:12 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-06-03 (13 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2021498] Re: Please merge 3.134 into mantic

[Mateus Rodrigues de Morais]

bdrung: thanks for your review! I addressed your requests accordingly:

* Fixed ubuntu/devel rebase on correct commit
* Fixed doc/adduser.8 rebase (on both the merge and the encrypt home MR)
* Yes, I added the test case to make our testing more robust and referenced the 
MR in d/changelog
* Fixed the adduser.conf merge changes in the comments
* Forwarded the autopkgtest fixes and referenced them in d/changelog 
(https://salsa.debian.org/debian/adduser/-/merge_requests/89)
* Removed the extra spaces added to d/t/f/firstlastuidgid.t
* Fixed d/changelog entries as stated

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

Title:
  Please merge 3.134 into mantic

Status in adduser package in Ubuntu:
  In Progress

Bug description:
  The upstream version 3.134 should be merged into mantic. The current
  version is 3.129ubuntu1.

  See the merge conflict report:
  https://merges.ubuntu.com/a/adduser/REPORT

  Note: this is a tracking bug

  PPA for review: https://launchpad.net/~mateus-
  morais/+archive/ubuntu/adduser-merge-mantic-3.134-lp2021498

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


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

[Touch-packages] [Bug 2021498] Re: Please merge 3.134 into mantic

[Mateus Rodrigues de Morais]

** Patch removed: "debdiff between debian adduser 1.134 and 1.134ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2021498/+attachment/5679707/+files/debian_adduser_3.134.debdiff

** Patch removed: "debdiff between ubuntu adduser 1.129ubuntu1 and 1.134ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2021498/+attachment/5679708/+files/debian_adduser_3.129ubuntu1.debdiff

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

Title:
  Please merge 3.134 into mantic

Status in adduser package in Ubuntu:
  In Progress

Bug description:
  The upstream version 3.134 should be merged into mantic. The current
  version is 3.129ubuntu1.

  See the merge conflict report:
  https://merges.ubuntu.com/a/adduser/REPORT

  Note: this is a tracking bug

  PPA for review: https://launchpad.net/~mateus-
  morais/+archive/ubuntu/adduser-merge-mantic-3.134-lp2021498

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


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

[Touch-packages] [Bug 2015562] Re: Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream)

[Miriam España Acebal]

Hi again,

I'm working on a set of DEP-8 tests to check the matching domain
functionality modified by this change that fixes the issue to make a
stronger SRU submission. Also, I could cover bug LP#1677827.

I found a DEP8 proposal on Debian at https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1034135, and I'm using it as a starting point (to
avoid the maximum diverge, in case it would be accepted in the future).

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

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

Title:
  Segfault in dnsmasq when using certain static domain entries + DoH
  (bugfix possibly exists upstream)

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  In Progress

Bug description:
  Hi folks,

  I've been using dnsmasq for my home DNS needs, which includes
  returning null entries for certain domain queries. The specific case
  in which I found this segfault was returning null  records for
  Netflix (to ensure Netflix does not try to use my IPv6 tunnel to
  egress traffic through).

  I've been using very simple configuration snippet to achieve this,
  this is attached as netflix-nov6.conf (the full file contains more
  entries).

  Ever since I've upgraded from Ubuntu 20.04 to 22.04, dnsmasq kept
  segfaulting at random occasions. I also attempted do an apt
  update&, but there are no newer versions of this package
  available.

  Further research into this issue showed that a surefire way to trigger
  this segfault was to go to a website blocked via this method (for
  testing purposes, a dig query works quite well). The segfault can be
  reproduced reliably, and always occurs after one or a few queries
  towards the "blocked" domain entries.

  I found a commit in the upstream dnsmasq git repo which seems to fix this 
issue, the fix made it into 2.87:
  
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=de372d6914ae20a1f9997815f258efbf3b14c39b

  Would it be possible to backport this into the version used in the
  current LTS Ubuntu release? Thanks!

  --

  $ lsb_release -d
  Description:  Ubuntu 22.04.2 LTS
  $ apt-cache policy dnsmasq
  dnsmasq:
    Installed: 2.86-1.1ubuntu0.2
    Candidate: 2.86-1.1ubuntu0.2
    Version table:
   *** 2.86-1.1ubuntu0.2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   2.86-1.1ubuntu0.1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-security/universe amd64 
Packages
   2.86-1.1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

  --

  Excerpt from the dnsmasq logs, with debugging enabled, after I loaded 
fast.com:
  Apr 07 13:47:41 budgie systemd[1]: Started dnsmasq - A lightweight DHCP and 
caching DNS server.
  Apr 07 13:47:42 budgie dnsmasq[109976]: query[type=65] 
fast.dradis.netflix.com from 192.168.10.82
  Apr 07 13:47:42 budgie dnsmasq[109976]: config error is REFUSED (EDE: network 
error)
  Apr 07 13:47:43 budgie dnsmasq[109976]: query[type=65] 
ichnaea-web.netflix.com from 192.168.10.82
  Apr 07 13:47:43 budgie systemd[1]: dnsmasq.service: Main process exited, 
code=dumped, status=11/SEGV
  Apr 07 13:47:43 budgie systemd[1]: dnsmasq.service: Failed with result 
'core-dump'.

  Core dump is also attached.

  Reproduction steps:
  - 1. Install dnsmasq on Ubuntu 22.04 (or any Ubuntu release using dnsmasq 
2.86)
  - 1.5. Configure one or multiple DNS servers for dnsmasq
  - 2. Copy netflix-nov6.conf into /etc/dnsmasq.d/
  - 3. Restart/reload dnsmasq
  - 3.5 Verify that dnsmasq resolves domains correctly:

  root@budgie:~# dig +short -tA ubuntu.com @127.0.0.1
  185.125.190.21
  185.125.190.20
  185.125.190.29
  root@budgie:~# dig +short -t ubuntu.com @127.0.0.1
  2620:2d:4000:1::28
  2620:2d:4000:1::26
  2620:2d:4000:1::27

  - 4. Perform a type65 / HTTPS recordtype query for netflix.com towards
  the dnsmasq server once or twice:

  root@budgie:~# dig +short -tTYPE65 netflix.com @127.0.0.1
  root@budgie:~# dig +short -tTYPE65 netflix.com @127.0.0.1
  ;; communications error to 127.0.0.1#53: timed out
  ;; communications error to 127.0.0.1#53: connection refused
  ;; communications error to 127.0.0.1#53: connection refused
  ;; no servers could be reached

  - 5. Check logs to verify segfault:

  Apr 07 14:03:28 budgie systemd[1]: Started dnsmasq - A lightweight DHCP and 
caching DNS server.
  Apr 07 14:03:32 budgie dnsmasq[111585]: query[type=65] netflix.com from 
127.0.0.1
  Apr 07 14:03:32 budgie dnsmasq[111585]: config error is REFUSED (EDE: network 
error)
  Apr 07 14:03:33 budgie dnsmasq[111585]: query[type=65] netflix.com from 
127.0.0.1
  Apr 07 14:03:33 budgie systemd[1]: dnsmasq.service: Main process exited, 
code=dumped, status=11/SEGV
  

[Touch-packages] [Bug 2024252] Re: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Unknown error occurred during auto-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Fri Jun 16 10:30:12 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-06-03 (13 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2024252] [NEW] package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Taed Wynnell]

Public bug reported:

Unknown error occurred during auto-upgrade.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
Date: Fri Jun 16 10:30:12 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2023-06-03 (13 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.9
SourcePackage: initramfs-tools
Title: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Unknown error occurred during auto-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Fri Jun 16 10:30:12 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-06-03 (13 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[Apport retracing service]

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

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

Title:
  evolution-alarm-notify crashed with signal 5

Status in evolution-data-server package in Ubuntu:
  Incomplete

Bug description:
  I have no details to provide sorry.

  This is a QA test install only.. with packages & VERY MINOR change(s)
  having taken place on it ...

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: evolution-data-server (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
  Uname: Linux 6.2.0-21-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: LXQt
  Date: Tue Jun  6 16:30:18 2023
  ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2023-06-06 (1 days ago)
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  JournalErrors: -- No entries --
  ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify
  Signal: 5
  SourcePackage: evolution-data-server
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution-alarm-notify crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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


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

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

[Apport retracing service]

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

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

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  evolution-alarm-notify crashed with signal 5

Status in evolution-data-server package in Ubuntu:
  Incomplete

Bug description:
  I have no details to provide sorry.

  This is a QA test install only.. with packages & VERY MINOR change(s)
  having taken place on it ...

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: evolution-data-server (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
  Uname: Linux 6.2.0-21-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: LXQt
  Date: Tue Jun  6 16:30:18 2023
  ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2023-06-06 (1 days ago)
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  JournalErrors: -- No entries --
  ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify
  Signal: 5
  SourcePackage: evolution-data-server
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution-alarm-notify crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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


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

[Touch-packages] [Bug 2023151] evolution-alarm-notify crashed with signal 5

[Apport retracing service]

StacktraceTop:
 g_settings_set_property (object=0x557a8ce8b390, prop_id=, 
value=, pspec=) at ../../../gio/gsettings.c:596
 object_set_property (object=object@entry=0x557a8ce8b390, pspec=0x557a8ce8b130, 
value=0x7ffe7f2f5130, nqueue=nqueue@entry=0x0, user_specified=) 
at ../../../gobject/gobject.c:1812
 g_object_new_internal (class=class@entry=0x557a8ce89b40, 
params=params@entry=0x7ffe7f2f5030, n_params=n_params@entry=1) at 
../../../gobject/gobject.c:2291
 g_object_new_valist (object_type=, 
first_property_name=first_property_name@entry=0x7fbd0429d23e "schema-id", 
var_args=var_args@entry=0x7ffe7f2f5300) at ../../../gobject/gobject.c:2585
 g_object_new (object_type=, 
first_property_name=first_property_name@entry=0x7fbd0429d23e "schema-id") at 
../../../gobject/gobject.c:2058

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

Title:
  evolution-alarm-notify crashed with signal 5

Status in evolution-data-server package in Ubuntu:
  Incomplete

Bug description:
  I have no details to provide sorry.

  This is a QA test install only.. with packages & VERY MINOR change(s)
  having taken place on it ...

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: evolution-data-server (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
  Uname: Linux 6.2.0-21-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: LXQt
  Date: Tue Jun  6 16:30:18 2023
  ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2023-06-06 (1 days ago)
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  JournalErrors: -- No entries --
  ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify
  Signal: 5
  SourcePackage: evolution-data-server
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution-alarm-notify crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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


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

[Touch-packages] [Bug 2023151] evolution-alarm-notify crashed with signal 5

[Apport retracing service]

StacktraceTop:
 g_settings_set_property (object=0x557a8ce8b390, prop_id=, 
value=, pspec=) at ../../../gio/gsettings.c:591
 object_set_property (object=object@entry=0x557a8ce8b390, pspec=0x557a8ce8b130, 
value=0x7ffe7f2f5130, nqueue=nqueue@entry=0x0, user_specified=) 
at ../../../gobject/gobject.c:1812
 g_object_new_internal (class=class@entry=0x557a8ce89b40, 
params=params@entry=0x7ffe7f2f5030, n_params=n_params@entry=1) at 
../../../gobject/gobject.c:2291
 g_object_new_valist (object_type=, 
first_property_name=first_property_name@entry=0x7fbd0429d23e "schema-id", 
var_args=var_args@entry=0x7ffe7f2f5300) at ../../../gobject/gobject.c:2585
 g_object_new (object_type=, 
first_property_name=first_property_name@entry=0x7fbd0429d23e "schema-id") at 
../../../gobject/gobject.c:2058


** Tags removed: need-amd64-retrace

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

Title:
  evolution-alarm-notify crashed with signal 5

Status in evolution-data-server package in Ubuntu:
  Incomplete

Bug description:
  I have no details to provide sorry.

  This is a QA test install only.. with packages & VERY MINOR change(s)
  having taken place on it ...

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: evolution-data-server (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
  Uname: Linux 6.2.0-21-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: LXQt
  Date: Tue Jun  6 16:30:18 2023
  ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2023-06-06 (1 days ago)
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  JournalErrors: -- No entries --
  ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify
  Signal: 5
  SourcePackage: evolution-data-server
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution-alarm-notify crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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


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

[Touch-packages] [Bug 2023439] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/2023439/+attachment/5678956/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2023439/+attachment/5678966/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2023439/+attachment/5678967/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/2023439/+attachment/5678968/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2023439/+attachment/5678970/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2023439/+attachment/5678971/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 2021884

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have changed the netplan according to following recommendation

  To fix that manually you can just edit the file
  /etc/netplan/NM-19f0fcca-816d-4375-9c48-081bae87768d.yaml, look for the
  allowed-ips section in the wireguard peer and add the prefix /32 to the
  IP, like this: "172.16.0.36/32".

  But it failed again, with following notice fron surfshark

  Error envoking remote method 'connect': Error: Error: to add ipv6leak 
protection! Message recipient disconnected from messagebus without replying
  Cause:ipv6_leak_protection_error

   The last time i got help from Danilo Egea Gondolfo. THX for that

  I remain 
  BR Peter

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.42.4-1ubuntu5
  ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
  Uname: Linux 6.2.0-21-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Jun 10 12:57:07 2023
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2023-05-30 (10 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230529)
  IpRoute:
   default via 192.168.0.1 dev enp0s25 proto dhcp src 192.168.0.111 metric 100 
   default via 192.168.0.1 dev enp0s25 proto dhcp src 192.168.0.111 metric 
20100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000 
   192.168.0.0/24 dev enp0s25 proto kernel scope link src 192.168.0.111 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: network-manager
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.
  separator:

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


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

[Touch-packages] [Bug 484786] Re: Better support for btrfs snapshots

[Simon Déziel]

Nowadays, btrfs snapshots can only be taken by the owner of the source
subvol. https://btrfs.readthedocs.io/en/latest/ch-mount-
options.html#btrfs-specific-mount-options:

> Historically, any user could create a snapshot even if he was not
owner of the source subvolume, the subvolume deletion has been
restricted for that reason. The subvolume creation has been restricted
...

I just tested this in a Jammy VM (FYI btrfsctl was replaced by `btrfs
subvolume snapshot`):

```
ubuntu@bj:~$ uname -a
Linux bj 5.15.0-75-generic #82-Ubuntu SMP Tue Jun 6 23:10:23 UTC 2023 x86_64 
x86_64 x86_64 GNU/Linux
ubuntu@bj:~$ dpkg -l| grep btrfs
ii  btrfs-progs 5.16.2-1
amd64Checksumming Copy on Write Filesystem utilities

ubuntu@bj:~$ mount | grep btrfs
/dev/sda3 on /home type btrfs (rw,noatime,space_cache=v2,subvolid=5,subvol=/)

# Trying while /home is root owned
ubuntu@bj:~$ btrfs subvolume snapshot /home ./homefoo
Create a snapshot of '/home' in './homefoo'
ERROR: cannot snapshot '/home': Operation not permitted

# Changing ownership of the source subvol
ubuntu@bj:~$ sudo chown ubuntu: /home

# Trying now that /home is owned by ubuntu:
ubuntu@bj:~$ btrfs subvolume snapshot /home ./homefoo
Create a snapshot of '/home' in './homefoo'
```

So I don't think it's a concern anymore but I won't fiddle with the bug
status and leave that to others ;)

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

Title:
  Better support for btrfs snapshots

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  I just realized that the btrfs snapshotting ioctl is usable by all
  users, not root as I previously assumed. This makes it concerningly
  easy for users on btrfs to defeat a path-based MAC framework like
  AppArmor.

  
  For example, consider the gdm-guest-session user. If I log into a 
gdm-guest-session on btrfs:

  
  (1) ls /home ==> Permission denied as expected, by AppArmor.

  
  (2) cd /tmp

  (3) btrfsctl -s test / (Make a snapshot of / in /tmp called test)

  (4) cd /tmp/test

  (5) Profit! Apparmor-unrestricted mirror of / in /tmp/test!

  
  As btrfs inevitably will become a mainstream filesystem, it's a good time to 
begin thinking about how to handle this situation.

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


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

[Touch-packages] [Bug 1199274] Re: sound is distorted [12.04] [the same as Bug #1183145]

[Kiren SA]

We encourage you to trust us and take advantage of our services. Choose
the massage course that suits your needs and contact us via phone or
text message.  https://lovelymsg.info/

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

Title:
  sound is distorted [12.04] [the same as Bug #1183145]

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  When you increase the volume to 60-70 % and above, there's a little
  sound distortion (it can be heard especially when human voice is being
  listened) and a lot sound distortion when the master volume is set to
  over 90 %.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15.3
  ProcVersionSignature: Ubuntu 3.5.0-36.57~precise1-generic 3.5.7.14
  Uname: Linux 3.5.0-36-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf470 irq 47'
     Mixer name : 'Analog Devices AD1981'
     Components : 'HDA:11d41981,103c309f,00100200 
HDA:14f12bfa,103c309f,0009'
     Controls  : 11
     Simple ctrls  : 9
  Date: Tue Jul  9 11:52:27 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YAF Ver. F.1D
  dmi.board.name: 309F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 54.3D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YAFVer.F.1D:bd07/11/2008:svnHewlett-Packard:pn:pvrF.1D:rvnHewlett-Packard:rn309F:rvrKBCVersion54.3D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.version: F.1D
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2013-07-09T11:25:24.466465

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


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

[Touch-packages] [Bug 2023016] Re: Merge 13.2-1 into mantic

[Steve Langasek]

** Changed in: gdb (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Merge 13.2-1 into mantic

Status in gdb package in Ubuntu:
  Fix Committed

Bug description:
  The upstream version 13.2-1 should be merged into mantic. The current
  version is 13.1-2ubuntu2.

  See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT

  Note: this is a tracking bug

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


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

[Touch-packages] [Bug 2023016] Re: Merge 13.2-1 into mantic

[Dominik Viererbe]

The Merge was more complicated that anticipated, but I finally managed to merge 
it.
I locally built it and did some trivial testing. Everything seems fine.

The Merge can be downloaded here:
https://launchpad.net/~dviererbe/+archive/ubuntu/lp2023016-gdb-merge-mantic

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

Title:
  Merge 13.2-1 into mantic

Status in gdb package in Ubuntu:
  In Progress

Bug description:
  The upstream version 13.2-1 should be merged into mantic. The current
  version is 13.1-2ubuntu2.

  See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT

  Note: this is a tracking bug

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


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

[Touch-packages] [Bug 2023437]

[Alan Modra]

Linking with your .so files still doesn't give me any difference between
gold-2.39 and gold mainline.  I'm using my crt*.o, libc_nonshared.a,
libgcc.a.  From ld -t output it seems nothing from libc_nonshared.a or
libgcc.a is extracted, so the only real difference ought to be crt1.o,
crti.o, crtn.o, crtbegin.o and crtend.o.  Please supply them too.  For
reference the linker command line I'm using on my x86_64 to powerpc64le
cross compiler setup is:

~/build/gas/all/gold/ld-new --sysroot=/home/gnu/powerpc64le-linux-gnu
--eh-frame-hdr -m elf64lppc -dynamic-linker /lib64/ld64.so.2 -o
bin/clang-16 /home/gnu/powerpc64le-linux-gnu/usr/lib64/crt1.o
/home/gnu/powerpc64le-linux-gnu/usr/lib64/crti.o
/usr/local/lib/gcc/powerpc64le-linux-gnu/12.2.0/crtbegin.o
-L/usr/local/lib/gcc/powerpc64le-linux-gnu/12.2.0 -v -Bsymbolic-
functions -z relro --build-id --gc-sections
tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o
tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o
tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o
tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o
tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -rpath
$ORIGIN/../lib: lib/libLLVMPowerPCCodeGen.a
lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a
lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a
lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a
lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a
lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a
lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a
lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a
lib/libLLVMTransformUtils.a lib/libLLVMVectorize.a lib/libclangBasic.a
lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a
lib/libclangFrontendTool.a lib/libclangSerialization.a
lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a
lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a
lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a
lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a
lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a
lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a
lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a
lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a
lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a
lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a
lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a
lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a
lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a
lib/libclangParse.a lib/libclangSerialization.a lib/libclangSema.a
lib/libclangAnalysis.a lib/libclangASTMatchers.a
lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a
lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a
lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a
lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a
lib/libLLVMProfileData.a lib/libLLVMSymbolize.a
lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a
lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a
lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a
lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a
lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a
lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a
lib/libclangToolingInclusions.a lib/libclangToolingCore.a
lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a
lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a
so/libz.so.1 so/libtinfo.so.6.4 so/libstdc++.so.6.0.32 so/libm.so.6
so/libgcc_s.so.1 -lgcc --start-group so/libc.so.6 /home/gnu/powerpc64le-
linux-gnu/usr/lib64/libc_nonshared.a so/ld64.so.2 --end-group
so/libgcc_s.so.1 -lgcc /usr/local/lib/gcc/powerpc64le-linux-
gnu/12.2.0/crtend.o /home/gnu/powerpc64le-linux-gnu/usr/lib64/crtn.o

This is the command line passed to the linker by g++-12 as shown by
adding -v to the g++ command line, with unneeded plugin and library path
stuff removed and modified to pick up your shared libraries.

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

Title:
  ppc64el gold linker produces unusable clang-16 binary

Status in binutils:
  In Progress
Status in binutils package in Ubuntu:
  New

Bug description:
  root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong 
-Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition 
-fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra 
-Wno-unused-parameter -Wwrite-strings -Wcast-qual 
-Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough 
-Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move 
-Wno-pessimizing-move 

[Touch-packages] [Bug 2024135] Re: Default right click method on touchpads should be with two fingers

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => Fix Released

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

Title:
  Default right click method on touchpads should be with two fingers

Status in gnome-control-center:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The default right click method on touchpads should be with two fingers
  so you can right click without having to look at the touchpad. Modern
  laptops have supported this for a decade, modern OSes like macOS and
  ChromeOS default to it, and upstream GNOME has defaulted to it since
  version 3.28 in 2018.

  This issue was fixed at the start of 2018 in bug 1699033, but then
  reverted again in: https://launchpad.net/ubuntu/+source/ubuntu-
  settings/18.10.8

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


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

[Touch-packages] [Bug 1990542] Re: initrd starts dhclient on interfaces that are not supposed to get an IP address

[Valentijn Sessink]

ip=off helps, thanks.

If initramfs-tools doesn't do bridges and this is the result, then
that's a bug. Although I admit it's probably quite an uncommon setup :-/

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

Title:
  initrd starts dhclient on interfaces that are not supposed to get an
  IP address

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged

Bug description:
  After trying several setups, I think this is a bug. If not - I can't
  find how to fix things.

  Setup: Ubuntu 22.04, with ubuntu-minimal installed (which depends on
  isc-dhcp-client). A network with a bridge interface. This can be
  anything, even an old /etc/network/interfaces file will do. For
  simplicity, the following netplan setup is used:

  network:
  version: 2
  ethernets:
  enp4s0:
wakeonlan: true
  dhcp4: no
  dhcp6: no
  bridges:
br0:
  interfaces: [enp4s0]
  dhcp4: yes
  dhcp6: yes
  parameters:
stp: false
forward-delay: 0

  
  What happens:
  Starting this machine will, during initrd phase, make dhclient fetch an IP 
address for enp4s0. Then netplan takes over and fetches an address for br0. If 
both enp4s0 and br0 have the same IP address from the DHCP-server, the machine 
will not be reachable.

  What should happen:
  enp4s0 should not get an IP address, as the netplan-configuration clearly 
says.

  A workaround is to remove isc-dhcp-client (which, in turn, removes
  meta-package ubuntu-minimal) and run update-initramfs -k all -u;
  afterwards, the dhclient in initrd is (obviously) not there anymore.

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


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

[Touch-packages] [Bug 1990542] Re: initrd starts dhclient on interfaces that are not supposed to get an IP address

[Benjamin Drung]

No, aoetools is not at fault here. The initrd does not take your netplan
configuration into account. You could specify the ip= kernel parameter
to let the initrd setup your network as you want it, but initramfs-tools
does not have any support for brigdes as far as I know.

If you do not need/use aoetools, then you can just remove that package
or specify "ip=off" on the kernel command line to disable configuring
the network in the initrd.

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

Title:
  initrd starts dhclient on interfaces that are not supposed to get an
  IP address

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged

Bug description:
  After trying several setups, I think this is a bug. If not - I can't
  find how to fix things.

  Setup: Ubuntu 22.04, with ubuntu-minimal installed (which depends on
  isc-dhcp-client). A network with a bridge interface. This can be
  anything, even an old /etc/network/interfaces file will do. For
  simplicity, the following netplan setup is used:

  network:
  version: 2
  ethernets:
  enp4s0:
wakeonlan: true
  dhcp4: no
  dhcp6: no
  bridges:
br0:
  interfaces: [enp4s0]
  dhcp4: yes
  dhcp6: yes
  parameters:
stp: false
forward-delay: 0

  
  What happens:
  Starting this machine will, during initrd phase, make dhclient fetch an IP 
address for enp4s0. Then netplan takes over and fetches an address for br0. If 
both enp4s0 and br0 have the same IP address from the DHCP-server, the machine 
will not be reachable.

  What should happen:
  enp4s0 should not get an IP address, as the netplan-configuration clearly 
says.

  A workaround is to remove isc-dhcp-client (which, in turn, removes
  meta-package ubuntu-minimal) and run update-initramfs -k all -u;
  afterwards, the dhclient in initrd is (obviously) not there anymore.

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


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

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[satyaarth chhabra]

i faced the same issue and here is a workaround to it

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[satyaarth chhabra]

i faced the same issue and here is a workaround to it
https://askubuntu.com/questions/1366735/how-to-make-chrome-browser-save-
as-dialog-to-be-on-focus-when-opening-under-ub

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[satyaarth chhabra]

i faced the same issue and here is a workaround to it
https://askubuntu.com/questions/1366735/how-to-make-chrome-browser-save-
as-dialog-to-be-on-focus-when-opening-under-ub

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Touch-packages] [Bug 1448690] Re: /sbin/dhclient-script has bashisms

[Benjamin Drung]

I just checked it on Ubuntu 23.04:

```
shellcheck -e SC2086,SC2154 -s dash /sbin/dhclient-script
grep shopt /sbin/dhclient-script
```

This does not complain about any bashism. So I am marking the bug as
fixed.

** Changed in: isc-dhcp (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  /sbin/dhclient-script has bashisms

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  /sbin/dhclient-script calls /bin/sh, which is of course dash, but
  contains bash-specific functions:

  root@mystic:~# ifup br0
  Internet Systems Consortium DHCP Client 4.3.1
  Copyright 2004-2014 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/br0/00:1d:92:d7:ad:8a
  Sending on   LPF/br0/00:1d:92:d7:ad:8a
  Sending on   Socket/fallback
  DHCPREQUEST of 172.31.3.6 on br0 to 255.255.255.255 port 67 (xid=0x7488da46)
  DHCPACK of 172.31.3.6 from 172.31.3.4
  RTNETLINK answers: File exists
  bound to 172.31.3.6 -- renewal in 38988 seconds.
  /sbin/dhclient-script: 55: /sbin/dhclient-script: shopt: not found
  /sbin/dhclient-script: 60: /sbin/dhclient-script: [[: not found
  /sbin/dhclient-script: 60: /sbin/dhclient-script: [[: not found
  /sbin/dhclient-script: 68: /sbin/dhclient-script: shopt: not found
  root@mystic:~# head -n1 /sbin/dhclient-script 
  #!/bin/sh
  root@mystic:~# 

  Shebang line needs to be /bin/bash, or the script needs to be
  rewritten.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: isc-dhcp-client 4.3.1-5ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Sun Apr 26 10:29:56 2015
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (1 days ago)

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


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

[Touch-packages] [Bug 1990542] Re: initrd starts dhclient on interfaces that are not supposed to get an IP address

[Valentijn Sessink]

Maybe the bug now should be filed against aoetools? That's in universe,
so maybe it should even be closed as "invalid"?

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

Title:
  initrd starts dhclient on interfaces that are not supposed to get an
  IP address

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged

Bug description:
  After trying several setups, I think this is a bug. If not - I can't
  find how to fix things.

  Setup: Ubuntu 22.04, with ubuntu-minimal installed (which depends on
  isc-dhcp-client). A network with a bridge interface. This can be
  anything, even an old /etc/network/interfaces file will do. For
  simplicity, the following netplan setup is used:

  network:
  version: 2
  ethernets:
  enp4s0:
wakeonlan: true
  dhcp4: no
  dhcp6: no
  bridges:
br0:
  interfaces: [enp4s0]
  dhcp4: yes
  dhcp6: yes
  parameters:
stp: false
forward-delay: 0

  
  What happens:
  Starting this machine will, during initrd phase, make dhclient fetch an IP 
address for enp4s0. Then netplan takes over and fetches an address for br0. If 
both enp4s0 and br0 have the same IP address from the DHCP-server, the machine 
will not be reachable.

  What should happen:
  enp4s0 should not get an IP address, as the netplan-configuration clearly 
says.

  A workaround is to remove isc-dhcp-client (which, in turn, removes
  meta-package ubuntu-minimal) and run update-initramfs -k all -u;
  afterwards, the dhclient in initrd is (obviously) not there anymore.

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


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

[Touch-packages] [Bug 1990542] Re: initrd starts dhclient on interfaces that are not supposed to get an IP address

[Valentijn Sessink]

It's not any cmdline options. (/proc/cmdline has root=[rootdev] ro)

But I searched on because I couldn't reproduce this bug on a virtual
machine. While on the host system that bugged me, a change in
/usr/share/initramfs-tools/scripts/functions to not start dhclient (but
echo it instead to a file somewhere) showed that the bug was still
there.

Turns out: installing aoetools is the culprit:
apt-get install aoetools
update-initramfs -k all -u

Skimming through local-top/aoe briefly, I can't see where this goes
wrong. Both iscsi and nfs seem to have the same "configure_networking"
settings. But I'm probably missing something, as I'm not 100% at home in
initrd scripts.

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

Title:
  initrd starts dhclient on interfaces that are not supposed to get an
  IP address

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged

Bug description:
  After trying several setups, I think this is a bug. If not - I can't
  find how to fix things.

  Setup: Ubuntu 22.04, with ubuntu-minimal installed (which depends on
  isc-dhcp-client). A network with a bridge interface. This can be
  anything, even an old /etc/network/interfaces file will do. For
  simplicity, the following netplan setup is used:

  network:
  version: 2
  ethernets:
  enp4s0:
wakeonlan: true
  dhcp4: no
  dhcp6: no
  bridges:
br0:
  interfaces: [enp4s0]
  dhcp4: yes
  dhcp6: yes
  parameters:
stp: false
forward-delay: 0

  
  What happens:
  Starting this machine will, during initrd phase, make dhclient fetch an IP 
address for enp4s0. Then netplan takes over and fetches an address for br0. If 
both enp4s0 and br0 have the same IP address from the DHCP-server, the machine 
will not be reachable.

  What should happen:
  enp4s0 should not get an IP address, as the netplan-configuration clearly 
says.

  A workaround is to remove isc-dhcp-client (which, in turn, removes
  meta-package ubuntu-minimal) and run update-initramfs -k all -u;
  afterwards, the dhclient in initrd is (obviously) not there anymore.

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


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

[Touch-packages] [Bug 2024164] [NEW] Replace dhclient with dhcpcd

[Benjamin Drung]

Public bug reported:

ISC has announced the end of life for ISC DHCP as of the end of 2022.
Kea is the recommended successor of the DHCP server (isc-dhcp-server).
This bug report is about replacing the DHCP client (isc-dhcp-client).

Ubuntu uses NetworkManager on the desktop and systemd-networkd on the
server as default DHCP client. However isc-dhcp-client is still
installed as part of all Ubuntu systems, because it is the only client
implementation that integrates with initramfs-tools. isc-dhcp-client is
also used by cloud-init and as a command line tool to configure
transient DHCP on an interface.

There are following requirements for the replacement DHCP client:
1. The DHCP client must support DHCPv6.
2. The DHCP client in the initramfs should be small enough to not increase the 
size noticeable.
3. The DHCP client needs to be callable from the shell (for initramfs and 
cloud-init)

The Ubuntu desktop uses network-manager and the server/cloud images uses
systemd-networkd. So there is no need for changing the DHCP client on
booted systems, but the initramfs uses dhclient from isc-dhcp-client.

ipconfig (from klibc-utils) does not support DHCPv6 (but there is work
in progress in
https://git.kernel.org/pub/scm/linux/kernel/git/bwh/klibc.git/?h=ipv6).
systemd-networkd, network-manager, and dhcpcanon pull in too many
packages/libraries for the initramfs use case (unless using a systemd-
based boot). For example, /lib/systemd/systemd-networkd is 1.6 MB big
and directly depends on 24 libraries.

systemd-networkd is designed to run as a service. It takes no arguments
when called. So it must run as daemon.

Therefore only dhcpcd and udhcpc remain as replacement (for the initramfs). 
From those two, I propose to use dhcpcd as replacement, because:
* It has many features (like classless static routes or DHCP over InfiniBand)
* It is actively developed (normally a few release per year)

** Affects: initramfs-tools (Ubuntu)
 Importance: High
 Assignee: Benjamin Drung (bdrung)
 Status: Triaged


** Tags: fr-2925

** Tags added: fr-2925

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Benjamin Drung (bdrung)

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

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  Replace dhclient with dhcpcd

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  ISC has announced the end of life for ISC DHCP as of the end of 2022.
  Kea is the recommended successor of the DHCP server (isc-dhcp-server).
  This bug report is about replacing the DHCP client (isc-dhcp-client).

  Ubuntu uses NetworkManager on the desktop and systemd-networkd on the
  server as default DHCP client. However isc-dhcp-client is still
  installed as part of all Ubuntu systems, because it is the only client
  implementation that integrates with initramfs-tools. isc-dhcp-client
  is also used by cloud-init and as a command line tool to configure
  transient DHCP on an interface.

  There are following requirements for the replacement DHCP client:
  1. The DHCP client must support DHCPv6.
  2. The DHCP client in the initramfs should be small enough to not increase 
the size noticeable.
  3. The DHCP client needs to be callable from the shell (for initramfs and 
cloud-init)

  The Ubuntu desktop uses network-manager and the server/cloud images
  uses systemd-networkd. So there is no need for changing the DHCP
  client on booted systems, but the initramfs uses dhclient from isc-
  dhcp-client.

  ipconfig (from klibc-utils) does not support DHCPv6 (but there is work
  in progress in
  https://git.kernel.org/pub/scm/linux/kernel/git/bwh/klibc.git/?h=ipv6).
  systemd-networkd, network-manager, and dhcpcanon pull in too many
  packages/libraries for the initramfs use case (unless using a systemd-
  based boot). For example, /lib/systemd/systemd-networkd is 1.6 MB big
  and directly depends on 24 libraries.

  systemd-networkd is designed to run as a service. It takes no
  arguments when called. So it must run as daemon.

  Therefore only dhcpcd and udhcpc remain as replacement (for the initramfs). 
From those two, I propose to use dhcpcd as replacement, because:
  * It has many features (like classless static routes or DHCP over InfiniBand)
  * It is actively developed (normally a few release per year)

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


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

[Touch-packages] [Bug 1980462] Re: manual sync with Debian 4.4.3

[Benjamin Drung]

Ubuntu has 4.4.3-P1-2ubuntu2 and therefore is in sync with Debian.

We are working on replacing dhclient with dhcpcd from dhcpcd-base. I am
in the process of replacing it in initramfs-tools and there are subtle
differences which needs more changes than just a command replacement. I
created bug #2024164 as tracking ticket.

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Fix Released

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

Title:
  manual sync with Debian 4.4.3

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  Debian has recently updated its isc-dhscp package with the latest
  upstream. It might be useful for Ubuntu to sync.

  This ISC DHCP will be upstream's very last release as they are
  retiring the codebase and focusing their efforts on a brand new DHCP
  server. Support will still be offered for the server for a while.

  Meanwhile, the client and relay are no longer supported. Upstream
  recommends migrating to other clients and relays.

  Debian has recently updated its package of dhcpcd to the latest
  upstream. The binary target "dhcpcd-base" works well as a drop-in
  replacement for dhclient on systems that boot using ifupdown. Ubuntu
  might wanna consider migrating to that now that ISC dhclient has been
  deprecated upstream.

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


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

[Touch-packages] [Bug 1922047]

[Botond-2]

(In reply to Alexander Browne from comment #7)
> > in gtk, kinetic scrolling stops after you put a finger on the touchpad 
> > (zwp_pointer_gesture_hold_v1 event), but in firefox it doesn't, you have to 
> > wait
> 
> In GTK 4, and Firefox uses GTK 3. So either someone need to add it to GTK 3 
> or Firefox needs to use to GTK 4.

Yeah. We have bug 1568722 open about this, and like you say it's blocked
on hold gestures being backported to GTK 3. It would be great if that
happened; as I mentioned in [this
comment](https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3454#note_1427920),
we only need a backport of the GDK layer of hold gestures, not the whole
thing.

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Confirmed
Status in GTK+:
  Fix Released
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Touch-packages] [Bug 1922047]

[Alexander Browne]

> in gtk, kinetic scrolling stops after you put a finger on the touchpad
(zwp_pointer_gesture_hold_v1 event), but in firefox it doesn't, you have
to wait

In GTK 4, and Firefox uses GTK 3. So either someone need to add it to
GTK 3 or Firefox needs to use to GTK 4.

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Confirmed
Status in GTK+:
  Fix Released
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Touch-packages] [Bug 1922047]

[Two-b]

> kept scrolling too long after releasing

this is probably another thing
in gtk, kinetic scrolling stops after you put a finger on the touchpad 
(zwp_pointer_gesture_hold_v1 event), but in firefox it doesn't, you have to wait

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Confirmed
Status in GTK+:
  Fix Released
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Touch-packages] [Bug 1922047]

[Z-val]

I did also like fast speed, but it should be in line with regular GTK
apps and shouldn't shock new users by feeling 5x faster that them…

> Would you like to write a patch?

I don't currently have a dev setup sooo no..

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Confirmed
Status in GTK+:
  Fix Released
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Touch-packages] [Bug 1922047]

[Botond-2]

Heh, I'm used to the faster speed now and the pref changes in the
previous comment feel quite slow :) But that's probably just familiarity
bias rather than the current defaults being objectively better.

So, yes, I'm open to changing the defaults. Maybe we can start with just
flipping `delta_mode` on the Nightly branch and see what feedback we
get?

Would you like to write a patch?

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Confirmed
Status in GTK+:
  Fix Released
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Touch-packages] [Bug 1922047]

[Z-val]

Hi, the person who originally implemented the scrolling with the wrong
mode only here :)

It's been a year since the original discussions and looks like everyone
has forgotten about it, oops :/

Was just talking with a friend who was trying Linux out and complained
about this:

> [scrolling] was just easily 5x worse in firefox. everything was too
fast and kept scrolling too long after releasing

Please do flip the default to `apz.gtk.kinetic_scroll.mode=2`,
*everyone* liked it in the Bug 1752862 discussion!

I would also suggest `apz.fling_friction=0.004-if-gtk`, and
`apz.gtk.kinetic_scroll.pixel_mode_multiplier=25` seems to be what
people have agreed on from that previous discussion, but those are
subtler and not nearly as crucial as the mode.

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Confirmed
Status in GTK+:
  Fix Released
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Touch-packages] [Bug 2024154] [NEW] package libcap2:amd64 1:2.44-1ubuntu0.22.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

[mohamed rjeb]

Public bug reported:

can't install samba to share my work folders locally
it says:

Package operation failed

The installation or removal of a software package failed.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libcap2:amd64 1:2.44-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Jun 16 09:29:48 2023
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2023-06-01 (14 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.9
SourcePackage: libcap2
Title: package libcap2:amd64 1:2.44-1ubuntu0.22.04.1 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: libcap2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package libcap2:amd64 1:2.44-1ubuntu0.22.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libcap2 package in Ubuntu:
  New

Bug description:
  can't install samba to share my work folders locally
  it says:

  Package operation failed

  The installation or removal of a software package failed.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libcap2:amd64 1:2.44-1ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Jun 16 09:29:48 2023
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2023-06-01 (14 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: libcap2
  Title: package libcap2:amd64 1:2.44-1ubuntu0.22.04.1 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)

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


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

[Touch-packages] [Bug 2024154] Re: package libcap2:amd64 1:2.44-1ubuntu0.22.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libcap2:amd64 1:2.44-1ubuntu0.22.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libcap2 package in Ubuntu:
  New

Bug description:
  can't install samba to share my work folders locally
  it says:

  Package operation failed

  The installation or removal of a software package failed.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libcap2:amd64 1:2.44-1ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Jun 16 09:29:48 2023
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2023-06-01 (14 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: libcap2
  Title: package libcap2:amd64 1:2.44-1ubuntu0.22.04.1 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)

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


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

[Touch-packages] [Bug 2024153] [NEW] package initramfs-tools 0.142ubuntu2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde

[René Meerts]

Public bug reported:

RaspberryPI image Berryboot Ubuntu latest version

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: initramfs-tools 0.142ubuntu2
Uname: Linux 5.10.43v64 aarch64
ApportVersion: 2.26.1-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Fri Jun 16 10:12:05 2023
ErrorMessage: subproces van pakket initramfs-tools werd script 
post-installation geïnstalleerd gaf de foutwaarde 2 terug
ImageMediaBuild: 20230417
PackageArchitecture: all
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.142ubuntu2 failed to install/upgrade: 
subproces van pakket initramfs-tools werd script post-installation 
geïnstalleerd gaf de foutwaarde 2 terug
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package arm64 arm64-image lunar raspi-image

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

Title:
  package initramfs-tools 0.142ubuntu2 failed to install/upgrade:
  subproces van pakket initramfs-tools werd script post-installation
  geïnstalleerd gaf de foutwaarde 2 terug

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  RaspberryPI image Berryboot Ubuntu latest version

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: initramfs-tools 0.142ubuntu2
  Uname: Linux 5.10.43v64 aarch64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri Jun 16 10:12:05 2023
  ErrorMessage: subproces van pakket initramfs-tools werd script 
post-installation geïnstalleerd gaf de foutwaarde 2 terug
  ImageMediaBuild: 20230417
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.142ubuntu2 failed to install/upgrade: 
subproces van pakket initramfs-tools werd script post-installation 
geïnstalleerd gaf de foutwaarde 2 terug
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2022927] Re: Busybox mount fails to mount Snaps

[Isaac True]

Hi Lucas, thanks for the assistance.

Here's the .debdiff without the ~ppa2 suffix. I opted to go with ubuntu2
because it's not really a security fix, so I wasn't sure if it's really
appropriate to add the security .1 suffix.

The .debdiff is valid for both lunar and mantic, as mantic is still
using the same version as lunar (see
https://git.launchpad.net/ubuntu/+source/busybox/tree/debian/changelog?h=ubuntu/mantic),
and still has the same series.

Our customer doesn't need jammy, so we don't need to go through the SRU
process for this - just getting it into the latest development release
is fine.

** Patch added: "busybox-1.35.0-4ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+attachment/5680138/+files/busybox-1.35.0-4ubuntu2.debdiff

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

Title:
  Busybox mount fails to mount Snaps

Status in busybox package in Ubuntu:
  New

Bug description:
  Snapd tries to mount squashfs Snaps with non-standard mount flags like
  "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to
  userspace programs that a given mount should not be shown in a list of
  mounted partitions/filesystems. Busybox does not support these flags,
  and so fails with "Invalid argument".

  $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test
  mount: mounting test on /tmp/test failed: Invalid argument

  These flags can likely be be safely ignored, as they don't actually
  affect the functionality of the mount. This goes for all mount options
  starting with "x-", as these generally denote non-standard mount
  option "extensions".

  I've created a patch against Busybox which adds an optional
  configuration item to ignore all mount options beginning with "x-". An
  additional verbose option has also been added to enable the ability to
  report that the mount flags have been ignored, rather than silently
  ignoring them.

  This is a requirement for a customer project, where we are limited to
  using Busybox (due to coreutils' GPL-3.0 licence) but would also
  require using Snaps like checkbox for testing and verification. This
  was posted on the Busybox mailing list a few months ago
  (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html)
  but patch acceptance there seems to take quite a long time, and we
  need this for the customer.

  A PPA containing the patched Busybox version is available on the
  project's Launchpad team: https://launchpad.net/~nemos-
  team/+archive/ubuntu/ppa

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


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

[Touch-packages] [Bug 1677827] Re: Missing dep8 tests

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~mirespace/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/442007

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

Title:
  Missing dep8 tests

Status in dnsmasq package in Ubuntu:
  New
Status in dnsmasq package in Debian:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source dnsmasq zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/dnsmasq
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3XcdAAoJEIP8BxPaZgwlCPUQAIeBwdnTYjMB0QFt7FZSUOqx
  9N4PMHdxodMVmtEW2FytBuuq0S1jTyu06GNsLwKBmzfyuICScCoGPt8KS14omp/R
  g0QAA4Fk2T6YMtVdsZIflUpMzlNTiFw2Ndgf7LOs3xX2lkB36xqbWlr+86fCTe+2
  O8pzYZoQeveHc7XQxlT0eDFCiZx83ZFwjF8OjgGfWY3iQsvcb2T00hKlkpQ2qCdT
  uiBTN6xnw9v50OGGlphObRy4YdE8x4u3/jWFOzwKUk5X1Qi31wK9hQYLSBAgX7Ph
  kkL681OBi5RIlUO5QsD3qJPvi3OIGMx2zhMvQfcK8Otn5DMwDoEETOAafMvPmhd/
  NUK/OaNcB2TR6Sl5Jt/NUp3E0LRTYgbMuEONkEeBm5YdABb7hUcYRPomnpzCcNBL
  iSdcEH2khGbiCK3oYcT5UgtBe4MFlpHHkkQzmew/nLNZ/BrgULFs0HWLXu8gWN8g
  Wn0iAF/Ft2kcWgRNXJ3JCd2nc04U0hqiUmMtVXku4r0f3fxfTudtvPACcZC7ctKb
  0rqChEm0r/ewtHvLcuOFIIJBaTQxoQmm8zBPv/y/S+YdkwmVYS9LlWKqG54KLlPy
  iAt7+/GvQ0fqqzmk88yQ5F4L19Dg+X5fLZVM1wBvvQ4nTsJRfUhf3+I2orcKDy6C
  zNZGvitiod7eMrypmXIA
  =k1Nj
  -END PGP SIGNATURE-

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


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

[Touch-packages] [Bug 2023979] Re: Ubuntu don't see second monitor after ssd replacing to another laptop.

[Daniel van Vugt]

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

** Tags added: amdgpu hybrid multigpu multimonitor nouveau

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

Title:
  Ubuntu don't see second monitor after ssd replacing to another laptop.

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu don't see second monitor after ssd replacing to another laptop.
  Also Ubuntu don't see that laptonp working from charger and not from
  battery.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 15 12:08:01 2023
  DistUpgraded: 2023-01-10 10:20:22,046 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtbth/3.9.8, 5.15.0-73-generic, x86_64: installed
   rtbth/3.9.8, 5.19.0-42-generic, x86_64: installed
   rtbth/3.9.8, 5.19.0-43-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GA106M [GeForce RTX 3060 Mobile / 
Max-Q] [1025:151f]
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Cezanne [1025:151f]
  InstallationDate: Installed on 2021-04-02 (803 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Acer Nitro AN517-41
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=9b25e014-685a-48c2-a845-93fba62dce47 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2023-01-10 (156 days ago)
  dmi.bios.date: 07/21/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kamiq_CAS
  dmi.board.vendor: CZ
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd07/21/2021:br1.8:efr1.5:svnAcer:pnNitroAN517-41:pvrV1.08:rvnCZ:rnKamiq_CAS:rvrV1.08:cvnAcer:ct10:cvrV1.08:sku:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN517-41
  dmi.product.sku: 
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2023927] Re: Screen flickering whe update images

[Daniel van Vugt]

Thanks for the bug report. Please try adding the following kernel
parameter:

  i915.enable_psr=0

to /etc/default/grub under GRUB_CMDLINE_LINUX_DEFAULT, then run:

  sudo update-grub

and reboot. Finally check to see that it's being used:

  cat /proc/cmdline

** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu)

** Changed in: linux-hwe-5.13 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Screen flickering whe update images

Status in linux-hwe-5.13 package in Ubuntu:
  Incomplete

Bug description:
  Often, when there are small changes in image displayed, an horizontal 
flickering is observed. This happen for example on a mouse right button menu, 
or when a hyperlink description appears on the screen bottom when mouse pointer 
cross some field on a webpage, also when favorites menu appear.
  The flickering usually disappear in a few moments, sometimes (usually when a 
few pixels are updating) it can last for seconds.
  This flickering is caused by a late updating of some horizontal lines, so for 
awhile a few lines of previous image coexist with a majority of new ones

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 14 22:44:12 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.32, 5.13.0-40-generic, x86_64: installed
   virtualbox, 6.1.32, 5.13.0-41-generic, x86_64: installed
   virtualbox, 6.1.32, 5.4.0-126-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Device [1e39:a025]
  InstallationDate: Installed on 2022-01-01 (529 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb: Error: command ['lsusb'] failed with exit code 127: lsusb: symbol 
lookup error: lsusb: undefined symbol: libusb_error_name
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 127: lsusb: 
symbol lookup error: lsusb: undefined symbol: libusb_error_name
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 127: lsusb: 
symbol lookup error: lsusb: undefined symbol: libusb_error_name
  MachineType: MEDION S15449
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic 
root=UUID=cbfc0023-baf3-4a11-b0aa-6dadbd0f60f7 ro quiet splash pci=noaer 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 212
  dmi.board.asset.tag: Default string
  dmi.board.name: M15T
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr212:bd04/09/2021:br5.19:svnMEDION:pnS15449:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:skuML-23000830031014:
  dmi.product.family: Akoya
  dmi.product.name: S15449
  dmi.product.sku: ML-230008 30031014
  dmi.product.version: Default string
  dmi.sys.vendor: MEDION
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Timo Aaltonen]

marking invalid for lunar as it's not currently affected, and the next
upload will bump to latest upstream version and also change the string
to address this bug, but no need to verify that one for lunar

** Changed in: mesa (Ubuntu Lunar)
   Status: Confirmed => Invalid

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  Invalid

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 1699033] Re: Two-finger right click does not work in gnome-shell

[Daniel van Vugt]

Now tracking in bug 2024135.

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

Title:
  Two-finger right click does not work in gnome-shell

Status in GSettings Desktop Schemas:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released

Bug description:
  Using two fingers on the clickpad to right click does not work in
  gnome-shell.

  It seems to be defaulting to the old-style single finger click in the
  bottom right corner to do a right click.

  Workaround:
  gnome-tweak-tool > Keyboard & Mouse > Touchpad > Click Method = Fingers

  Gsettings diff:
  < org.gnome.desktop.peripherals.touchpad click-method 'default'
  ---
  > org.gnome.desktop.peripherals.touchpad click-method 'fingers'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.11.0-7.12-generic 4.11.6
  Uname: Linux 4.11.0-7-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Tue Jun 20 14:50:10 2017
  DisplayManager: lightdm
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-06-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170613)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2024135] [NEW] Default right click method on touchpads should be with two fingers

[Daniel van Vugt]

Public bug reported:

The default right click method on touchpads should be with two fingers
so you can right click without having to look at the touchpad. Modern
laptops have supported this for a decade, modern OSes like macOS and
ChromeOS default to it, and upstream GNOME has defaulted to it since
version 3.28 in 2018.

This issue was fixed at the start of 2018 in bug 1699033, but then
reverted again in: https://launchpad.net/ubuntu/+source/ubuntu-
settings/18.10.8

** Affects: gnome-control-center
 Importance: Unknown
 Status: Unknown

** Affects: ubuntu-settings (Ubuntu)
 Importance: Wishlist
 Status: New

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2530
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2530

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2530
   Importance: Unknown
   Status: Unknown

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

Title:
  Default right click method on touchpads should be with two fingers

Status in gnome-control-center:
  Unknown
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The default right click method on touchpads should be with two fingers
  so you can right click without having to look at the touchpad. Modern
  laptops have supported this for a decade, modern OSes like macOS and
  ChromeOS default to it, and upstream GNOME has defaulted to it since
  version 3.28 in 2018.

  This issue was fixed at the start of 2018 in bug 1699033, but then
  reverted again in: https://launchpad.net/ubuntu/+source/ubuntu-
  settings/18.10.8

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


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