This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
nginx is full of autopkgtest errors in the excuses report[1]. For some
reason they were not reported here, perhaps they happened during one of
the past outages we had.
They also all have a reported version number of "unknown", which usually
indicates an infrastructure problem.
I retriggered them
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-
aws-6.8' to 'verification-done-jammy-linux-
** Tags added: pe-sponsoring-request
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072366
Title:
s390-tools zipl breaks when user provides target attributes
To manage notifications about this bug
I successfully completed both test cases on Ubuntu 24.04 LTS with
osinfo-db 0.20240523-0ubuntu0.24.04.1
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Notify-osd doesn't handle notification actions and that's usually the
reason why you get a fallback dialog. I think the notification is coming
from snapd-desktop-integration and not snapd though so that would be the
right component to target? I'm adding it to the bug
--
You received this bug noti
** Description changed:
Impact
--
This is a new stable release in the 3.52 series.
https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/3.52.3/NEWS
Test Case
-
Install the update
Log out and log back in (or restart)
- Ensure that GNOME Calendar and Evolutio
I successfully verified the SRU on my Raspberry Pi Zero 2W:
```
bdrung@zero2w:~$ sudo cp /boot/initrd.img-6.8.0-1007-raspi
/boot/initrd.img-6.8.0-1007-raspi.current-noble
bdrung@zero2w:~$ sudo sh -c '3cpio -t
/boot/initrd.img-6.8.0-1007-raspi.current-noble >
/boot/initrd.img-6.8.0-1007-raspi.cu
PPA for testing: https://launchpad.net/~zhsj/+archive/ubuntu/bug2072745
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072745
Title:
crash extensions are not built with CFLAGS from dpkg-buildflags
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/caracal
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/b
** Changed in: ghostwriter (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: ghostwriter (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.n
Public bug reported:
Impact
==
** Affects: gnome-online-accounts (Ubuntu)
Importance: High
Status: Fix Committed
** Affects: gnome-online-accounts (Ubuntu Noble)
Importance: High
Assignee: Jeremy Bícha (jbicha)
Status: Incomplete
** Tags: noble upgrade-soft
** Changed in: gnome-online-accounts (Ubuntu)
Status: New => Fix Released
** Also affects: gnome-online-accounts (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: gnome-online-accounts (Ubuntu Noble)
Status: New => In Progress
** Changed in: gnome-online-acc
** Description changed:
Impact
--
- There is a 90 second delay during the upgrade to gnome-remote-desktop (as in
the upgrade from Ubuntu Desktop 22.04 LTS or 23.10 to 24.04 LTS)
+ There is a 90 second timeout delay during the upgrade to gnome-remote-desktop
(as in the upgrade from Ubuntu
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046386
Title:
Ubuntu Studio images aren't being built with a live user
To manage notifications about this bug go to:
I was able to reproduce. Reverting to package 6.8.0-36 restores all
Intel Quick Sync functionality on my Arc GPU.
But the issues with Intel Arc GPUs and Quick Sync on 6.8.0-38 appears to
be limited to ffmpeg commands that scale the output resolution.
An example ffmpeg command that does NOT work.
** Changed in: privoxy (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/2071115
Title:
Please sync privoxy 3.0.34-5 from Debian sid into oracular
To manage
** Also affects: gnome-remote-desktop (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: gnome-remote-desktop (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: gnome-remote-desktop (Ubuntu Noble)
Status: New => In Progress
** Changed in: gnome-remo
duue to no willingness to update driver to mainline, i used straight from
nvidia website and problem gone
550.90.07 - closing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069092
Title:
whole sys
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2044104
Title:
[UBUNTU 20.04] chzdev -e is rebuilding initramfs ev
oracular has s390-tools 2.33.1-0ubuntu3. Is there any further change
needed on that package, or should that task be marked resolved?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2044104
Title:
[UB
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All autopkgtests for the newly accepted linux-meta-riscv (6.5.0.44.44.1) for
mantic have finished running.
The following regressions have been reported in tests triggered by the package:
backport-iwlwifi-dkms/unknown (amd64)
casper/unknown (amd64)
cryptsetup/unknown (ppc64el, s390x)
ipmitool/unkn
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065180
Title:
performance regression in dracut-install 060
To manage
Verified the version 1:46.1-1ubuntu1~24.04.1 against the test plan on
Ubuntu 24.04 LTS
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
What we're after is disabling the network for any child processes. It
doesn't matter specifically how that gets done.
If this can be done some other way with some other facility that doesn't
clash with efforts to harden the host distributions, I'm all ears.
--
You received this bug notification
Where are the initramfs-tools gone? Added it again ... (sorry)
** Also affects: initramfs-tools (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/20441
@vorlon yes, that's correct. (This bug became a bit abandoned ...)
I just changed the target release to oracular and set s390-tools to Fix
Released.
** Also affects: s390-tools (Ubuntu Oracular)
Importance: Medium
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
*
** Changed in: mdtraj (Ubuntu)
Status: New => In Progress
** Changed in: mdtraj (Ubuntu)
Assignee: (unassigned) => Sudip Mukherjee (sudipmuk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Hi Rodrigo,
Thanks for the debdiffs and SRU template!
I've had minor changes to the Jammy upload, and build-tested it in a PPA [1].
It looks good; uploading!
(I'm looking into/building Focal.)
[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1999814
** Changed in: nova (Ubuntu Jammy)
St
Using Ubuntu 24.04 LTS, I verified the failure test case. Then I
installed graphviz 2.42.2-9ubuntu0.1 and verified that the test now
passes.
Because Ubuntu 23.10 is scheduled for End of Life today, I will not
verify the fix on that release.
** Tags removed: verification-needed-noble
** Tags added
** Changed in: classmate (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/2052981
Title:
classmate: FTBFS with default Java 21
To manage notifications about
** Description changed:
- With the same NetApp stanza in the manila.conf file which was used without
any issue in the Zed release was used in the Bobcat release. In the Bobcat
release, the share creation worked normally, but adding access rule was not
worked and couldn't delete the share. Below
--- Comment From ar...@de.ibm.com 2024-07-11 12:51 EDT---
> [...]
> A test build of the new valgrind version is now available here:
> https://launchpad.net/~fheimes/+archive/ubuntu/lp1982335
The build contains the requested support, and I didn't notice any
issues. Looks good to me.
--
Y
Looking at your enabled repositories, you have an unsupported external
Docker repository (likely the official one from Docker themselves)
enabled. We do not support that, and that's likely interfering with the
upgrade process as the root of the problem appears to be package
interference in package
Public bug reported:
SRU Justification:
[Impact]
This is a cherry-pick fix from upstream to Add support for BF3 eMMC HW reset
[Fix]
BLueField eMMC RST_N register is implemented as secure, thus the default
hw_reset() implementation won't work. This patch provides BlueField specific
hw_reset() w
This bug was fixed in the package apache2 - 2.4.41-4ubuntu3.20
---
apache2 (2.4.41-4ubuntu3.20) focal-security; urgency=medium
* SECURITY REGRESSION: regression when proxying http2 (LP: #2072648)
- debian/patches/CVE-2024-38477-2.patch: restart from the original URL
on rec
This bug was fixed in the package apache2 - 2.4.58-1ubuntu8.3
---
apache2 (2.4.58-1ubuntu8.3) noble-security; urgency=medium
* SECURITY REGRESSION: regression when proxying http2 (LP: #2072648)
- debian/patches/CVE-2024-38477-2.patch: restart from the original URL
on recon
Using Ubuntu 22.04 LTS, I verified the failure test case. Then I
installed graphviz 2.42.2-6ubuntu0.1 and verified that the test now
passes.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notificati
Public bug reported:
I'm facing an issue some time. My screen turn black and there are some
colours line in it. It's impossible to do anything.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13
Uname: Linux 6
This bug was fixed in the package apache2 - 2.4.52-1ubuntu4.11
---
apache2 (2.4.52-1ubuntu4.11) jammy-security; urgency=medium
* SECURITY REGRESSION: regression when proxying http2 (LP: #2072648)
- debian/patches/CVE-2024-38477-2.patch: restart from the original URL
on rec
Update:
Editing /sys/module/snd_hda_intel/parameters/power_save' from '1' to '0'
is a temporary workaround. So it is indeed caused by the audio chipset's
power-saving.
Seems the root cause is that mouse clicks that were never intended to produce a
sound (i.e., clicking empty screen space) shoul
Public bug reported:
I'm facing an issue some time. My screen turn black and there are some
colours line in it. It's impossible to do anything.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13
Uname: Linux 6
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Oracular)
Status: New => Fix Committed
--
You received this bug notification because you are a me
Correction:
[Impact]
This is a bug fix to enable the hw_reset() support in sdhci-of-dwcmshc driver
for BlueField-3.
** Description changed:
SRU Justification:
[Impact]
- This is a cherry-pick fix from upstream to Add support for BF3 eMMC HW reset
+ This is an enhancement to enable the hw
Unfortunately again the issue kicks in
$ sudo fwupdmgr upgrade
Devices with no available firmware updates:
• ELAN0677:00 04F3:3196
• EM05-G
• Integrated Camera
• Prometheus IOTA Config
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Devi
I've updated to kernel 6.9.3 (6.9.3-060903-generic #202405300957 SMP
PREEMPT_DYNAMIC Thu May 30 11:39:13 UTC 2024 x86_64 x86_64 x86_64
GNU/Linux) using ppa:cappelikan/ppa and all my troubles with suspend
were successfully resolved.
Ubuntu 24.04, CPU AMD Ryzen7 6800H, ASUS ROG notebook.
--
You re
** Also affects: mdtraj (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: mdtraj (Ubuntu Noble)
Status: New => In Progress
** Changed in: mdtraj (Ubuntu Noble)
Assignee: (unassigned) => Sudip Mukherjee (sudipmuk)
--
You received this bug notification because
I spent a long time trying to understand what happened with this CVE.
- upstream's first attempt at a fix, which misses fixing "leak on binary fields
(EC2N class)": https://github.com/weidai11/cryptopp/issues/869
- it also introduced a regression, so besides an incomplete fix, it introduces
a bu
This regression persists in current Gwenview / KDE / Kubuntu versions.
Tested to persist in:
Kubuntu 22.04
Gwenview 21.12.3
KDE-Plasma 5.24.7
KDE-Framework 5.92.0
Qt 5.15.3
Kernel 6.5.0-1025-oem
X11
** Summary changed:
- [Regression] Infinite drag scrolling not working on Kubuntu 16.04
+ [Regr
This bug was fixed in the package horizon - 4:24.0.0-0ubuntu3
---
horizon (4:24.0.0-0ubuntu3) oracular; urgency=medium
* d/u/_styles.scss: use static_url variable instead of absolute path
(LP: #2067632).
-- Guillaume Boutry Thu, 11 Jul 2024
11:03:18 +0100
** Changed in: hor
*** This bug is a duplicate of bug 1594156 ***
https://bugs.launchpad.net/bugs/1594156
** This bug has been marked a duplicate of bug 1594156
KIPI plugins not working on Gwenview - Kubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Public bug reported:
File "/usr/share/appgrid/appdata.py", line 167, in
rebuild_db()
File "/usr/share/appgrid/appdata.py", line 62, in rebuild_db
for pkgname in get_apt_pkgnames():
^^
File "/usr/share/appgrid/appdata/apps/aptapp.py", line 250, in
ge
Public bug reported:
[Impact]
obs-studio 30.1 was released but, as obs does with their point releases,
includes far too many features to justify a simple SRU bugfix
microrelease. Therefore, the most logical way to get a bugfix release
like this into users is to backport it. Besides that, the feat
All autopkgtests for the newly accepted linux-meta-lowlatency (6.5.0.44.44.1)
for mantic have finished running.
The following regressions have been reported in tests triggered by the package:
linux-lowlatency/6.5.0-44.44.1 (amd64, arm64)
Please visit the excuses page listed below and investigat
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
LP is eating my indentation in the changelog entry example, but
hopefully you get the idea.
** Changed in: puppetdb (Ubuntu Noble)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Thanks for finding the minimal patches required for this. A few
organizational things:
1. 0008-Resolve-ftbfs-with-java-21.patch: It would be good to have an
Origin: field in the patch showing where you got this. It's good you
have the Author: for credit, but links are easier to follow. I also
pref
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
I have uploaded the patch (had to tweak it a bit to apply) and uploaded
to Debian where it will autosync to Ubuntu.
I have unsubscribed ubuntu-sponsors. Feel free to resubscribe if you
have something else that needs to be sponsored.
--
You received this bug notification because you are a member
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-40.40 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
** Also affects: puppetdb (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: puppetdb (Ubuntu Noble)
Assignee: (unassigned) => Pushkar Kulkarni (pushkarnk)
** Changed in: puppetdb (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: puppetdb (Ubuntu Noble)
See comment #4 and #5: /usr/share/initramfs-tools/hooks/udev is shipped
by the udev package (not by initramfs-tools)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2044104
Title:
[UBUNTU 20.04] chzde
Modify /usr/share/initramfs-tools/hooks/udev (shipped by udev, source:
system) to not copy the udev rules generated by chzdev. So changing:
Where are the initramfs-tools gone? Added them again ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Patch added: "lp2069125_jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/manila/+bug/2069125/+attachment/5796279/+files/lp2069125_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Patch added: "lp2069125_antelope.debdiff"
https://bugs.launchpad.net/ubuntu/+source/manila/+bug/2069125/+attachment/5796280/+files/lp2069125_antelope.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Patch added: "lp2069125_mantic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/manila/+bug/2069125/+attachment/5796281/+files/lp2069125_mantic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Patch added: "lp2069125_noble.debdiff"
https://bugs.launchpad.net/ubuntu/+source/manila/+bug/2069125/+attachment/5796282/+files/lp2069125_noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I haven't updated Tomcat in a year and a half because of this issue. Is
anyone reading these?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2002448
Title:
Tomcat upgrades alter file ownership
To m
** Package changed: ubuntu => xorg (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:/
The jammy upload has this changelog in its changes file:
cloud-init (24.2-0ubuntu1~22.04.1) jammy; urgency=medium
.
* d/apport-general-hook.py: Move apport hook to main branch
* d/cloud-init.maintscript: remove /etc/cloud/clean.d/README
* d/cloud-init.logrotate: add logrotate config for
So if O_NONBLOCK is set, you want a DIO read to stop after a single
subrequest?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056461
Title:
autopkgtest-virt-qemu on noble images sometimes hangs doi
(In reply to Christian from comment #48)
> Is there any chance that we can have 80105ed reverted until the correct
> cause has been identified and fixed?
Well, did anyone try if that is possible (with a reasonable amount of
work and churn) and makes things work again? FWIW, I just tried, a
simple
201 - 300 of 411 matches
Mail list logo
