Does this fix it for you?
https://lore.kernel.org/r/4058793.1720703...@warthog.procyon.org.uk/
--- a/fs/9p/vfs_addr.c
+++ b/fs/9p/vfs_addr.c
@@ -77,6 +77,10 @@ static void v9fs_issue_read(struct netfs_io_subrequest
*subreq)
* cache won't be on server and is zeroes */
__set_bit(N
That won't be enough imo, there are two problems:
- We're truncating the read request to the cached i_size
- that odd O_NONBLOCK behaviour on regular files 9p used to have
In this particular reproducer O_NONBLOCK happened to be set (in eofcat)
so that part of the discussion came up, but the proble
The same tests fail, with the same errors, on noble (puppetdb 7.12.1-3)
after fixing the FTBFS reported by LP#2069384
** Summary changed:
- autopkgtests fail with version 8.4.1-1 on oracular
+ autopkgtests fail with on oracular & noble
** Summary changed:
- autopkgtests fail with on oracular &
This bug was fixed in the package falkon - 24.05.2-0ubuntu1
---
falkon (24.05.2-0ubuntu1) oracular; urgency=medium
[ Scarlett Moore ]
* Properly address the apparmor profile issue by adding multiple
lines for the different architectures we want to support until
@multiarch
Regression fix USN has now been published:
https://ubuntu.com/security/notices/USN-6885-2
Thanks!
** Changed in: apache2 (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.
Public bug reported:
xilinx-runtime fails to build in Ubuntu Oracular Oriole[1] due to the
undefined fixed-width integers:
/<>/src/runtime_src/core/edge/common/aie_parser.h:87:3: error:
‘uint32_t’ does not name a type
87 | uint32_tid;
Would it be possible to include stdint.h that de
** Merge proposal linked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/xilinx-runtime/+git/xilinx-runtime/+merge/469242
--
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-
Thanks again, for the review!
> Points 1, 2, 3 above
I've addressed them in the newly attached diff. Test build in PPA [1].
> Point 4
Yes, I do have an MP created [2].
[1]
https://launchpad.net/~pushkarnk/+archive/ubuntu/puppetdb-retest/+build/28646990
[2]
https://code.launchpad.net/~pus
** Changed in: qemu
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072564
Title:
qemu-aarch64-static segfaults running ldconfig.real (amd64 host)
To manage notificatio
This bug was fixed in the package linux-nvidia - 6.8.0-1009.9
---
linux-nvidia (6.8.0-1009.9) noble; urgency=medium
* noble/linux-nvidia: 6.8.0-1009.9 -proposed tracker (LP: #2068306)
* mlxbf_gige: bring in latest 6.x upstream commits (LP: #2068067)
- mlxbf_gige: add support
This bug was fixed in the package linux-nvidia - 6.8.0-1009.9
---
linux-nvidia (6.8.0-1009.9) noble; urgency=medium
* noble/linux-nvidia: 6.8.0-1009.9 -proposed tracker (LP: #2068306)
* mlxbf_gige: bring in latest 6.x upstream commits (LP: #2068067)
- mlxbf_gige: add support
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
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 no
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
h
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:
gee
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 versi
** 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 upd
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
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 k
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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-l
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.
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
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
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 us
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 beca
*** 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 i
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
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:
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 Comp
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 S
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 Comp
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 subsc
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 Com
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
- DistUpgrad
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
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 *
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
** 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-
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.ne
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
** 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 mana
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
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.
** 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 not
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
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
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
** 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
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 thi
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-blue
*** 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.launch
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
--
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/207247
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 st
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
** 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
** 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
** 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 Lak
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-packa
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 rea
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
** 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-a
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 con
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 b
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/20242
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
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.
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 m
** 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:
** 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 de
** 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
** 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
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:
unr
[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
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
** Attachme
[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.n
[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
T
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:
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://
** 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 ]
+ Curren
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
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
301 - 400 of 411 matches
Mail list logo
