[Bug 1982335] Re: [24.10 FEAT] Valgrind: Support for new IBM Z Hardware (IBM z16)
Many thx Andreas for the quick validation! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1982335 Title: [24.10 FEAT] Valgrind: Support for new IBM Z Hardware (IBM z16) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072898] Re: tools-nrepl-clojure fail to build from source with Java 21
Usage of Thread.stop is removed in 1.2 version of the package. The package has following reverse build depends: Reverse-Build-Depends = * prismatic-schema-clojure (for libtools-nrepl-clojure) * rbac-client-clojure (for libtools-nrepl-clojure) The package has no reverse depends. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072898 Title: tools-nrepl-clojure fail to build from source with Java 21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tools-nrepl-clojure/+bug/2072898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072898] [NEW] tools-nrepl-clojure fail to build from source with Java 21
Public bug reported:
The package fails to build from source with default Java 21 due to
deprecation of Thread.stop().
The package updated override_dh_build target, and now runs a test that invokes
package's method that calls Thread.stop() causing a build timeout:
#'user/all-tests
(nil nil nil nil nil Testing with Clojure v1.11.2 on 21.0.4-ea
nil nil nil nil nil)
Testing clojure.tools.nrepl-test
Jul 12, 2024 4:00:32 PM clojure.tools.logging$eval797$fn__800 invoke
SEVERE: Unhandled REPL handler exception processing message {:id
e6e57230-8158-4de5-99ba-65ba6dfdb99e, :op interrupt, :session
49f718c0-b1ce-4629-a581-d050fd7bc399}
java.lang.UnsupportedOperationException
at java.base/java.lang.Thread.stop(Thread.java:1667)
at
clojure.tools.nrepl.middleware.interruptible_eval$interruptible_eval$fn__1397.invoke(interruptible_eval.clj:243)
at
clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1113.invoke(middleware.clj:22)
at
clojure.tools.nrepl.middleware.load_file$wrap_load_file$fn__1527.invoke(load_file.clj:79)
at
clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1113.invoke(middleware.clj:22)
at
clojure.tools.nrepl.middleware.session$add_stdin$fn__1483.invoke(session.clj:238)
at
clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1113.invoke(middleware.clj:22)
at
clojure.tools.nrepl.middleware.session$session$fn__1468.invoke(session.clj:192)
at
clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1113.invoke(middleware.clj:22)
at
clojure.tools.nrepl.middleware.pr_values$pr_values$fn__1312.invoke(pr_values.clj:22)
at
clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__1113.invoke(middleware.clj:22)
at clojure.tools.nrepl.server$handle_STAR_.invokeStatic(server.clj:19)
at clojure.tools.nrepl.server$handle_STAR_.invoke(server.clj:16)
at clojure.tools.nrepl.server$handle$fn__1542.invoke(server.clj:28)
at clojure.core$binding_conveyor_fn$fn__5823.invoke(core.clj:2047)
at clojure.lang.AFn.call(AFn.java:18)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
** Affects: tools-nrepl-clojure (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072898
Title:
tools-nrepl-clojure fail to build from source with Java 21
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tools-nrepl-clojure/+bug/2072898/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072885] Re: Lots of services of systemd 256 fail to start in nested LXD containers
*** This bug is a duplicate of bug 2046486 *** https://bugs.launchpad.net/bugs/2046486 ** This bug has been marked a duplicate of bug 2046486 units with credentials fail in LXD containers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072885 Title: Lots of services of systemd 256 fail to start in nested LXD containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2072885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046486] Re: units with credentials fail in LXD containers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046486 Title: units with credentials fail in LXD containers To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/2046486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070103] Re: package google-android-tools-installer 26.1.1+1710437545-3build2 failed to install/upgrade: installed google-android-tools-installer package post-installation script subprocess retur
Normally this directory "/usr/lib/android-sdk/tools" should not exist at the time of installation. Did you create it manually at some time in the past, or do you also install SDK components into "/usr/lib/android-sdk" by using another tool like sdkmanager (the one of google for example)? In that case, maybe the "tools" components was installed by one of these. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070103 Title: package google-android-tools-installer 26.1.1+1710437545-3build2 failed to install/upgrade: installed google-android-tools-installer package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-android-installers/+bug/2070103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067862] Re: Removing legacy virtio-pci devices causes kernel panic
Hi Matthew Ruffell Thank you for your long-time support on this case. I have installed the linux-image-6.8.0-40-generic package using the command provided by you, and have verified the issue on the machine running Ubuntu 24 with kernel version (6.8.0-40-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 5 10:34:03 UTC 2024). The problem has been resolved with this kernel version. I have changed the tag 'verification-needed-noble-linux' to 'verification-done-noble-linux'. Please verify. Thanks again. Dong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2067862 Title: Removing legacy virtio-pci devices causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067862] Re: Removing legacy virtio-pci devices causes kernel panic
** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2067862 Title: Removing legacy virtio-pci devices causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072777] Re: OK and cancel both unclear do nothing for snap refresh notification
** Description changed: With notify-osd, the snap refreshment is done via a dialogue window notification, which says > Update available for firefox. > > Close the application to update now. It will update automatically in 13 days. and has OK and cancel buttons. Why is either button mapped in this dialogue if no action is associated with either? Or at least it is not clear from the message what either button would do. + + I experienced the same, just with a different message, after Firefox + were refreshed. I don't remember the exact wording but it was something + like + + > Firefox has been updated. + > + > It is now ready to launch. + + I clicked OK button expecting it to launch Firefox but it did not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072777 Title: OK and cancel both unclear do nothing for snap refresh notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/2072777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072885] Re: Lots of services of systemd 256 fail to start in nested LXD containers
Another few things: I tested the system package from here https://launchpad.net/~enr0n/+archive/ubuntu/systemd and it still has the same problem. Executing /usr/lib/systemd/systemd-networkd just like that resurrects the network. Commenting out certain things in /usr/lib/systemd/system/systemd-networkd.service make the network service work again - this is obviously not a solution, but I'm mentioning it in case it helps to debug the problem. The things you have to do with that file to "fix" the problem with -networkd are: 1. comment out the "ImportCredential=network.wireguard.*" line 2. comment out all the "Protect" lines 3. remove "systemd-networkd-persistent-storage.service" from "Wants=" 4. systemctl daemon-reload 5. systemctl restart systemd-networkd Also please note there's also many other services broken, network and journal are just the most 2 noticeable examples. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072885 Title: Lots of services of systemd 256 fail to start in nested LXD containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2072885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072885] [NEW] Lots of services of systemd 256 fail to start in nested LXD containers
Public bug reported: Hi, since 256 packages entered oracular-proposed I noticed they don't work in nested containers. This is for me very easy to reproduce: 1. As LXD server I'm jammy and using the LXD 5.0 version from the snap. 2. I create a vm or a container 3. if it's a container set the security.nesting option as true 4. inside the container or vm created in 2. create another container (with "lxc launch ubuntu-daily:oracular test" for example) 5. I get into the container and 'apt dist-upgrade' 6. the system is broken, please see below how The first noticeable thing is that right in the package configuration, we can see how the network and journal services failed: Setting up systemd (256-1ubuntu1) ... Installing new version of config file /etc/systemd/journald.conf ... Installing new version of config file /etc/systemd/logind.conf ... Installing new version of config file /etc/systemd/networkd.conf ... Installing new version of config file /etc/systemd/sleep.conf ... Installing new version of config file /etc/systemd/system.conf ... /usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock", ignoring. Created symlink '/run/systemd/system/tmp.mount' → '/dev/null'. /usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock", ignoring. Job for systemd-networkd.service failed because the control process exited with error code. See "systemctl status systemd-networkd.service" and "journalctl -xeu systemd-networkd.service" for details. Job for systemd-journald.service failed because the control process exited with error code. See "systemctl status systemd-journald.service" and "journalctl -xeu systemd-journald.service" for details. Then we can see the network service exited with 243/CREDENTIALS code: root@test:~# systemctl status systemd-networkd × systemd-networkd.service - Network Configuration Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)\ Active: failed (Result: exit-code) since Fri 2024-07-12 05:40:04 UTC; 5min ago Invocation: 00540f4884c44ec7a9f286942b8109a2 TriggeredBy: × systemd-networkd.socket Docs: man:systemd-networkd.service(8)\ man:org.freedesktop.network1(5)\ Process: 455 ExecStart=/usr/lib/systemd/systemd-networkd (code=exited, status=243/CREDENTIALS) Main PID: 455 (code=exited, status=243/CREDENTIALS) FD Store: 0 (limit: 512) Same for the journal service: root@test:~# systemctl status systemd-journald.service × 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 Fri 2024-07-12 05:31:39 UTC; 16min ago Invocation: 13bc72060e6c4d588869721d57fdba8a TriggeredBy: × systemd-journald-dev-log.socket × systemd-journald.socket ○ systemd-journald-audit.socket Docs: man:systemd-journald.service(8)\ man:journald.conf(5)\ Process: 181 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=243/CREDENTIALS) Main PID: 181 (code=exited, status=243/CREDENTIALS) FD Store: 0 (limit: 4224) And, well, obviously the network doesn't work, neither the journal. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072885 Title: Lots of services of systemd 256 fail to start in nested LXD containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2072885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072472] Re: mescc-tools FTBFS on ppc64el
After remembering about gdb's starti command to start debugging at the very first instruction, I think this is an upstream bug in the test and filed https://github.com/oriansj/mescc-tools/issues/47 and will upload a simple fix. ** Bug watch added: github.com/oriansj/mescc-tools/issues #47 https://github.com/oriansj/mescc-tools/issues/47 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072472 Title: mescc-tools FTBFS on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mescc-tools/+bug/2072472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069384] Re: puppetdb fails to build from source on noble
Thanks! I added the SRU template on bug 2072516. And also addressed your comment on the oracular MP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069384 Title: puppetdb fails to build from source on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2069384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072516] Re: autopkgtests fail on oracular & noble
** Description changed: - Currently, both tests under debian/test fail on oracular [1]. + [ Impact ] + * The puppetdb autopkgtests fail on noble after the FTBFS bug [1] is fixed. + + [ Test Plan ] + * Running autopkgtests on noble reveals the failure. + + [ Where problems could occur ] + Currently, both tests under debian/test fail on oracular [2]. autopkgtest [00:30:43]: summary - standalone FAIL stderr: warn: JDK 21.0.4-ea is neither tested nor supported. Please use JDK 17 - with-puppetserverFAIL non-zero exit status 1 + standalone FAIL stderr: warn: JDK 21.0.4-ea is neither tested nor supported. Please use JDK 17 + with-puppetserver FAIL non-zero exit status 1 - Whilst "standalone" fails because a warning appears on stderr, "with- - puppetserver" fails because the contents of a configuration file - couldn't be parsed. + Test "standalone" fails because of Java 21 usage warning appears on stderr. Test "with-puppetserver" is an integration + test of puppetdb and puppetserver. The latter has been updated to 8.4.1-1 on noble. Use of a custom format named PSON was + completely abandoned in puppetserver 8. Any use of PSON in puppetdb 7 on noble needs to be removed. - [1] https://paste.ubuntu.com/p/74h3nmKpXB/ + [ Other Info ] + PuppetDB 7.X is compatible with PuppetServer 8.X [3] + + [1] https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2069384 + [2] https://paste.ubuntu.com/p/74h3nmKpXB/ + [3] https://www.puppet.com/docs/puppetdb/7/overview.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072516 Title: autopkgtests fail on oracular & noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2072516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072811] Re: Apparmor: New update broke flatpak with `apparmor="DENIED"`
Thanks for the initial analysis John, please let me know if you need more info. As a side note, I use BTRFS - given it's CoW, not sure if it's related to the behaviour observed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072811 Title: Apparmor: New update broke flatpak with `apparmor="DENIED"` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2072811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072755] Re: Request backport of two i915/Intel Arc GPU patches
Hi nyanmisaka, I have built you a test kernel based on 6.8.0-38-generic with the following two commits added ontop: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd commit ee01b6a386eaf9984b58a2476e8f531149679da9 Author: Andi Shyti Date: Fri May 17 11:06:16 2024 +0200 Subject: drm/i915/gt: Fix CCS id's calculation for CCS mode setting Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee01b6a386eaf9984b58a2476e8f531149679da9 Can you try it out and let me know if it fixes your issue: Please note this package is NOT SUPPORTED by Canonical, and is for TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment. Instructions to Install (On a noble system): 1) sudo add-apt-repository ppa:mruffell/lp2072755-test 2) sudo apt update 3) sudo apt install linux-image-unsigned-6.8.0-38-generic linux-modules-6.8.0-38-generic linux-modules-extra-6.8.0-38-generic linux-headers-6.8.0-38-generic 4) sudo reboot 5) uname -rv 6.8.0-38-generic #38+TEST2072755v20240712b1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 12 If you are asked to abort removal of the running kernel, say no. Let me know if it works, and if it does, I will send "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" for SRU. Thanks, Matthew ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072755 Title: Request backport of two i915/Intel Arc GPU patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064873] Re: crash when trying an AppImage
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064873 Title: crash when trying an AppImage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065058] Re: package python3-inputremapper 2.0.1-1 failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/input_remapper-2.0.1.egg-info/PKG-INFO', which is also in package
[Expired for input-remapper (Ubuntu) because there has been no activity for 60 days.] ** Changed in: input-remapper (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065058 Title: package python3-inputremapper 2.0.1-1 failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist- packages/input_remapper-2.0.1.egg-info/PKG-INFO', which is also in package input-remapper 2.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/input-remapper/+bug/2065058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065315] Re: NOBLE 24.04 Persistence is not enabled
[Expired for casper (Ubuntu) because there has been no activity for 60 days.] ** Changed in: casper (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065315 Title: NOBLE 24.04 Persistence is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2065315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
Everything in powertop is Good after running `powertop --auto-tune` But: root@hp-spectre-x360:/home/kstoilov# cat /sys/kernel/debug/pmc_core/package_cstate_show Package C2 : 385537117 Package C3 : 70166720 Package C6 : 0 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 0 ** Attachment added: "Screenshot from 2024-07-12 07-17-41.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072679/+attachment/5796395/+files/Screenshot%20from%202024-07-12%2007-17-41.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072679 Title: Regression: unable to reach low idle states on Tiger Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1992327] Re: unrecognized option '--background'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: inadyn (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1992327 Title: unrecognized option '--background' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inadyn/+bug/1992327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054245] Re: metro-policy: FTBFS with default Java 21
** Changed in: metro-policy (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054245 Title: metro-policy: FTBFS with default Java 21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metro-policy/+bug/2054245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072724] Re: please remove: facet-analyser 0.0~git20221121142040.6be10b8+ds1-3 has conflicting build dependencies
** Summary changed: - facet-analyser 0.0~git20221121142040.6be10b8+ds1-3 has conflicting build dependencies + please remove: facet-analyser 0.0~git20221121142040.6be10b8+ds1-3 has conflicting build dependencies ** Description changed: facet-analyser build-depends on both python3-paraview and libinsighttoolkit5-dev - unfortunately, libinsighttoolkit5-dev recently added a dependency on libvtk9-dev + libinsighttoolkit5-dev recently has a dependency on libvtk9-dev which depends on python3-vtk9 which conflicts with python3-paraview. + + The package exists only in -proposed and has no reverse-dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072724 Title: please remove: facet-analyser 0.0~git20221121142040.6be10b8+ds1-3 has conflicting build dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facet-analyser/+bug/2072724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072723] Re: jupyter-ydoc dependency-wait on ypy
** Description changed: - jupyter-ydoc misses ypy build dependency[1]. - ypy package is not present in Ubuntu. - The package misses build dependencies in Debian[2] that do not exist. + jupyter-ydoc misses ypy build dependency[1]. + ypy package is not present in Ubuntu. + The package has build dependencies in Debian[2] that do not exist. + + The package only exists in -proposed. [1] https://launchpad.net/ubuntu/+source/jupyter-ydoc/1.0.2-2/+build/28151934 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071899 ** Summary changed: - jupyter-ydoc dependency-wait on ypy + please remove jupyter-ydoc due to dependency-wait on ypy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072723 Title: please remove jupyter-ydoc due to dependency-wait on ypy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jupyter-ydoc/+bug/2072723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069200] Re: RM: gitaly from Oracular; mistakenly sync'ed from Debian
** Summary changed: - RM: gitably from Oracular; mistakenly sync'ed from Debian + RM: gitaly from Oracular; mistakenly sync'ed from Debian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069200 Title: RM: gitaly from Oracular; mistakenly sync'ed from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitaly/+bug/2069200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072709] Re: tools-namespace-clojure proposed migration vs fressian
synced from Debian ** Changed in: tools-namespace-clojure (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072709 Title: tools-namespace-clojure proposed migration vs fressian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tools-namespace-clojure/+bug/2072709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069231] Re: [MTL] ACPI: PM: s2idle: Backport Linux ACPI s2idle patches to fix suspend/resume issue
Tested on 6.8.40-generic from noble-proposed. System can suspend properly now. ** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069231 Title: [MTL] ACPI: PM: s2idle: Backport Linux ACPI s2idle patches to fix suspend/resume issue To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2069231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064492] Re: failed to execvp: /usr/lib/aarch64-linux-gnu/qt5/libexec/QtWebEngineProcess
This bug was fixed in the package digikam - 4:8.3.0-2ubuntu3 --- digikam (4:8.3.0-2ubuntu3) oracular; urgency=medium * Properly address the apparmor profile issue by adding multiple lines for the different architectures we want to support until @multiarch is supported. This closes (LP: #2064492) -- Scarlett Moore Thu, 11 Jul 2024 04:22:02 -0700 ** Changed in: digikam (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064492 Title: failed to execvp: /usr/lib/aarch64-linux- gnu/qt5/libexec/QtWebEngineProcess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2064492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024258] Re: Performance degradation archiving DB with large numbers of FK related records
Noble 3:29.0.1-0ubuntu1.3 already contains the patch, so no changes are needed. ** Changed in: nova (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024258 Title: Performance degradation archiving DB with large numbers of FK related records To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2024258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072806] Re: proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-dials 1.2.0-2
The error is caused by the usage of JunitReporter:
junit = JunitReporter$new(file = "test-results.xml")
test_check("dials", reporter = junit)
Results in
Error in UseMethod("xml_add_child") :
no applicable method for 'xml_add_child' applied to an object of class "NULL"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072806
Title:
proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-dials 1.2.0-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/r-cran-dials/+bug/2072806/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072858] [NEW] Fix L2CAP/LE/CPU/BI-02-C bluetooth certification failure
Public bug reported: SRU Jusitification for Kernel [Impact] Noble failed the L2CAP/LE/CPU/BI-02-C test in the Porfile Tuning Suite (PTS), which Jammy could pass. This is due to new behavior introduced in e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). The kernel only accept Connection Parameter Update Requests whose incoming conn_max_interval are lower than the current conn_max_interval, and adjust the newer conn_max_interval to that received max value. However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the linux-next fixed this by accepting connection parameter unconditionally. The relavent test procedure is also on the mailing list[2]. [1] https://github.com/bluez/bluez/issues/847 [2] https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326 [Fix] Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the linux-next. [1] https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/ [Test Case] 1. Install the kernel with the backported patch 2. Run the following test case in the PTS: L2CAP/LE/CPU/BI-02-C GAP/CONN/CPUP/BV-05-C [Where problems could occur] This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes. [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Leo Lin (0xff07) Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Leo Lin (0xff07) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072858 Title: Fix L2CAP/LE/CPU/BI-02-C bluetooth certification failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072819] Re: package grub-efi-amd64-signed 1.202+2.12-1ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072819 Title: package grub-efi-amd64-signed 1.202+2.12-1ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/2072819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072819] [NEW] package grub-efi-amd64-signed 1.202+2.12-1ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status
Public bug reported: I was doing a do-release-update -d to 24.04 from 22.04. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: grub-efi-amd64-signed 1.202+2.12-1ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13 Uname: Linux 6.5.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 11 21:04:18 2024 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-25 (230 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) 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: grub2-signed Title: package grub-efi-amd64-signed 1.202+2.12-1ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-07-12 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-23T06:30:10 ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072819 Title: package grub-efi-amd64-signed 1.202+2.12-1ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/2072819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
Hi @Kostadin Stoilov, Could you please run the `powertop --auto-tune` to see if the cpu reaches the C10 state? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072679 Title: Regression: unable to reach low idle states on Tiger Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072673] Re: [needs-packaging] oxipng
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072673 Title: [needs-packaging] oxipng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
** Changed in: linux (Ubuntu) Assignee: (unassigned) => En-Wei Wu (rickywu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072679 Title: Regression: unable to reach low idle states on Tiger Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072807] Re: proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-dplyr/1.1.4-1
** Bug watch added: Debian Bug tracker #1072630 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072630 ** Also affects: r-cran-dplyr (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072630 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072807 Title: proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-dplyr/1.1.4-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/r-cran-dplyr/+bug/2072807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072806] Re: proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-dials 1.2.0-2
** Bug watch added: Debian Bug tracker #1072629 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072629 ** Also affects: r-cran-dials (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072629 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072806 Title: proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-dials 1.2.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/r-cran-dials/+bug/2072806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067862] Re: Removing legacy virtio-pci devices causes kernel panic
Hi Dong, The Kernel team has built the new kernel with the fix. Would be able to help test it and verify that it fixes the issue? Instructions to Install (On a noble system): 1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed main universe EOF 2) sudo apt update 3) sudo apt install linux-image-6.8.0-40-generic linux-modules-6.8.0-40-generic linux-modules-extra-6.8.0-40-generic linux-headers-6.8.0-40-generic 4) sudo reboot 5) uname -rv 6.8.0-40-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 5 10:34:03 UTC 2024 Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2067862 Title: Removing legacy virtio-pci devices causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2017939] Re: Firefox fails to start
Thanks Amin, I will give it a try on the next Ubuntu release to see how it goes. Makes sense closing the ticket then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2017939 Title: Firefox fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2017939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072472] Re: mescc-tools FTBFS on ppc64el
same issue with 1.4 version of the package. The elf stub provided in elf_headers/elf64-PPC64LE.hex2 does not point to the entrypoint of hello.hex. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072472 Title: mescc-tools FTBFS on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mescc-tools/+bug/2072472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072787] Re: Screen flickering
Thanks for the bug report. Please try adding kernel parameter: i915.enable_psr=0 and tell us if that solves the problem. If not then please take a photo of the problem and attach it here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072787 Title: Screen flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072788] Re: Screen flickering
*** This bug is a duplicate of bug 2072787 *** https://bugs.launchpad.net/bugs/2072787 ** This bug has been marked a duplicate of bug 2072787 Screen flickering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072788 Title: Screen flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2072788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071715] Re: LAG with CT causes DPU Kernel Panic
This bug is awaiting verification that the linux- bluefield/5.15.0-1047.49 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-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071715 Title: LAG with CT causes DPU Kernel Panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2071715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072752] Re: App switching not affecting ubuntu-dock
Sounds like it's just not listening for gsettings changes, which is why restarting the extension works. I imagine locking the screen and unlocking would also work? See also bug 2004554. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072752 Title: App switching not affecting ubuntu-dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2072752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072761] Re: Stuck keys while shifting virtual desk
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072761 Title: Stuck keys while shifting virtual desk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2072761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072795] Re: xilinx-runtime ftbfs due to the missing includes
This bug was fixed in the package xilinx-runtime - 2.8.743-0ubuntu11 --- xilinx-runtime (2.8.743-0ubuntu11) oracular; urgency=medium * d/p/include_csdtdint.patch: apply upstream patch to fix ftbfs (LP: #2072795). -- Vladimir Petko Thu, 11 Jul 2024 18:40:42 +1200 ** Changed in: xilinx-runtime (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072795 Title: xilinx-runtime ftbfs due to the missing includes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xilinx-runtime/+bug/2072795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
Sure. I'm going to try to reproduce it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072679 Title: Regression: unable to reach low idle states on Tiger Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072774] Re: Crash lock screen
Hi Cong, Could you upload logs after the issue is reproduced? ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072774 Title: Crash lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914853] Re: regression-update: Unexpected Results 'iw reg set US'
** Changed in: wireless-regdb (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914853 Title: regression-update: Unexpected Results 'iw reg set US' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1914853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072815] [NEW] gvfsd-smb keeps running out of file descriptors fast
Public bug reported: After a couple of days of uptime, gvfsd-smb always runs out of file descriptors for me. Symptoms: * nautilus will throw a "too many open files" error when trying to access a Samba share (even if already mounted). * Saving files, e.g. LibreOffice, to a Samba share will fail. Unfortunately, this also applies to files that are already open. Have to save a copy somewhere else, nothing doing. For every open file, every time this happens. * Same for opening files from Samba shares, obviously. * GVFS behaviour in general becomes erratic. * Log spam that isn't caught by any rate limiting mechanisms. Think a /var/log hundreds of GB in size. Until / is full. That was fun. Things crashing and burning aside, poor NVMe ... Workaround: Periodically killall gvfsd-smb. This is a regular desktop, I mostly do office stuff, nothing that should tax this subsystem at all. I might have 10 files on a Samba share open concurrently sometimes, but the last couple of days it was more like 2 or 3. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs-backends 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-41.41.1~22.04.1-lowlatency 6.5.13 Uname: Linux 6.5.0-41-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 12 02:52:30 2024 InstallationDate: Installed on 2023-08-02 (344 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072815 Title: gvfsd-smb keeps running out of file descriptors fast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2072815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072811] Re: Apparmor: New update broke flatpak with `apparmor="DENIED"`
There 3 profiles involved here (probably should be 4), with a call dependency chain of flatpak -> bwrap -> bwrap_unpriv the flatpak profile does not show up in the logs but does end up launching bwrap. The comm is being set by flatpak, and can not be considered reliable for which executable is running for a given entry. The bwrap profile will be recorded for while bwrap code is running, and bwrap_unpriv AND bwrap stacked for the actual keepassxc application. There are 2 distinct class of failures here 1. Deleted files being re-validated. These have the info="Failed name lookup - deleted dentry". Basically fd delegation is not allowed to by- pass mediation. The files are no longer part of the namespace, and were never validated for access under the current confinement. 2. files that are in the namespace that the application doesn't have permissions to access. breaking this down by profiles bwrap: l /home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211 -> /**, # case 1. target is actually unknown at this point, but likely the same as the following l /home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini -> /home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211, #case 2 unpriv_bwrap: l /home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211 -> /**, # target again is unknown but like the same as the following l /home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini -> /home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211, # case 2 that bwrap and bwrap_unpriv are attempting to do the same thing, and each once with a deleted file then again with one that exists is extremely interesting. I need to dig into this a little more, to figure out exactly what is going on. The 2nd entry at first pass should be allowed by the profile, unless it is related to the same syscall that is causing the deleted entry denial, and is do to stacking denying the deleted dentry. If that is the case the question becomes how does the dentry stop being deleted during the single syscall. Like I said further investigation is needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072811 Title: Apparmor: New update broke flatpak with `apparmor="DENIED"` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2072811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072793] Re: [BPO] obs-studio/30.1.2+dfsg-1build1 from oracular
** Changed in: obs-studio (Ubuntu Oracular) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072793 Title: [BPO] obs-studio/30.1.2+dfsg-1build1 from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/2072793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069649] Re: lshw hangs running forever at Network Interfaces CLASS
Also on 24.04, lshw version is also the same.
Here's the tail of "sudo strace lshw" (yes strace freezes and doesn't
finish printing the line):
readlink("/sys/class/net", 0x7ffd187682a0, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/class/net/dev", 0x7ffd187682a0, 1023) = -1 ENOENT (No such file
or directory)
access("/sys/class/net//dev/vmnet1/device", F_OK) = -1 ENOENT (No such file or
directory)
readlink("/sys", 0x7ffd18768330, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/class", 0x7ffd18768330, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/class/net", 0x7ffd18768330, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/class/net/dev", 0x7ffd18768330, 1023) = -1 ENOENT (No such file
or directory)
openat(AT_FDCWD, "/sys/class/net//dev/vmnet1/modalias", O_RDONLY) = -1 ENOENT
(No such file or directory)
socket(AF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
ioctl(4, SIOCGIFADDR, {ifr_name="/dev/vmnet1"
vmnet1 is an interface for VMware Workstation Pro 17.5.2 with modified
kernel modules from https://github.com/mkubecek/vmware-host-
modules/tree/workstation-17.5.1 that work with newer kernels.
I'm curious if Carlos is also using Workstation pro with those kernel
modules.
Curious where strace stalls for Carlos: sudo strace lshw 2>&1 | tee -a
/tmp/out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069649
Title:
lshw hangs running forever at Network Interfaces CLASS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/2069649/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072813] [NEW] Please merge 2.40.2-1 into oracular
Public bug reported: tracking bug ** Affects: util-linux (Ubuntu) Importance: Undecided Assignee: Chris Peterson (cpete) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072813 Title: Please merge 2.40.2-1 into oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2072813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072810] [NEW] proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-rsqlite/2.3.7-1
Public bug reported:
The autopkgtest fails with the following error[1]
134s autopkgtest [10:24:59]: test run-unit-test: [---
134s
134s R version 4.4.1 (2024-06-14) -- "Race for Your Life"
134s Copyright (C) 2024 The R Foundation for Statistical Computing
134s Platform: x86_64-pc-linux-gnu
134s
134s R is free software and comes with ABSOLUTELY NO WARRANTY.
134s You are welcome to redistribute it under certain conditions.
134s Type 'license()' or 'licence()' for distribution details.
134s
134s R is a collaborative project with many contributors.
134s Type 'contributors()' for more information and
134s 'citation()' on how to cite R or R packages in publications.
134s
134s Type 'demo()' for some demos, 'help()' for on-line help, or
134s 'help.start()' for an HTML browser interface to help.
134s Type 'q()' to quit R.
134s
134s > # This file is part of the standard setup for testthat.
134s > # It is recommended that you do not modify it.
134s > #
134s > # Where should you do additional test configuration?
134s > # Learn more about the roles of various files in:
134s > # * https://r-pkgs.org/tests.html
134s > # * https://testthat.r-lib.org/reference/test_package.html#special-files
134s >
134s > library(testthat)
134s > library(RSQLite)
135s >
135s > test_check("RSQLite")
135s Reason: On CRAN
145s [ FAIL 1 | WARN 842 | SKIP 9 | PASS 684 ]
145s
145s ══ Skipped tests (9)
═══
146s • .Platform$OS.type == "windows" is not TRUE (2): 'test-encoding.R:37:3',
146s 'test-encoding.R:134:3'
146s • astyle not found (1): 'test-astyle.R:2:3'
146s • NYI (1): 'test-affinity.R:110:3'
146s • On Appveyor (2): 'test-blob.R:3:3', 'test-blob.R:21:3'
146s • On CRAN (3): 'test-dbConnect.R:150:3', 'test-dbConnect.R:211:3',
146s 'test-DBItest.R:2:1'
146s
146s ══ Failed tests
146s ── Failure ('test-affinity.R:98:3'): affinity checks for dbFetch()
─
146s `expect_equal(class(dbFetch(rs, 1)$a), real_type)` threw an unexpected
warning.
146s Message: Changing language has no effect when envvar LC_ALL='C.UTF-8'
146s Class: simpleWarning/warning/condition
146s Backtrace:
146s ▆
146s 1. ├─... %>% expect_warning("coercing") at test-affinity.R:98:3
146s 2. ├─testthat::expect_warning(., "coercing")
146s 3. │ └─testthat:::expect_condition_matching(...)
146s 4. │ └─testthat:::quasi_capture(...)
146s 5. │ ├─testthat (local) .capture(...)
146s 6. │ │ └─base::withCallingHandlers(...)
146s 7. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
146s 8. ├─testthat::expect_warning(., "coercing")
146s 9. │ └─testthat:::expect_condition_matching(...)
146s 10. │ └─testthat:::quasi_capture(...)
146s 11. │ ├─testthat (local) .capture(...)
146s 12. │ │ └─base::withCallingHandlers(...)
146s 13. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
146s 14. ├─testthat::expect_warning(., "coercing")
146s 15. │ └─testthat:::expect_condition_matching(...)
146s 16. │ └─testthat:::quasi_capture(...)
146s 17. │ ├─testthat (local) .capture(...)
146s 18. │ │ └─base::withCallingHandlers(...)
146s 19. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
146s 20. ├─testthat::expect_warning(., "coercing")
146s 21. │ └─testthat:::expect_condition_matching(...)
146s 22. │ └─testthat:::quasi_capture(...)
146s 23. │ ├─testthat (local) .capture(...)
146s 24. │ │ └─base::withCallingHandlers(...)
146s 25. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
146s 26. ├─testthat::expect_warning(., "coercing")
146s 27. │ └─testthat:::expect_condition_matching(...)
146s 28. │ └─testthat:::quasi_capture(...)
146s 29. │ ├─testthat (local) .capture(...)
146s 30. │ │ └─base::withCallingHandlers(...)
146s 31. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
146s 32. ├─testthat::expect_warning(., "coercing")
146s 33. │ └─testthat:::expect_condition_matching(...)
146s 34. │ └─testthat:::quasi_capture(...)
146s 35. │ ├─testthat (local) .capture(...)
146s 36. │ │ └─base::withCallingHandlers(...)
146s 37. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
146s 38. ├─testthat::expect_warning(., "coercing")
146s 39. │ └─testthat:::expect_condition_matching(...)
146s 40. │ └─testthat:::quasi_capture(...)
146s 41. │ ├─testthat (local) .capture(...)
146s 42. │ │ └─base::withCallingHandlers(...)
146s 43. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
146s 44. ├─testthat::expect_warning(., "coercing")
146s 45. │ └─testthat:::expect_condition_matching(...)
146s 46. │ └─testthat:::quasi_capture(...)
146s 47. │ ├─testthat (local) .capture(...)
146s 48. │ │ └─base::withCallingHandlers(...)
146s 49. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
146s 50. └─RSQLite (local) check_affinity_fetch("BLO
[Bug 2072811] Re: Apparmor: New update broke flatpak with `apparmor="DENIED"`
** Package changed: evolution (Ubuntu) => apparmor (Ubuntu)
** Description changed:
The recent apparmor update appear to have broken some flatpak's ability to
save file, e.g.:
- org.keepassxc.KeePassXC
- org.ksnip.ksnip
It seems update introduced a new profile ("/etc/apparmor.d/bwrap-userns-
restrict"), which is causing the issue below.
-
To reproduce
(I'm using KeepassXC as example, but same issue for ksnip):
1. Install and run KeepassXC
```bash
flatpak install org.keepassxc.KeePassXC
flatpak run org.keepassxc.KeePassXC
```
2. Got error: "Access error for config file
/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
-
Looking at `journalctl -f`, I see these apparmor DENIED entries:
```txt
Jul 12 09:44:36 ubuntu2404 systemd[2144]: Started
app-flatpak-org.keepassxc.KeePassXC-4010.scope.
Jul 12 09:44:37 ubuntu2404 kernel: kauditd_printk_skb: 6 callbacks suppressed
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400
audit(1720741477.106:310): apparmor="DENIED" operation="link" class="file"
info="Failed name lookup - deleted entry" error=-2 profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400
audit(1720741477.106:311): apparmor="DENIED" operation="link" class="file"
profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211"
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400
audit(1720741477.106:312): apparmor="DENIED" operation="link" class="file"
info="Failed name lookup - deleted entry" error=-2 profile="unpriv_bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400
audit(1720741477.106:313): apparmor="DENIED" operation="link" class="file"
profile="unpriv_bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211"
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400
audit(1720741477.341:314): apparmor="DENIED" operation="link" class="file"
info="Failed name lookup - deleted entry" error=-2 profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400
audit(1720741477.341:315): apparmor="DENIED" operation="link" class="file"
profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214"
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400
audit(1720741477.341:316): apparmor="DENIED" operation="link" class="file"
info="Failed name lookup - deleted entry" error=-2 profile="unpriv_bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400
audit(1720741477.341:317): apparmor="DENIED" operation="link" class="file"
profile="unpriv_bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214"
Jul 12 09:44:38 ubuntu2404 kernel: audit: type=1400
audit(1720741478.704:318): apparmor="DENIED" operation="link" class="file"
info="Failed name lookup - deleted entry" error=-2 profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317217"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
Jul 12 09:44:38 ubuntu2404 kernel: audit: type=1400
audit(1720741478.704:319): apparmor="DENIED" operation="link" class="file"
profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317217"
```
-
-
Workaround
For now, work-around is by disabling "/etc/apparmor.d/bwrap-userns-
- restrict".
+ restrict" profile.
```bash
sudo aa-disable /usr/bin/bwrap
```
-
-
Version info
$
[Bug 2072811] [NEW] Apparmor: New update broke flatpak with `apparmor="DENIED"`
Public bug reported:
The recent apparmor update appear to have broken some flatpak's ability to save
file, e.g.:
- org.keepassxc.KeePassXC
- org.ksnip.ksnip
It seems update introduced a new profile ("/etc/apparmor.d/bwrap-userns-
restrict"), which is causing the issue below.
To reproduce
(I'm using KeepassXC as example, but same issue for ksnip):
1. Install and run KeepassXC
```bash
flatpak install org.keepassxc.KeePassXC
flatpak run org.keepassxc.KeePassXC
```
2. Got error: "Access error for config file
/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
Looking at `journalctl -f`, I see these apparmor DENIED entries:
```txt
Jul 12 09:44:36 ubuntu2404 systemd[2144]: Started
app-flatpak-org.keepassxc.KeePassXC-4010.scope.
Jul 12 09:44:37 ubuntu2404 kernel: kauditd_printk_skb: 6 callbacks suppressed
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 audit(1720741477.106:310):
apparmor="DENIED" operation="link" class="file" info="Failed name lookup -
deleted entry" error=-2 profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 audit(1720741477.106:311):
apparmor="DENIED" operation="link" class="file" profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211"
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 audit(1720741477.106:312):
apparmor="DENIED" operation="link" class="file" info="Failed name lookup -
deleted entry" error=-2 profile="unpriv_bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 audit(1720741477.106:313):
apparmor="DENIED" operation="link" class="file" profile="unpriv_bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211"
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 audit(1720741477.341:314):
apparmor="DENIED" operation="link" class="file" info="Failed name lookup -
deleted entry" error=-2 profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 audit(1720741477.341:315):
apparmor="DENIED" operation="link" class="file" profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214"
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 audit(1720741477.341:316):
apparmor="DENIED" operation="link" class="file" info="Failed name lookup -
deleted entry" error=-2 profile="unpriv_bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 audit(1720741477.341:317):
apparmor="DENIED" operation="link" class="file" profile="unpriv_bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214"
Jul 12 09:44:38 ubuntu2404 kernel: audit: type=1400 audit(1720741478.704:318):
apparmor="DENIED" operation="link" class="file" info="Failed name lookup -
deleted entry" error=-2 profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317217"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
Jul 12 09:44:38 ubuntu2404 kernel: audit: type=1400 audit(1720741478.704:319):
apparmor="DENIED" operation="link" class="file" profile="bwrap"
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000
ouid=1000
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317217"
```
Workaround
For now, work-around is by disabling "/etc/apparmor.d/bwrap-userns-
restrict" profile.
```bash
sudo aa-disable /usr/bin/bwrap
```
Version info
$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04
$ apt-cache policy apparmor
apparmor:
Installed: 4.0.1-0ubuntu0.24.04.2
Candidate: 4.0.1-0u
[Bug 2072812] [NEW] proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-testthat/3.2.1-1
Public bug reported:
The autopkgtest fails with the following error[1]
139s autopkgtest [10:25:06]: test run-unit-test: [---
140s
140s R version 4.4.1 (2024-06-14) -- "Race for Your Life"
140s Copyright (C) 2024 The R Foundation for Statistical Computing
140s Platform: x86_64-pc-linux-gnu
140s
140s R is free software and comes with ABSOLUTELY NO WARRANTY.
140s You are welcome to redistribute it under certain conditions.
140s Type 'license()' or 'licence()' for distribution details.
140s
140s R is a collaborative project with many contributors.
140s Type 'contributors()' for more information and
140s 'citation()' on how to cite R or R packages in publications.
140s
140s Type 'demo()' for some demos, 'help()' for on-line help, or
140s 'help.start()' for an HTML browser interface to help.
140s Type 'q()' to quit R.
140s
140s > library(testthat)
140s > test_check("testthat")
140s Starting 2 test processes
182s [ FAIL 10 | WARN 1412 | SKIP 122 | PASS 819 ]
182s
182s ══ Skipped tests (122)
═
184s • file.exists(rd_path) is not TRUE (2): 'test-test-example.R:3:3',
184s 'test-test-example.R:11:3'
184s • On CRAN (119): 'test-parallel-crash.R:5:3', 'test-watcher.R:40:3',
184s 'test-deprec-condition.R:2:3', 'test-describe.R:23:5',
'test-edition.R:14:3',
184s 'test-expect-condition.R:8:3', 'test-expect-condition.R:19:3',
184s 'test-expect-condition.R:38:3', 'test-expect-condition.R:56:3',
184s 'test-expect-condition.R:216:3', 'test-expect-constant.R:7:3',
184s 'test-expect-constant.R:25:3', 'test-expect-equality.R:71:3',
184s 'test-expect-inheritance.R:23:3', 'test-expect-inheritance.R:42:3',
184s 'test-expect-inheritance.R:49:3', 'test-expect-known.R:45:3',
184s 'test-expect-no-condition.R:5:3', 'test-expect-no-condition.R:35:3',
184s 'test-expect-setequal.R:27:3', 'test-expect-setequal.R:33:3',
184s 'test-expect-setequal.R:94:3', 'test-expect-setequal.R:112:3',
184s 'test-local.R:35:3', 'test-local.R:44:3', 'test-mock2.R:45:3',
184s 'test-mock2.R:76:3', 'test-quasi-label.R:22:3',
'test-quasi-label.R:51:3',
184s 'test-reporter-check.R:3:3', 'test-reporter-check.R:12:3',
184s 'test-reporter-check.R:18:3', 'test-reporter-check.R:27:3',
184s 'test-reporter-junit.R:2:3', 'test-reporter-debug.R:12:3',
184s 'test-reporter-location.R:2:3', 'test-reporter-minimal.R:2:3',
184s 'test-reporter-rstudio.R:2:3', 'test-reporter-silent.R:3:3',
184s 'test-reporter-stop.R:2:3', 'test-reporter-stop.R:6:3',
184s 'test-reporter-summary.R:2:3', 'test-reporter-summary.R:7:3',
184s 'test-reporter-tap.R:2:3', 'test-reporter-teamcity.R:2:3',
184s 'test-reporter.R:9:3', 'test-skip.R:2:3', 'test-skip.R:35:3',
184s 'test-skip.R:43:3', 'test-skip.R:50:3', 'test-skip.R:59:3',
184s 'test-skip.R:77:3', 'test-skip.R:85:3', 'test-skip.R:92:3',
184s 'test-skip.R:100:3', 'test-skip.R:109:3', 'test-skip.R:115:3',
184s 'test-skip.R:121:3', 'test-skip.R:133:3', 'test-snapshot-cleanup.R:3:3',
184s 'test-reporter-progress.R:4:3', 'test-reporter-progress.R:11:3',
184s 'test-reporter-progress.R:27:3', 'test-reporter-progress.R:34:3',
184s 'test-reporter-progress.R:46:3', 'test-reporter-progress.R:53:3',
184s 'test-reporter-progress.R:62:3', 'test-reporter-progress.R:69:3',
184s 'test-snapshot-manage.R:4:3', 'test-snapshot-manage.R:12:3',
184s 'test-snapshot-manage.R:29:3', 'test-snapshot-reporter.R:16:3',
184s 'test-snapshot-reporter.R:45:3', 'test-snapshot-reporter.R:81:3',
184s 'test-snapshot-reporter.R:104:3', 'test-snapshot-reporter.R:118:3',
184s 'test-snapshot-file.R:3:3', 'test-snapshot-file.R:43:3',
184s 'test-snapshot-file.R:50:3', 'test-snapshot-file.R:63:3',
184s 'test-snapshot-file.R:88:3', 'test-snapshot-file.R:161:3',
184s 'test-snapshot-value.R:3:3', 'test-snapshot-value.R:10:3',
184s 'test-snapshot-value.R:18:3', 'test-snapshot-value.R:44:3',
184s 'test-source.R:44:3', 'test-source.R:62:3', 'test-source.R:71:3',
184s 'test-source.R:83:3', 'test-snapshot.R:2:3', 'test-snapshot.R:7:3',
184s 'test-snapshot.R:20:3', 'test-snapshot.R:30:3', 'test-snapshot.R:34:3',
184s 'test-snapshot.R:50:3', 'test-snapshot.R:62:3', 'test-snapshot.R:71:3',
184s 'test-snapshot.R:77:3', 'test-snapshot.R:84:3', 'test-snapshot.R:95:3',
184s 'test-snapshot.R:105:3', 'test-snapshot.R:109:3',
'test-snapshot.R:114:3',
184s 'test-snapshot.R:121:3', 'test-snapshot.R:133:3',
'test-snapshot.R:142:3',
184s 'test-snapshot.R:160:3', 'test-test-env.R:23:3', 'test-test-path.R:44:3',
184s 'test-test-state.R:2:3', 'test-test-state.R:10:3',
184s 'test-verify-output.R:2:3', 'test-verify-output.R:23:3',
184s 'test-verify-output.R:47:3', 'test-verify-output.R:55:3',
184s 'test-verify-output.R:65:3', 'test-verify-output.R:82:3',
184s 'test-test-files.R:18:3'
184s • teardown errors are ignored (1): 'test-parallel-teardown.R:3:3'
184s
184s ══ Failed tests
══
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
This bug was fixed in the package ubuntu-release-upgrader - 1:24.10.5 --- ubuntu-release-upgrader (1:24.10.5) oracular; urgency=medium [ Nick Rosbrook ] * Only rewrite deb822 sources on upgrade - DistUpgradeController: migrate to deb822 before updating sources - DistUpgrade: don't make Deb822SourceEntry import conditional - DistUpgrade: only leave comment in sources.list if we migrated it - DistUpgrade: handle deb822 migration rollback on abort - DistUpgrade: clean up backup sources * Remove dead code - DistUpgradeQuirks: remove unused quirks - test: remove unused interactive_fetch_release_upgrader.py - DistUpgrade: remove old and unused DistUpgradePatcher - DistUpgrade: remove unused zz-update-grub - DistUpgrade: remove apt_clone.py symlink - DistUpgrade: remove imported/invoke-rc.d.diff - DistUpgradeController: remove .list update/re-write functions - DistUpgradeController: remove unused distro.py import and symlink - DistUpgrade: remove DistUpgradeQuirks.run - DistUpgrade: remove un-used PreRequists logic - all: remove unused config and test data - all: remove unused imports - DistUpgradeCache: remove unused methods and variables * DistUpgrade: fix several typos of 'upgrade' * DistUpgradeController: fix attribute typos * Run pre-build.sh: updating mirrors, demotions, and translations. [ Julian Andres Klode ] * Move the actiongroup out of the obsoletes loop * Reimplement obsolete removal with resolve_by_keep (LP: #1874272) -- Nick Rosbrook Thu, 11 Jul 2024 15:04:57 -0400 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072809] [NEW] proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-performance/0.12.0-1
Public bug reported:
The autopkgtest fails with the following error[1]
158s autopkgtest [10:23:35]: test run-unit-test: [---
158s BEGIN TEST testthat.R
158s
158s R version 4.4.1 (2024-06-14) -- "Race for Your Life"
158s Copyright (C) 2024 The R Foundation for Statistical Computing
158s Platform: x86_64-pc-linux-gnu
158s
158s R is free software and comes with ABSOLUTELY NO WARRANTY.
158s You are welcome to redistribute it under certain conditions.
158s Type 'license()' or 'licence()' for distribution details.
158s
158s R is a collaborative project with many contributors.
158s Type 'contributors()' for more information and
158s 'citation()' on how to cite R or R packages in publications.
158s
158s Type 'demo()' for some demos, 'help()' for on-line help, or
158s 'help.start()' for an HTML browser interface to help.
158s Type 'q()' to quit R.
158s
158s > library(testthat)
158s > library(performance)
159s >
159s > test_check("performance")
159s Starting 2 test processes
178s [ FAIL 2 | WARN 552 | SKIP 72 | PASS 266 ]
178s
178s ══ Skipped tests (72)
══
178s • betareg cannot be loaded (1): 'test-model_performance-various.R:4:3'
178s • bigutilsr cannot be loaded (3): 'test-check_outliers.R:80:3',
178s 'test-check_outliers.R:203:3', 'test-check_outliers.R:232:3'
178s • DHARMa cannot be loaded (4): 'test-check_normality.R:89:3',
178s 'test-check_overdispersion.R:147:3', 'test-check_zeroinflation.R:143:3',
178s 'test-check_outliers.R:365:3'
178s • fixest cannot be loaded (9): 'test-check_collinearity.R:182:3',
178s 'test-pkg-fixest.R:5:3', 'test-pkg-fixest.R:18:3',
'test-pkg-fixest.R:28:3',
178s 'test-pkg-fixest.R:36:3', 'test-pkg-fixest.R:53:3',
'test-pkg-fixest.R:62:3',
178s 'test-pkg-fixest.R:72:3', 'test-pkg-fixest.R:80:3'
178s • getRversion() > "4.3.3" is TRUE (13): 'test-check_collinearity.R:27:3',
178s 'test-check_collinearity.R:54:3', 'test-check_convergence.R:32:3',
178s 'test-check_normality.R:38:3', 'test-check_overdispersion.R:2:3',
178s 'test-check_overdispersion.R:53:3', 'test-check_overdispersion.R:81:3',
178s 'test-check_overdispersion.R:186:3', 'test-check_zeroinflation.R:2:3',
178s 'test-check_zeroinflation.R:25:3', 'test-check_zeroinflation.R:112:3',
178s 'test-check_zeroinflation.R:169:3', 'test-r2.R:49:5'
178s • ISLR cannot be loaded (1): 'test-roc.R:1:1'
178s • ivreg cannot be loaded (1): 'test-pkg-ivreg.R:2:3'
178s • nonnest2 cannot be loaded (2): 'test-test_vuong.R:2:3',
178s 'test-test_vuong.R:31:3'
178s • On CRAN (35): 'test-bootstrapped_icc_ci.R:2:3',
178s 'test-bootstrapped_icc_ci.R:44:3', 'test-binned_residuals.R:137:3',
178s 'test-binned_residuals.R:164:3', 'test-check_collinearity.R:178:3',
178s 'test-check_collinearity.R:215:3', 'test-check_distribution.R:35:3',
178s 'test-check_itemscale.R:28:3', 'test-check_model.R:1:1',
178s 'test-check_predictions.R:2:1', 'test-check_residuals.R:2:3',
178s 'test-check_singularity.R:2:3', 'test-check_singularity.R:23:3',
178s 'test-check_zeroinflation.R:75:3', 'test-helpers.R:1:1',
'test-icc.R:4:3',
178s 'test-icc.R:10:3', 'test-icc.R:28:3', 'test-icc.R:40:3',
'test-icc.R:57:3',
178s 'test-icc.R:71:3', 'test-icc.R:89:3', 'test-icc.R:120:3',
'test-icc.R:131:3',
178s 'test-logLik.R:1:1', 'test-mclogit.R:53:3',
178s 'test-model_performance.bayesian.R:2:3',
178s 'test-model_performance.bayesian.R:34:3',
178s 'test-model_performance.bayesian.R:75:3',
178s 'test-model_performance.merMod.R:2:3',
178s 'test-model_performance.merMod.R:22:3',
'test-model_performance.rma.R:33:3',
178s 'test-check_outliers.R:110:3', 'test-r2_nakagawa.R:19:1',
178s 'test-test_likelihoodratio.R:55:1'
178s • On Linux (3): 'test-nestedLogit.R:1:1', 'test-r2_bayes.R:1:1',
178s 'test-test_wald.R:1:1'
178s
178s ══ Failed tests
178s ── Failure ('test-compare_performance.R:8:3'): compare_performance
─
178s `expect_identical(...)` produced warnings.
178s ── Failure ('test-compare_performance.R:20:3'): compare_performance
178s `expect_identical(...)` produced warnings.
178s
178s [ FAIL 2 | WARN 552 | SKIP 72 | PASS 266 ]
178s Error: Test failures
179s Execution halted
179s autopkgtest [10:23:56]: test run-unit-test: ---]
179s autopkgtest [10:23:56]: test run-unit-test: - - - - - - - - - - results -
- - - - - - - - -
179s run-unit-testFAIL non-zero exit status 1
[1]
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-oracular/oracular/amd64/r/r-cran-performance/20240616_102627_e6e91@/log.gz
** Affects: r-cran-performance (Ubuntu)
Importance: Undecided
Status: New
** Affects: r-cran-withr (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Tags added: update-excuse
** Also affects: r-cran-performance (Ubuntu)
[Bug 2072456] Re: boot failure on kv260
The issue is caused by this upstream commit: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-xilinx- zynqmp/+git/jammy/commit/?h=master- next&id=3a6feb4f69d905bf247148ce3f6447f614ea4e7b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072456 Title: boot failure on kv260 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2072456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072808] [NEW] proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-mockr/0.2.1-1
Public bug reported:
The autopkgtest fails with the following error[1]
130s autopkgtest [10:24:53]: test run-unit-test: [---
130s BEGIN TEST testthat.R
130s
130s R version 4.4.1 (2024-06-14) -- "Race for Your Life"
130s Copyright (C) 2024 The R Foundation for Statistical Computing
130s Platform: x86_64-pc-linux-gnu
130s
130s R is free software and comes with ABSOLUTELY NO WARRANTY.
130s You are welcome to redistribute it under certain conditions.
130s Type 'license()' or 'licence()' for distribution details.
130s
130s R is a collaborative project with many contributors.
130s Type 'contributors()' for more information and
130s 'citation()' on how to cite R or R packages in publications.
130s
130s Type 'demo()' for some demos, 'help()' for on-line help, or
130s 'help.start()' for an HTML browser interface to help.
130s Type 'q()' to quit R.
130s
131s > library(testthat)
131s > library(mockr)
131s
131s Attaching package: 'mockr'
131s
131s The following objects are masked from 'package:testthat':
131s
131s local_mock, with_mock
131s
131s >
131s > test_check("mockr")
131s [ FAIL 1 | WARN 27 | SKIP 0 | PASS 51 ]
131s
131s == Failed tests
131s -- Failure ('test-mock.R:116:3'): empty or no-op mock
--
131s `expect_null(with_mock())` produced unexpected warnings.
131s Expected match: Not (?:mocking|evaluating) anything
131s Actual values:
131s * Not mocking anything. Please use named arguments to specify the
functions you want to mock.
131s * Not evaluating anything. Please use unnamed arguments to specify
expressions you want to evaluate.
131s * Changing language has no effect when envvar LC_ALL='C'
131s
131s [ FAIL 1 | WARN 27 | SKIP 0 | PASS 51 ]
132s Error: Test failures
132s Execution halted
[1]
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
oracular/oracular/amd64/r/r-cran-mockr/20240616_102524_aa0c8@/log.gz
** Affects: r-cran-mockr (Ubuntu)
Importance: Undecided
Status: New
** Affects: r-cran-withr (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Tags added: update-excuse
** Also affects: r-cran-mockr (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072808
Title:
proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-mockr/0.2.1-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/r-cran-mockr/+bug/2072808/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072806] [NEW] proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-dials 1.2.0-2
Public bug reported:
The autopkgtest fails with the following error[1]
88s autopkgtest [11:32:09]: test run-unit-test: [---
89s BEGIN TEST testthat.R
89s
89s R version 4.4.1 (2024-06-14) -- "Race for Your Life"
89s Copyright (C) 2024 The R Foundation for Statistical Computing
89s Platform: x86_64-pc-linux-gnu
89s
89s R is free software and comes with ABSOLUTELY NO WARRANTY.
89s You are welcome to redistribute it under certain conditions.
89s Type 'license()' or 'licence()' for distribution details.
89s
89s R is a collaborative project with many contributors.
89s Type 'contributors()' for more information and
89s 'citation()' on how to cite R or R packages in publications.
89s
89s Type 'demo()' for some demos, 'help()' for on-line help, or
89s 'help.start()' for an HTML browser interface to help.
89s Type 'q()' to quit R.
89s
89s > library(testthat)
89s > library(dials)
89s Loading required package: scales
89s >
89s > if (requireNamespace("xml2")) {
89s + test_check("dials", reporter = MultiReporter$new(reporters =
list(JunitReporter$new(file = "test-results.xml"), CheckReporter$new(
89s + } else {
89s + test_check("dials")
89s + }
89s Loading required namespace: xml2
89s Error in UseMethod("xml_add_child") :
89s no applicable method for 'xml_add_child' applied to an object of class
"NULL"
89s Calls: test_check ... o_apply -> lapply -> FUN -> ->
89s Execution halted
90s autopkgtest [11:32:11]: test run-unit-test: ---]
90s run-unit-testFAIL non-zero exit status 1
[1]
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
oracular/oracular/amd64/r/r-cran-dials/20240616_113414_97ba1@/log.gz
** Affects: r-cran-dials (Ubuntu)
Importance: Undecided
Status: New
** Affects: r-cran-withr (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Tags added: update-excuse
** Also affects: r-cran-dials (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072806
Title:
proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-dials 1.2.0-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/r-cran-dials/+bug/2072806/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072807] [NEW] proposed migration r-cran-withr 3.0.0+dfsg-1 vs r-cran-dplyr/1.1.4-1
Public bug reported:
The autopkgtest fails with the following error[1]
11s autopkgtest [11:04:50]: test run-unit-test: [---
412s grep: testthat/_snaps: Is a directory
412s
412s R version 4.4.1 (2024-06-14) -- "Race for Your Life"
412s Copyright (C) 2024 The R Foundation for Statistical Computing
412s Platform: x86_64-pc-linux-gnu
412s
412s R is free software and comes with ABSOLUTELY NO WARRANTY.
412s You are welcome to redistribute it under certain conditions.
412s Type 'license()' or 'licence()' for distribution details.
412s
412s R is a collaborative project with many contributors.
412s Type 'contributors()' for more information and
412s 'citation()' on how to cite R or R packages in publications.
412s
412s Type 'demo()' for some demos, 'help()' for on-line help, or
412s 'help.start()' for an HTML browser interface to help.
412s Type 'q()' to quit R.
412s
412s > library(testthat)
412s > library(dplyr)
412s
412s Attaching package: ‘dplyr’
412s
412s The following object is masked from ‘package:testthat’:
412s
412s matches
412s
412s The following objects are masked from ‘package:stats’:
412s
412s filter, lag
412s
412s The following objects are masked from ‘package:base’:
412s
412s intersect, setdiff, setequal, union
412s
412s >
412s > test_check("dplyr")
489s [ FAIL 2 | WARN 5031 | SKIP 329 | PASS 2860 ]
489s
489s ══ Skipped tests (329)
═
492s • Can't set a non-UTF-8 encoding (4): 'test-colwise-mutate.R:136:3',
492s 'test-colwise-mutate.R:150:3', 'test-group-by.R:265:3',
'test-mutate.R:426:3'
492s • Can't use 'en_US' locale (2): 'test-arrange.R:325:3',
492s 'test-grouped-df.R:206:3'
492s • On CRAN (323): 'test-across.R:138:3', 'test-across.R:146:3',
492s 'test-across.R:198:3', 'test-across.R:210:3', 'test-across.R:588:3',
492s 'test-across.R:735:3', 'test-across.R:762:3', 'test-across.R:1110:3',
492s 'test-across.R:1120:3', 'test-across.R:1152:3', 'test-across.R:1180:3',
492s 'test-across.R:1209:3', 'test-across.R:1242:3', 'test-across.R:1253:3',
492s 'test-all-equal.R:2:3', 'test-all-equal.R:27:3', 'test-all-equal.R:36:3',
492s 'test-all-equal.R:47:3', 'test-all-equal.R:61:3',
'test-all-equal.R:114:3',
492s 'test-all-equal.R:142:3', 'test-all-equal.R:155:3',
'test-all-equal.R:163:3',
492s 'test-all-equal.R:171:3', 'test-all-equal.R:182:3',
'test-arrange.R:28:3',
492s 'test-arrange.R:156:3', 'test-arrange.R:164:3', 'test-arrange.R:177:3',
492s 'test-arrange.R:302:3', 'test-bind-cols.R:41:3',
'test-bind-cols.R:116:3',
492s 'test-bind-cols.R:132:3', 'test-bind-rows.R:137:3',
'test-bind-rows.R:152:3',
492s 'test-bind-rows.R:242:3', 'test-by.R:70:3', 'test-by.R:79:3',
492s 'test-by.R:88:3', 'test-by.R:97:3', 'test-case-match.R:23:3',
492s 'test-case-match.R:40:3', 'test-case-match.R:50:3',
'test-case-match.R:59:3',
492s 'test-case-when.R:219:3', 'test-case-when.R:227:3',
'test-case-when.R:239:3',
492s 'test-case-when.R:247:3', 'test-case-when.R:253:3',
'test-case-when.R:262:3',
492s 'test-case-when.R:271:3', 'test-coalesce.R:26:3', 'test-coalesce.R:90:3',
492s 'test-coalesce.R:96:3', 'test-coalesce.R:112:3', 'test-coalesce.R:118:3',
492s 'test-colwise-filter.R:82:3', 'test-colwise-mutate.R:89:3',
492s 'test-colwise-mutate.R:295:3', 'test-colwise-mutate.R:342:3',
492s 'test-colwise-select.R:174:3', 'test-colwise.R:22:3',
492s 'test-conditions.R:3:3', 'test-conditions.R:20:3',
'test-conditions.R:27:3',
492s 'test-conditions.R:39:3', 'test-conditions.R:62:3',
492s 'test-conditions.R:150:3', 'test-conditions.R:188:3',
492s 'test-consecutive-id.R:14:3', 'test-consecutive-id.R:20:3',
492s 'test-context.R:57:3', 'test-context.R:69:3', 'test-copy-to.R:11:3',
492s 'test-count-tally.R:45:3', 'test-count-tally.R:117:3',
492s 'test-count-tally.R:132:3', 'test-count-tally.R:159:3',
492s 'test-count-tally.R:182:3', 'test-count-tally.R:214:3',
'test-defunct.R:2:3',
492s 'test-deprec-combine.R:2:3', 'test-deprec-combine.R:244:3',
492s 'test-deprec-context.R:6:3', 'test-deprec-context.R:14:3',
492s 'test-deprec-context.R:78:3', 'test-deprec-dbi.R:5:3',
492s 'test-deprec-do.R:197:3', 'test-deprec-funs.R:119:3',
492s 'test-deprec-funs.R:127:3', 'test-deprec-lazyeval.R:34:3',
492s 'test-deprec-lazyeval.R:45:3', 'test-deprec-src-local.R:26:3',
492s 'test-desc.R:2:3', 'test-distinct.R:175:3', 'test-filter.R:386:3',
492s 'test-filter.R:403:3', 'test-filter.R:411:3', 'test-filter.R:417:3',
492s 'test-filter.R:627:3', 'test-filter.R:671:3', 'test-filter.R:680:3',
492s 'test-filter.R:689:3', 'test-filter.R:697:3', 'test-funs.R:57:3',
492s 'test-funs.R:69:3', 'test-group-by.R:87:3', 'test-group-by.R:169:3',
492s 'test-group-by.R:217:3', 'test-group-by.R:606:3',
'test-group-map.R:120:3',
492s 'test-grouped-df.R:153:3', 'test-grouped-df.R:187:3',
'test-if-else.R:49:3',
492s 'test-if-else.R:57:3', 'test-if-else.R:72:3', 'test-if-else.
[Bug 2072755] Re: Request backport of two i915/Intel Arc GPU patches
Hi nyanmisaka, "drm/i915/gt: Automate CCS Mode setting during engine resets" is already queued up in master-next, so it should be available in the next SRU cycle or so: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd $ git describe --contains aee54e282002a127612b71255bbe879ec0103afd fatal: cannot describe 'aee54e282002a127612b71255bbe879ec0103afd' Its not tagged to any release yet, but its in the pipeline. I think the Kernel Team are currently at upstream stable 6.8.12, and havne't begun 6.9.x patches, so at the moment, "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" hasn't been applied yet. I can make you a test kernel with the fix, and we can do a manual SRU if you like? Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072755 Title: Request backport of two i915/Intel Arc GPU patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072490] Re: [needs-packaging] U-Boot for Microchip PIC64GX
Hello Steve,
thanks for reviewing.
As mentioned above I have already repackaged as u-boot-
pic64gx_2024.06-0ubuntu0.22.4.1~ppa1 as Microchip created a tag
v2024.06.
v2024.06 is a version number chosen by Microchip which is not related to
the upstream U-Boot version numbering scheme. Actually it is based on
upstream v2023.07. Once the Microchip has upstreamed the U-Boot code we
will put the binaries in u-boot-microchip built from the u-boot source
package.
The file drivers/dma/MCD_tasks.c was introduced in 2008 with commit
11865ea844e7 ("ColdFire: Add MCF547x_8x dma code - 1") by employees of
the copyright holding company. In this commit it was already marked as
GPL-2-or-later. I cannot see any tort in distributing a GPLed file in
our orig.tar.xz which we do not compile. In upstream U-Boot the file was
removed since due to obsolescence.
Best regards
Heinrich
** Changed in: ubuntu
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072490
Title:
[needs-packaging] U-Boot for Microchip PIC64GX
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2072490/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041480] Re: Netplan 0.106.1-7ubuntu0.22.04.2 breaks mac address match
*** This bug is a duplicate of bug 2022947 *** https://bugs.launchpad.net/bugs/2022947 I'm having the following warnings when issuing 'netplan apply' for nics which are members of bonds (since they share the same mac address after they're brought up) WARNING:root:Cannot find unique matching interface for eno2 WARNING:root:Cannot find unique matching interface for eno1 WARNING:root:Cannot find unique matching interface for enp4s0f1 WARNING:root:Cannot find unique matching interface for enp4s0f0 I believe this is due to netifaces returning the spoofed mac address and not the permanent one [1][2]. [1] - https://github.com/canonical/netplan/blob/5df4140c49f242cb63efcd5edffe6a06419150fb/netplan/cli/commands/apply.py#L381 [2] - https://github.com/canonical/netplan/blob/5df4140c49f242cb63efcd5edffe6a06419150fb/netplan/cli/utils.py#L173 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041480 Title: Netplan 0.106.1-7ubuntu0.22.04.2 breaks mac address match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071815] Re: Investigate ASLR re-randomization being disabled for children
These might be related and might help the underlying problem: https://github.com/openssh/openssh-portable/commit/8785491123d4d722b310c20f383570be758f8263 https://github.com/openssh/openssh-portable/commit/c0cb3b8c837761816a60a3cdb54062668df09652 Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071815 Title: Investigate ASLR re-randomization being disabled for children To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2071815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069202] Re: hypercorn depends on node-mermaid which has been removed from the archive
I have tried to build node-mermaid in oracular. First it failed to build due to rollup3 [1] issue. After applying upstream patch, the build failed with the following error: webpack --mode production --progress [webpack-cli] Unable load '/<>/webpack.config.babel.js' [webpack-cli] Unable to use specified module loaders for ".babel.js". [webpack-cli] Cannot find module '@babel/register' from '/<>' [webpack-cli] Cannot find module 'babel-register' from '/<>' [webpack-cli] Cannot find module 'babel-core/register' from '/<>' [webpack-cli] Cannot find module 'babel/register' from '/<>' [webpack-cli] Please install one of them [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022630 ** Bug watch added: Debian Bug tracker #1022630 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022630 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069202 Title: hypercorn depends on node-mermaid which has been removed from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hypercorn/+bug/2069202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069649] Re: lshw hangs running forever at Network Interfaces CLASS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lshw (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069649 Title: lshw hangs running forever at Network Interfaces CLASS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/2069649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors
Firmware was already updated (verified both with fwupdmgr and by booting into Windows and using Lenovo tools). I will work on installing a mainline kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999814] Re: [SRU] Allow for specifying common baseline CPU model with disabled feature
Hello Paul, or anyone else affected, Accepted nova into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nova/3:25.2.1-0ubuntu2.4 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: nova (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1999814 Title: [SRU] Allow for specifying common baseline CPU model with disabled feature To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1999814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037688] Re: Pull-request to address TPM bypass issue
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037688 Title: Pull-request to address TPM bypass issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045560] Re: TCP memory leak, slow network (arm64)
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046315] Re: panel flickering after the i915.psr2 is enabled
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: panel flickering after the i915.psr2 is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062135] Re: Add Cirrus Logic CS35L56 amplifier support
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062135 Title: Add Cirrus Logic CS35L56 amplifier support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2062135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064064] Re: Add support of TAS2781 amp of audio
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064064 Title: Add support of TAS2781 amp of audio To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2064064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064689] Re: Fix inaudible HDMI/DP audio on USB-C MST dock
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064689 Title: Fix inaudible HDMI/DP audio on USB-C MST dock To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2064689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066332] Re: net:fib_rule_tests.sh in ubuntu_kselftests_net fails on Noble
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066332 Title: net:fib_rule_tests.sh in ubuntu_kselftests_net fails on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2066332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068024] Re: race_sched in ubuntu_stress_smoke_test will cause kernel panic on 6.8 with Azure Standard_A2_v2 instance
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068024 Title: race_sched in ubuntu_stress_smoke_test will cause kernel panic on 6.8 with Azure Standard_A2_v2 instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2068024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068544] Re: Export kernel symbols required for NVIDIA GDS
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068544 Title: Export kernel symbols required for NVIDIA GDS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2068544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068591] Re: Noble: btrfs: re-introduce 'norecovery' mount option
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068591 Title: Noble: btrfs: re-introduce 'norecovery' mount option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470091] Re: update for V3 kernel bits and improved multiple fan slice support
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470091 Title: update for V3 kernel bits and improved multiple fan slice support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1470091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061040] Re: I2C HID device sometimes fails to initialize causing touchpad to not work
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061040 Title: I2C HID device sometimes fails to initialize causing touchpad to not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063417] Re: Fix system hang while entering suspend with AMD Navi3x graphics
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063417 Title: Fix system hang while entering suspend with AMD Navi3x graphics To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064508] Re: re-enable Ubuntu FAN in the Noble kernel
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064508 Title: re-enable Ubuntu FAN in the Noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065376] Re: [X13s] Fingerprint reader is not working
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065376 Title: [X13s] Fingerprint reader is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068067] Re: mlxbf_gige: bring in latest 6.x upstream commits
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1009.9~22.04.1 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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. 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-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068067 Title: mlxbf_gige: bring in latest 6.x upstream commits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2068067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072490] Re: [needs-packaging] U-Boot for Microchip PIC64GX
u-boot-pic64gx_2024.06 well, somewhat unfortunate wrt license review that this doesn't align with any of the u-boot upstream tags; I guess I'll compare with 2024.04... The u-boot source package has in debian/copyright: Files-Excluded: drivers/dma/MCD_tasks.c u-boot-pic64gx does not. Do you know why this was excluded in the Debian u-boot package, and why it would be ok to ship it in the pic64gx build? If not, I recommend that you follow the u-boot source package's lead to avoid any doubts. There's also an 8kloc diff between the debian/copyright in u-boot 2024.01+dfsg-1ubuntu5 and the one in u-boot-pic64gx 20240624-0ubuntu1. That is a rather significant barrier to using u-boot as a base for review of correct licensing / copyright declaration of the new package. Can you explain this difference? Also, speaking of '20240624-0ubuntu1' - note that this is not consistent with the versioning scheme used by the u-boot source package; 20240624 sorts >> the .MM style version numbers. This will make it difficult to later build the u-boot-pic64gx binary out of the u-boot source package due to inconsistent version numbers. I suggest you avoid this now by packaging this instead as 2024.06.24-0ubuntu1. ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072490 Title: [needs-packaging] U-Boot for Microchip PIC64GX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067632] Re: No logo in Horizon - 404 logo-canonical-openstack-splash.svg
Hello Nobuto, or anyone else affected, Accepted horizon into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/horizon/4:24.0.0-0ubuntu1.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- 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: horizon (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067632 Title: No logo in Horizon - 404 logo-canonical-openstack-splash.svg To manage notifications about this bug go to: https://bugs.launchpad.net/snap-openstack/+bug/2067632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064762] Re: Update gnome-control-center to 46.3
** Description changed: Impact -- There was a new bugfix release in the stable 46 series. https://gitlab.gnome.org/GNOME/gnome-control-center/-/compare/46.0...46.3 https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.3/NEWS Test Case 1 --- Install the update. Make sure that gnome-control-center continues to run well. Test Case 2 --- Install gnome-session Log out. Click your name on the login screen. Click the gear in the bottom right corner and choose GNOME. Finish logging in. Make sure that gnome-control-center continues to run well. This test case is because some of our Ubuntu customizations only show in the Ubuntu session, not other sessions like vanilla GNOME. Test Case 3 --- Open gnome-control-center Click the last item in the left sidebar named About Click Device Name. Type in a different name for your computer. Press Enter. The Rename Device dialog should close and your new computer name should take effect. + Test Plan + - + + We started drafting the corresponding testplan on + https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeControlCenter + + We will use the SRU verification as an opportunity to complete the + wikipage, documenting what was tested and setting a basis for the next + updates + What Could Go Wrong --- gnome-control-center is used by Ubuntu Desktop and Edubuntu. It is a critical app for viewing and changing a huge variety of settings for these desktops. gnome-control-center is part of GNOME Core and has a microrelease exception for Ubuntu stable release updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064762 Title: Update gnome-control-center to 46.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069384] Re: puppetdb fails to build from source on noble
Thanks! I have gone ahead and uploaded. I did make one minor adjustment because I forgot to mention something before. Generally, it is a good idea to follow [1] when selecting a version number for SRUs. In this case, it might not technically matter because oracular already has a new upstream version in -release, but still. > Yes, I do have an MP created [2]. I left a quick comment there. To make the SRU team's job easier, it would be good to also fill out the SRU template on bug 2072516 (even though it's trivial since it's about making autopkgtest pass). [1] https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging ** Changed in: puppetdb (Ubuntu Noble) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069384 Title: puppetdb fails to build from source on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2069384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071729] Re: geeqie crashes when switching to "float file list" mode (after dist-upgrade to noble)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: geeqie (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071729 Title: geeqie crashes when switching to "float file list" mode (after dist- upgrade to noble) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geeqie/+bug/2071729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071939] Please test proposed package
Hello Alex, or anyone else affected, Accepted ceilometer into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ceilometer/2:22.0.0-0ubuntu1.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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071939 Title: [caraca|2024.1] the 22.0 version of python3-ceilometer is missing files thus breaking the notification service To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2071939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071939] Re: [caraca|2024.1] the 22.0 version of python3-ceilometer is missing files thus breaking the notification service
Can we also do a diff of the package listing with this patch, to be sure we are not including unwanted files all of a sudden? ** Changed in: ceilometer (Ubuntu Noble) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071939 Title: [caraca|2024.1] the 22.0 version of python3-ceilometer is missing files thus breaking the notification service To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2071939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071889] Re: a critical typo in the code managing the ASPM settings for PCI Express devices
Kernel 6.8.0-40.40 solves this problem. ** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071889 Title: a critical typo in the code managing the ASPM settings for PCI Express devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2071889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
