from:"A"

Hello Chris, or anyone else affected,

Accepted apport into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu82.6 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: apport (Ubuntu Jammy)
   Status: New => 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/2067775

Title:
  subiquity package-hook is outdated

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Jammy:
  Fix Committed
Status in apport source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  The Subiquity package hook in Apport has not been updated to collect
  the type of information we are typically interested in (e.g.
  /var/log/installer/\*). This means users who run `ubuntu-bug
  subiquity` from the terminal will not automatically collect relevant
  information to attach to their bug reports. This upload fixes this by
  updating Subiquity's package hook to collect logs and information
  typically used for debugging Subiquity bugs. This fix needs to be SRUd
  to Noble and Jammy so that users performing these installs can run
  `ubuntu-bug subiquity` and collect relevant information.

  [Test Plan]

  The test plan is focused on testing the behavior of apport within the
  live installation environment, where we primarily expect users to
  submit bug reports from. Thus the test plan is split into three
  different test plans: Two for Desktop images and one for Server. For
  Noble, all three test scenarios are relevant. For Jammy, it is only
  necessary to test Server since the Desktop installer for Jammy is not
  Subiquity based.

  Desktop - Manual:
  1) Download the latest Noble Desktop ISO [1].
  2) Begin an installation using the media you downloaded. You may progress the 
install as far as you like, with the following restrictions: (1) At minimum you 
need wait for the first screen to show up and (2) at most you may allow the 
install to finish but do not allow the system to restart (you need to be in the 
live-environment to proceed).
  3) Open a terminal (ctl + alt + t) 
  4) Enable proposed[4] and update apport
  5) Run the following command "APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug 
subiquity"
  6) 4 authorization prompts will display, requesting access to collect 
information from the system. Allow all of them.
  7) Inspect the fields of the report and ensure that none report "permission 
denied" or similar. 
  8) Click "Send" on the resulting dialog to send the report. Firefox will open 
up to finish filling out the bug information on launchpad.
  9) Log in and enter anything as the title and hit continue. Click "No, I need 
to report a new bug" if necessary
  10) Enter anything in the "further information section". Ensure that the 
field below this section, titled "This bug contains information that is", is 
marked "Private" by default.
  11) You can now submit the bug and inspect the automatically filled 
description for further errors in the report. (Errors messages are typically 
short enough to show up in the body of the bug description while larger 
attachments with real information end up as attachments)

  Desktop - Automatic:
  1) Download the latest Noble Desktop ISO [1].
  2) Begin an installation using the media you downloaded. You may progress the 
install as far as you like, with the following restrictions: (1) At minimum you 
need wait for the first screen to show up and (2) at most you may allow the 
install to finish but do not allow the system to restart (you need to be in the 
live-environment to proceed).
  3) Open a terminal (ctl + alt + t) 
  4) Enable proposed[4] and update apport
  5) Create a fake subiquity crash file: sudo printf "Package: 
subiquity\nProblemType: crash\n" >

[Touch-packages] [Bug 2067775] Re: subiquity package-hook is outdated

Hello Chris, or anyone else affected,

Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: apport (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  subiquity package-hook is outdated

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Jammy:
  New
Status in apport source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  The Subiquity package hook in Apport has not been updated to collect
  the type of information we are typically interested in (e.g.
  /var/log/installer/\*). This means users who run `ubuntu-bug
  subiquity` from the terminal will not automatically collect relevant
  information to attach to their bug reports. This upload fixes this by
  updating Subiquity's package hook to collect logs and information
  typically used for debugging Subiquity bugs. This fix needs to be SRUd
  to Noble and Jammy so that users performing these installs can run
  `ubuntu-bug subiquity` and collect relevant information.

  [Test Plan]

  The test plan is focused on testing the behavior of apport within the
  live installation environment, where we primarily expect users to
  submit bug reports from. Thus the test plan is split into three
  different test plans: Two for Desktop images and one for Server. For
  Noble, all three test scenarios are relevant. For Jammy, it is only
  necessary to test Server since the Desktop installer for Jammy is not
  Subiquity based.

  Desktop - Manual:
  1) Download the latest Noble Desktop ISO [1].
  2) Begin an installation using the media you downloaded. You may progress the 
install as far as you like, with the following restrictions: (1) At minimum you 
need wait for the first screen to show up and (2) at most you may allow the 
install to finish but do not allow the system to restart (you need to be in the 
live-environment to proceed).
  3) Open a terminal (ctl + alt + t) 
  4) Enable proposed[4] and update apport
  5) Run the following command "APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug 
subiquity"
  6) 4 authorization prompts will display, requesting access to collect 
information from the system. Allow all of them.
  7) Inspect the fields of the report and ensure that none report "permission 
denied" or similar. 
  8) Click "Send" on the resulting dialog to send the report. Firefox will open 
up to finish filling out the bug information on launchpad.
  9) Log in and enter anything as the title and hit continue. Click "No, I need 
to report a new bug" if necessary
  10) Enter anything in the "further information section". Ensure that the 
field below this section, titled "This bug contains information that is", is 
marked "Private" by default.
  11) You can now submit the bug and inspect the automatically filled 
description for further errors in the report. (Errors messages are typically 
short enough to show up in the body of the bug description while larger 
attachments with real information end up as attachments)

  Desktop - Automatic:
  1) Download the latest Noble Desktop ISO [1].
  2) Begin an installation using the media you downloaded. You may progress the 
install as far as you like, with the following restrictions: (1) At minimum you 
need wait for the first screen to show up and (2) at most you may allow the 
install to finish but do not allow the system to restart (you need to be in the 
live-environment to proceed).
  3) Open a terminal (ctl + alt + t) 
  4) Enable proposed[4] and update apport
  5) Create a fake subiquity crash file: sudo printf "Package: 
subiquity\nProblemType: crash\n" >

[Touch-packages] [Bug 2067120] Re: apport-retrace crashed with subprocess.CalledProcessError in check_call(): Command '['dpkg', '-x', '/srv/vms/apport-retrace/Ubuntu 24.04/apt/var/cache/apt/archives//

Hello Brian, or anyone else affected,

Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: apport (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  apport-retrace crashed with subprocess.CalledProcessError in
  check_call(): Command '['dpkg', '-x', '/srv/vms/apport-retrace/Ubuntu
  24.04/apt/var/cache/apt/archives//base-files_13ubuntu9_amd64.deb',
  '/tmp/apport_sandbox_zj9wto2z']' returned non-zero exit status 2.

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  I'm finding it impossible to retrace any crashes with the version of
  apport packaged in noble or with upstream commit id
  adfe3698731b69b0f19ca36ecca90d8e96001250.

  The retracing process ends with the following lines:

  Extracting downloaded debs...
  tar: ./lib: Cannot create symlink to ‘usr/lib’: File exists
  tar: Exiting with failure status due to previous errors
  dpkg-deb: error: tar subprocess returned error exit status 2
  Traceback (most recent call last):
    File "/usr/bin/apport-retrace", line 696, in 
  main()
    File "/usr/bin/apport-retrace", line 465, in main
  sandbox, cache, outdated_msg = apport.sandboxutils.make_sandbox(
     ^
    File "/usr/lib/python3/dist-packages/apport/sandboxutils.py", line 227, in 
make_sandbox
  outdated_msg = packaging.install_packages(
     ^^^
    File "/usr/lib/python3/dist-packages/apport/packaging_impl/apt_dpkg.py", 
line 1350, in install_packages
  subprocess.check_call(["dpkg", "-x", i.destfile, rootdir])
    File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['dpkg', '-x', 
'/srv/vms/apport-retrace/Ubuntu 
24.04/apt/var/cache/apt/archives//base-files_13ubuntu9_amd64.deb', 
'/tmp/apport_sandbox_zj9wto2z']' returned non-zero exit status 2.

  I've tried cleaning the cache, /srv/vms/apport-retrace/Ubuntu 24.04/,
  but the retracing process continues to fail. The crashes I'm trying to
  retrace have been uploaded to Launchpad and still have the coredumps
  attached but I'd be happy to subscribe an apport developer to them.

  [ Test Plan ]

  The fix for this bug adds four new system test cases. These system
  test cases are run in the autopkgtest. Check that those four test
  cases succeed on amd64 on autopkgtest.

  [ Where problems could occur ]

  The fix touches apport-retrace. This binary is not installed by
  default, but is used by us to retrace users reports and by users to
  retrace their own crashes. This fix might reveal new issues with
  apport-retrace and it will hopefully help retracing more bugs on
  Launchpad. This should lead to more bug reports.

  [ Other Info ]

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: apport-retrace 2.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset wl nvidia zfs
  ApportLog:

  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 24 16:03:45 2024
  ExecutablePath: /usr/bin/apport-retrace
  ExecutableTimestamp: 1713871810
  InstallationDate: Installed on 2018-08-10 (2114 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterpreterPath:

[Touch-packages] [Bug 2066995] Re: /var/crash has perm 1777 (was: apport-gtk keeps prompting to report crashes in a loop)

Hello Steve, or anyone else affected,

Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: apport (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  /var/crash has perm 1777 (was: apport-gtk keeps prompting to report
  crashes in a loop)

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  On affected systems, Python crashes will be owned by the crashing
  group instead of whoopsie. This causes whoopsie to fail reading and
  uploading the crash report. So a lot of Python crashes were not
  reporting and keeping us blind.

  [ Test Plan ]

  1. Reconstruct the problem by setting the permission of /var/crash to 1777.
  2. Upgrade Apport to the fixed version
  3. Verify that /var/crash has the permission 3777 after the update.
  4. Run and crash a random Python script (needs to be from a Ubuntu package)
  5. Verify that the Python crash was correctly uploaded.

  [ Where problems could occur ]

  The fix touched the /var/crash permission and the apport.service
  startup code. This might lead to failures on custom setup (despite
  using similar postinst code than whoopsie).

  This fix might still not address the initial bug report of reporting
  crashes in a loop. In this case a follow-up bug report should be
  started.

  [ Original report ]

  /var/crash has the following contents:

  -rw-r- 1 vorlon   vorlon   107490 May 23 16:05 
_usr_bin_gourmand.1000.crash
  -rw-rw-r-- 1 vorlon   vorlon0 May 23 16:06 
_usr_bin_gourmand.1000.upload
  -rw--- 1 whoopsie whoopsie  5 May 23 16:07 
_usr_bin_gourmand.1000.uploaded
  -rw-r- 1 vorlon   vorlon23647 May 23 13:57 
_usr_bin_python-argcomplete-check-easy-install-script.1000.crash
  -rw-rw-r-- 1 vorlon   vorlon0 May 23 13:59 
_usr_bin_python-argcomplete-check-easy-install-script.1000.upload
  -rw--- 1 whoopsie whoopsie  5 May 23 13:59 
_usr_bin_python-argcomplete-check-easy-install-script.1000.uploaded

  As seen, the .upload / .uploaded files were created within 2 minutes
  of each of the crashes.

  But after submitting the crash report for /usr/bin/python-argcomplete-
  check-easy-install-script, I left my desktop for a while.  I came back
  to find at least TWENTY dialogs prompting me to submit the same crash
  report.

  The only way to stop the system from creating more prompts is to
  remove these files from disk.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportLog:

  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 23 16:06:43 2024
  InstallationDate: Installed on 2019-12-23 (1613 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to noble on 2024-05-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2066995/+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 2069360] Re: apport-autoreport.service fails if autoreporting is disabled

Hello Benjamin, or anyone else affected,

Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: apport (Ubuntu Noble)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  apport-autoreport.service fails if autoreporting is disabled

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  apport-autoreport.service fails if auto-reporting is disabled:

  ```
  $ systemctl status apport-autoreport.service
  × apport-autoreport.service - Process error reports when automatic reporting 
is enabled
   Loaded: loaded (/usr/lib/systemd/system/apport-autoreport.service; 
static)
   Active: failed (Result: exit-code) since Thu 2024-06-13 21:55:08 CEST; 
1h 9min ago
  TriggeredBy: ● apport-autoreport.timer
   ● apport-autoreport.path
  Process: 1059564 ExecStart=/usr/share/apport/whoopsie-upload-all 
--timeout 20 (code=exited, status=1/FAILURE)
     Main PID: 1059564 (code=exited, status=1/FAILURE)
  CPU: 86ms

  Jun 13 21:55:08 host systemd[1]: Starting apport-autoreport.service - Process 
error reports when automatic reporting is enabled...
  Jun 13 21:55:08 host whoopsie-upload-all[1059564]: ERROR: whoopsie.path is 
not enabled
  Jun 13 21:55:08 host systemd[1]: apport-autoreport.service: Main process 
exited, code=exited, status=1/FAILURE
  Jun 13 21:55:08 host systemd[1]: apport-autoreport.service: Failed with 
result 'exit-code'.
  Jun 13 21:55:08 host systemd[1]: Failed to start apport-autoreport.service - 
Process error reports when automatic reporting is enabled.
  ```

  This service failure might mislead user thinking that there is a
  problem.

  [ Test Plan ]

  1. Disable auto-reporting in the system setting:
* open gnome-control-center or unity-control-center
* Switch to "Security & Privacy" panel
* Select "Diagnosticts" tab
* unselect "Send error reports to Canonical"
  2. Produce a crash, e.g. by running divide-by-zero from chaos-marmosets
  3. Check that apport-autoreport.service is failing as above
  4. Upgrade Apport to the fixed version
  5. Restart apport-autoreport.service
  6. apport-autoreport.service should exit successfully

  [ Where problems could occur ]

  This code change touches the auto-reporting part. Failures there could
  lead to less bugs being forwarded to the error tracker. This might be
  noticeable when looking at the number of submissions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2069360/+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 2072751] Re: The ubuntu-desktop-bootstrap hook isn't working

Hello Sebastien, or anyone else affected,

Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: apport (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  The ubuntu-desktop-bootstrap hook isn't working

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Noble:
  Fix Committed

Bug description:
  * Impact

  The current ubuntu-desktop-bootstrap hook has some errors and isn't
  working properly as a result

  - it's reporting issues to https://launchpad.net/ubuntu-desktop-
  bootstrap which is the wrong project (bootstrap is the snap name but
  it's built from ubuntu-desktop-provision)

  - it's failing to attach the subiquity log since that one isn't user
  readable

  - the name of some of the curting files is incorrect

  * Test case

  - start a Noble desktop ISO
  - install the apport package update
  - do an installation, select custom partitioning and define a vfat partition 
to use for /boot (which is going to make the installer error out)
  - go through the other installer steps, keeping default
  - wait for the error screen to show
  - run
  $ ubuntu-bug ubuntu-desktop-installer
  - log into launchpad and submit the report

  The report should be sent against the ubuntu-desktop-provision project
  on launchpad and include ubuntu_bootstrap.log, subiquity-server-
  debug.log and curtin-install.log/curtin-error.tar

  * Regression potential

  The changes in the ubuntu-desktop-bootstrap hook and should impact
  only reporting against that component

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2072751/+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 2036467] Please test proposed package

Hello Krister, or anyone else affected,

Accepted e2fsprogs into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/e2fsprogs/1.45.5-2ubuntu1.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-
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 e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2036467

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  Fix Committed
Status in e2fsprogs source package in Jammy:
  Fix Committed
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in e2fsprogs source package in Mantic:
  Won't Fix
Status in e2fsprogs source package in Noble:
  Fix Committed
Status in e2fsprogs source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

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

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

Hello Krister, or anyone else affected,

Accepted e2fsprogs into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/e2fsprogs/1.46.5-2ubuntu1.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: e2fsprogs (Ubuntu Focal)
   Status: In Progress => 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 e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2036467

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  Fix Committed
Status in e2fsprogs source package in Jammy:
  Fix Committed
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in e2fsprogs source package in Mantic:
  Won't Fix
Status in e2fsprogs source package in Noble:
  Fix Committed
Status in e2fsprogs source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in

[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

Hello Krister, or anyone else affected,

Accepted e2fsprogs into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/e2fsprogs/1.47.0-2.4~exp1ubuntu4.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: e2fsprogs (Ubuntu Noble)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  Fix Committed
Status in e2fsprogs source package in Jammy:
  Fix Committed
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in e2fsprogs source package in Mantic:
  Won't Fix
Status in e2fsprogs source package in Noble:
  Fix Committed
Status in e2fsprogs source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not

[Touch-packages] [Bug 2075204] Re: gdb on s390x chokes on divide-by-zero from chaos-marmosets

2024-07-31 Thread Frank Heimes

** Tags added: reverse-proxy-bugzilla s390x

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => bugproxy (bugproxy)

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

Title:
  gdb on s390x chokes on divide-by-zero from chaos-marmosets

Status in Ubuntu on IBM z Systems:
  New
Status in gdb package in Ubuntu:
  New

Bug description:
  To help in the development of apport we're using the chaos-marmosets
  set of binaries, which triggers various crashes. In particular, we're
  using /usr/bin/divide-by-zero which does as its name indicates, which
  naturally triggers a native crash.

  However, GDB fails on s390x. Note that for the following I have the
  debugging symbols from ddebs.ubuntu.com installed:

  ubuntu@glibc-proposed:/tmp$ gdb /usr/bin/divide-by-zero
  [snip]
  Reading symbols from /usr/bin/divide-by-zero...
  Reading symbols from 
/usr/lib/debug/.build-id/14/82d2d64c3383ca479f17bfd17b314295c99f13.debug...
  (gdb) run
  Starting program: /usr/bin/divide-by-zero
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1".

  Program received signal SIGTRAP, Trace/breakpoint trap.
  0x02aa0814 in ?? ()
  (gdb) bt
  #0  0x02aa0814 in ?? ()
  #1  0x03fff7d2baac in __libc_start_call_main (main=0x2aa0690 , 
main@entry=, 
argc=argc@entry=1, argv=argv@entry=0x3ffa468)
  at ../sysdeps/nptl/libc_start_call_main.h:58
  #2  0x03fff7d2bbae in __libc_start_main_impl (main=, 
argc=1, argv=0x3ffa468, init=, fini=, 
rtld_fini=0x3fff7f85650 <_dl_fini>,
  stack_end=0x3ffa3b0) at ../csu/libc-start.c:360
  #3  0x02aa0720 in _start ()
  (gdb) info address divide_by_zero
  Symbol "divide_by_zero" is a function at address 0x2aa0810.
  (gdb)

  So at this point GDB isn't capable of identifying the various symbols
  on the stack, which isn't ideal.

  Now, if I try to step in:

  ubuntu@glibc-proposed:/tmp$ gdb -q /usr/bin/divide-by-zero
  Reading symbols from /usr/bin/divide-by-zero...
  Reading symbols from 
/usr/lib/debug/.build-id/14/82d2d64c3383ca479f17bfd17b314295c99f13.debug...
  (gdb) start
  Temporary breakpoint 1 at 0x690: file divide-by-zero.c, line 29.
  Starting program: /usr/bin/divide-by-zero
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1".

  Temporary breakpoint 1, main (argc=1, argv=0x3ffa468) at 
divide-by-zero.c:29
  warning: 29 divide-by-zero.c: No such file or directory
  (gdb) s
  34  in divide-by-zero.c
  (gdb)
  divide_by_zero () at divide-by-zero.c:25
  25  in divide-by-zero.c
  (gdb)
  /build/gdb-nviNEX/gdb-15.1/gdb/infrun.c:2982: internal-error: resume_1: 
Assertion `pc_in_thread_step_range (pc, tp)' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  - Backtrace -
  0x2aa100a247f ???
  0x2aa104efce5 ???
  0x2aa104eff7f ???
  0x2aa10668c13 ???
  0x2aa102553db ???
  0x2aa10255bd1 ???
  0x2aa10255f5f ???
  0x2aa10259195 ???
  0x2aa1025c315 ???
  0x2aa1025e9a5 ???
  0x2aa10260015 ???
  0x2aa1066951b ???
  0x2aa10669e6d ???
  0x2aa102b01cd ???
  0x2aa102b3607 ???
  0x2aa0ffed839 ???
  0x3ffb142baab __libc_start_call_main
  ../sysdeps/nptl/libc_start_call_main.h:58
  0x3ffb142bbad __libc_start_main_impl
  ../csu/libc-start.c:360
  0x2aa0fff8f8f ???
  0x ???
  -
  /build/gdb-nviNEX/gdb-15.1/gdb/infrun.c:2982: internal-error: resume_1: 
Assertion `pc_in_thread_step_range (pc, tp)' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n)

  I can provide a core dump if you think that'd help, but it seems
  trivially reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2075204/+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 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined

2024-07-31 Thread Gianfranco Costamagna

** Also affects: deal.ii (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
  defined

Status in asymptote package in Ubuntu:
  Fix Released
Status in curl package in Ubuntu:
  Fix Released
Status in deal.ii package in Ubuntu:
  New
Status in doxygen package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Triaged
Status in graphite2 package in Ubuntu:
  Fix Released
Status in gsequencer package in Ubuntu:
  Fix Released
Status in gsl package in Ubuntu:
  New
Status in haskell-devscripts package in Ubuntu:
  Fix Released
Status in jose package in Ubuntu:
  New
Status in ksmtuned package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libtpms package in Ubuntu:
  New
Status in mosh package in Ubuntu:
  Fix Released
Status in mpich package in Ubuntu:
  New
Status in mwrap package in Ubuntu:
  Fix Released
Status in proftpd package in Ubuntu:
  New
Status in proftpd-dfsg package in Ubuntu:
  Fix Released
Status in quantlib package in Ubuntu:
  Fix Released
Status in serf package in Ubuntu:
  Fix Released
Status in setserial package in Ubuntu:
  Fix Released
Status in speech-dispatcher package in Ubuntu:
  New
Status in squid package in Ubuntu:
  Fix Released
Status in swtpm package in Ubuntu:
  Fix Released
Status in texinfo package in Ubuntu:
  Triaged
Status in tix package in Ubuntu:
  Fix Released

Bug description:
  The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
  (refined in 1.22.6ubuntu14) can cause this failure:

  ```
  gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
  ```

  This happens when the `-specs=/usr/share/dpkg/elf-package-
  metadata.specs` parameter is set but the needed environment variables
  are not set. Cases:

  1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
  packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
  rp-pppoe fail to build)

  2. autopkgtests

  3. debugging a crash of an application build with the -spec parameter

  4. People like to iteratively continue building the software in the
  build dir while hacking on the package and then have no environment
  variable set.

  This approach is too fragile. An alternative approach would be to specify the 
`--package-metadata` linker flag directly. The problem with that approach is 
that the curly brackets and quotation marks need to be escaped. Example 
failure: Building dpkg would add this parameter to the LDFLAGS:
  ```
  
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
  ```
  The following configure script call (non-relevant parameters deleted):
  ```
  $ gcc 
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
  /usr/bin/ld: cannot find {type:deb: No such file or directory
  /usr/bin/ld: cannot find os:ubuntu: No such file or directory
  /usr/bin/ld: cannot find name:dpkg: No such file or directory
  /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
  /usr/bin/ld: cannot find architecture:amd64}: No such file or directory
  ```

  Proposed solution: Add support for an `--escaped-package-metadata` parameter 
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
  ```
  
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+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 2075283] Re: After putting my system to sleep the whole system just glitches out.

2024-07-31 Thread Daniel van Vugt

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

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


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

** This bug has been marked a duplicate of bug 1876632
   [nvidia] Corrupted/missing shell textures when switching users, switching 
VTs or resuming from suspend

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

Title:
  After putting my system to sleep the whole system just glitches out.

Status in mutter package in Ubuntu:
  New

Bug description:
   Fonts break, system widgets are missing but all applications work fine, the 
glitch is limited to system gui like app tray, toolbar, notiication pannel, 
lock screen etc.
  this can only be then fixed by either logout and login or restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.183.01  Sun May 12 
19:39:15 UTC 2024
   GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 31 11:14:33 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117M [17aa:3a43]
  InstallationDate: Installed on 2024-06-05 (55 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 82B5
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-45-generic 
root=UUID=4ac5db34-f4b4-45c8-94d4-cb551d66fb5d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2022
  dmi.bios.release: 1.39
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55724 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.ec.firmware.release: 1.39
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN39WW:bd09/09/2022:br1.39:efr1.39:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:skuLENOVO_MT_82B5_BU_idea_FM_Legion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  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:21.1.4-2ubuntu1.7~22.04.11
  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/2075283/+subscriptions


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

[Touch-packages] [Bug 2075283] [NEW] After putting my system to sleep the whole system just glitches out.

2024-07-31 Thread Shivam Bansal

Public bug reported:

 Fonts break, system widgets are missing but all applications work fine, the 
glitch is limited to system gui like app tray, toolbar, notiication pannel, 
lock screen etc.
this can only be then fixed by either logout and login or restart.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.183.01  Sun May 12 
19:39:15 UTC 2024
 GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 31 11:14:33 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117M [17aa:3a43]
InstallationDate: Installed on 2024-06-05 (55 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: LENOVO 82B5
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-45-generic 
root=UUID=4ac5db34-f4b4-45c8-94d4-cb551d66fb5d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/09/2022
dmi.bios.release: 1.39
dmi.bios.vendor: LENOVO
dmi.bios.version: EUCN39WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55724 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Legion 5 15ARH05
dmi.ec.firmware.release: 1.39
dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN39WW:bd09/09/2022:br1.39:efr1.39:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:skuLENOVO_MT_82B5_BU_idea_FM_Legion515ARH05:
dmi.product.family: Legion 5 15ARH05
dmi.product.name: 82B5
dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
dmi.product.version: Lenovo Legion 5 15ARH05
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
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:21.1.4-2ubuntu1.7~22.04.11
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

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session

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

Title:
  After putting my system to sleep the whole system just glitches out.

Status in xorg package in Ubuntu:
  New

Bug description:
   Fonts break, system widgets are missing but all applications work fine, the 
glitch is limited to system gui like app tray, toolbar, notiication pannel, 
lock screen etc.
  this can only be then fixed by either logout and login or restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.183.01  Sun May 12 
19:39:15 UTC 2024
   GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture:

[Touch-packages] [Bug 2065180] Re: performance regression in dracut-install 060

2024-07-30 Thread Chris Halse Rogers

Hello Viraniac, or anyone else affected,

Accepted cloud-initramfs-tools into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/cloud-initramfs-tools/0.49~24.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: cloud-initramfs-tools (Ubuntu Noble)
   Status: New => Fix Committed

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

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

Title:
  performance regression in dracut-install 060

Status in Dracut:
  New
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in dracut package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Fix Released
Status in miniramfs package in Ubuntu:
  Fix Released
Status in open-iscsi package in Ubuntu:
  Invalid
Status in thin-provisioning-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Noble:
  Fix Committed
Status in cryptsetup source package in Noble:
  Fix Committed
Status in dracut source package in Noble:
  Fix Released
Status in initramfs-tools source package in Noble:
  Fix Committed
Status in lvm2 source package in Noble:
  Fix Committed
Status in miniramfs source package in Noble:
  New
Status in open-iscsi source package in Noble:
  Fix Released
Status in thin-provisioning-tools source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  When compared to Ubuntu 23.10, creating intramfs files with update-
  initramfs takes 2 to 5 times more time on ARM devices.

  IIUC, dracut-install usage was added to initramfs-tools to speed up
  the process. But now its way slower. Even running update-initramfs on
  jammy, which doesn't use dracut-install, is way faster then the time
  taken on Noble.

  first bad commit -
  
https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870

  Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble)
  with initramfs-tools 0.142ubuntu25.1 takes over six minutes:

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 402.751 s ±  5.592 s[User: 166.316 s, System: 
228.909 s]
    Range (min … max):   394.380 s … 411.445 s10 runs
  ```

  [ Test Plan ]

  1. Measure `update-initramfs -u` before the update.
  2. Log the content of the initrd before the update: `lsinitramfs 
/boot/initrd.img`
  3. update dracut-install / initramfs-tools-core
  4. Measure `update-initramfs -u`. It should be faster (the performance 
improvements on amd64 should be very small and might be within the measurement 
uncertainty).
  5. Check with lsinitramfs that the content of the newly generated initrd 
hasn't changed.

  [ Where problems could occur ]

  The code that is responsible for including the kernel modules into the
  initrd is touched. Negative consequences could be that some needed
  kernel modules will not be included any more (should be covered by the
  test case) or that building new initrds will fail.

  The initramfs-tools fix changes how manual_add_modules behaves.
  `manual_add_modules` does not copy kernel modules, but queues them for
  being copied when the newly added function `apply_add_modules` is
  called.

  I checked all instances of calls to `manual_add_modules` for possible
  regressions (see comment #15). Only miniramfs needs to be adjusted to
  also call `apply_add_modules`. But this change could break consumers
  of the `manual_add_modules` function that are outside of the Ubuntu
  archive. I googled for `apply_add_modules` but found no public outside
  users.

  [ Benchmarks ]

  Stock noble on a Raspberry Pi Zero 2W:

  ```

[Touch-packages] [Bug 2065180] Re: performance regression in dracut-install 060

This bug was fixed in the package dracut - 060+5-1ubuntu3.2

---
dracut (060+5-1ubuntu3.2) noble; urgency=medium

  * Cherry-pick upstream performance fixes (LP: #2065180):
- perf(dracut-install): memoize find_kmod_module_from_sysfs_node
- perf(dracut-install): use driver/module sysfs dirs for module name
  * Depend on isc-dhcp-client for upstream-dracut-network autopkgtest

 -- Benjamin Drung   Mon, 08 Jul 2024 22:47:24 +0200

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

Title:
  performance regression in dracut-install 060

Status in Dracut:
  New
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in dracut package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Fix Released
Status in miniramfs package in Ubuntu:
  Fix Released
Status in open-iscsi package in Ubuntu:
  Invalid
Status in thin-provisioning-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Noble:
  Fix Committed
Status in cryptsetup source package in Noble:
  Fix Committed
Status in dracut source package in Noble:
  Fix Released
Status in initramfs-tools source package in Noble:
  Fix Committed
Status in lvm2 source package in Noble:
  Fix Committed
Status in miniramfs source package in Noble:
  New
Status in open-iscsi source package in Noble:
  Fix Released
Status in thin-provisioning-tools source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  When compared to Ubuntu 23.10, creating intramfs files with update-
  initramfs takes 2 to 5 times more time on ARM devices.

  IIUC, dracut-install usage was added to initramfs-tools to speed up
  the process. But now its way slower. Even running update-initramfs on
  jammy, which doesn't use dracut-install, is way faster then the time
  taken on Noble.

  first bad commit -
  
https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870

  Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble)
  with initramfs-tools 0.142ubuntu25.1 takes over six minutes:

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 402.751 s ±  5.592 s[User: 166.316 s, System: 
228.909 s]
    Range (min … max):   394.380 s … 411.445 s10 runs
  ```

  [ Test Plan ]

  1. Measure `update-initramfs -u` before the update.
  2. Log the content of the initrd before the update: `lsinitramfs 
/boot/initrd.img`
  3. update dracut-install / initramfs-tools-core
  4. Measure `update-initramfs -u`. It should be faster (the performance 
improvements on amd64 should be very small and might be within the measurement 
uncertainty).
  5. Check with lsinitramfs that the content of the newly generated initrd 
hasn't changed.

  [ Where problems could occur ]

  The code that is responsible for including the kernel modules into the
  initrd is touched. Negative consequences could be that some needed
  kernel modules will not be included any more (should be covered by the
  test case) or that building new initrds will fail.

  The initramfs-tools fix changes how manual_add_modules behaves.
  `manual_add_modules` does not copy kernel modules, but queues them for
  being copied when the newly added function `apply_add_modules` is
  called.

  I checked all instances of calls to `manual_add_modules` for possible
  regressions (see comment #15). Only miniramfs needs to be adjusted to
  also call `apply_add_modules`. But this change could break consumers
  of the `manual_add_modules` function that are outside of the Ubuntu
  archive. I googled for `apply_add_modules` but found no public outside
  users.

  [ Benchmarks ]

  Stock noble on a Raspberry Pi Zero 2W:

  ```
  bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s]
    Range (min … max): 409.139 s … 422.632 s 5 runs
  ```

  noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on
  2024-07-01):

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 248.054 s ±  5.569 s[User: 67.410 s, System: 
169.412 s]
    Range (min … max):   238.909 s … 257.384 s10 runs
  ```

  noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on
  2024-07-11):

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
Time (mean ± σ): 232.001 s ± 5.678 s [User: 55.456 s, System: 166.510 s]
Range (min … max): 222.120 s … 239.610 s 10 runs
  ```

  [ Reduce manual_add_modules calls ]

  Besides making the dracut-install calls

[Touch-packages] [Bug 2065180] Re: performance regression in dracut-install 060

This bug was fixed in the package open-iscsi - 2.1.9-3ubuntu5.1

---
open-iscsi (2.1.9-3ubuntu5.1) noble; urgency=medium

  * initramfs-hook: Combine calls to manual_add_modules (LP: #2065180)

 -- Benjamin Drung   Mon, 01 Jul 2024 21:01:25 +0200

** Changed in: open-iscsi (Ubuntu Noble)
   Status: Fix Committed => Fix Released

** Changed in: thin-provisioning-tools (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  performance regression in dracut-install 060

Status in Dracut:
  New
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in dracut package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Fix Released
Status in miniramfs package in Ubuntu:
  Fix Released
Status in open-iscsi package in Ubuntu:
  Invalid
Status in thin-provisioning-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Noble:
  Fix Committed
Status in cryptsetup source package in Noble:
  Fix Committed
Status in dracut source package in Noble:
  Fix Released
Status in initramfs-tools source package in Noble:
  Fix Committed
Status in lvm2 source package in Noble:
  Fix Committed
Status in miniramfs source package in Noble:
  New
Status in open-iscsi source package in Noble:
  Fix Released
Status in thin-provisioning-tools source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  When compared to Ubuntu 23.10, creating intramfs files with update-
  initramfs takes 2 to 5 times more time on ARM devices.

  IIUC, dracut-install usage was added to initramfs-tools to speed up
  the process. But now its way slower. Even running update-initramfs on
  jammy, which doesn't use dracut-install, is way faster then the time
  taken on Noble.

  first bad commit -
  
https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870

  Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble)
  with initramfs-tools 0.142ubuntu25.1 takes over six minutes:

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 402.751 s ±  5.592 s[User: 166.316 s, System: 
228.909 s]
    Range (min … max):   394.380 s … 411.445 s10 runs
  ```

  [ Test Plan ]

  1. Measure `update-initramfs -u` before the update.
  2. Log the content of the initrd before the update: `lsinitramfs 
/boot/initrd.img`
  3. update dracut-install / initramfs-tools-core
  4. Measure `update-initramfs -u`. It should be faster (the performance 
improvements on amd64 should be very small and might be within the measurement 
uncertainty).
  5. Check with lsinitramfs that the content of the newly generated initrd 
hasn't changed.

  [ Where problems could occur ]

  The code that is responsible for including the kernel modules into the
  initrd is touched. Negative consequences could be that some needed
  kernel modules will not be included any more (should be covered by the
  test case) or that building new initrds will fail.

  The initramfs-tools fix changes how manual_add_modules behaves.
  `manual_add_modules` does not copy kernel modules, but queues them for
  being copied when the newly added function `apply_add_modules` is
  called.

  I checked all instances of calls to `manual_add_modules` for possible
  regressions (see comment #15). Only miniramfs needs to be adjusted to
  also call `apply_add_modules`. But this change could break consumers
  of the `manual_add_modules` function that are outside of the Ubuntu
  archive. I googled for `apply_add_modules` but found no public outside
  users.

  [ Benchmarks ]

  Stock noble on a Raspberry Pi Zero 2W:

  ```
  bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s]
    Range (min … max): 409.139 s … 422.632 s 5 runs
  ```

  noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on
  2024-07-01):

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 248.054 s ±  5.569 s[User: 67.410 s, System: 
169.412 s]
    Range (min … max):   238.909 s … 257.384 s10 runs
  ```

  noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on
  2024-07-11):

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
Time (mean ± σ): 232.001 s ± 5.678 s [User: 55.456 s, System: 166.510 s]
Range (min … max): 222.120 s … 239.610 s 10 runs
  ```

  [ Reduce manual_add_modules calls ]

  Besides making the dracut-install calls faster,

[Touch-packages] [Bug 2065180] Re: performance regression in dracut-install 060

This bug was fixed in the package thin-provisioning-tools -
0.9.0-2ubuntu5.1

---
thin-provisioning-tools (0.9.0-2ubuntu5.1) noble; urgency=medium

  * initramfs-hook: Combine calls to manual_add_modules (LP: #2065180)

 -- Benjamin Drung   Mon, 01 Jul 2024 20:48:29 +0200

** Changed in: dracut (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  performance regression in dracut-install 060

Status in Dracut:
  New
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in dracut package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Fix Released
Status in miniramfs package in Ubuntu:
  Fix Released
Status in open-iscsi package in Ubuntu:
  Invalid
Status in thin-provisioning-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Noble:
  Fix Committed
Status in cryptsetup source package in Noble:
  Fix Committed
Status in dracut source package in Noble:
  Fix Released
Status in initramfs-tools source package in Noble:
  Fix Committed
Status in lvm2 source package in Noble:
  Fix Committed
Status in miniramfs source package in Noble:
  New
Status in open-iscsi source package in Noble:
  Fix Released
Status in thin-provisioning-tools source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  When compared to Ubuntu 23.10, creating intramfs files with update-
  initramfs takes 2 to 5 times more time on ARM devices.

  IIUC, dracut-install usage was added to initramfs-tools to speed up
  the process. But now its way slower. Even running update-initramfs on
  jammy, which doesn't use dracut-install, is way faster then the time
  taken on Noble.

  first bad commit -
  
https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870

  Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble)
  with initramfs-tools 0.142ubuntu25.1 takes over six minutes:

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 402.751 s ±  5.592 s[User: 166.316 s, System: 
228.909 s]
    Range (min … max):   394.380 s … 411.445 s10 runs
  ```

  [ Test Plan ]

  1. Measure `update-initramfs -u` before the update.
  2. Log the content of the initrd before the update: `lsinitramfs 
/boot/initrd.img`
  3. update dracut-install / initramfs-tools-core
  4. Measure `update-initramfs -u`. It should be faster (the performance 
improvements on amd64 should be very small and might be within the measurement 
uncertainty).
  5. Check with lsinitramfs that the content of the newly generated initrd 
hasn't changed.

  [ Where problems could occur ]

  The code that is responsible for including the kernel modules into the
  initrd is touched. Negative consequences could be that some needed
  kernel modules will not be included any more (should be covered by the
  test case) or that building new initrds will fail.

  The initramfs-tools fix changes how manual_add_modules behaves.
  `manual_add_modules` does not copy kernel modules, but queues them for
  being copied when the newly added function `apply_add_modules` is
  called.

  I checked all instances of calls to `manual_add_modules` for possible
  regressions (see comment #15). Only miniramfs needs to be adjusted to
  also call `apply_add_modules`. But this change could break consumers
  of the `manual_add_modules` function that are outside of the Ubuntu
  archive. I googled for `apply_add_modules` but found no public outside
  users.

  [ Benchmarks ]

  Stock noble on a Raspberry Pi Zero 2W:

  ```
  bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s]
    Range (min … max): 409.139 s … 422.632 s 5 runs
  ```

  noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on
  2024-07-01):

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 248.054 s ±  5.569 s[User: 67.410 s, System: 
169.412 s]
    Range (min … max):   238.909 s … 257.384 s10 runs
  ```

  noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on
  2024-07-11):

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
Time (mean ± σ): 232.001 s ± 5.678 s [User: 55.456 s, System: 166.510 s]
Range (min … max): 222.120 s … 239.610 s 10 runs
  ```

  [ Reduce manual_add_modules calls ]

  Besides making the dracut-install calls faster, group the dracut-
  install calls. Since the fix in oracular can cause

[Touch-packages] [Bug 2058104] Re: package libldap-common 2.5.16+dfsg-0ubuntu0.22.04.2 failed to install/upgrade: unable to create '/etc/ldap/ldap.conf.dpkg-new' (while processing './etc/ldap/ldap.con

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

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

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

Title:
  package libldap-common 2.5.16+dfsg-0ubuntu0.22.04.2 failed to
  install/upgrade: unable to create '/etc/ldap/ldap.conf.dpkg-new'
  (while processing './etc/ldap/ldap.conf'): Read-only file system

Status in openldap package in Ubuntu:
  Expired

Bug description:
  Error

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libldap-common 2.5.16+dfsg-0ubuntu0.22.04.2
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Mar 16 14:41:08 2024
  Dependencies:
   
  DuplicateSignature:
   package:libldap-common:2.5.16+dfsg-0ubuntu0.22.04.2
   Unpacking apache2 (2.4.52-1ubuntu4.8) over (2.4.52-1ubuntu4.7) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-rFn5N9/01-apache2_2.4.52-1ubuntu4.8_amd64.deb (--unpack):
unable to create '/etc/apache2/apache2.conf.dpkg-new' (while processing 
'./etc/apache2/apache2.conf'): Read-only file system
  ErrorMessage: unable to create '/etc/ldap/ldap.conf.dpkg-new' (while 
processing './etc/ldap/ldap.conf'): Read-only file system
  InstallationDate: Installed on 2023-06-11 (279 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.11
  SourcePackage: openldap
  Title: package libldap-common 2.5.16+dfsg-0ubuntu0.22.04.2 failed to 
install/upgrade: unable to create '/etc/ldap/ldap.conf.dpkg-new' (while 
processing './etc/ldap/ldap.conf'): Read-only file system
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2058104/+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 1920933] Re: live desktop system booted with ip=dhcp has the right lease, hostname not set at all

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

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

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

Title:
  live desktop system booted with ip=dhcp has the right lease, hostname
  not set at all

Status in initramfs-tools package in Ubuntu:
  Expired
Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Here the cmdline:

  vmlinuz initrd=initrd rootfstype=nfs netboot=nfs
  nfsroot=162.38.151.26:/exports/focal-desktop boot=casper ip=dhcp
  fsck.mode=skip automatic-ubiquity
  url=http://162.38.151.26/preseed/fds/focal-efi.seed

  File /run/systemd/netif/leases/2:

  # This is private data. Do not parse.
  ADDRESS=162.38.80.32
  NETMASK=255.255.248.0
  ROUTER=162.38.80.1
  SERVER_ADDRESS=162.38.87.254
  NEXT_SERVER=162.38.151.26
  T1=7200
  T2=12600
  LIFETIME=14400
  DNS=162.38.151.23 162.38.151.24
  NTP=193.51.157.3
  DOMAINNAME=fdsetu.infra.domain.fr
  DOMAIN_SEARCH_LIST=infra.domain.fr fdsetu.infra.domain.fr
  HOSTNAME=focal-uefi
  CLIENTID=0152540071e1f2

  But the hostname is still the default one "ubuntu"

  $ hostnamectl
   Static hostname: ubuntu
 Icon name: computer-vm
   Chassis: vm
Machine ID: cbb8d889829d4e2594ab55a53749e7e9
   Boot ID: c93c8cc26fa040f6b010077e676bf7ec
Virtualization: kvm
  Operating System: Ubuntu 20.04.2 LTS
Kernel: Linux 5.8.0-43-generic
  Architecture: x86-64

  It should be "focal-uefi".
  I had the same issue with ubuntu server autoinstall

  See https://bugs.launchpad.net/subiquity/+bug/1905932

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.4
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperVersion: 1.445.1
  Date: Tue Mar 23 15:30:42 2021
  LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: vmlinuz initrd=initrd rootfstype=nfs netboot=nfs 
nfsroot=162.38.151.26:/exports/focal-desktop boot=casper ip=dhcp fsck.mode=skip 
automatic-ubiquity url=http://162.38.151.26/preseed/fds/focal-efi.seed
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.1
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1920933/+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 2064399] Re: Merge cyrus-sasl2 from Debian unstable for oracular

Marking fix committed while it migrates.

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

Title:
  Merge cyrus-sasl2 from Debian unstable for oracular

Status in cyrus-sasl2 package in Ubuntu:
  Fix Committed

Bug description:
  Upstream: tbd
  Debian:   2.1.28+dfsg1-6
  Ubuntu:   2.1.28+dfsg1-5ubuntu3


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

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Oracular Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  cyrus-sasl2 (2.1.28+dfsg1-6) unstable; urgency=medium

* Team upload
* Patch: Prevent six import (Closes: #1067425)

   -- Bastian Germann   Thu, 21 Mar 2024 19:19:46 +

  cyrus-sasl2 (2.1.28+dfsg1-5) unstable; urgency=medium

* Team upload
* Fix implicit function declaration (Closes: #1066214)
* Prevent linking via intersphinx (Closes: #1065436)
* Extend the time_t format specifiers to long long (Closes: #1066811)

   -- Bastian Germann   Wed, 20 Mar 2024 19:03:11 +

  cyrus-sasl2 (2.1.28+dfsg1-4) unstable; urgency=medium

* Team upload
* Clean docsrc/exts/themes (Closes: #1045111)
* Drop gen-auth and saslfinger
* Remove Uploaders who contributed more than a decade ago
* Remove myself from Uploaders

   -- Bastian Germann   Sat, 11 Nov 2023 22:17:13 +0100

  cyrus-sasl2 (2.1.28+dfsg1-3) unstable; urgency=medium

* Let libsasl2-dev depend on libssl-dev (Closes: #1042937)

   -- Bastian Germann   Fri, 04 Aug 2023 00:35:18 +0200

  cyrus-sasl2 (2.1.28+dfsg1-2) unstable; urgency=medium

* Eliminate RSA-MD from binaries (Closes: #748061)

   -- Bastian Germann   Tue, 01 Aug 2023 16:16:30 +0200

  cyrus-sasl2 (2.1.28+dfsg1-1) unstable; urgency=medium

* Exclude crypto-compat
* New upstream version 2.1.28+dfsg1
* Get rid of BSD-4-clause-KTH
* Use SPDX name for the primary license
* Add Turkish translation (Closes: #1036910)

[ Andreas Hasenack ]
* d/t/saslauthd: fix test flakiness (Closes: #1036893)

   -- Bastian Germann   Mon, 05 Jun 2023 23:24:14 +0200

  cyrus-sasl2 (2.1.28+dfsg-11) unstable; urgency=medium

[ Debian Janitor ]
* Apply multi-arch hints. + cyrus-sasl2-doc: Add Multi-Arch: foreign.

[ Bastian Germann ]
* Add Romanian translation (Closes: #1031499)
* Fix lintian depends-on-obsolete-package (lsb-base)
* Add saslauthd.service (Closes: #981438)
* Remove dh_installinit params
* Install saslauthd.service similar to saslauthd.init
* Drop old NEWS
* Fix systemd-service-file-missing-documentation-key

   -- Bastian Germann   Wed, 01 Mar 2023 00:52:04 +0100

  cyrus-sasl2 (2.1.28+dfsg-10) unstable; urgency=medium

[ Helmut Grohne ]
* Explicitly B-D on libcrypt-dev (Closes: #1024644)

   -- Bastian Germann   Tue, 22 Nov 2022 17:48:33 +0100

  cyrus-sasl2 (2.1.28+dfsg-9) unstable; urgency=medium

* d/watch: Scan GitHub release API

[ Helmut Grohne ]
* Depend on ABI-less libc-dev rather than libc6-dev (Closes: #1023838)

   -- Bastian Germann   Fri, 11 Nov 2022 12:27:36 +0100

  cyrus-sasl2 (2.1.28+dfsg-8) unstable; urgency=medium

[ Andreas Hasenack ]
* Add SASL channel binding support for GSSAPI and GSS-SPNEGO
  (LP: #1912256):
  - d/p/0034-channel-binding-gssapi-gss-spnego.patch: add SASL channel
binding support for GSSAPI and GSS-SPNEGO
  - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-1.patch:
allow setting maxssf to 0 when using GSS-SPNEGO inside SSL/TLS
  - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-2.patch:
be more conformant to RFC4752

   -- Bastian Germann   Mon, 05 Sep 2022 14:30:39 +0200

  cyrus-sasl2 (2.1.28+dfsg-7) unstable; urgency=medium

* d/tests: Relicense to GPL-3


  ### Old Ubuntu Delta ###

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu3) noble; urgency=medium

* No-change rebuild for time_t transition.

   -- Sergio Durigan Junior   Fri, 05 Apr
  2024 15:59:59 -0400

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu2) noble; urgency=medium

* No-change rebuild for CVE-2024-3094

   -- Steve Langasek   Sun, 31 Mar 2024
  07:31:27 +

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu1) noble; urgency=medium

* Add Depends: python3-six

   -- Jeremy Bícha   Thu, 21 Mar 2024 09:33:35 -0400

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


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

[Touch-packages] [Bug 2064399] Re: Merge cyrus-sasl2 from Debian unstable for oracular

This bug was fixed in the package cyrus-sasl2 - 2.1.28+dfsg1-6

---
cyrus-sasl2 (2.1.28+dfsg1-6) unstable; urgency=medium

  * Team upload
  * Patch: Prevent six import (Closes: #1067425)

 -- Bastian Germann   Thu, 21 Mar 2024 19:19:46 +

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  Merge cyrus-sasl2 from Debian unstable for oracular

Status in cyrus-sasl2 package in Ubuntu:
  Fix Committed

Bug description:
  Upstream: tbd
  Debian:   2.1.28+dfsg1-6
  Ubuntu:   2.1.28+dfsg1-5ubuntu3


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

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Oracular Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  cyrus-sasl2 (2.1.28+dfsg1-6) unstable; urgency=medium

* Team upload
* Patch: Prevent six import (Closes: #1067425)

   -- Bastian Germann   Thu, 21 Mar 2024 19:19:46 +

  cyrus-sasl2 (2.1.28+dfsg1-5) unstable; urgency=medium

* Team upload
* Fix implicit function declaration (Closes: #1066214)
* Prevent linking via intersphinx (Closes: #1065436)
* Extend the time_t format specifiers to long long (Closes: #1066811)

   -- Bastian Germann   Wed, 20 Mar 2024 19:03:11 +

  cyrus-sasl2 (2.1.28+dfsg1-4) unstable; urgency=medium

* Team upload
* Clean docsrc/exts/themes (Closes: #1045111)
* Drop gen-auth and saslfinger
* Remove Uploaders who contributed more than a decade ago
* Remove myself from Uploaders

   -- Bastian Germann   Sat, 11 Nov 2023 22:17:13 +0100

  cyrus-sasl2 (2.1.28+dfsg1-3) unstable; urgency=medium

* Let libsasl2-dev depend on libssl-dev (Closes: #1042937)

   -- Bastian Germann   Fri, 04 Aug 2023 00:35:18 +0200

  cyrus-sasl2 (2.1.28+dfsg1-2) unstable; urgency=medium

* Eliminate RSA-MD from binaries (Closes: #748061)

   -- Bastian Germann   Tue, 01 Aug 2023 16:16:30 +0200

  cyrus-sasl2 (2.1.28+dfsg1-1) unstable; urgency=medium

* Exclude crypto-compat
* New upstream version 2.1.28+dfsg1
* Get rid of BSD-4-clause-KTH
* Use SPDX name for the primary license
* Add Turkish translation (Closes: #1036910)

[ Andreas Hasenack ]
* d/t/saslauthd: fix test flakiness (Closes: #1036893)

   -- Bastian Germann   Mon, 05 Jun 2023 23:24:14 +0200

  cyrus-sasl2 (2.1.28+dfsg-11) unstable; urgency=medium

[ Debian Janitor ]
* Apply multi-arch hints. + cyrus-sasl2-doc: Add Multi-Arch: foreign.

[ Bastian Germann ]
* Add Romanian translation (Closes: #1031499)
* Fix lintian depends-on-obsolete-package (lsb-base)
* Add saslauthd.service (Closes: #981438)
* Remove dh_installinit params
* Install saslauthd.service similar to saslauthd.init
* Drop old NEWS
* Fix systemd-service-file-missing-documentation-key

   -- Bastian Germann   Wed, 01 Mar 2023 00:52:04 +0100

  cyrus-sasl2 (2.1.28+dfsg-10) unstable; urgency=medium

[ Helmut Grohne ]
* Explicitly B-D on libcrypt-dev (Closes: #1024644)

   -- Bastian Germann   Tue, 22 Nov 2022 17:48:33 +0100

  cyrus-sasl2 (2.1.28+dfsg-9) unstable; urgency=medium

* d/watch: Scan GitHub release API

[ Helmut Grohne ]
* Depend on ABI-less libc-dev rather than libc6-dev (Closes: #1023838)

   -- Bastian Germann   Fri, 11 Nov 2022 12:27:36 +0100

  cyrus-sasl2 (2.1.28+dfsg-8) unstable; urgency=medium

[ Andreas Hasenack ]
* Add SASL channel binding support for GSSAPI and GSS-SPNEGO
  (LP: #1912256):
  - d/p/0034-channel-binding-gssapi-gss-spnego.patch: add SASL channel
binding support for GSSAPI and GSS-SPNEGO
  - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-1.patch:
allow setting maxssf to 0 when using GSS-SPNEGO inside SSL/TLS
  - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-2.patch:
be more conformant to RFC4752

   -- Bastian Germann   Mon, 05 Sep 2022 14:30:39 +0200

  cyrus-sasl2 (2.1.28+dfsg-7) unstable; urgency=medium

* d/tests: Relicense to GPL-3


  ### Old Ubuntu Delta ###

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu3) noble; urgency=medium

* No-change rebuild for time_t transition.

   -- Sergio Durigan Junior   Fri, 05 Apr
  2024 15:59:59 -0400

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu2) noble; urgency=medium

* No-change rebuild for CVE-2024-3094

   -- Steve Langasek   Sun, 31 Mar 2024
  07:31:27 +

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu1) noble; urgency=medium

* Add Depends: python3-six

   --

[Touch-packages] [Bug 2064399] Re: Merge cyrus-sasl2 from Debian unstable for oracular

Upon inspection, this can become a sync, because our delta is:
+cyrus-sasl2 (2.1.28+dfsg1-5ubuntu1) noble; urgency=medium
+
+  * Add Depends: python3-six
+
+ -- Jeremy Bícha   Thu, 21 Mar 2024 09:33:35 -0400


And the new debian upload is:
cyrus-sasl2 (2.1.28+dfsg1-6) unstable; urgency=medium

  * Team upload
  * Patch: Prevent six import (Closes: #1067425)


** Changed in: cyrus-sasl2 (Ubuntu)
Milestone: ubuntu-24.08 => ubuntu-24.07

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Merge cyrus-sasl2 from Debian unstable for oracular

Status in cyrus-sasl2 package in Ubuntu:
  Fix Committed

Bug description:
  Upstream: tbd
  Debian:   2.1.28+dfsg1-6
  Ubuntu:   2.1.28+dfsg1-5ubuntu3


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

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Oracular Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  cyrus-sasl2 (2.1.28+dfsg1-6) unstable; urgency=medium

* Team upload
* Patch: Prevent six import (Closes: #1067425)

   -- Bastian Germann   Thu, 21 Mar 2024 19:19:46 +

  cyrus-sasl2 (2.1.28+dfsg1-5) unstable; urgency=medium

* Team upload
* Fix implicit function declaration (Closes: #1066214)
* Prevent linking via intersphinx (Closes: #1065436)
* Extend the time_t format specifiers to long long (Closes: #1066811)

   -- Bastian Germann   Wed, 20 Mar 2024 19:03:11 +

  cyrus-sasl2 (2.1.28+dfsg1-4) unstable; urgency=medium

* Team upload
* Clean docsrc/exts/themes (Closes: #1045111)
* Drop gen-auth and saslfinger
* Remove Uploaders who contributed more than a decade ago
* Remove myself from Uploaders

   -- Bastian Germann   Sat, 11 Nov 2023 22:17:13 +0100

  cyrus-sasl2 (2.1.28+dfsg1-3) unstable; urgency=medium

* Let libsasl2-dev depend on libssl-dev (Closes: #1042937)

   -- Bastian Germann   Fri, 04 Aug 2023 00:35:18 +0200

  cyrus-sasl2 (2.1.28+dfsg1-2) unstable; urgency=medium

* Eliminate RSA-MD from binaries (Closes: #748061)

   -- Bastian Germann   Tue, 01 Aug 2023 16:16:30 +0200

  cyrus-sasl2 (2.1.28+dfsg1-1) unstable; urgency=medium

* Exclude crypto-compat
* New upstream version 2.1.28+dfsg1
* Get rid of BSD-4-clause-KTH
* Use SPDX name for the primary license
* Add Turkish translation (Closes: #1036910)

[ Andreas Hasenack ]
* d/t/saslauthd: fix test flakiness (Closes: #1036893)

   -- Bastian Germann   Mon, 05 Jun 2023 23:24:14 +0200

  cyrus-sasl2 (2.1.28+dfsg-11) unstable; urgency=medium

[ Debian Janitor ]
* Apply multi-arch hints. + cyrus-sasl2-doc: Add Multi-Arch: foreign.

[ Bastian Germann ]
* Add Romanian translation (Closes: #1031499)
* Fix lintian depends-on-obsolete-package (lsb-base)
* Add saslauthd.service (Closes: #981438)
* Remove dh_installinit params
* Install saslauthd.service similar to saslauthd.init
* Drop old NEWS
* Fix systemd-service-file-missing-documentation-key

   -- Bastian Germann   Wed, 01 Mar 2023 00:52:04 +0100

  cyrus-sasl2 (2.1.28+dfsg-10) unstable; urgency=medium

[ Helmut Grohne ]
* Explicitly B-D on libcrypt-dev (Closes: #1024644)

   -- Bastian Germann   Tue, 22 Nov 2022 17:48:33 +0100

  cyrus-sasl2 (2.1.28+dfsg-9) unstable; urgency=medium

* d/watch: Scan GitHub release API

[ Helmut Grohne ]
* Depend on ABI-less libc-dev rather than libc6-dev (Closes: #1023838)

   -- Bastian Germann   Fri, 11 Nov 2022 12:27:36 +0100

  cyrus-sasl2 (2.1.28+dfsg-8) unstable; urgency=medium

[ Andreas Hasenack ]
* Add SASL channel binding support for GSSAPI and GSS-SPNEGO
  (LP: #1912256):
  - d/p/0034-channel-binding-gssapi-gss-spnego.patch: add SASL channel
binding support for GSSAPI and GSS-SPNEGO
  - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-1.patch:
allow setting maxssf to 0 when using GSS-SPNEGO inside SSL/TLS
  - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-2.patch:
be more conformant to RFC4752

   -- Bastian Germann   Mon, 05 Sep 2022 14:30:39 +0200

  cyrus-sasl2 (2.1.28+dfsg-7) unstable; urgency=medium

* d/tests: Relicense to GPL-3


  ### Old Ubuntu Delta ###

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu3) noble; urgency=medium

* No-change rebuild for time_t transition.

   -- Sergio Durigan Junior   Fri, 05 Apr
  2024 15:59:59 -0400

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu2) noble; urgency=medium

* No-change rebuild for

[Touch-packages] [Bug 2064399] Re: Merge cyrus-sasl2 from Debian unstable for oracular

** Changed in: cyrus-sasl2 (Ubuntu)
Milestone: ubuntu-24.07 => ubuntu-24.08

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

Title:
  Merge cyrus-sasl2 from Debian unstable for oracular

Status in cyrus-sasl2 package in Ubuntu:
  New

Bug description:
  Upstream: tbd
  Debian:   2.1.28+dfsg1-6
  Ubuntu:   2.1.28+dfsg1-5ubuntu3


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

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Oracular Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  cyrus-sasl2 (2.1.28+dfsg1-6) unstable; urgency=medium

* Team upload
* Patch: Prevent six import (Closes: #1067425)

   -- Bastian Germann   Thu, 21 Mar 2024 19:19:46 +

  cyrus-sasl2 (2.1.28+dfsg1-5) unstable; urgency=medium

* Team upload
* Fix implicit function declaration (Closes: #1066214)
* Prevent linking via intersphinx (Closes: #1065436)
* Extend the time_t format specifiers to long long (Closes: #1066811)

   -- Bastian Germann   Wed, 20 Mar 2024 19:03:11 +

  cyrus-sasl2 (2.1.28+dfsg1-4) unstable; urgency=medium

* Team upload
* Clean docsrc/exts/themes (Closes: #1045111)
* Drop gen-auth and saslfinger
* Remove Uploaders who contributed more than a decade ago
* Remove myself from Uploaders

   -- Bastian Germann   Sat, 11 Nov 2023 22:17:13 +0100

  cyrus-sasl2 (2.1.28+dfsg1-3) unstable; urgency=medium

* Let libsasl2-dev depend on libssl-dev (Closes: #1042937)

   -- Bastian Germann   Fri, 04 Aug 2023 00:35:18 +0200

  cyrus-sasl2 (2.1.28+dfsg1-2) unstable; urgency=medium

* Eliminate RSA-MD from binaries (Closes: #748061)

   -- Bastian Germann   Tue, 01 Aug 2023 16:16:30 +0200

  cyrus-sasl2 (2.1.28+dfsg1-1) unstable; urgency=medium

* Exclude crypto-compat
* New upstream version 2.1.28+dfsg1
* Get rid of BSD-4-clause-KTH
* Use SPDX name for the primary license
* Add Turkish translation (Closes: #1036910)

[ Andreas Hasenack ]
* d/t/saslauthd: fix test flakiness (Closes: #1036893)

   -- Bastian Germann   Mon, 05 Jun 2023 23:24:14 +0200

  cyrus-sasl2 (2.1.28+dfsg-11) unstable; urgency=medium

[ Debian Janitor ]
* Apply multi-arch hints. + cyrus-sasl2-doc: Add Multi-Arch: foreign.

[ Bastian Germann ]
* Add Romanian translation (Closes: #1031499)
* Fix lintian depends-on-obsolete-package (lsb-base)
* Add saslauthd.service (Closes: #981438)
* Remove dh_installinit params
* Install saslauthd.service similar to saslauthd.init
* Drop old NEWS
* Fix systemd-service-file-missing-documentation-key

   -- Bastian Germann   Wed, 01 Mar 2023 00:52:04 +0100

  cyrus-sasl2 (2.1.28+dfsg-10) unstable; urgency=medium

[ Helmut Grohne ]
* Explicitly B-D on libcrypt-dev (Closes: #1024644)

   -- Bastian Germann   Tue, 22 Nov 2022 17:48:33 +0100

  cyrus-sasl2 (2.1.28+dfsg-9) unstable; urgency=medium

* d/watch: Scan GitHub release API

[ Helmut Grohne ]
* Depend on ABI-less libc-dev rather than libc6-dev (Closes: #1023838)

   -- Bastian Germann   Fri, 11 Nov 2022 12:27:36 +0100

  cyrus-sasl2 (2.1.28+dfsg-8) unstable; urgency=medium

[ Andreas Hasenack ]
* Add SASL channel binding support for GSSAPI and GSS-SPNEGO
  (LP: #1912256):
  - d/p/0034-channel-binding-gssapi-gss-spnego.patch: add SASL channel
binding support for GSSAPI and GSS-SPNEGO
  - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-1.patch:
allow setting maxssf to 0 when using GSS-SPNEGO inside SSL/TLS
  - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-2.patch:
be more conformant to RFC4752

   -- Bastian Germann   Mon, 05 Sep 2022 14:30:39 +0200

  cyrus-sasl2 (2.1.28+dfsg-7) unstable; urgency=medium

* d/tests: Relicense to GPL-3


  ### Old Ubuntu Delta ###

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu3) noble; urgency=medium

* No-change rebuild for time_t transition.

   -- Sergio Durigan Junior   Fri, 05 Apr
  2024 15:59:59 -0400

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu2) noble; urgency=medium

* No-change rebuild for CVE-2024-3094

   -- Steve Langasek   Sun, 31 Mar 2024
  07:31:27 +

  cyrus-sasl2 (2.1.28+dfsg1-5ubuntu1) noble; urgency=medium

* Add Depends: python3-six

   -- Jeremy Bícha   Thu, 21 Mar 2024 09:33:35 -0400

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


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

[Touch-packages] [Bug 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

2024-07-30 Thread Bug Watch Updater

** Changed in: jupyter-client (Debian)
   Status: Confirmed => Fix Released

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  Fix Released
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Released
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  Fix Released
Status in cython-legacy package in Debian:
  Fix Released
Status in ipykernel package in Debian:
  Fix Released
Status in jupyter-client package in Debian:
  Fix Released
Status in numpy package in Debian:
  Fix Released
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Fix Released
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2075104] Re: user session is randomly terminated by systemd-oom when the system is left alone for a while

systemctl cat -- user@$(id -u).service:

# /usr/lib/systemd/system/user@.service
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=User Manager for UID %i
Documentation=man:user@.service(5)
After=user-runtime-dir@%i.service dbus.service systemd-oomd.service
Requires=user-runtime-dir@%i.service
IgnoreOnIsolate=yes

[Service]
User=%i
PAMName=systemd-user
Type=notify-reload
ExecStart=/usr/lib/systemd/systemd --user
Slice=user-%i.slice
KillMode=mixed
Delegate=pids memory cpu
DelegateSubgroup=init.scope
TasksMax=infinity
TimeoutStopSec=120s
KeyringMode=inherit
OOMScoreAdjust=100
MemoryPressureWatch=skip

# /usr/lib/systemd/system/user@.service.d/10-login-barrier.conf
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
# Make sure user instances are started after logins are allowed. However this
# is not desirable for user@0.service since root should be able to log in
# earlier during the boot process especially if something goes wrong.
After=systemd-user-sessions.service

# /usr/lib/systemd/system/user@.service.d/10-oomd-user-service-defaults.conf
[Service]
ManagedOOMMemoryPressure=kill
ManagedOOMMemoryPressureLimit=50%

# /usr/lib/systemd/system/user@.service.d/timeout.conf
# Avoid long hangs during shutdown if user services fail/hang due to X.org
# going away too early
[Service]
TimeoutStopSec=5

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

Title:
  user session is randomly terminated by systemd-oom when the system is
  left alone for a while

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I was surprised last week to find that my computer had logged me out
  when I had left it alone for some 15 minutes.  I did not bother to
  research at the time and did not see any reason as the problem did not
  manifest again .

  Then today, it happens again. The circumstances are similar: I leave
  the system long enough for the screen to power off and come back to
  find myself kicked out of my session. Yes, kicked out, not simply
  locked out. I need  to log in again and find that all running apps and
  open files have all been  closed.

  My journal would appear to show that gnome-shell got stopped as a
  consequence of systemd-oomd killing several applications (see the
  included journalctl snippet - mind that the output is in reverse order
  (journalctl -r)).

  Should not  oomd terminate single applications instead of complete
  user sessions?

  And I do have some doubts about the statistics listed in the journal.
  One of the killed  apps is reported as consuming over 22GB or RAM (out
  of 32). I have been using that app for many years and cannot remember
  having see it use more than a few GB.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd-oomd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 30 04:00:27 2024
  InstallationDate: Installed on 2022-03-27 (855 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+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 2075104] Re: user session is randomly terminated by systemd-oom when the system is left alone for a while

systemd-analyze cat-config systemd/oomd.conf:

# /etc/systemd/oomd.conf
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it under the
#  terms of the GNU Lesser General Public License as published by the Free
#  Software Foundation; either version 2.1 of the License, or (at your option)
#  any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in
# the /etc/systemd/oomd.conf.d/ directory. The latter is generally recommended.
# Defaults can be restored by simply deleting the main configuration file and
# all drop-ins located in /etc/.
#
# Use 'systemd-analyze cat-config systemd/oomd.conf' to display the full config.
#
# See oomd.conf(5) for details

[OOM]
#SwapUsedLimit=90%
#DefaultMemoryPressureLimit=60%
#DefaultMemoryPressureDurationSec=30s

# /usr/lib/systemd/oomd.conf.d/10-oomd-defaults.conf
[OOM]
DefaultMemoryPressureDurationSec=20s

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

Title:
  user session is randomly terminated by systemd-oom when the system is
  left alone for a while

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I was surprised last week to find that my computer had logged me out
  when I had left it alone for some 15 minutes.  I did not bother to
  research at the time and did not see any reason as the problem did not
  manifest again .

  Then today, it happens again. The circumstances are similar: I leave
  the system long enough for the screen to power off and come back to
  find myself kicked out of my session. Yes, kicked out, not simply
  locked out. I need  to log in again and find that all running apps and
  open files have all been  closed.

  My journal would appear to show that gnome-shell got stopped as a
  consequence of systemd-oomd killing several applications (see the
  included journalctl snippet - mind that the output is in reverse order
  (journalctl -r)).

  Should not  oomd terminate single applications instead of complete
  user sessions?

  And I do have some doubts about the statistics listed in the journal.
  One of the killed  apps is reported as consuming over 22GB or RAM (out
  of 32). I have been using that app for many years and cannot remember
  having see it use more than a few GB.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd-oomd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 30 04:00:27 2024
  InstallationDate: Installed on 2022-03-27 (855 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+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 2075104] Re: user session is randomly terminated by systemd-oom when the system is left alone for a while

oomctl:

Dry Run: no
Swap Used Limit: 90.00%
Default Memory Pressure Limit: 60.00%
Default Memory Pressure Duration: 20s
System Context:
Memory: Used: 0B Total: 0B
Swap: Used: 0B Total: 0B
Swap Monitored CGroups:
Memory Pressure Monitored CGroups:
Path: /user.slice/user-1002.slice/user@1002.service
Memory Pressure Limit: 50.00%
Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 4us
Current Memory Usage: 5.0G
Memory Min: 0B
Memory Low: 0B
Pgscan: 0
Last Pgscan: 0

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

Title:
  user session is randomly terminated by systemd-oom when the system is
  left alone for a while

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I was surprised last week to find that my computer had logged me out
  when I had left it alone for some 15 minutes.  I did not bother to
  research at the time and did not see any reason as the problem did not
  manifest again .

  Then today, it happens again. The circumstances are similar: I leave
  the system long enough for the screen to power off and come back to
  find myself kicked out of my session. Yes, kicked out, not simply
  locked out. I need  to log in again and find that all running apps and
  open files have all been  closed.

  My journal would appear to show that gnome-shell got stopped as a
  consequence of systemd-oomd killing several applications (see the
  included journalctl snippet - mind that the output is in reverse order
  (journalctl -r)).

  Should not  oomd terminate single applications instead of complete
  user sessions?

  And I do have some doubts about the statistics listed in the journal.
  One of the killed  apps is reported as consuming over 22GB or RAM (out
  of 32). I have been using that app for many years and cannot remember
  having see it use more than a few GB.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd-oomd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 30 04:00:27 2024
  InstallationDate: Installed on 2022-03-27 (855 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+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 2075104] Re: user session is randomly terminated by systemd-oom when the system is left alone for a while

systemctl cat -- '-.slice':

# /usr/lib/systemd/system/-.slice.d/10-oomd-root-slice-defaults.conf
[Slice]
ManagedOOMSwap=auto

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

Title:
  user session is randomly terminated by systemd-oom when the system is
  left alone for a while

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I was surprised last week to find that my computer had logged me out
  when I had left it alone for some 15 minutes.  I did not bother to
  research at the time and did not see any reason as the problem did not
  manifest again .

  Then today, it happens again. The circumstances are similar: I leave
  the system long enough for the screen to power off and come back to
  find myself kicked out of my session. Yes, kicked out, not simply
  locked out. I need  to log in again and find that all running apps and
  open files have all been  closed.

  My journal would appear to show that gnome-shell got stopped as a
  consequence of systemd-oomd killing several applications (see the
  included journalctl snippet - mind that the output is in reverse order
  (journalctl -r)).

  Should not  oomd terminate single applications instead of complete
  user sessions?

  And I do have some doubts about the statistics listed in the journal.
  One of the killed  apps is reported as consuming over 22GB or RAM (out
  of 32). I have been using that app for many years and cannot remember
  having see it use more than a few GB.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd-oomd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 30 04:00:27 2024
  InstallationDate: Installed on 2022-03-27 (855 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+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 2075104] Re: user session is randomly terminated by systemd-oom when the system is left alone for a while

Oops, I forgot to upload the journal fragment I was referring to. Here
it is.

** Attachment added: "journalctl-snip.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+attachment/5801493/+files/journalctl-snip.txt

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

Title:
  user session is randomly terminated by systemd-oom when the system is
  left alone for a while

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I was surprised last week to find that my computer had logged me out
  when I had left it alone for some 15 minutes.  I did not bother to
  research at the time and did not see any reason as the problem did not
  manifest again .

  Then today, it happens again. The circumstances are similar: I leave
  the system long enough for the screen to power off and come back to
  find myself kicked out of my session. Yes, kicked out, not simply
  locked out. I need  to log in again and find that all running apps and
  open files have all been  closed.

  My journal would appear to show that gnome-shell got stopped as a
  consequence of systemd-oomd killing several applications (see the
  included journalctl snippet - mind that the output is in reverse order
  (journalctl -r)).

  Should not  oomd terminate single applications instead of complete
  user sessions?

  And I do have some doubts about the statistics listed in the journal.
  One of the killed  apps is reported as consuming over 22GB or RAM (out
  of 32). I have been using that app for many years and cannot remember
  having see it use more than a few GB.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd-oomd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 30 04:00:27 2024
  InstallationDate: Installed on 2022-03-27 (855 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+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 2064435] Re: Merge openssh from Debian unstable for oracular

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

Title:
  Merge openssh from Debian unstable for oracular

Status in openssh package in Ubuntu:
  Fix Committed

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1:9.7p1-4
  Ubuntu:   1:9.6p1-3ubuntu13

  Other teams have maintained this package's merge in the past.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Oracular Release Notes:
  https://discourse.ubuntu.com/c/release/38

  ### New Debian Changes ###

  openssh (1:9.7p1-4) unstable; urgency=medium

    * Rework systemd readiness notification and socket activation patches to
  not link against libsystemd (the former via an upstream patch).
    * Force -fzero-call-used-regs=used not to be used on ppc64el (it's
  unsupported, but configure fails to detect this).

   -- Colin Watson   Wed, 03 Apr 2024 12:06:08
  +0100

  openssh (1:9.7p1-3) unstable; urgency=medium

    * Fix gssapi-keyex declaration further (thanks, Andreas Hasenack;
  LP: #2053146).
    * Extend -fzero-call-used-regs check to catch m68k gcc bug (closes:
  #1067243).
    * debian/tests/regress: Set a different IP address for UNKNOWN.
    * Re-enable ssh-askpass-gnome on all architectures.
    * regress: Redirect conch stdin from /dev/zero (re-enables conch interop
  tests).
    * Drop 'Work around RSA SHA-2 signature issues in conch' patch (no longer
  needed now that Twisted is fixed).

   -- Colin Watson   Sun, 31 Mar 2024 11:55:38
  +0100

  openssh (1:9.7p1-2) unstable; urgency=medium

    [ Simon McVittie ]
    * d/control, d/rules: Disable ssh-askpass-gnome on 32-bit, except i386
  (closes: #1066847).

   -- Colin Watson   Thu, 14 Mar 2024 11:45:12
  +

  openssh (1:9.7p1-1) unstable; urgency=medium

    * Add the isolation-container restriction to the 'regress' autopkgtest.
  Our setup code wants to ensure that the haveged service is running, and
  furthermore at least the agent-subprocess test assumes that there's an
  init to reap zombie processes and doesn't work in (e.g.)
  autopkgtest-virt-unshare.
    * New upstream release (https://www.openssh.com/releasenotes.html#9.7p1):
  - ssh(1), sshd(8): add a 'global' ChannelTimeout type that watches all
    open channels and will close all open channels if there is no traffic
    on any of them for the specified interval. This is in addition to the
    existing per-channel timeouts added recently.
    This supports situations like having both session and x11 forwarding
    channels open where one may be idle for an extended period but the
    other is actively used. The global timeout could close both channels
    when both have been idle for too long (closes: #165185).
  - All: make DSA key support compile-time optional, defaulting to on.
  - sshd(8): don't append an unnecessary space to the end of subsystem
    arguments (bz3667)
  - ssh(1): fix the multiplexing 'channel proxy' mode, broken when
    keystroke timing obfuscation was added. (GHPR#463)
  - ssh(1), sshd(8): fix spurious configuration parsing errors when
    options that accept array arguments are overridden (bz3657).
  - ssh-agent(1): fix potential spin in signal handler (bz3670)
  - Many fixes to manual pages and other documentation.
  - Greatly improve interop testing against PuTTY.
    * Skip utimensat test on ZFS, since it seems to leave the atime set to 0.
    * Allow passing extra options to debian/tests/regress, for debugging.
    * Fix gssapi-keyex declaration, broken when rebasing onto 8.9p1
  (LP: #2053146).

   -- Colin Watson   Thu, 14 Mar 2024 10:47:58
  +

  openssh (1:9.6p1-5) unstable; urgency=medium

    * Restore systemd template unit for per-connection sshd instances,
  although without any corresponding .socket unit for now; this is mainly
  for use with the forthcoming systemd-ssh-generator (closes: #1061516).
  It's now called sshd@.service, since unlike the main service there's no
  need to be concerned about compatibility with the slightly confusing
  'ssh' service name that Debian has traditionally used.

   -- Colin Watson   Wed, 06 Mar 2024 09:45:56
  +

  openssh (1:9.6p1-4) unstable; urgency=medium

    * Add sshd_config checksums for 1:9.2p1-1 to ucf reference file, and add a
  test to ensure it doesn't get out of date again.
    * Drop manual adjustment of OpenSSL dependencies; OpenSSH relaxed its
  checks for OpenSSL >= 3 in 9.4p1.
    * Build-depend on pkgconf rather than pkg-config.
    * Adjust

[Touch-packages] [Bug 2075204] [NEW] gdb on s390x chokes on divide-by-zero from chaos-marmosets

2024-07-30 Thread Simon Chopin

Public bug reported:

To help in the development of apport we're using the chaos-marmosets set
of binaries, which triggers various crashes. In particular, we're using
/usr/bin/divide-by-zero which does as its name indicates, which
naturally triggers a native crash.

However, GDB fails on s390x. Note that for the following I have the
debugging symbols from ddebs.ubuntu.com installed:

ubuntu@glibc-proposed:/tmp$ gdb /usr/bin/divide-by-zero
[snip]
Reading symbols from /usr/bin/divide-by-zero...
Reading symbols from 
/usr/lib/debug/.build-id/14/82d2d64c3383ca479f17bfd17b314295c99f13.debug...
(gdb) run
Starting program: /usr/bin/divide-by-zero
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1".

Program received signal SIGTRAP, Trace/breakpoint trap.
0x02aa0814 in ?? ()
(gdb) bt
#0  0x02aa0814 in ?? ()
#1  0x03fff7d2baac in __libc_start_call_main (main=0x2aa0690 , 
main@entry=, 
argc=argc@entry=1, argv=argv@entry=0x3ffa468)
at ../sysdeps/nptl/libc_start_call_main.h:58
#2  0x03fff7d2bbae in __libc_start_main_impl (main=, argc=1, 
argv=0x3ffa468, init=, fini=, 
rtld_fini=0x3fff7f85650 <_dl_fini>,
stack_end=0x3ffa3b0) at ../csu/libc-start.c:360
#3  0x02aa0720 in _start ()
(gdb) info address divide_by_zero
Symbol "divide_by_zero" is a function at address 0x2aa0810.
(gdb)

So at this point GDB isn't capable of identifying the various symbols on
the stack, which isn't ideal.

Now, if I try to step in:

ubuntu@glibc-proposed:/tmp$ gdb -q /usr/bin/divide-by-zero
Reading symbols from /usr/bin/divide-by-zero...
Reading symbols from 
/usr/lib/debug/.build-id/14/82d2d64c3383ca479f17bfd17b314295c99f13.debug...
(gdb) start
Temporary breakpoint 1 at 0x690: file divide-by-zero.c, line 29.
Starting program: /usr/bin/divide-by-zero
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x3ffa468) at divide-by-zero.c:29
warning: 29 divide-by-zero.c: No such file or directory
(gdb) s
34  in divide-by-zero.c
(gdb)
divide_by_zero () at divide-by-zero.c:25
25  in divide-by-zero.c
(gdb)
/build/gdb-nviNEX/gdb-15.1/gdb/infrun.c:2982: internal-error: resume_1: 
Assertion `pc_in_thread_step_range (pc, tp)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
- Backtrace -
0x2aa100a247f ???
0x2aa104efce5 ???
0x2aa104eff7f ???
0x2aa10668c13 ???
0x2aa102553db ???
0x2aa10255bd1 ???
0x2aa10255f5f ???
0x2aa10259195 ???
0x2aa1025c315 ???
0x2aa1025e9a5 ???
0x2aa10260015 ???
0x2aa1066951b ???
0x2aa10669e6d ???
0x2aa102b01cd ???
0x2aa102b3607 ???
0x2aa0ffed839 ???
0x3ffb142baab __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0x3ffb142bbad __libc_start_main_impl
../csu/libc-start.c:360
0x2aa0fff8f8f ???
0x ???
-
/build/gdb-nviNEX/gdb-15.1/gdb/infrun.c:2982: internal-error: resume_1: 
Assertion `pc_in_thread_step_range (pc, tp)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

I can provide a core dump if you think that'd help, but it seems
trivially reproducible.

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

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

Title:
  gdb on s390x chokes on divide-by-zero from chaos-marmosets

Status in gdb package in Ubuntu:
  New

Bug description:
  To help in the development of apport we're using the chaos-marmosets
  set of binaries, which triggers various crashes. In particular, we're
  using /usr/bin/divide-by-zero which does as its name indicates, which
  naturally triggers a native crash.

  However, GDB fails on s390x. Note that for the following I have the
  debugging symbols from ddebs.ubuntu.com installed:

  ubuntu@glibc-proposed:/tmp$ gdb /usr/bin/divide-by-zero
  [snip]
  Reading symbols from /usr/bin/divide-by-zero...
  Reading symbols from 
/usr/lib/debug/.build-id/14/82d2d64c3383ca479f17bfd17b314295c99f13.debug...
  (gdb) run
  Starting program: /usr/bin/divide-by-zero
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1".

  Program received signal SIGTRAP, Trace/breakpoint trap.
  0x02aa0814 in ?? ()
  (gdb) bt
  #0  0x02aa0814 in ?? ()
  #1  0x03fff7d2baac in __libc_start_call_main (main=0x2aa0690 , 
main@entry=, 
argc=argc@entry=1, argv=argv@entry=0x3ffa468)
  at ../sysdeps/nptl/libc_start_call_main.h:58
  #2  0x03fff7d2bbae in __libc_start_main_impl (main=, 
argc=1, argv=0x3ffa468, init=, fini=, 
rtld_fini=0x3fff7f85650 <_dl_fini>,
  stack_end=0x3ffa3b0) at ../csu/libc-start.c:360

[Touch-packages] [Bug 2064435] Re: Merge openssh from Debian unstable for oracular

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

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

Title:
  Merge openssh from Debian unstable for oracular

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1:9.7p1-4
  Ubuntu:   1:9.6p1-3ubuntu13

  Other teams have maintained this package's merge in the past.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Oracular Release Notes:
  https://discourse.ubuntu.com/c/release/38

  ### New Debian Changes ###

  openssh (1:9.7p1-4) unstable; urgency=medium

    * Rework systemd readiness notification and socket activation patches to
  not link against libsystemd (the former via an upstream patch).
    * Force -fzero-call-used-regs=used not to be used on ppc64el (it's
  unsupported, but configure fails to detect this).

   -- Colin Watson   Wed, 03 Apr 2024 12:06:08
  +0100

  openssh (1:9.7p1-3) unstable; urgency=medium

    * Fix gssapi-keyex declaration further (thanks, Andreas Hasenack;
  LP: #2053146).
    * Extend -fzero-call-used-regs check to catch m68k gcc bug (closes:
  #1067243).
    * debian/tests/regress: Set a different IP address for UNKNOWN.
    * Re-enable ssh-askpass-gnome on all architectures.
    * regress: Redirect conch stdin from /dev/zero (re-enables conch interop
  tests).
    * Drop 'Work around RSA SHA-2 signature issues in conch' patch (no longer
  needed now that Twisted is fixed).

   -- Colin Watson   Sun, 31 Mar 2024 11:55:38
  +0100

  openssh (1:9.7p1-2) unstable; urgency=medium

    [ Simon McVittie ]
    * d/control, d/rules: Disable ssh-askpass-gnome on 32-bit, except i386
  (closes: #1066847).

   -- Colin Watson   Thu, 14 Mar 2024 11:45:12
  +

  openssh (1:9.7p1-1) unstable; urgency=medium

    * Add the isolation-container restriction to the 'regress' autopkgtest.
  Our setup code wants to ensure that the haveged service is running, and
  furthermore at least the agent-subprocess test assumes that there's an
  init to reap zombie processes and doesn't work in (e.g.)
  autopkgtest-virt-unshare.
    * New upstream release (https://www.openssh.com/releasenotes.html#9.7p1):
  - ssh(1), sshd(8): add a 'global' ChannelTimeout type that watches all
    open channels and will close all open channels if there is no traffic
    on any of them for the specified interval. This is in addition to the
    existing per-channel timeouts added recently.
    This supports situations like having both session and x11 forwarding
    channels open where one may be idle for an extended period but the
    other is actively used. The global timeout could close both channels
    when both have been idle for too long (closes: #165185).
  - All: make DSA key support compile-time optional, defaulting to on.
  - sshd(8): don't append an unnecessary space to the end of subsystem
    arguments (bz3667)
  - ssh(1): fix the multiplexing 'channel proxy' mode, broken when
    keystroke timing obfuscation was added. (GHPR#463)
  - ssh(1), sshd(8): fix spurious configuration parsing errors when
    options that accept array arguments are overridden (bz3657).
  - ssh-agent(1): fix potential spin in signal handler (bz3670)
  - Many fixes to manual pages and other documentation.
  - Greatly improve interop testing against PuTTY.
    * Skip utimensat test on ZFS, since it seems to leave the atime set to 0.
    * Allow passing extra options to debian/tests/regress, for debugging.
    * Fix gssapi-keyex declaration, broken when rebasing onto 8.9p1
  (LP: #2053146).

   -- Colin Watson   Thu, 14 Mar 2024 10:47:58
  +

  openssh (1:9.6p1-5) unstable; urgency=medium

    * Restore systemd template unit for per-connection sshd instances,
  although without any corresponding .socket unit for now; this is mainly
  for use with the forthcoming systemd-ssh-generator (closes: #1061516).
  It's now called sshd@.service, since unlike the main service there's no
  need to be concerned about compatibility with the slightly confusing
  'ssh' service name that Debian has traditionally used.

   -- Colin Watson   Wed, 06 Mar 2024 09:45:56
  +

  openssh (1:9.6p1-4) unstable; urgency=medium

    * Add sshd_config checksums for 1:9.2p1-1 to ucf reference file, and add a
  test to ensure it doesn't get out of date again.
    * Drop manual adjustment of OpenSSL dependencies; OpenSSH relaxed its
  checks for OpenSSL >= 3 in 9.4p1.
    * Build-depend on pkgconf rather than pkg-config.
    * Adjust debian/copyright to

[Touch-packages] [Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen

This bug was fixed in the package qtbase-opensource-src -
5.15.13+dfsg-4ubuntu1

---
qtbase-opensource-src (5.15.13+dfsg-4ubuntu1) oracular; urgency=medium

  * Merge with Debian unstable, remaining change:
- Force -D_FORTIFY_SOURCE=2 to avoid Qt/KDE apps crashing on start.

qtbase-opensource-src (5.15.13+dfsg-4) unstable; urgency=medium

  * Backport upstream patch to fix qfutureinterface.h for GCC 14
(closes: #1075430).
  * Backport three upstream patches to improve D-Bus tray integration,
in particular on non-X11 desktops (LP: #2059819).
  * Update symbols files for GCC 14.

qtbase-opensource-src (5.15.13+dfsg-3) unstable; urgency=medium

  * Backport upstream patch to delay any communication until encrypted() can
be responded to (CVE-2024-39936, closes: #1076293).
  * Populate ${libssl:Depends} properly for libqt5network5t64.

qtbase-opensource-src (5.15.13+dfsg-2) unstable; urgency=medium

  * Upload to unstable.

  [ Lisandro Damián Nicanor Pérez Meyer ]
  * Remove myself from Uploaders.

 -- Dmitry Shachnev   Fri, 26 Jul 2024 14:47:52
+0300

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Fix Released

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

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Released
Status in qtbase-opensource-src source package in Noble:
  New

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of
  the screen without proper theming.

  See attached image.

  [ Test case ]

  Note: this only tests the appindicator-side that may have lead to
  "activating" the application, it's not something that will fix the
  applications issues that is a QT bug.

  1. Start a QT application with indicator
 (after gnome-shell has started; e.g. clementine, barrier...)
  2. The applindicator menu with shell theme should appear
  3. No activation happens on the application (e.g. the window is not opened)

  [ Regression potential ]

  Mouse events aren't properly exposed to the indicators

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 2075104] Re: user session is randomly terminated by systemd-oom when the system is left alone for a while

Can you share the journal output that you're describing? And, can you
share the output of the following commands?

$ oomctl
$ systemd-analyze cat-config systemd/oomd.conf
$ systemctl cat -- '-.slice'
$ systemctl cat -- user@$(id -u).service

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

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Low

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

Title:
  user session is randomly terminated by systemd-oom when the system is
  left alone for a while

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I was surprised last week to find that my computer had logged me out
  when I had left it alone for some 15 minutes.  I did not bother to
  research at the time and did not see any reason as the problem did not
  manifest again .

  Then today, it happens again. The circumstances are similar: I leave
  the system long enough for the screen to power off and come back to
  find myself kicked out of my session. Yes, kicked out, not simply
  locked out. I need  to log in again and find that all running apps and
  open files have all been  closed.

  My journal would appear to show that gnome-shell got stopped as a
  consequence of systemd-oomd killing several applications (see the
  included journalctl snippet - mind that the output is in reverse order
  (journalctl -r)).

  Should not  oomd terminate single applications instead of complete
  user sessions?

  And I do have some doubts about the statistics listed in the journal.
  One of the killed  apps is reported as consuming over 22GB or RAM (out
  of 32). I have been using that app for many years and cannot remember
  having see it use more than a few GB.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd-oomd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 30 04:00:27 2024
  InstallationDate: Installed on 2022-03-27 (855 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+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 2073126] Re: More nuanced public key algorithm revocation

2024-07-30 Thread Julian Andres Klode

** Description changed:

[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning to an error, breaking them.

We also revoked additional ECC curves, which may still be considered
trusted, so we should not bump them to errors.
+
+ Also existing users may have third-party repositories that use 1024-bit
+ RSA keys and we have not adequately informed them yet perhaps.

[Solution]
Hence we will restore all elliptic curve keys of 256 or more bit to trusted:

">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512,brainpoolP256r1,brainpoolP320r1,brainpoolP384r1,brainpoolP512r1,secp256k1";

At the same time we will also introduce a more nuanced approach to
revocations by introducing a 'next' level that issues a warning if the
key is not allowed in it and a 'future' level that will issue an audit
message with the --audit option.

For the next level, we will set it to:

">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512"

This means we restrict warnings to Brainpool curves and the secp256k1
key, which we have not received any feedback about them being used yet.

For the future level, we will take a strong approach to best practices
as it is only seen when explictly running with --audit and the intention
is to highlight best practices. It will be set to

">=rsa3072,ed25519,ed448";

Which corresponds to the NIST recommendations for 2031 (and as little
- curves as possible)
+ curves as possible).
+
+ We are also introducing a mitigation for existing systems to not upgrade
+ the policy yet; by creating an apt.conf.d configuration file that
+ temporarily allows the 1024-bit RSA keys with the plan to remove them in
+ 24.04.2.

[Test plan]
Tests are included in the library unit tests for parsing the specification
strings; we have also included a test for the gpgv method to ensure that it
produces the correct outcome for both 'next' and 'future' revoked keys.

A spot check with a 1024-bit RSA repository and a 4096 RSA repository
would still be nice.

+ Check a clean install of apt/an upgrade from mantic vs an existing noble
+ system:
+
+ - An existing noble system should create
/etc/apt/apt.conf.d/00-temporary-rsa1024 and continue to trust weak RSA
signatures with a warning
+ - Bootstrap a new noble with proposed enabled using e.g. mmdebstrap and check
that this is not the case
+ - Also check upgrading from mantic directly to proposed and ensure that 1024R
repositories are rejected.
+
[Where problems could occur]
There could of course be bugs in the implementation of the new feature; this
could result in verification of files failing. This also happens if you specify
an invalid `next` or `future` string.

There cannot be any false positives: The new levels are only
*additional* checks, anything not in the `Assert-Pubkey-Algo` list is
still revoked.

** Description changed:

We also revoked additional ECC curves, which may still be considered
trusted, so we should not bump them to errors.

Also existing users may have third-party repositories that use 1024-bit
RSA keys and we have not adequately informed them yet perhaps.

[Solution]
Hence we will restore all elliptic curve keys of 256 or more bit to trusted:

">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512,brainpoolP256r1,brainpoolP320r1,brainpoolP384r1,brainpoolP512r1,secp256k1";

For the next level, we will set it to:

">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512"

This means we restrict warnings to Brainpool curves and the secp256k1
key, which we have not received any feedback about them being used yet.

For the future level, we will take a strong approach to best practices
as it is only seen when explictly running with --audit and the intention
is to highlight best practices. It will be set to

">=rsa3072,ed25519,ed448";

Which corresponds to the NIST recommendations for 2031 (and as little
curves as possible).

- We are also introducing a mitigation for existing systems to not upgrade
- the policy yet; by creating an apt.conf.d configuration file that
- temporarily allows the 1024-bit RSA keys with the plan to remove them in
- 24.04.2.
+ We are also introducing a mitigation for existing 24.04 systems to not
+ upgrade the policy yet; by creating an apt.conf.d configuration file
+ that

[Touch-packages] [Bug 2060721] Re: APT 2.8.0: Promote weak key warnings to errors

2024-07-30 Thread Julian Andres Klode

** Description changed:

  ⚠️ Only land this in the release/updates pocket after PPAs have been
  resigned
  
  (This bumps the apt version to 2.8.0. APT uses the odd/even number
  system, with 2.7.x being the development series for 2.8, and this is the
  only change left for the 2.8 release, safe for some minor
  translation/test suite improvements)
  
- (This will be uploaded after the beta and may be released before noble
- release, as a zero day SRU or within the weeks following the release)
+ (Please also look at bug 2073126 for the follow-up changes to mitigate
+ regression potential).
  
  [Impact]
  APT is currently just warning about keys that it should be rejecting to give 
Launchpad time to resign PPAs. This needs to be bumped to an error such that 
the crypto policy is fully implemented and we only trust keys that are still 
being trusted. #2055193
  
  A warning provides some help right now to third-parties to fix their
  repositories, but it's not *safe*: A repository could have multiple
  signing keys and be signed by a good key now, then later, a previous key
  still in trusted.gpg.d could be revoked and we'd degrade to warnings,
  which, given that we update in the background automatically, the user
  may not see.
  
  Other fixes:
  - The test suite has been made less flaky in two places
  - Documentation translation has been unfuzzied for URL changes in 2.7.14
  
  [Test plan]
  The vast regression test suite prevents regression in other components. 
Additional tests are:
  
- 1. (promotion to error) Take a repository that has a weak key warning, 
upgrade apt and check that it is an error
+ 1. (promotion to error) Take a repository that has a weak RSA key warning, 
upgrade apt and check that it is an error
  2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs 
work correctly.
  
  We don't have any tests for the test changes or the documentation
  translation URL unfuzzying.
  
  [Where problems could occur]
- apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates for 24.04.1, this seems the right tradeoff 
for future security.
+ apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates from 22.04.1 for 24.04.1, this seems the 
right tradeoff for future security.

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

Title:
  APT 2.8.0: Promote weak key warnings to errors

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Noble:
  Fix Committed

Bug description:
  ⚠️ Only land this in the release/updates pocket after PPAs have been
  resigned

  (This bumps the apt version to 2.8.0. APT uses the odd/even number
  system, with 2.7.x being the development series for 2.8, and this is
  the only change left for the 2.8 release, safe for some minor
  translation/test suite improvements)

  (Please also look at bug 2073126 for the follow-up changes to mitigate
  regression potential).

  [Impact]
  APT is currently just warning about keys that it should be rejecting to give 
Launchpad time to resign PPAs. This needs to be bumped to an error such that 
the crypto policy is fully implemented and we only trust keys that are still 
being trusted. #2055193

  A warning provides some help right now to third-parties to fix their
  repositories, but it's not *safe*: A repository could have multiple
  signing keys and be signed by a good key now, then later, a previous
  key still in trusted.gpg.d could be revoked and we'd degrade to
  warnings, which, given that we update in the background automatically,
  the user may not see.

  Other fixes:
  - The test suite has been made less flaky in two places
  - Documentation translation has been unfuzzied for URL changes in 2.7.14

  [Test plan]
  The vast regression test suite prevents regression in other components. 
Additional tests are:

  1. (promotion to error) Take a repository that has a weak RSA key warning, 
upgrade apt and check that it is an error
  2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs 
work correctly.

  We don't have any tests for the test changes or the documentation
  translation URL unfuzzying.

  [Where problems could occur]
  apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates from 22.04.1 for 24.04.1, this seems the 
right tradeoff for future security.

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


-- 
Mailing list:

[Touch-packages] [Bug 2073126] Re: More nuanced public key algorithm revocation

2024-07-30 Thread Julian Andres Klode

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

** Tags added: regression-proposed

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

Title:
  More nuanced public key algorithm revocation

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Noble:
  New
Status in apt source package in Oracular:
  Fix Committed

Bug description:
  [Impact]
  We have received feedback from users that use NIST-P256 keys for their 
repositories that are upset about receiving a warning. APT 2.8.0 in 
noble-proposed would bump the warning to an error, breaking them.

  We also revoked additional ECC curves, which may still be considered
  trusted, so we should not bump them to errors.

  [Solution]
  Hence we will restore all elliptic curve keys of 256 or more bit to trusted:

  
">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512,brainpoolP256r1,brainpoolP320r1,brainpoolP384r1,brainpoolP512r1,secp256k1";

  At the same time we will also introduce a more nuanced approach to
  revocations by introducing a 'next' level that issues a warning if the
  key is not allowed in it and a 'future' level that will issue an audit
  message with the --audit option.

  For the next level, we will set it to:

  ">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512"

  This means we restrict warnings to Brainpool curves and the secp256k1
  key, which we have not received any feedback about them being used
  yet.

  For the future level, we will take a strong approach to best practices
  as it is only seen when explictly running with --audit and the
  intention is to highlight best practices. It will be set to

  ">=rsa3072,ed25519,ed448";

  Which corresponds to the NIST recommendations for 2031 (and as little
  curves as possible)

  [Test plan]
  Tests are included in the library unit tests for parsing the specification 
strings; we have also included a test for the gpgv method to ensure that it 
produces the correct outcome for both 'next' and 'future' revoked keys.

  A spot check with a 1024-bit RSA repository and a 4096 RSA repository
  would still be nice.

  [Where problems could occur]
  There could of course be bugs in the implementation of the new feature; this 
could result in verification of files failing. This also happens if you specify 
an invalid `next` or `future` string.

  There cannot be any false positives: The new levels are only
  *additional* checks, anything not in the `Assert-Pubkey-Algo` list is
  still revoked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2073126/+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 2075104] Re: user session is randomly terminated by systemd-oom when the system is left alone for a while

It has just happened again, right as I was using the computer. Same
error messages in the system journal.

In fact, this time it was worse: I did not get sent back to the login
screen, but returned to the console without any way to use my keyboard
or mouse. I had to reboot.

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

Title:
  user session is randomly terminated by systemd-oom when the system is
  left alone for a while

Status in systemd package in Ubuntu:
  New

Bug description:
  I was surprised last week to find that my computer had logged me out
  when I had left it alone for some 15 minutes.  I did not bother to
  research at the time and did not see any reason as the problem did not
  manifest again .

  Then today, it happens again. The circumstances are similar: I leave
  the system long enough for the screen to power off and come back to
  find myself kicked out of my session. Yes, kicked out, not simply
  locked out. I need  to log in again and find that all running apps and
  open files have all been  closed.

  My journal would appear to show that gnome-shell got stopped as a
  consequence of systemd-oomd killing several applications (see the
  included journalctl snippet - mind that the output is in reverse order
  (journalctl -r)).

  Should not  oomd terminate single applications instead of complete
  user sessions?

  And I do have some doubts about the statistics listed in the journal.
  One of the killed  apps is reported as consuming over 22GB or RAM (out
  of 32). I have been using that app for many years and cannot remember
  having see it use more than a few GB.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd-oomd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 30 04:00:27 2024
  InstallationDate: Installed on 2022-03-27 (855 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+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 2004179] Re: neutron-linuxbridge-agent flat network incompatibility with systemd-networkd

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

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

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

Title:
  neutron-linuxbridge-agent flat network incompatibility with systemd-
  networkd

Status in systemd package in Ubuntu:
  Expired

Bug description:
  We are running an OpenStack installation from Ubuntu's Cloud Archive,
  and our computer hosts have their network configured with systemd-
  networkd. For example, a bond and several VLANs on top, including two
  VLANs used for OpenStack flat networks. We are using neutron-
  linuxbridge-agent, i.e. no OVS or OVN.

  Network interface overview:

   ┌──┐ ┌──┐ ┌──┐
   │ eno2 │ │ eno3 │ │ eno4 │
   └───┬──┘ └───┬──┘ └───┬──┘
   │││
   ┌───┴┴┴──┐
   │ bond0  │
   └─┬───┬─┬┘
 │   │ │
 ┌───┴──┐ ┌──┴───┐ ┌───┴┐
 │ tnet │ │ stor │ │ public │
 └──┘ └──┘ └┘

  The "public" network is a flat provider network (VLAN) that shall be
  used by neutron-linuxbridge-agent and nova-compute to attach to
  virtual machines. "tnet" is used for VXLAN overlay networks, and
  "stor" for Ceph. The issue is with "public" only.

  The systemd-networkd configuration sets up all interfaces. We
  previously used netplan, but missing some needed options. It does use
  systemd-networkd too, so no relevant change to the problem.

  Since merging https://github.com/systemd/systemd/pull/17392, systemd-
  network will remove the master flag from the "public" interface, that
  neutron-linuxbridge-agent assigned to the bridge for the network, e.g.
  brq88363244-5f, breaking all network on the flat network.

  The fix was revered in bug #1929560, but the behavior will not be
  reverted in newer releases. Therefore, every reload of systemd-
  networkd will remove the physical network interface from neutrons
  bridge.

  Using "bridge_mappings" with nova-compute has never been finished,
  according to bug #1105488. nova-compute always requires the dynamic
  bridge, e.g. brq88363244-5f, to be present.

  @ddstreet asked for a new bug and the network configuration:

  # /etc/systemd/network/10-eno1.network:
  [..]

  # /etc/systemd/network/10-eno2.network:
  [Match]
  Name=eno2
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-eno3.network:
  [Match]
  Name=eno3
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-eno4.network:
  [Match]
  Name=eno4
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-bond0.netdev:
  [NetDev]
  Name=bond0
  Kind=bond
  MTUBytes=9000

  [Bond]
  Mode=802.3ad
  LACPTransmitRate=fast
  MIIMonitorSec=100ms
  TransmitHashPolicy=layer3+4

  # /etc/systemd/network/10-bond0.network:
  [Match]
  Name=bond0

  [Link]
  MTUBytes=9000

  [Network]
  LinkLocalAddressing=no
  ConfigureWithoutCarrier=yes
  VLAN=tnet
  VLAN=stor
  VLAN=pulic

  # /etc/systemd/network/10-public.netdev:
  [NetDev]
  Name=public
  Kind=vlan
  MTUBytes=1500

  [VLAN]
  Id=82

  # /etc/systemd/network/10-public.network:
  [Match]
  Name=public

  [Link]
  MTUBytes=1500

  [Network]
  LinkLocalAddressing=no
  ConfigureWithoutCarrier=yes

  # /etc/systemd/network/10-tnet.netdev:
  [..]

  # /etc/systemd/network/10-tnet.network:
  [..]

  # /etc/systemd/network/10-stor.netdev:
  [..]

  # /etc/systemd/network/10-stor.network:
  [..]

  
  neutron-linuxbridge-agent is configured to use "public" as a flat network, 
e.g.:

  # /etc/neutron/plugins/ml2/linuxbridge_agent.ini
  [linux_bridge]
  physical_interface_mappings = public:public
  [..]
  
  When everything is started and a VM needs to be connected to the flat 
network, neutron-linuxbridge-agent creates a dynamic bridge for nova-compute, 
e.g. brq88363244-5f:

  14: public@bond0:  mtu 1500 master 
brqe240c66b-da state UP
  59: brqe240c66b-da:  mtu 1500 state UP

  When systemd-networkd is restarted, it will see that "public" is up
  but has a master assigned. It will be unassigned and break the flat
  network:

  14: public@bond0:  mtu 1500 state UP
  59: brqe240c66b-da:  mtu 1500 state UP

  What would be the recommended why to configure networking on compute
  hosts with Ubuntu OpenStack and flat networks? Not using systemd-
  networkd or netplan at all, but only /etc/network/interfaces?

  Is there any modern alternative?

To manage notifications about this bug go to:

[Touch-packages] [Bug 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI

2024-07-30 Thread Chris Chiu

** Description changed:

  [SRU Justifications]
  
  [Impact]
  Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on 
Soundwire instead of HDA, but the soundwire devices are not well reflected on 
the alsa-info report. In order to meet the increasing demands for SoundWire 
debugging, we must enable alsa-info to provide more information about SoundWire.
  
  [Fix]
- Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire 
devices reported in ACPI"). The reported information can reflect which 
soundwire devices are connected and which soundware link the device connects 
to. It's quite sufficient for what driver should be ready and what 
tplg/firmware file should be loaded. 
+ Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire 
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with 
v1.2.12 and we may not have to backport to Oracular. The reported information 
can reflect which soundwire devices are connected and which soundware link the 
device connects to. It's quite sufficient for what driver should be ready and 
what tplg/firmware file should be loaded.
  
  [Test Case]
- 1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device. 
+ 1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
  2. Install the new alsa-utils debian package
  3. Execute `alsa-info` to generate the report
- 4. Check if the section "ACPI SoundWire Device Status Information" exists in 
the output report. 
+ 4. Check if the section "ACPI SoundWire Device Status Information" exists in 
the output report.
  
  [Where problems could occur]
  It's simply an additional soundwire information when ACPI exposed the 
soundwire device. The risk for regression is low.
+ 
+ [Other Info]
+ Verify if the official Oracular starts from version v1.2.12 to determine if 
we have to land it on Oracular.

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

Title:
  Add SoundWire devices to alsa-info reported in ACPI

Status in alsa-utils package in Ubuntu:
  New
Status in alsa-utils source package in Jammy:
  In Progress
Status in alsa-utils source package in Noble:
  In Progress

Bug description:
  [SRU Justifications]

  [Impact]
  Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on 
Soundwire instead of HDA, but the soundwire devices are not well reflected on 
the alsa-info report. In order to meet the increasing demands for SoundWire 
debugging, we must enable alsa-info to provide more information about SoundWire.

  [Fix]
  Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire 
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with 
v1.2.12 and we may not have to backport to Oracular. The reported information 
can reflect which soundwire devices are connected and which soundware link the 
device connects to. It's quite sufficient for what driver should be ready and 
what tplg/firmware file should be loaded.

  [Test Case]
  1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
  2. Install the new alsa-utils debian package
  3. Execute `alsa-info` to generate the report
  4. Check if the section "ACPI SoundWire Device Status Information" exists in 
the output report.

  [Where problems could occur]
  It's simply an additional soundwire information when ACPI exposed the 
soundwire device. The risk for regression is low.

  [Other Info]
  Verify if the official Oracular starts from version v1.2.12 to determine if 
we have to land it on Oracular.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+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 2075104] [NEW] user session is randomly terminated by systemd-oom when the system is left alone for a while

Public bug reported:

I was surprised last week to find that my computer had logged me out
when I had left it alone for some 15 minutes.  I did not bother to
research at the time and did not see any reason as the problem did not
manifest again .

Then today, it happens again. The circumstances are similar: I leave the
system long enough for the screen to power off and come back to find
myself kicked out of my session. Yes, kicked out, not simply locked out.
I need  to log in again and find that all running apps and open files
have all been  closed.

My journal would appear to show that gnome-shell got stopped as a
consequence of systemd-oomd killing several applications (see the
included journalctl snippet - mind that the output is in reverse order
(journalctl -r)).

Should not  oomd terminate single applications instead of complete user
sessions?

And I do have some doubts about the statistics listed in the journal.
One of the killed  apps is reported as consuming over 22GB or RAM (out
of 32). I have been using that app for many years and cannot remember
having see it use more than a few GB.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd-oomd 255.4-1ubuntu8.2
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 30 04:00:27 2024
InstallationDate: Installed on 2022-03-27 (855 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

** Description changed:

  I was surprised last week to find that my computer had logged me out
  when I came back to it after about fifteen minutes. I did not bother to
  research at the time and did not see any reason as the problem did not
  manifest again .
  
  Today, however, it has happened again. The circumstances are similar: I
  leave the system long enough for the screen to power off and come back
  to find myself kicked out of my session. Yes, kicked out, not simply
  locked out. I have to log in again and find that running applications
  have been terminated and open files closed.
  
  My journal would appear to show that gnome-shell got stopped as a
- conseuqence of systemd-oom killing several applications (see journalctl
+ consequence of systemd-oomd killing several applications (see journalctl
  snip, mind that the output is in reverse order (journalctl -r)).
  
  But I thought the point of oomd was to terminate single applications,
  not the whole user session?
  
  I also have my doubts about the statistics listed in the journal. One
  app is reported as consuming over 22GB or RAM (out of 32). I have been
  using that app for years and have not once seen it use more than a few
  GB.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd-oomd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 30 04:00:27 2024
  InstallationDate: Installed on 2022-03-27 (855 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  I was surprised last week to find that my computer had logged me out
- when I came back to it after about fifteen minutes. I did not bother to
+ when I had left it alone for some 15 minutes.  I did not bother to
  research at the time and did not see any reason as the problem did not
  manifest again .
  
- Today, however, it has happened again. The circumstances are similar: I
- leave the system long enough for the screen to power off and come back
- to find myself kicked out of my session. Yes, kicked out, not simply
- locked out. I have to log in again and find that running applications
- have been terminated and open files closed.
+ Then today, it happens again. The circumstances are similar: I leave the
+ system long enough for the screen to power off and come back to find
+ myself kicked out of my session. Yes, kicked out, not simply locked out.
+ I need  to log in again and find that all running apps and open files
+ have all been  closed.
  
  My journal would appear to show that gnome-shell got stopped as a
- consequence of systemd-oomd killing several applications (see journalctl
- snip, mind that the output is in reverse order (journalctl -r)).
+ consequence of systemd-oomd killing several applications (see the
+ included journalctl snippet - mind that the output is in reverse order
+ (journalctl

[Touch-packages] [Bug 1677668] Re: no GARPs during ephemeral boot

2024-07-30 Thread Brett Holman

Cloud-init now prefers dhcpcd over dhclient, which includes RFC 5227
support. Closing.

** Changed in: cloud-init (Ubuntu)
   Status: Incomplete => 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/1677668

Title:
  no GARPs during ephemeral boot

Status in MAAS:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Deploys time out with an error on the console that says,

  "Can not apply stage final, no datasource found! Likely bad things to
  come!"

  How to duplicate:
  MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1)
  1) Rack Controller and Region Controller in different VLANs
  2) Use Cisco ASA as the router with "ARP Inspection" enabled
  3) Clear the router ARP cache
  4) Deploy 2 maas machines with interfaces set to "Static assign"
  5) Observe deploys successfully
  6) Release both machines and swap IP's.
  7) Redeploy the same 2 machines
  8) Observe deploy failure with the machine consoles stuck in the "ubuntu 
login" screen with "Can not apply stage final, no datasource Found! Likely bad 
things to come!"
   
  The root cause is that during ephemeral PXE booting, no GARPs are sent, which 
in our environment will cause our router (Cisco ASA) to hold on to ARP table 
entries until it expires (default= 4 hours).  Then combined with ASA feature 
"ARP Inspection" will drop packets from a MaaS machine using the previously 
used IP from a different MaaS machine.

  The ephemeral boot image ephemeral-ubuntu-amd64-ga-16.04-xenial-daily.

  Running tcpdump on the Rack Controller, showed no GARPs from the
  deploying MaaS machine.  If there were GARPs sent, then the router
  would refresh its ARP cache thus avoiding the ARP Inspection dropping.

  [Excerpt from Cisco ASA]
  
http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/basic-arp-mac.pdf
  When you enable ARP inspection, the ASA compares the MAC address, IP address, 
and source interface in
  all ARP packets to static entries in the ARP table, and takes the following 
actions:
  • If the IP address, MAC address, and source interface match an ARP entry, 
the packet is passed through.
  • If there is a mismatch between the MAC address, the IP address, or the 
interface, then the ASA drops
  the packet.
  • If the ARP packet does not match any entries in the static ARP table, then 
you can set the ASA to either
  forward the packet out all interfaces (flood), or to drop the packet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1677668/+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 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

Thanks for the bug report. Please try adding this to /etc/environment:

  MUTTER_DEBUG_FORCE_KMS_MODE=simple

and then reboot.

** Summary changed:

- Top margin of secondary monitor covered with black flickering rectangle
+ [nouveau] Top margin of secondary monitor covered with black flickering 
rectangle

** Tags added: nouveau

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

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

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

** Changed in: mutter (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/2074559

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The system has two monitors. Workspaces are activated on the primary
  monitor, but not the second. A custom background image is used on both
  monitor desktops. Windows created on primary monitor then moved to
  secondary e.g. firefox. Window moved towards top of secondary monitor.
  However, window is clipped. Background image is also clipped. The
  clipped area is about one eighth of the monitor, from the top, and
  spans the full area from left to right.

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 24.04 LTS
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 29 15:35:05 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. TU116 [GeForce GTX 1660 SUPER] [3842:1068]
  InstallationDate: Installed on 2024-07-29 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: To Be Filled By O.E.M. Z590 Phantom Gaming 4
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=01105987-3c51-4daa-947e-0b4af195e3a6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.10
  dmi.board.name: Z590 Phantom Gaming 4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.10:bd10/21/2021:br5.19:svnToBeFilledByO.E.M.:pnZ590PhantomGaming4:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: Z590 Phantom Gaming 4
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/linux/+bug/2074559/+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 2074374] Re: Display flikering occationally

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

Please try adding kernel parameter:

  i915.enable_psr=0

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

** Changed in: linux (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/2074374

Title:
  Display flikering occationally

Status in linux package in Ubuntu:
  New

Bug description:
  I'm new linux user, started using ubuntu. My kernel version is Linux 
6.8.0-39-generic x86_64.
  The screen flikers occutionally while using the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 29 18:16:11 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a6]
  InstallationDate: Installed on 2024-07-19 (10 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 04f2:b67f Chicony Electronics Co., Ltd HP TrueVision 
HD Camera
   Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP Laptop 15-da0xxx
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=3c0f8c85-f978-4e69-aaab-be4360a0163f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2023
  dmi.bios.release: 15.45
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.45
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84A6
  dmi.board.vendor: HP
  dmi.board.version: 80.50
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 80.50
  dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd05/23/2023:br15.45:efr80.50:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.50:cvnHP:ct10:cvrChassisVersion:sku4TT04PA#ACJ:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-da0xxx
  dmi.product.sku: 4TT04PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/linux/+bug/2074374/+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 2074059] Re: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1

2024-07-30 Thread Jeremy Bícha

** Changed in: wayland (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  libwayland: breaks plasma desktop start after last upgrade to version
  1.23.0-1

Status in kwin package in Ubuntu:
  Fix Released
Status in wayland package in Ubuntu:
  Fix Released
Status in wayland package in Debian:
  Fix Released

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2074059/+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 2074059] Re: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1

This bug was fixed in the package kwin - 4:5.27.11-0ubuntu4

---
kwin (4:5.27.11-0ubuntu4) oracular; urgency=medium

  * No-change rebuild against wayland 1.23.0 (LP: #2074059)

 -- Rik Mills   Mon, 29 Jul 2024 17:48:33 +0100

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

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

Title:
  libwayland: breaks plasma desktop start after last upgrade to version
  1.23.0-1

Status in kwin package in Ubuntu:
  Fix Released
Status in wayland package in Ubuntu:
  In Progress
Status in wayland package in Debian:
  Fix Released

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2074059/+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 2074059] Re: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1

2024-07-30 Thread Rik Mills

** Tags removed: block-proposed

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

Title:
  libwayland: breaks plasma desktop start after last upgrade to version
  1.23.0-1

Status in kwin package in Ubuntu:
  Fix Committed
Status in wayland package in Ubuntu:
  In Progress
Status in wayland package in Debian:
  Fix Released

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2074059/+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 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined

This bug was fixed in the package quantlib - 1.35-1ubuntu1

---
quantlib (1.35-1ubuntu1) oracular; urgency=medium

  * Also include buildflags.mk to fix FBTFS due to new dpkg
flags (LP: #2071468)

 -- Gianfranco Costamagna   Mon, 29 Jul 2024
09:40:42 +0200

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

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

Title:
  ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
  defined

Status in asymptote package in Ubuntu:
  Fix Released
Status in curl package in Ubuntu:
  Fix Released
Status in doxygen package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Triaged
Status in graphite2 package in Ubuntu:
  Fix Released
Status in gsequencer package in Ubuntu:
  Fix Released
Status in gsl package in Ubuntu:
  New
Status in haskell-devscripts package in Ubuntu:
  Fix Released
Status in jose package in Ubuntu:
  New
Status in ksmtuned package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libtpms package in Ubuntu:
  New
Status in mosh package in Ubuntu:
  Fix Released
Status in mpich package in Ubuntu:
  New
Status in mwrap package in Ubuntu:
  Fix Released
Status in proftpd package in Ubuntu:
  New
Status in proftpd-dfsg package in Ubuntu:
  Fix Released
Status in quantlib package in Ubuntu:
  Fix Released
Status in serf package in Ubuntu:
  Fix Released
Status in setserial package in Ubuntu:
  Fix Released
Status in speech-dispatcher package in Ubuntu:
  New
Status in squid package in Ubuntu:
  Fix Released
Status in swtpm package in Ubuntu:
  Fix Released
Status in texinfo package in Ubuntu:
  Triaged
Status in tix package in Ubuntu:
  New

Bug description:
  The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
  (refined in 1.22.6ubuntu14) can cause this failure:

  ```
  gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
  ```

  This happens when the `-specs=/usr/share/dpkg/elf-package-
  metadata.specs` parameter is set but the needed environment variables
  are not set. Cases:

  1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
  packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
  rp-pppoe fail to build)

  2. autopkgtests

  3. debugging a crash of an application build with the -spec parameter

  4. People like to iteratively continue building the software in the
  build dir while hacking on the package and then have no environment
  variable set.

  This approach is too fragile. An alternative approach would be to specify the 
`--package-metadata` linker flag directly. The problem with that approach is 
that the curly brackets and quotation marks need to be escaped. Example 
failure: Building dpkg would add this parameter to the LDFLAGS:
  ```
  
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
  ```
  The following configure script call (non-relevant parameters deleted):
  ```
  $ gcc 
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
  /usr/bin/ld: cannot find {type:deb: No such file or directory
  /usr/bin/ld: cannot find os:ubuntu: No such file or directory
  /usr/bin/ld: cannot find name:dpkg: No such file or directory
  /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
  /usr/bin/ld: cannot find architecture:amd64}: No such file or directory
  ```

  Proposed solution: Add support for an `--escaped-package-metadata` parameter 
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
  ```
  
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+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 2064435] Re: Merge openssh from Debian unstable for oracular

I have context for most of the delta here, so I will take this merge.

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

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

Title:
  Merge openssh from Debian unstable for oracular

Status in openssh package in Ubuntu:
  New

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1:9.7p1-4
  Ubuntu:   1:9.6p1-3ubuntu13

  Other teams have maintained this package's merge in the past.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Oracular Release Notes:
  https://discourse.ubuntu.com/c/release/38

  ### New Debian Changes ###

  openssh (1:9.7p1-4) unstable; urgency=medium

    * Rework systemd readiness notification and socket activation patches to
  not link against libsystemd (the former via an upstream patch).
    * Force -fzero-call-used-regs=used not to be used on ppc64el (it's
  unsupported, but configure fails to detect this).

   -- Colin Watson   Wed, 03 Apr 2024 12:06:08
  +0100

  openssh (1:9.7p1-3) unstable; urgency=medium

    * Fix gssapi-keyex declaration further (thanks, Andreas Hasenack;
  LP: #2053146).
    * Extend -fzero-call-used-regs check to catch m68k gcc bug (closes:
  #1067243).
    * debian/tests/regress: Set a different IP address for UNKNOWN.
    * Re-enable ssh-askpass-gnome on all architectures.
    * regress: Redirect conch stdin from /dev/zero (re-enables conch interop
  tests).
    * Drop 'Work around RSA SHA-2 signature issues in conch' patch (no longer
  needed now that Twisted is fixed).

   -- Colin Watson   Sun, 31 Mar 2024 11:55:38
  +0100

  openssh (1:9.7p1-2) unstable; urgency=medium

    [ Simon McVittie ]
    * d/control, d/rules: Disable ssh-askpass-gnome on 32-bit, except i386
  (closes: #1066847).

   -- Colin Watson   Thu, 14 Mar 2024 11:45:12
  +

  openssh (1:9.7p1-1) unstable; urgency=medium

    * Add the isolation-container restriction to the 'regress' autopkgtest.
  Our setup code wants to ensure that the haveged service is running, and
  furthermore at least the agent-subprocess test assumes that there's an
  init to reap zombie processes and doesn't work in (e.g.)
  autopkgtest-virt-unshare.
    * New upstream release (https://www.openssh.com/releasenotes.html#9.7p1):
  - ssh(1), sshd(8): add a 'global' ChannelTimeout type that watches all
    open channels and will close all open channels if there is no traffic
    on any of them for the specified interval. This is in addition to the
    existing per-channel timeouts added recently.
    This supports situations like having both session and x11 forwarding
    channels open where one may be idle for an extended period but the
    other is actively used. The global timeout could close both channels
    when both have been idle for too long (closes: #165185).
  - All: make DSA key support compile-time optional, defaulting to on.
  - sshd(8): don't append an unnecessary space to the end of subsystem
    arguments (bz3667)
  - ssh(1): fix the multiplexing 'channel proxy' mode, broken when
    keystroke timing obfuscation was added. (GHPR#463)
  - ssh(1), sshd(8): fix spurious configuration parsing errors when
    options that accept array arguments are overridden (bz3657).
  - ssh-agent(1): fix potential spin in signal handler (bz3670)
  - Many fixes to manual pages and other documentation.
  - Greatly improve interop testing against PuTTY.
    * Skip utimensat test on ZFS, since it seems to leave the atime set to 0.
    * Allow passing extra options to debian/tests/regress, for debugging.
    * Fix gssapi-keyex declaration, broken when rebasing onto 8.9p1
  (LP: #2053146).

   -- Colin Watson   Thu, 14 Mar 2024 10:47:58
  +

  openssh (1:9.6p1-5) unstable; urgency=medium

    * Restore systemd template unit for per-connection sshd instances,
  although without any corresponding .socket unit for now; this is mainly
  for use with the forthcoming systemd-ssh-generator (closes: #1061516).
  It's now called sshd@.service, since unlike the main service there's no
  need to be concerned about compatibility with the slightly confusing
  'ssh' service name that Debian has traditionally used.

   -- Colin Watson   Wed, 06 Mar 2024 09:45:56
  +

  openssh (1:9.6p1-4) unstable; urgency=medium

    * Add sshd_config checksums for 1:9.2p1-1 to ucf reference file, and add a
  test to ensure it doesn't get out of date again.
    * Drop manual adjustment of OpenSSL dependencies; OpenSSH relaxed its
  checks for OpenSSL >= 3 in 9.4p1.

[Touch-packages] [Bug 2074559] [NEW] Top margin of secondary monitor covered with black flickering rectangle

2024-07-30 Thread Jackson Smith

Public bug reported:

The system has two monitors. Workspaces are activated on the primary
monitor, but not the second. A custom background image is used on both
monitor desktops. Windows created on primary monitor then moved to
secondary e.g. firefox. Window moved towards top of secondary monitor.
However, window is clipped. Background image is also clipped. The
clipped area is about one eighth of the monitor, from the top, and spans
the full area from left to right.

$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 29 15:35:05 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. TU116 [GeForce GTX 1660 SUPER] [3842:1068]
InstallationDate: Installed on 2024-07-29 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: To Be Filled By O.E.M. Z590 Phantom Gaming 4
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=01105987-3c51-4daa-947e-0b4af195e3a6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P2.10
dmi.board.name: Z590 Phantom Gaming 4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.10:bd10/21/2021:br5.19:svnToBeFilledByO.E.M.:pnZ590PhantomGaming4:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: Z590 Phantom Gaming 4
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

** Attachment added: "Movie that shows flickering black rectangle at top of 
monitor."
   
https://bugs.launchpad.net/bugs/2074559/+attachment/5801216/+files/VID_20240729_153047814~2.mp4

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

Title:
  Top margin of secondary monitor covered with black flickering
  rectangle

Status in xorg package in Ubuntu:
  New

Bug description:
  The system has two monitors. Workspaces are activated on the primary
  monitor, but not the second. A custom background image is used on both
  monitor desktops. Windows created on primary monitor then moved to
  secondary e.g. firefox. Window moved towards top of secondary monitor.
  However, window is clipped. Background image is also clipped. The
  clipped area is about one eighth of the monitor, from the top, and
  spans the full area from left to right.

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 24.04 LTS
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 29 15:35:05 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) 
(prog-if

[Touch-packages] [Bug 2074302] Re: Asus Laptop (R558U) does not suspend after upgrade to 24.04

2024-07-30 Thread Leonard Peris

** Tags added: suspend-resume

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

Title:
  Asus Laptop (R558U) does not suspend after upgrade to 24.04

Status in systemd package in Ubuntu:
  New

Bug description:
  I was previously running Ubuntu 23.10 on my laptop. I performed a
  `dist-upgrade` about a week back. Since the upgrade to 24.04 my laptop
  does not suspend - either by pressing the power-key (previously
  working on 23.10) or by using the GNOME system power menu.

  My laptop has integrated Intel graphics as well as NVIDIA GeForce
  930MX (GM108M), but i haven't installed proprietary video drivers. It
  is currently using xserver-x-org-video-nouveau as the video driver. My
  system reports as running a wayland session, but I find the above
  X.Org detail confusing.

  There is currently one inhibitor running `gsd-media-keys`.

  I filed a bug under systemd as ubuntu-bug would not let me file a bug
  without a package name. If this is incorrect, please change the
  package-name as appropriate.

  I would like to restore previous functionality - system suspend on
  command.

  I'd be happy to provide additional logs and to troubleshoot any
  possible fixes.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 19:11:12 2024
  InstallationDate: Installed on 2019-04-20 (1926 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. X556UR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to noble on 2024-07-20 (8 days ago)
  dmi.bios.date: 10/24/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UR.309:bd10/24/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnX556UR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X556UR
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2074302/+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 2074523] [NEW] pulseaudio always crashes

2024-07-30 Thread Ahmed Tarek Ashour

Public bug reported:

Pulseaudio always crashes and sound only active for a while then there
is no sound at all

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu10
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:ahmedtarek   2009 F pipewire
 /dev/snd/controlC0:  ahmedtarek   2014 F wireplumber
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 29 21:25:44 2024
InstallationDate: Installed on 2024-07-29 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X3500PC_K3500PC
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: X3500PC.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X3500PC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX3500PC.302:bd08/08/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX3500PC_K3500PC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX3500PC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Vivobook
dmi.product.name: Vivobook_ASUSLaptop X3500PC_K3500PC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  pulseaudio always crashes

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pulseaudio always crashes and sound only active for a while then there
  is no sound at all

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu10
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:ahmedtarek   2009 F pipewire
   /dev/snd/controlC0:  ahmedtarek   2014 F wireplumber
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 29 21:25:44 2024
  InstallationDate: Installed on 2024-07-29 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X3500PC_K3500PC
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X3500PC.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X3500PC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX3500PC.302:bd08/08/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX3500PC_K3500PC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX3500PC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Vivobook
  dmi.product.name: Vivobook_ASUSLaptop X3500PC_K3500PC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2074523/+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 2055825] Re: fips-updates: upgrade from 20.04 to 22.04 fails

2024-07-30 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the linux-aws-
fips/5.4.0-1130.140+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-focal-linux-aws-fips' to
'verification-done-focal-linux-aws-fips'. If the problem still exists,
change the tag 'verification-needed-focal-linux-aws-fips' to
'verification-failed-focal-linux-aws-fips'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-aws-fips-v2 
verification-needed-focal-linux-aws-fips

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

Title:
  fips-updates: upgrade from 20.04 to 22.04 fails

Status in apt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in apt source package in Focal:
  New
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  Focal systems with fips-updates enabled cannot be upgraded to Jammy.  During
  the upgrade, there is a point where the userspace packages are upgraded to
  their Jammy version, but are run on a Focal FIPS kernel.  Specifically, the
  Jammy version of libgcrypt relies on the getrandom syscall with the 
GRND_RESEED
  flag set. This flag, however, is only implemented on the Jammy FIPS kernel. 
So,
  when the Jammy version of libgcrypt is run alongside a Focal FIPS kernel,
  a fatal error occurs.

  [Fix]
  Have getrandom not reject the GRND_RESEED flag. For Focal systems, this flag
  should only be used during the upgrade process from Focal to Jammy, as the
  Jammy userspace packages running on the Focal kernel will rely on it.

  [Test]
  Summary: In a FIPS enabled machine using the fips-updates channel, test the
  upgrade from Focal to Jammy.

  [Where things could go wrong]
  This touches the getrandom syscall, so we have many places where things could
  go wrong. However, we are just adding another possible flag for it, and not
  really adding/removing/altering any other functionality, so the regression
  potential is low.

   Original Report 
---
  Upgrade from 20.04 to 22.04 failed with "Fatal: unexpected error from 
getentropy: Invalid argument". We have fips-updates enabled thru Ubuntu pro 
subscription. Tried to upgrade from 18.04 to 22.04. Upgrade from 18.04 to 204 
is successful but upgrade from 20.04 to 22.04 failed. Apt or do-release-upgrade 
commands no longer working after the upgrade failed so we have to restore the 
host to the Ubuntu 20.04 snapshots.

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.6 LTS
  Release:20.04
  Codename:   focal

  Upgrade log:
  Processing triggers for libc-bin (2.35-0ubuntu3.6) ...
  Errors were encountered while processing:
   systemd
   ntfs-3g
   dbus
   libpam-systemd:amd64
   systemd-sysv
   libnss-systemd:amd64
   friendly-recovery
   samba-common-bin
   samba
   update-notifier-common
  Fatal: unexpected error from getentropy: Invalid argument
  fatal error in libgcrypt, file ../../src/misc.c, line 146, function 
_gcry_logv: internal error (fatal or bug)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055825/+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 2074059] Re: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1

2024-07-30 Thread Rik Mills

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

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

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

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

Title:
  libwayland: breaks plasma desktop start after last upgrade to version
  1.23.0-1

Status in kwin package in Ubuntu:
  Fix Committed
Status in wayland package in Ubuntu:
  In Progress
Status in wayland package in Debian:
  Fix Released

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2074059/+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 2073633] Re: padsp binary missing from pulseaudio-utils

2024-07-30 Thread Hans Joachim Desserud

Thanks for reporting.

Took a look at the package content and changes. Looks like padsp was present in 
Ubuntu 23.10 [1] and then removed in 24.04 [2]. Which means something happened 
between versions
1:16.1+dfsg1-2ubuntu4 [3]
1:16.1+dfsg1-2ubuntu10 [4]

Checking the changelog between these two versions led me to
https://launchpad.net/ubuntu/+source/pulseaudio/1:16.1+dfsg1-2ubuntu8
which disabled padsp. though is short on details why. So there might be
other issues which should be resolved before it can be re-enabled.

Regardless, now that it is disabled, looks like additionally:
* the package still contains bash completions for the binary even though it 
isn't included [2}
* the database for command-not-found doesn't seem to have been updated after 
the binary was removed. It probably should to reflect which binaries exists and 
are offered by the package.


[1] https://packages.ubuntu.com/mantic/amd64/pulseaudio-utils/filelist
[2] https://packages.ubuntu.com/noble/amd64/pulseaudio-utils/filelist
[3] https://packages.ubuntu.com/mantic/pulseaudio-utils
[4] https://packages.ubuntu.com/noble/pulseaudio-utils

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

** Also affects: command-not-found (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  padsp binary missing from pulseaudio-utils

Status in command-not-found package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This package is supposed* to include the padsp binary, but it is not
  installed with the package.

  steps to reproduce:

  sudo apt install pulseaudio-utils

  padsp

  result:

  Command 'padsp' not found, but can be installed with:
  sudo apt install pulseaudio-utils

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: pulseaudio-utils 1:16.1+dfsg1-2ubuntu10
  ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:eamonnm1373 F pipewire
   /dev/snd/controlC1:  eamonnm1376 F wireplumber
   /dev/snd/controlC0:  eamonnm1376 F wireplumber
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Fri Jul 19 15:40:30 2024
  InstallationDate: Installed on 2024-07-15 (4 days ago)
  InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 
(20240425.1)
  MachineType: AAEON MF-001
  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: 01/30/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: MFC1AM12
  dmi.board.asset.tag: Default string
  dmi.board.name: MF-001
  dmi.board.vendor: AAEON
  dmi.board.version: V1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: AAEON
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMFC1AM12:bd01/30/2018:br5.11:svnAAEON:pnMF-001:pvrV1.0:rvnAAEON:rnMF-001:rvrV1.0:cvnAAEON:ct3:cvrV1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MF-001
  dmi.product.sku: Default string
  dmi.product.version: V1.0
  dmi.sys.vendor: AAEON

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/2073633/+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 1675571] Re: Cloud-init update renders secondary addresses to be incompatible with standard tools

2024-07-30 Thread Brett Holman

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Cloud-init update renders secondary addresses to be incompatible with
  standard tools

Status in cloud-init:
  Expired
Status in curtin:
  Confirmed
Status in cloud-init package in Ubuntu:
  Won't Fix
Status in resolvconf package in Ubuntu:
  New
Status in resolvconf package in Debian:
  Won't Fix

Bug description:
  The change of how cloud-init renders 
/etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as 
expected:
  * resolvconf will nullify nameservers
  * if* commands ignore secondary addresses

  [ORIGINAL REPORT]

  Regresion from Bug #1657940.

  When provisioning with multiple eth0 addresses, /etc/resolv.conf is
  empty:

  Consider:
  root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
  address 138.197.98.102
  dns-nameservers 8.8.8.8 8.8.4.4
  gateway 138.197.96.1
  netmask 255.255.240.0

  # control-alias eth0
  iface eth0 inet static
  address 10.17.0.11
  netmask 255.255.0.0

  Which then yields an empty /etc/resolv.conf:
  root@tester:/run/resolvconf# cat interface/eth0.inet

  root@tester:/run/resolvconf# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  The problem is that resolvconfg does pattern matching for eth*.inet.
  The second definition of eth0 has no nameserver and therefore
  overrides the definition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1675571/+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 2046486] Re: units with credentials fail in LXD containers

2024-07-30 Thread Thomas Parrott

OK excellent, so as discussed we'll need to vendor the upstream version
of apparmor into the LXD snap (so we don't have to prematurely rush the
core24 switch) along with the cherry-picks you identified in the GH
issue.

I'll work on landing that in latest/edge first and then we can perform
an interim release into latest/candidate and latest/stable after that.

If there are no issues with that then we can perform the same approach
for 5.21/stable.

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

Title:
  units with credentials fail in LXD containers

Status in cloud-images:
  Confirmed
Status in lxd:
  New
Status in lxd package in Ubuntu:
  Fix Committed
Status in samba package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Many units shipped by systemd use credentials in some way by default
  now (in v256). So this issue is now about much more than the original
  test case failure.

  For example,

  root@oracular:~# apt policy systemd
  systemd:
    Installed: 256-1ubuntu1
    Candidate: 256-1ubuntu1
    Version table:
   *** 256-1ubuntu1 100
  100 http://archive.ubuntu.com/ubuntu oracular-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   255.4-1ubuntu8 500
  500 http://archive.ubuntu.com/ubuntu oracular/main amd64 Packages
  root@oracular:~# for service in $(find /usr/lib/systemd/system -maxdepth 1 
-name "systemd-*.service"); do grep -q "Credential.*=" "$service" && echo 
"$service"; done
  /usr/lib/systemd/system/systemd-sysusers.service
  /usr/lib/systemd/system/systemd-resolved.service
  /usr/lib/systemd/system/systemd-firstboot.service
  /usr/lib/systemd/system/systemd-network-generator.service
  /usr/lib/systemd/system/systemd-journald.service
  /usr/lib/systemd/system/systemd-sysctl.service
  /usr/lib/systemd/system/systemd-tmpfiles-setup-dev-early.service
  /usr/lib/systemd/system/systemd-tmpfiles-setup-dev.service
  /usr/lib/systemd/system/systemd-tmpfiles-setup.service
  /usr/lib/systemd/system/systemd-udev-load-credentials.service
  /usr/lib/systemd/system/systemd-tmpfiles-clean.service
  /usr/lib/systemd/system/systemd-networkd.service

  root@oracular:~# systemctl status systemd-sysusers.service 
systemd-resolved.service systemd-firstboot.service 
systemd-network-generator.service systemd-journald.service 
systemd-sysctl.service systemd-tmpfiles-setup-dev-early.service 
systemd-tmpfiles-setup-dev.service systemd-tmpfiles-setup.service 
systemd-udev-load-credentials.service systemd-tmpfiles-clean.service 
systemd-networkd.service
  ○ systemd-sysusers.service - Create System Users
   Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static)
   Active: inactive (dead)
Condition: start condition unmet at Mon 2024-06-24 18:58:48 UTC; 1min 0s ago
   ├─ ConditionNeedsUpdate=|/etc was not met
   └─ ConditionCredential=|sysusers.extra was not met
 Docs: man:sysusers.d(5)
   man:systemd-sysusers.service(8)

  × systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; 
enabled; preset: enabled)
   Active: failed (Result: exit-code) since Mon 2024-06-24 18:58:49 UTC; 
59s ago
   Invocation: b1aaa662750f48868fe3388e4524c462
 Docs: man:systemd-resolved.service(8)
   man:org.freedesktop.resolve1(5)
   https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
   https://systemd.io/WRITING_RESOLVER_CLIENTS
  Process: 258 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, 
status=243/CREDENTIALS)
 Main PID: 258 (code=exited, status=243/CREDENTIALS)

  ○ systemd-firstboot.service - First Boot Wizard
   Loaded: loaded (/usr/lib/systemd/system/systemd-firstboot.service; 
static)
   Active: inactive (dead)
Condition: start condition unmet at Mon 2024-06-24 18:58:48 UTC; 59s ago
   └─ ConditionFirstBoot=yes was not met
 Docs: man:systemd-firstboot(1)

  ○ systemd-network-generator.service - Generate network units from Kernel 
command line
   Loaded: loaded 
(/usr/lib/systemd/system/systemd-network-generator.service; disabled; preset: 
enabled)
   Active: inactive (dead)
 Docs: man:systemd-network-generator.service(8)

  × systemd-journald.service - Journal Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
  Drop-In: /usr/lib/systemd/system/systemd-journald.service.d
   └─nice.conf
   Active: failed (Result: exit-code) since Mon 2024-06-24 18:58:48 UTC; 
1min 0s ago
   Invocation: 7caace7a15c749f3a86fb15fcfb94dff
  TriggeredBy: × systemd-journald-dev-log.socket
   × systemd-journald.socket
   ○ systemd-journald-audit.socket
 Docs: man:systemd-journald.service(8)

[Touch-packages] [Bug 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined

This bug was fixed in the package tix - 8.4.3-14ubuntu1

---
tix (8.4.3-14ubuntu1) oracular; urgency=medium

  * Also include buildflags.mk to fix FBTFS due to new dpkg
flags (LP: #2071468)

 -- Gianfranco Costamagna   Mon, 29 Jul 2024
08:22:39 +0200

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

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

Title:
  ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
  defined

Status in asymptote package in Ubuntu:
  Fix Released
Status in curl package in Ubuntu:
  Fix Released
Status in doxygen package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Triaged
Status in graphite2 package in Ubuntu:
  Fix Released
Status in gsequencer package in Ubuntu:
  Fix Released
Status in gsl package in Ubuntu:
  New
Status in haskell-devscripts package in Ubuntu:
  Fix Released
Status in jose package in Ubuntu:
  New
Status in ksmtuned package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libtpms package in Ubuntu:
  New
Status in mosh package in Ubuntu:
  Fix Released
Status in mpich package in Ubuntu:
  New
Status in mwrap package in Ubuntu:
  Fix Released
Status in proftpd package in Ubuntu:
  New
Status in proftpd-dfsg package in Ubuntu:
  Fix Released
Status in quantlib package in Ubuntu:
  Fix Released
Status in serf package in Ubuntu:
  Fix Released
Status in setserial package in Ubuntu:
  Fix Released
Status in speech-dispatcher package in Ubuntu:
  New
Status in squid package in Ubuntu:
  Fix Released
Status in swtpm package in Ubuntu:
  Fix Released
Status in texinfo package in Ubuntu:
  Triaged
Status in tix package in Ubuntu:
  Fix Released

Bug description:
  The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
  (refined in 1.22.6ubuntu14) can cause this failure:

  ```
  gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
  ```

  This happens when the `-specs=/usr/share/dpkg/elf-package-
  metadata.specs` parameter is set but the needed environment variables
  are not set. Cases:

  1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
  packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
  rp-pppoe fail to build)

  2. autopkgtests

  3. debugging a crash of an application build with the -spec parameter

  4. People like to iteratively continue building the software in the
  build dir while hacking on the package and then have no environment
  variable set.

  This approach is too fragile. An alternative approach would be to specify the 
`--package-metadata` linker flag directly. The problem with that approach is 
that the curly brackets and quotation marks need to be escaped. Example 
failure: Building dpkg would add this parameter to the LDFLAGS:
  ```
  
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
  ```
  The following configure script call (non-relevant parameters deleted):
  ```
  $ gcc 
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
  /usr/bin/ld: cannot find {type:deb: No such file or directory
  /usr/bin/ld: cannot find os:ubuntu: No such file or directory
  /usr/bin/ld: cannot find name:dpkg: No such file or directory
  /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
  /usr/bin/ld: cannot find architecture:amd64}: No such file or directory
  ```

  Proposed solution: Add support for an `--escaped-package-metadata` parameter 
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
  ```
  
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+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 2073776] Re: nsswitch.conf "passwd" entry misses "systemd", breaking DynamicUser=yes systemd units

2024-07-30 Thread Martin Pitt

OK, thanks for confirming!

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

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

Title:
  nsswitch.conf "passwd" entry misses "systemd", breaking
  DynamicUser=yes systemd units

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The 321-1~bpo22.04.1 version of cockpit-ws calls the cockpit user 
"cockpit-wsinstance":
  $ cat usr/lib/sysusers.d/cockpit-wsinstance.conf
  u cockpit-wsinstance - "User for cockpit-ws instances" -

  However the following systemd files still reference the old "cockpit-ws" 
username, so the service fails to start:
  $ grep -r cockpit-ws$ lib/systemd/system
  lib/systemd/system/cockpit-ws-user.service:Description=Dynamic user for 
cockpit-ws
  lib/systemd/system/cockpit-ws-user.service:User=cockpit-ws
  lib/systemd/system/cockpit-ws-user.service:Group=cockpit-ws
  lib/systemd/system/cockpit-wsinstance-https@.socket:SocketUser=cockpit-ws
  
lib/systemd/system/cockpit-wsinstance-https-factory.socket:SocketUser=cockpit-ws
  lib/systemd/system/cockpit.service:User=cockpit-ws
  lib/systemd/system/cockpit.service:Group=cockpit-ws
  lib/systemd/system/cockpit-wsinstance-http.socket:SocketUser=cockpit-ws

  Can these systemd files be updated to use the new username? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2073776/+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 2074374] [NEW] Display flikering occationally

2024-07-30 Thread Pritto Ruban

Public bug reported:

I'm new linux user, started using ubuntu. My kernel version is Linux 
6.8.0-39-generic x86_64.
The screen flikers occutionally while using the laptop.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 29 18:16:11 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a6]
InstallationDate: Installed on 2024-07-19 (10 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 04f2:b67f Chicony Electronics Co., Ltd HP TrueVision HD 
Camera
 Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 
4.2 Adapter
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: HP HP Laptop 15-da0xxx
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=3c0f8c85-f978-4e69-aaab-be4360a0163f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2023
dmi.bios.release: 15.45
dmi.bios.vendor: Insyde
dmi.bios.version: F.45
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 84A6
dmi.board.vendor: HP
dmi.board.version: 80.50
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 80.50
dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd05/23/2023:br15.45:efr80.50:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.50:cvnHP:ct10:cvrChassisVersion:sku4TT04PA#ACJ:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-da0xxx
dmi.product.sku: 4TT04PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  Display flikering occationally

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm new linux user, started using ubuntu. My kernel version is Linux 
6.8.0-39-generic x86_64.
  The screen flikers occutionally while using the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 29 18:16:11 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a6]
  InstallationDate: Installed on 2024-07-19 (10 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 04f2:b67f Chicony Electronics Co., Ltd HP TrueVision 
HD Camera
   Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP Laptop 15-da0xxx
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=3c0f8c85-f978-4e69-aaab-be4360a0163f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably

[Touch-packages] [Bug 2073776] Re: nsswitch.conf "passwd" entry misses "systemd", breaking DynamicUser=yes systemd units

2024-07-30 Thread Andrew Martin

Yes, I had changed it with ansible

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

Title:
  nsswitch.conf "passwd" entry misses "systemd", breaking
  DynamicUser=yes systemd units

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The 321-1~bpo22.04.1 version of cockpit-ws calls the cockpit user 
"cockpit-wsinstance":
  $ cat usr/lib/sysusers.d/cockpit-wsinstance.conf
  u cockpit-wsinstance - "User for cockpit-ws instances" -

  However the following systemd files still reference the old "cockpit-ws" 
username, so the service fails to start:
  $ grep -r cockpit-ws$ lib/systemd/system
  lib/systemd/system/cockpit-ws-user.service:Description=Dynamic user for 
cockpit-ws
  lib/systemd/system/cockpit-ws-user.service:User=cockpit-ws
  lib/systemd/system/cockpit-ws-user.service:Group=cockpit-ws
  lib/systemd/system/cockpit-wsinstance-https@.socket:SocketUser=cockpit-ws
  
lib/systemd/system/cockpit-wsinstance-https-factory.socket:SocketUser=cockpit-ws
  lib/systemd/system/cockpit.service:User=cockpit-ws
  lib/systemd/system/cockpit.service:Group=cockpit-ws
  lib/systemd/system/cockpit-wsinstance-http.socket:SocketUser=cockpit-ws

  Can these systemd files be updated to use the new username? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2073776/+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 1880839] Re: Clock skew on testbeds

2024-07-30 Thread Skia

** Changed in: auto-package-testing
   Status: New => Won't Fix

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

Title:
  Clock skew on testbeds

Status in Auto Package Testing:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Clock stepped backward on a testbed:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  groovy/groovy/amd64/b/boost1.71/20200501_151103_1e387@/log.gz

  ...
  context  FAIL stderr: make[2]: Warning: File 
'/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification time 0.52 s in the future
  autopkgtest [13:55:37]: test context:  - - - - - - - - - - stderr - - - - - - 
- - - -
  make[2]: Warning: File '/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification 
time 0.52 s in the future
  make[2]: warning:  Clock skew detected.  Your build may be incomplete.
  ..

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1880839/+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 2073787] Re: apport-retrace needs more than 1 GB memory (when using sandbox)

For reference the sizes of the Contents files:

## jammy

Compressed:

```
$ du -B M -s *jammy*Contents* | sort -n
19M jammy-proposed-Contents-amd64.gz
45M jammy-Contents-amd64.gz
122Mjammy-security-Contents-amd64.gz
126Mjammy-updates-Contents-amd64.gz
```

Uncompressed:

```
$ du -B M -s *jammy*Contents* | sort -n
339Mjammy-proposed-Contents-amd64
717Mjammy-Contents-amd64
2242M   jammy-security-Contents-amd64
2306M   jammy-updates-Contents-amd64
```

## noble

Compressed:

```
$ du -B M -s *noble*Contents* | sort -n
3M  noble-proposed-Contents-amd64.gz
11M noble-security-Contents-amd64.gz
11M noble-updates-Contents-amd64.gz
49M noble-Contents-amd64.gz
```

Uncompressed:

```
$ du -B M -s *noble*Contents* | sort -n
44M noble-proposed-Contents-amd64
182Mnoble-security-Contents-amd64
188Mnoble-updates-Contents-amd64
791Mnoble-Contents-amd64
```

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

Title:
  apport-retrace needs more than 1 GB memory (when using sandbox)

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  The system tests test_retrace_system_sandbox and
  test_retrace_jammy_sandbox fail on arm64, ppc64el, s390x, because
  apport-retrace is killed by the OOM killer. Example:

  autopkgtest kernel: Out of memory: Killed process 3597 (apport-
  retrace) total-vm:1512420kB, anon-rss:1241460kB, file-rss:2592kB,
  shmem-rss:0kB, UID:0 pgtables:2554kB oom_score_adj:0

  Log: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-
  bdrung-apport/oracular/s390x/a/apport/20240722_145904_d3c2f@/log.gz

  apport-retrace should be able to retrace crashes without needing
  multiple gigabytes of memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2073787/+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 2073787] Re: apport-retrace needs more than 1 GB memory (when using sandbox)

** Summary changed:

- apport-retrace needs more than 1 GB
+ apport-retrace needs more than 1 GB memory (when using sandbox)

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

Title:
  apport-retrace needs more than 1 GB memory (when using sandbox)

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  The system tests test_retrace_system_sandbox and
  test_retrace_jammy_sandbox fail on arm64, ppc64el, s390x, because
  apport-retrace is killed by the OOM killer. Example:

  autopkgtest kernel: Out of memory: Killed process 3597 (apport-
  retrace) total-vm:1512420kB, anon-rss:1241460kB, file-rss:2592kB,
  shmem-rss:0kB, UID:0 pgtables:2554kB oom_score_adj:0

  Log: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-
  bdrung-apport/oracular/s390x/a/apport/20240722_145904_d3c2f@/log.gz

  apport-retrace should be able to retrace crashes without needing
  multiple gigabytes of memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2073787/+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 2073787] Re: apport-retrace needs more than 1 GB

Takeaway from the benchmarks:

The current implementation (dict + pickle) is the fastest as long as
there is enough memory without swapping. In case the data does not fit
into the memory any more, SQLite (v1 < v2 < v3) is the fastest. In case
of low memory without swap, only SQLite were not killed. So I propose we
implement the SQLite solution.

The question is which variant?

* v1: simple key value store. Benefit: fastest and simplest solution.
Drawback: Biggest files on disk (jammy: 1511 MB vs 777 MB of the pickle
file)

* v2: norm form with packages stores in a separate table. Benefit:
smaller than v1 (jammy: 1.31 GB vs 1.51 GB), makes database fetishists
happy, only slightly slower than v1. Drawback: More code.

* v3: like v2 but key split into beginning and end of path. Benefit:
smaller than v2 and can even beat the pickle file (jammy: 710 MB vs 777
MB pickle vs 1313 MB v2). Drawback: significantly slower than v2 and v1,
only slightly more complex than v2.

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

Title:
  apport-retrace needs more than 1 GB memory (when using sandbox)

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  The system tests test_retrace_system_sandbox and
  test_retrace_jammy_sandbox fail on arm64, ppc64el, s390x, because
  apport-retrace is killed by the OOM killer. Example:

  autopkgtest kernel: Out of memory: Killed process 3597 (apport-
  retrace) total-vm:1512420kB, anon-rss:1241460kB, file-rss:2592kB,
  shmem-rss:0kB, UID:0 pgtables:2554kB oom_score_adj:0

  Log: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-
  bdrung-apport/oracular/s390x/a/apport/20240722_145904_d3c2f@/log.gz

  apport-retrace should be able to retrace crashes without needing
  multiple gigabytes of memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2073787/+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 2073787] Re: apport-retrace needs more than 1 GB

Here comes the result of benchmark with different databases. I pushed
the test code to the benchmark-databases:
https://github.com/bdrung/apport/tree/benchmark-databases You can
execute the test file or use `run_all` to execute them all.

## Creation and query time

Results on jammy Contents with a Ryzen 7 5700G:

```
$ ./contents_leveldb.py -jd
Creation duration: 39.186 s
Access duration: 1.529 ms
Total duration: 39.566 s

$ ./contents_lmdb.py -jd
Creation duration: 42.202 s
Access duration: 0.292 ms
Total duration: 42.746 s

$ ./contents_sqlite_v1.py -jd
Creation duration: 47.238 s
Access duration: 1.090 ms
Total duration: 47.734 s

$ ./contents_sqlite_v2.py -jd
Creation duration: 47.416 s
Access duration: 1.232 ms
Total duration: 48.882 s

$ ./contents_sqlite_v3.py -jds
Creation duration: 54.331 s
Entries in packages table: 72,036
Entries in directories table: 92,679
Total entries: 8,037,545
Access duration: 1.537 ms
Total duration: 54.657 s

$ ./contents_sqlite_v3b.py -jds
Creation duration: 53.860 s
Entries in packages table: 72,036
Entries in directories table: 30,219
Total entries: 8,037,545
Access duration: 1.606 ms
Total duration: 54.120 s

$ ./contents_ndbm.py -jd
Creation duration: 1 min 41.623 s (= 101.623 s)
Access duration: 0.274 ms
Total duration: 1 min 43.074 s (= 103.074 s)

$ ./contents_dbm.py -jd
Creation duration: 2 min 6.741 s (= 126.741 s)
Access duration: 0.364 ms
Total duration: 2 min 7.168 s (= 127.168 s)

$ ./contents_pickle.py -jd
Creation duration: 36.603 s
Save duration: 4.301 s
Access duration: 0.017 ms
Total duration: 41.456 s

$ ./contents_unoptimized_pickle.py -jd
Creation duration: 59.445 s
Save duration: 4.354 s
Access duration: 0.018 ms
Total duration: 1 min 4.296 s (= 64.296 s)
```

Results on a Raspberry Pi 2W on 2024-07-26 with jammy Contents (dbm and
ndbm were too slow):

```
$ ./contents_leveldb.py -dsj
Creation duration: 28 min 38.402 s (= 1718.402 s)
Total entries: 7,911,114
Access duration: 153.075 ms
Total duration: 32 min 17.500 s (= 1937.500 s)

$ ./contents_lmdb.py -dsj
Creation duration: 35 min 15.257 s (= 2115.257 s)
Total entries: 7,911,114
Access duration: 508.313 ms
Total duration: 36 min 47.932 s (= 2207.932 s)

$ ./contents_sqlite_v1.py -dsj
Creation duration: 14 min 32.801 s (= 872.801 s)
Total entries: 7,911,114
Access duration: 39.372 ms
Total duration: 16 min 0.188 s (= 960.188 s)

$ ./contents_sqlite_v2.py -dsj
Creation duration: 14 min 45.833 s (= 885.833 s)
Total entries: 7,911,114
Access duration: 37.519 ms
Total duration: 15 min 55.706 s (= 955.706 s)

$ ./contents_sqlite_v3.py -dsj
Creation duration: 16 min 20.365 s (= 980.365 s)
Entries in packages table: 72,036
Entries in directories table: 92,679
Total entries: 8,037,545
Access duration: 45.323 ms
Total duration: 18 min 6.704 s (= 1086.704 s)

$ ./contents_pickle.py -dsj
Creation duration: 24 min 36.127 s (= 1476.127 s)
Save duration: 4 h 9 min 1.947 s (= 14941.947 s)
Total entries: 7,911,114
Access duration: 33.207 ms
Total duration: 4 h 37 min 24.957 s (= 16644.957 s)
```

Results on a Raspberry Pi 2W on 2024-07-25 with noble (dbm and ndbm were
too slow):

```
$ ./run_all -ds
$ ./contents_leveldb.py -ds
Creation duration: 8 min 15.134 s (= 495.134 s)
Total entries: 4,267,770
Access duration: 28.648 ms
Total duration: 8 min 43.739 s (= 523.739 s)

$ ./contents_lmdb.py -ds
Creation duration: 10 min 5.755 s (= 605.755 s)
Total entries: 4,267,770
Access duration: 55.521 ms
Total duration: 11 min 42.699 s (= 702.699 s)

$ ./contents_sqlite_v1.py -ds
Creation duration: 4 min 37.866 s (= 277.866 s)
Total entries: 4,267,770
Access duration: 38.377 ms
Total duration: 5 min 14.372 s (= 314.372 s)

$ ./contents_sqlite_v2.py -ds
Creation duration: 4 min 41.446 s (= 281.446 s)
Total entries: 4,267,770
Access duration: 40.402 ms
Total duration: 5 min 14.173 s (= 314.173 s)

$ ./contents_sqlite_v3.py -ds
Creation duration: 5 min 27.911 s (= 327.911 s)
Entries in packages table: 66,602
Entries in directories table: 79,371
Total entries: 4,333,447
Access duration: 51.763 ms
Total duration: 5 min 56.019 s (= 356.019 s)

$ ./contents_sqlite_v3b.py -ds
Creation duration: 5 min 34.859 s (= 334.859 s)
Entries in packages table: 66,602
Entries in directories table: 26,298
Total entries: 4,333,447
Access duration: 46.310 ms
Total duration: 5 min 59.153 s (= 359.153 s)
```

## Results on low memory systems

Benchmark results on a Raspberry Pi 2W with swap disabled (so only 512
MB):

```
$ ./contents_leveldb.py -dsj
Killed
./contents_leveldb.py failed with 137

$ ./contents_lmdb.py -dsj
Killed
./contents_lmdb.py failed with 137

$ ./contents_sqlite_v1.py -dsj
Creation duration: 14 min 42.957 s (= 882.957 s)
Total entries: 8,037,545
Access duration: 36.858 ms
Total duration: 16 min 11.612 s (= 971.612 s)

$ ./contents_sqlite_v2.py -dsj
Creation duration: 15 min 2.569 s (= 902.569 s)
Entries in packages table: 72,036
Total entries: 8,037,545
Access duration: 38.994 ms
Total duration: 16 min 12.557 s (= 972.557 s)

[Touch-packages] [Bug 2068940] Re: bad environment variable in padsp script

2024-07-30 Thread bivanbi

A quick dirty workaround for 64-bit binaries:
```
diff --git a/usr/bin/padsp.dpkg b/usr/bin/padsp
index 1f6bfd5..62e8686 100755
--- a/usr/bin/padsp.dpkg
+++ b/usr/bin/padsp
@@ -73,11 +73,7 @@ done
 
 shift $(( $OPTIND - 1 ))
 
-if [ x"$LD_PRELOAD" = x ] ; then
-   LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so"
-else
-   LD_PRELOAD="$LD_PRELOAD /usr/\\$$LIB/pulseaudio/libpulsedsp.so"
-fi
+LD_PRELOAD=/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsedsp.so
 
 export LD_PRELOAD
 
```

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

Title:
  bad environment variable in padsp script

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  On jammy 22.04 LTS.  I need padsp for an old program that writes to /dev/dsp. 
 The /usr/bin/padsp script from pulseaudio-utils 1:15.99.1+dfsg1-1ubuntu2.2 has 
the lines
  if [ x"$LD_PRELOAD" = x ] ; then
 LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so"
  else
 LD_PRELOAD="$LD_PRELOAD /usr/\\$$LIB/pulseaudio/libpulsedsp.so"
  fi
  I don't know where it is supposed to be picking up a value for $LIB, but it 
isn't working.  I get an error message: ld.so: object 
'/usr/\788488LIB/pulseaudio/libpulsedsp.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
  The libpulsedsp 1:15.99.1+dfsg1-1ubuntu2.2  package put libpulsedsp.so in 
/usr/lib/x86_64-linux-gnu/pulseaudio and if I edit that into the script in 
place of the call to $LIB, everything works.  So I think it is just a problem 
with the use of LIB in the script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2068940/+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 2058976] Re: Configuration files for networkd are created when NetworkManager is the default renderer

2024-07-30 Thread Danilo Egea Gondolfo

I have found another case where reloading networkd will not be enough to
apply the configuration. I'm not sure if it's the same root cause but it
looks similar so I'll use this ticket to document it.

The scenario looks like this (it's all done in a LXD VM running
Oracular):

1) Start with the default ethernet configuration
2) Add the ethernet interface to a bond and apply
3) Remove the bond from the configuration and apply
4) Add the interface back to the bond and apply
5) At this point the configuration will not be applied anymore and one needs to 
either restart networkd or delete the bond.

It smells like some state is not being dropped and causing the issue.

Details on how to reproduce:

Start with this config:

network:
  version: 2
  ethernets:
enp5s0:
  dhcp4: true
  
  
Add a bond:

network:
  version: 2
  ethernets:
enp5s0: {}
  bonds:
bond0:
  dhcp4: true
  interfaces:
- enp5s0


Apply the config and observe it worked as intended.

Now restore the initial config and netplan apply again:

network:
  version: 2
  ethernets:
enp5s0:
  dhcp4: true

At this point enp4s0 will get an IP address and the bond0 interface will
be left behind as netplan apply will not delete it.

Now add the bond back and netplan apply again:

network:
  version: 2
  ethernets:
enp5s0: {}
  bonds:
bond0:
  dhcp4: true
  interfaces:
- enp5s0


At this point the configuration will not by applied anymore.
The bond state will get stuck at "State: no-carrier (configuring)".
One needs to either delete the bond or restart networkd to make it work again.

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

Title:
  Configuration files for networkd are created when NetworkManager is
  the default renderer

Status in Netplan:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  This is happening in a UC image created with a gadget that disables
  console-conf:

  $ ubuntu-image snap --snap=network-manager=22 --snap pc_22.snap

  The snaps are:

  $ snap list
  Name Version RevTracking Publisher   Notes
  core22   202403211344   latest/edge  canonical✓  base
  network-manager  1.36.6-987622/stablecanonical✓  -
  pc   22-0.3  x1 --   
gadget
  pc-kernel5.15.0-102.112.1+1  1731   22/beta  canonical✓  
kernel
  snapd2.62+git2017.g1afc063e  21490  latest/edge  canonical✓  snapd

  On first boot, the content in /etc/netplan is:

  ubuntu@ubuntu:~$ cat /etc/netplan/00-default-nm-renderer.yaml 
  network:
renderer: NetworkManager
  ubuntu@ubuntu:~$ cat /etc/netplan/50-cloud-init.yaml 
  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: '52:54:00:12:34:56'
  set-name: ens3
  version: 2

  
  But we have a configuration file for systemd-networkd that should not be 
there:

  ubuntu@ubuntu:~$ cat /run/systemd/network/10-netplan-ens3.link 
  [Match]
  PermanentMACAddress=52:54:00:12:34:56

  [Link]
  Name=ens3
  WakeOnLan=off

  ubuntu@ubuntu:~$ networkctl 
  IDX LINK TYPE OPERATIONAL SETUP 
1 lo   loopback carrier unmanaged
2 ens3 etherroutableconfigured

  While having to:

  ubuntu@ubuntu:~$ sudo cat 
/run/NetworkManager/system-connections/netplan-ens3.nmconnection
  [connection]
  id=netplan-ens3
  type=ethernet
  interface-name=ens3

  [ethernet]
  wake-on-lan=0

  [ipv4]
  method=auto

  [ipv6]
  method=ignore

  ubuntu@ubuntu:~$ nmcli c
  NAME  UUID  TYPE  DEVICE 
  netplan-ens3  bec3d02a-c9e5-3283-92ab-ee43a4246c85  ethernet  ens3   

  ubuntu@ubuntu:~$ nmcli d
  DEVICE  TYPE  STATE  CONNECTION   
  ens3ethernet  connected  netplan-ens3 
  lo  loopback  unmanaged  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2058976/+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 2073338] Re: Please merge shadow 1:4.15.3-2 into Oracular

2024-07-30 Thread Simon Chopin

** Merge proposal linked:
   
https://code.launchpad.net/~hectorcao/ubuntu/+source/shadow/+git/shadow/+merge/469556

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

Title:
  Please merge shadow 1:4.15.3-2 into Oracular

Status in shadow package in Ubuntu:
  In Progress

Bug description:
  Current debian version in Oracular: 1:4.13+dfsg1 (upstream version
  4.13)

  New version 1:4.15.3-2 has been released in Debian unstable (upstream
  version 4.15)

  4.15 is the current supported stable version of upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2073338/+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 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined

This bug was fixed in the package setserial - 2.17-55ubuntu1

---
setserial (2.17-55ubuntu1) oracular; urgency=medium

  * Also include buildflags.mk to fix FBTFS due to new dpkg
flags (LP: #2071468)

 -- Gianfranco Costamagna   Mon, 29 Jul 2024
08:23:13 +0200

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

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

Title:
  ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
  defined

Status in asymptote package in Ubuntu:
  Fix Released
Status in curl package in Ubuntu:
  Fix Released
Status in doxygen package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Triaged
Status in graphite2 package in Ubuntu:
  Fix Released
Status in gsequencer package in Ubuntu:
  Fix Released
Status in gsl package in Ubuntu:
  New
Status in haskell-devscripts package in Ubuntu:
  Fix Released
Status in jose package in Ubuntu:
  New
Status in ksmtuned package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libtpms package in Ubuntu:
  New
Status in mosh package in Ubuntu:
  Fix Released
Status in mpich package in Ubuntu:
  New
Status in mwrap package in Ubuntu:
  Fix Released
Status in proftpd package in Ubuntu:
  New
Status in proftpd-dfsg package in Ubuntu:
  Fix Released
Status in quantlib package in Ubuntu:
  New
Status in serf package in Ubuntu:
  Fix Released
Status in setserial package in Ubuntu:
  Fix Released
Status in speech-dispatcher package in Ubuntu:
  New
Status in squid package in Ubuntu:
  Fix Released
Status in swtpm package in Ubuntu:
  Fix Released
Status in texinfo package in Ubuntu:
  Triaged
Status in tix package in Ubuntu:
  New

Bug description:
  The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
  (refined in 1.22.6ubuntu14) can cause this failure:

  ```
  gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
  ```

  This happens when the `-specs=/usr/share/dpkg/elf-package-
  metadata.specs` parameter is set but the needed environment variables
  are not set. Cases:

  1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
  packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
  rp-pppoe fail to build)

  2. autopkgtests

  3. debugging a crash of an application build with the -spec parameter

  4. People like to iteratively continue building the software in the
  build dir while hacking on the package and then have no environment
  variable set.

  This approach is too fragile. An alternative approach would be to specify the 
`--package-metadata` linker flag directly. The problem with that approach is 
that the curly brackets and quotation marks need to be escaped. Example 
failure: Building dpkg would add this parameter to the LDFLAGS:
  ```
  
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
  ```
  The following configure script call (non-relevant parameters deleted):
  ```
  $ gcc 
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
  /usr/bin/ld: cannot find {type:deb: No such file or directory
  /usr/bin/ld: cannot find os:ubuntu: No such file or directory
  /usr/bin/ld: cannot find name:dpkg: No such file or directory
  /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
  /usr/bin/ld: cannot find architecture:amd64}: No such file or directory
  ```

  Proposed solution: Add support for an `--escaped-package-metadata` parameter 
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
  ```
  
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+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 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined

2024-07-30 Thread Gianfranco Costamagna

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

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

Title:
  ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
  defined

Status in asymptote package in Ubuntu:
  Fix Released
Status in curl package in Ubuntu:
  Fix Released
Status in doxygen package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Triaged
Status in graphite2 package in Ubuntu:
  Fix Released
Status in gsequencer package in Ubuntu:
  Fix Released
Status in gsl package in Ubuntu:
  New
Status in haskell-devscripts package in Ubuntu:
  Fix Released
Status in jose package in Ubuntu:
  New
Status in ksmtuned package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libtpms package in Ubuntu:
  New
Status in mosh package in Ubuntu:
  Fix Released
Status in mpich package in Ubuntu:
  New
Status in mwrap package in Ubuntu:
  Fix Released
Status in proftpd package in Ubuntu:
  New
Status in proftpd-dfsg package in Ubuntu:
  Fix Released
Status in quantlib package in Ubuntu:
  New
Status in serf package in Ubuntu:
  Fix Released
Status in setserial package in Ubuntu:
  New
Status in speech-dispatcher package in Ubuntu:
  New
Status in squid package in Ubuntu:
  Fix Released
Status in swtpm package in Ubuntu:
  Fix Released
Status in texinfo package in Ubuntu:
  Triaged
Status in tix package in Ubuntu:
  New

Bug description:
  The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
  (refined in 1.22.6ubuntu14) can cause this failure:

  ```
  gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
  ```

  This happens when the `-specs=/usr/share/dpkg/elf-package-
  metadata.specs` parameter is set but the needed environment variables
  are not set. Cases:

  1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
  packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
  rp-pppoe fail to build)

  2. autopkgtests

  3. debugging a crash of an application build with the -spec parameter

  4. People like to iteratively continue building the software in the
  build dir while hacking on the package and then have no environment
  variable set.

  This approach is too fragile. An alternative approach would be to specify the 
`--package-metadata` linker flag directly. The problem with that approach is 
that the curly brackets and quotation marks need to be escaped. Example 
failure: Building dpkg would add this parameter to the LDFLAGS:
  ```
  
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
  ```
  The following configure script call (non-relevant parameters deleted):
  ```
  $ gcc 
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
  /usr/bin/ld: cannot find {type:deb: No such file or directory
  /usr/bin/ld: cannot find os:ubuntu: No such file or directory
  /usr/bin/ld: cannot find name:dpkg: No such file or directory
  /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
  /usr/bin/ld: cannot find architecture:amd64}: No such file or directory
  ```

  Proposed solution: Add support for an `--escaped-package-metadata` parameter 
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
  ```
  
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+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 2074278] Re: smash the window

Thanks for the bug report. Please attach a video or photo of the
problem. You can create either by pressing PrtScn.

** Tags added: nouveau

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

** Summary changed:

- smash the window
+ [nouveau] menu turns on and off at a very high speed

** Changed in: 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/2074278

Title:
  [nouveau] menu turns on and off at a very high speed

Status in Ubuntu:
  Incomplete

Bug description:
  When I open the shutter and bottom menus and every drop down menus. Instead 
of opening the menu correctly. The menu turns on and off at a very high speed 
and causes the window to crash. 
  Laptop model: Dell Latitude E6410

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 02:17:21 2024
  DistUpgraded: 2024-07-28 01:39:08,562 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GT218M [NVS 3100M] [1028:040a]
  InstallationDate: Installed on 2024-07-27 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: Dell Inc. Latitude E6410
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=8393ad29-8de9-4017-a55c-4b34074194be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-07-27 (0 days ago)
  dmi.bios.date: 05/12/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 07XJP9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd05/12/2017:br4.6:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn07XJP9:rvrA01:cvnDellInc.:ct9:cvr:sku:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/+bug/2074278/+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 2074335] Re: Xorg freeze

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

** Changed in: 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/2074335

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Last night, early in the morning(July 29 around 00:20, the wholesystem
  crashed and I had to push the restart button on the desktop.  I had
  just finished building a kernel for gentoo  in VM workstation pro.  I
  just tried to close google chrome on my main ubuntu desktop, computer
  froze. This morning at cli, typed journalctl -p error, and it's saying
  bunch of stuff about cpu being stuck.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.183.01  Sun May 12 
19:39:15 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 29 08:48:26 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GA106 [GeForce RTX 
3060 Lite Hash Rate] [1462:397b]
   Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c4) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Raphael [1462:7d75]
  InstallationDate: Installed on 2024-07-20 (9 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Micro-Star International Co., Ltd. MS-7D75
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=7a79c852-07bb-478d-9cac-84c35c500341 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2024
  dmi.bios.release: 5.35
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.J4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAG B650 TOMAHAWK WIFI (MS-7D75)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.J4:bd07/17/2024:br5.35:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D75:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB650TOMAHAWKWIFI(MS-7D75):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D75
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A

[Touch-packages] [Bug 2074265] Re: Crashing System

Thanks for the bug report.

This looks similar to Nvidia bug 2061079 so please try adding
GSK_RENDERER=gl to /etc/environment and reboot.

** Tags added: nouveau

** Summary changed:

- Crashing System
+ Graphics corruption in Nautilus

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

** Changed in: ubuntu
   Status: New => Incomplete

** Summary changed:

- Graphics corruption in Nautilus
+ [nouveau] Graphics corruption in Nautilus

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

Title:
  [nouveau] Graphics corruption in Nautilus

Status in Ubuntu:
  Incomplete

Bug description:
  When I use the system with Gnome, rendering errors appear, and
  sometimes, almost always, the system crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 12:43:00 2024
  DistUpgraded: 2024-07-27 11:36:36,601 DEBUG running apport_crash()
  DistroCodename: noble
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce G210] [10de:0a60] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GT218 [GeForce G210] [10de:]
  InstallationDate: Installed on 2024-07-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-45-generic 
root=UUID=316df0de-ff13-457d-8ba7-42e616dabe56 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to noble on 2024-07-27 (0 days ago)
  dmi.bios.date: 03/04/2017
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX/BR
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.init.d.apport: 2024-04-23T08:30:10
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/+bug/2074265/+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 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined

2024-07-30 Thread Gianfranco Costamagna

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

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

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

Title:
  ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
  defined

Status in asymptote package in Ubuntu:
  Fix Released
Status in curl package in Ubuntu:
  Fix Released
Status in doxygen package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Triaged
Status in graphite2 package in Ubuntu:
  Fix Released
Status in gsequencer package in Ubuntu:
  Fix Released
Status in gsl package in Ubuntu:
  New
Status in haskell-devscripts package in Ubuntu:
  Fix Released
Status in jose package in Ubuntu:
  New
Status in ksmtuned package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libtpms package in Ubuntu:
  New
Status in mosh package in Ubuntu:
  Fix Released
Status in mpich package in Ubuntu:
  New
Status in mwrap package in Ubuntu:
  Fix Released
Status in proftpd package in Ubuntu:
  New
Status in proftpd-dfsg package in Ubuntu:
  Fix Released
Status in serf package in Ubuntu:
  Fix Released
Status in setserial package in Ubuntu:
  New
Status in speech-dispatcher package in Ubuntu:
  New
Status in squid package in Ubuntu:
  Fix Released
Status in swtpm package in Ubuntu:
  Fix Released
Status in texinfo package in Ubuntu:
  Triaged
Status in tix package in Ubuntu:
  New

Bug description:
  The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
  (refined in 1.22.6ubuntu14) can cause this failure:

  ```
  gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
  ```

  This happens when the `-specs=/usr/share/dpkg/elf-package-
  metadata.specs` parameter is set but the needed environment variables
  are not set. Cases:

  1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
  packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
  rp-pppoe fail to build)

  2. autopkgtests

  3. debugging a crash of an application build with the -spec parameter

  4. People like to iteratively continue building the software in the
  build dir while hacking on the package and then have no environment
  variable set.

  This approach is too fragile. An alternative approach would be to specify the 
`--package-metadata` linker flag directly. The problem with that approach is 
that the curly brackets and quotation marks need to be escaped. Example 
failure: Building dpkg would add this parameter to the LDFLAGS:
  ```
  
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
  ```
  The following configure script call (non-relevant parameters deleted):
  ```
  $ gcc 
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
  /usr/bin/ld: cannot find {type:deb: No such file or directory
  /usr/bin/ld: cannot find os:ubuntu: No such file or directory
  /usr/bin/ld: cannot find name:dpkg: No such file or directory
  /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
  /usr/bin/ld: cannot find architecture:amd64}: No such file or directory
  ```

  Proposed solution: Add support for an `--escaped-package-metadata` parameter 
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
  ```
  
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+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 2074335] [NEW] Xorg freeze

2024-07-30 Thread Toygar Par

Public bug reported:

Last night, early in the morning(July 29 around 00:20, the wholesystem
crashed and I had to push the restart button on the desktop.  I had just
finished building a kernel for gentoo  in VM workstation pro.  I just
tried to close google chrome on my main ubuntu desktop, computer froze.
This morning at cli, typed journalctl -p error, and it's saying bunch of
stuff about cpu being stuck.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.183.01  Sun May 12 
19:39:15 UTC 2024
 GCC version:
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 29 08:48:26 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: This is the first time
GraphicsCard:
 NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GA106 [GeForce RTX 3060 
Lite Hash Rate] [1462:397b]
 Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c4) (prog-if 
00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Raphael [1462:7d75]
InstallationDate: Installed on 2024-07-20 (9 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Micro-Star International Co., Ltd. MS-7D75
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=7a79c852-07bb-478d-9cac-84c35c500341 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2024
dmi.bios.release: 5.35
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.J4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAG B650 TOMAHAWK WIFI (MS-7D75)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.J4:bd07/17/2024:br5.35:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D75:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB650TOMAHAWKWIFI(MS-7D75):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7D75
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.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:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze noble ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Last night, early in the morning(July 29 around 00:20, the wholesystem
  crashed and I had to push the restart button on the desktop.  I had
  just finished building a kernel for gentoo  in VM workstation pro.  I
  just tried to close google chrome on my main ubuntu desktop, computer
  froze. This morning at cli, typed journalctl -p error, and it's saying
  bunch of stuff about cpu being stuck.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules:

[Touch-packages] [Bug 2070476] Re: My Sony WH-1000XM4 headset is no more seen as bluetooth device after upgrade from 22.04 to 24.04

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

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

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

Title:
  My Sony WH-1000XM4 headset is no more seen as bluetooth device  after
  upgrade from 22.04 to 24.04

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Dear Ubuntu developpers,

  I used my headset through Bluetooth without any trouble under Ubuntu 22.04.
  Now that I have upgraded (erased everything and reinstalled from scratch) to 
24.04, the bluetooth soft does not see my headset, even when it is visible by 
other devices. 
  I have checked with bluetoothctl and its MAC @ never appears.
  I've also checked the bluetooth connection with my phone, without any issue.

  A manual pairing with it MAC@  (88:c9:e8 ...) says the device is not
  available.

  I managed to pair another headset.

  Any idea ?

  Thanks for your interest and your work.

  Best

  Arnaud

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

  bluez:
Installed : 5.72-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2070476/+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 2074302] [NEW] Asus Laptop (R558U) does not suspend after upgrade to 24.04

2024-07-30 Thread Leonard Peris

Public bug reported:

I was previously running Ubuntu 23.10 on my laptop. I performed a `dist-
upgrade` about a week back. Since the upgrade to 24.04 my laptop does
not suspend - either by pressing the power-key (previously working on
23.10) or by using the GNOME system power menu.

My laptop has integrated Intel graphics as well as NVIDIA GeForce 930MX
(GM108M), but i haven't installed proprietary video drivers. It is
currently using xserver-x-org-video-nouveau as the video driver. My
system reports as running a wayland session, but I find the above X.Org
detail confusing.

There is currently one inhibitor running `gsd-media-keys`.

I filed a bug under systemd as ubuntu-bug would not let me file a bug
without a package name. If this is incorrect, please change the package-
name as appropriate.

I would like to restore previous functionality - system suspend on
command.

I'd be happy to provide additional logs and to troubleshoot any possible
fixes.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 255.4-1ubuntu8.2
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 28 19:11:12 2024
InstallationDate: Installed on 2019-04-20 (1926 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: ASUSTeK COMPUTER INC. X556UR
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to noble on 2024-07-20 (8 days ago)
dmi.bios.date: 10/24/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X556UR.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X556UR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UR.309:bd10/24/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnX556UR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: X
dmi.product.name: X556UR
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

** Description changed:

  I was previously running Ubuntu 23.10 on my laptop. I performed a `dist-
  upgrade` about a week back. Since the upgrade to 24.04 my laptop does
  not suspend - either by pressing the power-key (previously working on
  23.10) or by using the GNOME system power menu.
  
  My laptop has integrated Intel graphics as well as NVIDIA GeForce 930MX
  (GM108M), but i haven't installed proprietary video drivers. It is
  currently using xserver-x-org-video-nouveau as the video driver. My
  system reports as running a wayland session, but I find the above X.Org
  detail confusing.
  
  There is currently one inhibitor running `gsd-media-keys`.
  
  I filed a bug under systemd as ubuntu-bug would not let me file a bug
  without a package name. If this is incorrect, please change the package-
  name as appropriate.
  
- I would like to retain previous functionality - system suspend on
+ I would like to restore previous functionality - system suspend on
  command.
  
  I'd be happy to provide additional logs and to troubleshoot any possible
  fixes.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 19:11:12 2024
  InstallationDate: Installed on 2019-04-20 (1926 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. X556UR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to noble on 2024-07-20 (8 days ago)
  dmi.bios.date: 10/24/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UR.309:bd10/24/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnX556UR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X556UR

[Touch-packages] [Bug 2074300] [NEW] Unable to upgrade Network Manager (SKIP NetworkManager not ready ...) on Ubuntu 22->24 upgrade

2024-07-30 Thread Odin Hørthe Omdal

Public bug reported:

root@kaa:/var/log/dist-upgrade# dpkg --configure -a
Setting up network-manager (1.46.0-1ubuntu2) ...
SKIP: NetworkManager is not ready ...
SKIP: NetworkManager is not ready ...
SKIP: NetworkManager is not ready ...
SKIP: NetworkManager is not ready ...
SKIP: NetworkManager is not ready ...
SKIP: NetworkManager is not ready ...
SKIP: NetworkManager is not ready ...
SKIP: NetworkManager is not ready ...


I tried stopping it and retried a few times. It's not doing the stopping or 
whatever it needs right. It should probably force whatever it wants to do when 
it's clear (after a minute or so) that whatever it's waiing for ain't going to 
happen.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: network-manager 1.46.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-38.38~22.04.1-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 28 16:08:05 2024
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-08-28 (2161 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 192.168.10.1 dev wlp60s0 proto dhcp src 192.168.10.222 metric 600 
linkdown 
 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
 192.168.10.0/24 dev wlp60s0 proto kernel scope link src 192.168.10.222 metric 
600 linkdown
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: network-manager
UpgradeStatus: Upgraded to noble on 2024-07-28 (0 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-04-23T13:30:10
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  WIFI 
WWAN-HW  WWAN
 running  1.46.0   connected  starting  full  enabled enabled  
enabled  missing  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Unable to upgrade Network Manager (SKIP NetworkManager not ready ...)
  on Ubuntu 22->24 upgrade

Status in network-manager package in Ubuntu:
  New

Bug description:
  root@kaa:/var/log/dist-upgrade# dpkg --configure -a
  Setting up network-manager (1.46.0-1ubuntu2) ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...

  
  I tried stopping it and retried a few times. It's not doing the stopping or 
whatever it needs right. It should probably force whatever it wants to do when 
it's clear (after a minute or so) that whatever it's waiing for ain't going to 
happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-38.38~22.04.1-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 16:08:05 2024
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-28 (2161 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.10.1 dev wlp60s0 proto dhcp src 192.168.10.222 metric 
600 linkdown 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   192.168.10.0/24 dev wlp60s0 proto kernel scope link src 192.168.10.222 
metric 600 linkdown
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-07-28 (0 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-04-23T13:30:10
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.46.0   connected  starting  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2074300/+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 2068940] Re: bad environment variable in padsp script

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

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

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

Title:
  bad environment variable in padsp script

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  On jammy 22.04 LTS.  I need padsp for an old program that writes to /dev/dsp. 
 The /usr/bin/padsp script from pulseaudio-utils 1:15.99.1+dfsg1-1ubuntu2.2 has 
the lines
  if [ x"$LD_PRELOAD" = x ] ; then
 LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so"
  else
 LD_PRELOAD="$LD_PRELOAD /usr/\\$$LIB/pulseaudio/libpulsedsp.so"
  fi
  I don't know where it is supposed to be picking up a value for $LIB, but it 
isn't working.  I get an error message: ld.so: object 
'/usr/\788488LIB/pulseaudio/libpulsedsp.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
  The libpulsedsp 1:15.99.1+dfsg1-1ubuntu2.2  package put libpulsedsp.so in 
/usr/lib/x86_64-linux-gnu/pulseaudio and if I edit that into the script in 
place of the call to $LIB, everything works.  So I think it is just a problem 
with the use of LIB in the script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2068940/+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 2071815] Re: Investigate ASLR re-randomization being disabled for children

This bug was fixed in the package openssh - 1:9.6p1-3ubuntu18

---
openssh (1:9.6p1-3ubuntu18) oracular; urgency=medium

  * d/p/systemd-socket-activation.patch: don't clear rexec_flag
It was pointed out that this is generally not a good idea, so undo this
change. In order to do this, we need to restore the logic to ensure
that when we have been re-executed, we ignore $LISTEN_PID because it
won't match, but we still need to know $LISTEN_FDS. And, do not set
FD_CLOEXEC on the fds passed from systemd, because we want them to
survive the re-execution. (LP: #2071815)
  * d/p/systemd-socket-activation.patch: refresh patch

 -- Nick Rosbrook   Fri, 26 Jul 2024 11:54:36 -0400

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

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

Title:
  Investigate ASLR re-randomization being disabled for children

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  The systemd-socket-activation.patch patch has an Ubuntu delta to fix
  bug 2011458, but this results in ASLR not being re-randomized for
  children because the patch delta does "rexec_flag = 0;".

  This was discovered as part of the CVE-2024-6387 discovery by Qualys,
  and is mentioned in the disclosure itself:

  Side note: we discovered that Ubuntu 24.04 does not re-randomize the
  ASLR of its sshd children (it is randomized only once, at boot time); we
  tracked this down to the patch below, which turns off sshd's rexec_flag.
  This is generally a bad idea, but in the particular case of this signal
  handler race condition, it prevents sshd from being exploitable: the
  syslog() inside the SIGALRM handler does not call any of the malloc
  functions, because it is never the very first call to syslog().

  This is also mentioned in the release notes of OpenSSH 9.8:

  Exploitation on non-glibc systems is conceivable but has not been
  examined. Systems that lack ASLR or users of downstream Linux
  distributions that have modified OpenSSH to disable per-connection
  ASLR re-randomisation (yes - this is a thing, no - we don't
  understand why) may potentially have an easier path to exploitation.

  We should investigate why that was needed, and if an alternative way
  of fixing the original bug can be done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2071815/+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 2074280] [NEW] The progress bar of nautilus dock icon doesn't work.

2024-07-30 Thread Larry Wei

Public bug reported:

The progress bar of nautilus dock icon doesn't work when 
compression/decompression is handling.  
  

# System Details Report
---

## Report details
- **Date generated:**  2024-07-28 09:26:28

## Hardware Information:
- **Hardware Model:**  GITSTAR GDC-1461
- **Memory:**  32.0 GiB
- **Processor:**   ZHAOXIN KaiXian 
KX-6000G/4@3.0GHz × 4
- **Graphics:**Software Rendering
- **Disk Capacity:**   512.1 GB

## Software Information:
- **Firmware Version:**03.04
- **OS Name:** Ubuntu 24.04 LTS
- **OS Build:**(null)
- **OS Type:** 64-bit
- **GNOME Version:**   46
- **Windowing System:**Wayland
- **Kernel Version:**  Linux 6.8.0-39-generic

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

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

Title:
   The progress bar of nautilus dock icon doesn't work.

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The progress bar of nautilus dock icon doesn't work when 
compression/decompression is handling.  


  # System Details Report
  ---

  ## Report details
  - **Date generated:**  2024-07-28 09:26:28

  ## Hardware Information:
  - **Hardware Model:**  GITSTAR GDC-1461
  - **Memory:**  32.0 GiB
  - **Processor:**   ZHAOXIN KaiXian 
KX-6000G/4@3.0GHz × 4
  - **Graphics:**Software Rendering
  - **Disk Capacity:**   512.1 GB

  ## Software Information:
  - **Firmware Version:**03.04
  - **OS Name:** Ubuntu 24.04 LTS
  - **OS Build:**(null)
  - **OS Type:** 64-bit
  - **GNOME Version:**   46
  - **Windowing System:**Wayland
  - **Kernel Version:**  Linux 6.8.0-39-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2074280/+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 2074280] Re: The progress bar of nautilus dock icon doesn't work.

2024-07-30 Thread Larry Wei

** Attachment added: "Screenshot from 2024-07-27 13-11-15.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2074280/+attachment/5800791/+files/Screenshot%20from%202024-07-27%2013-11-15.png

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

Title:
   The progress bar of nautilus dock icon doesn't work.

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The progress bar of nautilus dock icon doesn't work when 
compression/decompression is handling.  


  # System Details Report
  ---

  ## Report details
  - **Date generated:**  2024-07-28 09:26:28

  ## Hardware Information:
  - **Hardware Model:**  GITSTAR GDC-1461
  - **Memory:**  32.0 GiB
  - **Processor:**   ZHAOXIN KaiXian 
KX-6000G/4@3.0GHz × 4
  - **Graphics:**Software Rendering
  - **Disk Capacity:**   512.1 GB

  ## Software Information:
  - **Firmware Version:**03.04
  - **OS Name:** Ubuntu 24.04 LTS
  - **OS Build:**(null)
  - **OS Type:** 64-bit
  - **GNOME Version:**   46
  - **Windowing System:**Wayland
  - **Kernel Version:**  Linux 6.8.0-39-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2074280/+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 2074278] Re: smash the window

2024-07-30 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  smash the window

Status in xorg package in Ubuntu:
  New

Bug description:
  When I open the shutter and bottom menus and every drop down menus. Instead 
of opening the menu correctly. The menu turns on and off at a very high speed 
and causes the window to crash. 
  Laptop model: Dell Latitude E6410

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 02:17:21 2024
  DistUpgraded: 2024-07-28 01:39:08,562 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GT218M [NVS 3100M] [1028:040a]
  InstallationDate: Installed on 2024-07-27 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: Dell Inc. Latitude E6410
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=8393ad29-8de9-4017-a55c-4b34074194be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-07-27 (0 days ago)
  dmi.bios.date: 05/12/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 07XJP9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd05/12/2017:br4.6:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn07XJP9:rvrA01:cvnDellInc.:ct9:cvr:sku:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/xorg/+bug/2074278/+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 2074278] [NEW] smash the window

You have been subscribed to a public bug:

When I open the shutter and bottom menus and every drop down menus. Instead of 
opening the menu correctly. The menu turns on and off at a very high speed and 
causes the window to crash. 
Laptop model: Dell Latitude E6410

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 28 02:17:21 2024
DistUpgraded: 2024-07-28 01:39:08,562 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Dell GT218M [NVS 3100M] [1028:040a]
InstallationDate: Installed on 2024-07-27 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: Dell Inc. Latitude E6410
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=8393ad29-8de9-4017-a55c-4b34074194be ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-07-27 (0 days ago)
dmi.bios.date: 05/12/2017
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 07XJP9
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd05/12/2017:br4.6:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn07XJP9:rvrA01:cvnDellInc.:ct9:cvr:sku:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug corruption noble ubuntu wayland-session
-- 
smash the window
https://bugs.launchpad.net/bugs/2074278
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 2074272] [NEW] I have no sound at all in the ubuntu 24 lts

2024-07-30 Thread Ahmed Tarek Ashour

Public bug reported:

Cant hear any sound from my computer and pulseaudio crashes

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu10
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:ahmedtarek   2329 F pipewire
 /dev/snd/controlC0:  ahmedtarek   2334 F wireplumber
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 27 23:28:12 2024
InstallationDate: Installed on 2024-07-24 (3 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X3500PC_K3500PC
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: X3500PC.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X3500PC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX3500PC.302:bd08/08/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX3500PC_K3500PC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX3500PC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Vivobook
dmi.product.name: Vivobook_ASUSLaptop X3500PC_K3500PC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  I have no sound at all in the ubuntu 24 lts

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Cant hear any sound from my computer and pulseaudio crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu10
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:ahmedtarek   2329 F pipewire
   /dev/snd/controlC0:  ahmedtarek   2334 F wireplumber
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 23:28:12 2024
  InstallationDate: Installed on 2024-07-24 (3 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X3500PC_K3500PC
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X3500PC.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X3500PC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX3500PC.302:bd08/08/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX3500PC_K3500PC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX3500PC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Vivobook
  dmi.product.name: Vivobook_ASUSLaptop X3500PC_K3500PC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2074272/+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 2074265] [NEW] Crashing System

2024-07-30 Thread Marcelo Pires

Public bug reported:

When I use the system with Gnome, rendering errors appear, and
sometimes, almost always, the system crashes.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 27 12:43:00 2024
DistUpgraded: 2024-07-27 11:36:36,601 DEBUG running apport_crash()
DistroCodename: noble
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce G210] [10de:0a60] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GT218 [GeForce G210] [10de:]
InstallationDate: Installed on 2024-07-25 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-45-generic 
root=UUID=316df0de-ff13-457d-8ba7-42e616dabe56 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to noble on 2024-07-27 (0 days ago)
dmi.bios.date: 03/04/2017
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M LX/BR
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
mtime.conffile..etc.init.d.apport: 2024-04-23T08:30:10
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

** Attachment added: "Screencast from 2024-07-27 12-29-35.mp4"
   
https://bugs.launchpad.net/bugs/2074265/+attachment/5800719/+files/Screencast%20from%202024-07-27%2012-29-35.mp4

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

Title:
  Crashing System

Status in xorg package in Ubuntu:
  New

Bug description:
  When I use the system with Gnome, rendering errors appear, and
  sometimes, almost always, the system crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 12:43:00 2024
  DistUpgraded: 2024-07-27 11:36:36,601 DEBUG running apport_crash()
  DistroCodename: noble
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce G210] [10de:0a60] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GT218 [GeForce G210] [10de:]
  InstallationDate: Installed on 2024-07-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-45-generic 
root=UUID=316df0de-ff13-457d-8ba7-42e616dabe56 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to noble on 2024-07-27 (0 days ago)
  dmi.bios.date: 03/04/2017
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX/BR
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Touch-packages] [Bug 2074103] Re: package libgdk-pixbuf-2.0-0:i386 2.42.10+dfsg-3ubuntu3.1 failed to install/upgrade: paleidikliai vykdomi ciklu, palikta

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

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libgdk-pixbuf-2.0-0:i386 2.42.10+dfsg-3ubuntu3.1 failed to
  install/upgrade: paleidikliai vykdomi ciklu, palikta

Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  Update manager package doesn't run...

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: libgdk-pixbuf-2.0-0:i386 2.42.10+dfsg-3ubuntu3.1
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul 25 20:35:27 2024
  ErrorMessage: paleidikliai vykdomi ciklu, palikta
  InstallationDate: Installed on 2024-07-25 (0 days ago)
  InstallationMedia: Ubuntu Unity 22.04
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.6ubuntu6
   apt  2.7.14build2
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf-2.0-0:i386 2.42.10+dfsg-3ubuntu3.1 failed to 
install/upgrade: paleidikliai vykdomi ciklu, palikta
  UpgradeStatus: Upgraded to noble on 2024-07-25 (0 days ago)
  mtime.conffile..etc.init.d.apport: 2024-04-23T14:30:10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2074103/+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 2041831] Re: /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup

2024-07-30 Thread Konrad

I can also confirm #4. I could reproduce the bug in 23.04, 23.10 and
24.04.

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

Title:
  /usr/bin/update-
  
manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup

Status in pygobject package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:23.10.1, the problem page at 
https://errors.ubuntu.com/problem/dff72cd5c27c916b2d887a56311ba08ef15b0dff 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2041831/+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 1826271] Re: virt-manager does not save preferences

2024-07-30 Thread hanshenrik

I had the same problem on 24.04 but only when running on root.
installing dbux-x11 fixed it on root as well.

IMO dbus-x11 should be made a recommended dependency for virt-manager.

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

Title:
  virt-manager does not save preferences

Status in d-conf package in Ubuntu:
  Confirmed
Status in virt-manager package in Ubuntu:
  Incomplete

Bug description:
  running Ubuntu 18.04.2 LTS with KDE Plasma 5.12.7 (Qt 5.9.5)
  after a recent discover software update virt-manager no longer saves 
preferences. preferences were correctly saved previously (march 2019 and 
earlier)

  /usr/bin/virt-manager
  edit -> preferences -> polling
  select poll disk i/o
  select memory stats
  close window

  virt-manager displays cpu usage only.
  on restart preferences have not been saved

  also, when starting vm's the virtual machine terminal is too small.
  previously (march 2019 and earlier) the vm terminals would 'remember'
  the window-size that had been made.

  something must be 'broken'. can't find virt-manager preferences in any text
  file to determine if the file is written-to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1826271/+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 2060900] Re: gst-plugin-scanner crashed with SIGABRT in __assert_fail_base()

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

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gst-plugin-scanner crashed with SIGABRT in __assert_fail_base()

Status in gstreamer1.0 package in Ubuntu:
  Expired

Bug description:
  this give me error from some files

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: libgstreamer1.0-0 1.24.1-1build1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 11 11:07:09 2024
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  InstallationDate: Installed on 2024-04-04 (7 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/../../lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
 -l /usr/bin/rhythmbox
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SignalName: SIGABRT
  SourcePackage: gstreamer1.0
  StacktraceTop:
   __assert_fail_base (fmt=0x702a92dd01e8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x702a7b4e1c90 "subsampling == 
SUBSAMPLE_YUV420 || subsampling == SUBSAMPLE_YUV422H || subsampling == 
SUBSAMPLE_YUV422V || subsampling == SUBSAMPLE_RGBX", 
file=file@entry=0x702a7b4e44b6 "i965_drv_video.c", line=line@entry=4653, 
function=function@entry=0x702a7b511600 "i965_check_alloc_surface_bo") at 
./assert/assert.c:94
   __assert_fail (assertion=0x702a7b4e1c90 "subsampling == SUBSAMPLE_YUV420 || 
subsampling == SUBSAMPLE_YUV422H || subsampling == SUBSAMPLE_YUV422V || 
subsampling == SUBSAMPLE_RGBX", file=0x702a7b4e44b6 "i965_drv_video.c", 
line=4653, function=0x702a7b511600 "i965_check_alloc_surface_bo") at 
./assert/assert.c:103
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaCreateSurfaces () from /lib/x86_64-linux-gnu/libva.so.2
  Title: gst-plugin-scanner crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2060900/+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 2067219] Re: No working printers available after upgrading from 23.10 to 24.04

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

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

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

Title:
  No working printers available after upgrading from 23.10 to 24.04

Status in cups package in Ubuntu:
  Expired

Bug description:
  After upgrading from Ubuntu 23.10 to 24.04 all printers are non
  functional. They can be pinged, printing seems to work, but nothing
  gets printed.

  Trying to connect to cups by https://localhost:631 connects, displays
  the entry page, but non of the links given works. All give back: "Not
  found".

  Looks like cups is not installed in a useful way making it work as
  expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: cups-common 2.4.7-1.2ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun May 26 21:36:32 2024
  Dependencies:
   
  InstallationDate: Installed on 2021-05-31 (1091 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lpstat:
   device for HL-1430-series: usb://Brother/HL-1430%20series
   device for Kyocera_FS-1300D_FS-1300D: dnssd://mir._pdl-datastream._tcp.local/
  MachineType: LENOVO 20BWS33U00
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   Kyocera_FS-1300D_FS-1300D: Kyocera FS-1200
   HL-1430-series: Brother HL-1430 Foomatic/hl1250 (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_jou8br@/vmlinuz-6.8.0-31-generic 
root=ZFS=rpool/ROOT/ubuntu_jou8br ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.release: 1.37
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS33U00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:br1.37:efr1.4:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS33U00
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2067219/+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 2074059] Re: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1

2024-07-30 Thread Jeremy Bícha

Rik, the Debian bug suggests that it might be fixed by rebuilding kwin.
Could you try that?

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

Title:
  libwayland: breaks plasma desktop start after last upgrade to version
  1.23.0-1

Status in wayland package in Ubuntu:
  New
Status in wayland package in Debian:
  Fix Released

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2074059/+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 2073787] Re: apport-retrace needs more than 1 GB

** Tags added: foundations-todo

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Benjamin Drung (bdrung)

** Also affects: apport
   Importance: Undecided
   Status: New

** Changed in: apport
Milestone: None => 2.30.0

** Changed in: apport
   Importance: Undecided => High

** Changed in: apport
   Status: New => Triaged

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

Title:
  apport-retrace needs more than 1 GB

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  The system tests test_retrace_system_sandbox and
  test_retrace_jammy_sandbox fail on arm64, ppc64el, s390x, because
  apport-retrace is killed by the OOM killer. Example:

  autopkgtest kernel: Out of memory: Killed process 3597 (apport-
  retrace) total-vm:1512420kB, anon-rss:1241460kB, file-rss:2592kB,
  shmem-rss:0kB, UID:0 pgtables:2554kB oom_score_adj:0

  Log: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-
  bdrung-apport/oracular/s390x/a/apport/20240722_145904_d3c2f@/log.gz

  apport-retrace should be able to retrace crashes without needing
  multiple gigabytes of memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2073787/+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 2074212] Re: libdmapsharing doesn't have frame pointers enabled