Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
All autopkgtests for the newly accepted
linux-restricted-modules-lowlatency-hwe-6.8 (6.8.0-60.63.1~22.04.1) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-470/unknown (amd64)
Please visit the excuses page
This bug is awaiting verification that the linux-nvidia/6.8.0-1028.31
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-nvidia' to 'verification-done-
noble-linux-nvidia'. If
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.4.0-1151.158) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/unknown (amd64, i386)
Please visit the excuses page listed below a
This might be related to bug 2107597.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2102006
Title:
Xorg freeze
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
Thanks. I forgot to mention; please also tell us the date and time the
freeze occurred :)
** Tags added: i915 nvidia
** Tags added: hybrid multigpu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/21020
This might be related to bug 2102006 or bug 2108692.
** Tags added: hybrid i915 multigpu
** Tags added: freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107597
Title:
[i915 + Nvidia + Xorg] E
** Tags added: nvidia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2108692
Title:
One screen freezes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/
** Description changed:
I experience drop frame using 0.40.0-3ubuntu1. Here are the ways that
can reproduce the situation on my laptop:
+ ```
# Download a 720p VP9.2 60fps sample video from Youtube
yt-dlp -f 334+249 LXb3EKWsInQ -o test.webm
# Play the video
mpv test.webm --fs --star
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
For months now using the latest/candidate/core24 channel of the firefox
snap has worked to reactivate the Nvidia driver (both on 24.10 and
25.04). However, I just got an update for the snap that breaks this even
in that channel. :(
--
You received this bug notification because you are a member of
** Tags added: kubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106202
Title:
Kubuntu 24.10 do-release-upgrade and Steam (or other) dependencies
installed produces not booting desktop
To m
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
Tesiing the upgrade procedure with method in #1 on bare metal, pristine
24.10 fully updated with steam.deb from the Steam website: upgrade was
flawless!
Again, this upgrade experience is so much faster and issue free than it
has been for several cycles.
I will attempt an upgrade with Ubuntu's Str
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
** Merge proposal linked:
https://code.launchpad.net/~juliank/update-manager/+git/update-manager/+merge/485017
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2109339
Title:
Test suite failures: D
*** This bug is a duplicate of bug 2097605 ***
https://bugs.launchpad.net/bugs/2097605
I'm marking this one as a duplicate of bug 2097605, as it's included in
the 19.2.1 release according to upstream [0][1]. We should get 19.2.1
released instead, given Ceph already has an SRU exception as part
** Merge proposal linked:
https://code.launchpad.net/~juliank/update-manager/+git/update-manager/+merge/485017
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2109340
Title:
Test suite failures: s
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
FWIW, We don't have a dedicated questing upload, but the plucky one is
in the main branch so it's queued in git regardless (or we copy it up).
** Changed in: update-manager (Ubuntu Noble)
Status: New => In Progress
** Changed in: update-manager (Ubuntu Plucky)
Status: New => In Pro
** Changed in: linux (Ubuntu Oracular)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2109301
Title:
Oracular update: upstream stable patchset 2025-04-24
** Changed in: linux (Ubuntu Plucky)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2108854
Title:
Plucky update: v6.14.3 upstream stable release
To manag
** Description changed:
[ Impact ]
* On Jammy FIPS, gpg prints a warning "out of core handler ignored in
FIPS mode" on every single command. Listing keys, exporting keys,
running the help command, and even tabbing to autocomplete commands
produces this warning.
* It's not neces
FWIW, We don't have a dedicated questing upload, but the plucky one is
in the main branch so it's queued in git regardless (or we copy it up).
** Changed in: update-manager (Ubuntu Plucky)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
The autopkgtests for APT have passed on all releases, so marking the bug
as verified per the test plan (as the test suite includes the tests for
this bug).
All regressions except for update-manager/noble have been resolved by
retries. The update-manager regressions in noble are caused by the
chang
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Journal while logging in without moving the mouse with MUTTER_DEBUG=kms
** Attachment added: "prevjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2089709/+attachment/5874220/+files/prevjournal.txt
--
You received this bug notification because you are a member of Ubunt
Journal while logging in moving the mouse with MUTTER_DEBUG=kms
> Repeat step 3 until the bug happens again.
For what it's worth the bug is repeatable 100% of the time. just start
moving the mouse when logging in and keep moving it for 10 seconds or
so, long enough so that it's obvious that the G
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
Aborted due to failure (While pulling
runtime/org.gnome.Platform/x86_64/48 from remote flathub: opcode set-
read-source: Opening content object
ba1db158e80cb2200b3eb2a5ee65c28393bcf12baddc28b54e96a02dfb4c7bfd:
Opening content object
ba1db158e80cb2200b3eb2a5ee65c28393bcf12baddc
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Bug report did not expire due to bug watch
Upstream issue closed "RESOLVED NOTOURBUG" on 2015-03-25
No response to comment #2 so closing as bug report is no longer valid
** Changed in: hundredpapercuts
Status: Incomplete => Invalid
** Changed in: fontconfig (Ubuntu)
Status: Incomple
@fuchanglin Intel released firmware for this card but it requires a 6.14
kernel. We'll soon have an HWE 6.14 kernel in Noble. In the meantime, you can
either install the plucky kernel from:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/30614565
or the latest mainl
This issue is still present on Ubuntu 22.04 to 24.04 upgrade process.
Quick workaround is just creating ``/var/lib/cephadm`` before start any
upgrading.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
Public bug reported:
iwlwifi driver not loading
it works fine in kernel 6.12
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-modules-6.14.0-1002-realtime 6.14.0-1002.2
ProcVersionSignature: Ubuntu 6.14.0-1002.2-realtime 6.14.0
Uname: Linux 6.14.0-1002-realtime x86_64
ApportVersion: 2
Public bug reported:
Easyeffects can not open some of the calf related .so files because they
point to a /build path.
Failed to open library /usr/lib/lv2/calf.lv2/calf.so
(/usr/lib/lv2/calf.lv2/calf.so: cannot open...
$ ls -la /usr/lib/lv2/calf.lv2/
...
lrwxrwxrwx 1 root root 80 Mar 26 01:0
There are so many problems experienced on these systems. I opened the bug but
since I have upgraded kernel
6.8.0-58-generic and driver to 550.120. However, monitors keep misbehaving
where by sometimes one monitor will not work, others after sleeping one will
die and i have to set to join monit
Yes, this is a known issue in pemmican
(https://github.com/waveform80/pemmican/issues/1) but last time I looked
into it (admittedly last year), I didn't manage to find anything that
looked like a "proper" solution. In other words, everything wound up
being some variation of "back-off and restart" (
Anyway, I'll leave this open (and bookmark it) as a periodic reminder I
should look at this again and see if I can come up with a better
solution than the current horrid hack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-550 (Ubuntu Plucky)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-550 (Ubuntu Oracular)
Status: New => Invalid
** Summary changed
Ok. It's not an important issue at all.
In my case it's just starting 1 second early... Putting an "sleep x"
before the command exec should work but it's not an elegant solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Hello Arnaud, or anyone else affected,
Accepted gnome-shell-extension-ubuntu-dock into noble-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/90ubuntu3 in a few hours, and then in the -proposed repository.
Please help
On 25/04/2025 04:54, Darin Miller wrote:
> With libc6:i386 installed and using the procedure mentioned in #1
> (thanks Rik!), the ugrade worked perfectly! It also fixed the issue
> with the agonizing slow "Searching for software" step
Fantastic!
We now need some validation for when steam is insta
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
** Changed in: plasma-discover (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/2077103
Title:
upgrade snapd-glib to v1.65 - Qt6 port required to build
As discussed before and documented in the bug description, we are
ignoring this for verification purposes, and setting this to done. The
bug will be reopened once the update has been released to be fixed
properly in a future upload.
** Tags removed: block-proposed block-proposed-noble verification
The autopkgtests for apt/noble have passed; per the documented test plan
> To validate the APT change on noble, we must rely on the test suite as
we won't have a noble->oracular upgrade bug causing it, most likely.
I am hence setting this to verification-done-noble.
** Tags removed: verification
6.8.0-1022.26 was superseded by 6.8.0-1024.28.
Installed linux-raspi/6.8.0-1024.28 from noble-proposed and verified
CONFIG_SERIAL_8250_NR_UARTS is set to 16.
$ uname -a
Linux rpi-cm5-4gb-rev1d0-1f53 6.8.0-1024-raspi #28-Ubuntu SMP PREEMPT_DYNAMIC
Thu Apr 17 12:20:20 UTC 2025 aarch64 aarch64 aarc
6.8.0-1022.26 was superseded by 6.8.0-1024.28.
Installed linux-raspi/6.8.0-1024.28 from noble-proposed and verified
GPIO_SYSFS is enabled.
$ uname -a
Linux rpi-cm5-4gb-rev1d0-1f53 6.8.0-1024-raspi #28-Ubuntu SMP PREEMPT_DYNAMIC
Thu Apr 17 12:20:20 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
$ sud
** Changed in: ceph (Ubuntu Oracular)
Status: Triaged => In Progress
** Changed in: ceph (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: ceph (Ubuntu Noble)
Assignee: (unassigned) => Peter Sabaini (peter-sabaini)
** Changed in: ceph (Ubuntu Oracular)
Assignee
You're welcome, but can you verify that that firmware is actually
working with the 6.14 so I can start the process of adding it to the
linux-firmware package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Installed linux-raspi/6.8.0-1024.28 from noble-proposed and verified
that a CM5 not boots successfully from eMMMc.
$ uname -a
Linux rpi-cm5-4gb-rev1d0-1f53 6.8.0-1024-raspi #28-Ubuntu SMP PREEMPT_DYNAMIC
Thu Apr 17 12:20:20 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
$ sudo dmesg | grep -i mmc
[
** Changed in: ceph (Ubuntu Oracular)
Status: Triaged => In Progress
** Changed in: ceph (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: ceph (Ubuntu Noble)
Assignee: (unassigned) => Peter Sabaini (peter-sabaini)
** Changed in: ceph (Ubuntu Oracular)
Assignee
All autopkgtests for the newly accepted tzdata (2025b-0ubuntu0.22.04.1) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
chrony/unknown (amd64)
libical3/unknown (amd64)
php8.1/unknown (amd64, ppc64el)
postgresql-14/unknown (amd64)
py
I first upgraded apt, libapt-pkg6.0t64 to 2.8.3.
Validation for RSA1024 remaining weak:
root@noble:~# gpg --quick-gen-key j...@debian.org rsa1024
gpg: directory '/root/.gnupg' created
gpg: keybox '/root/.gnupg/pubring.kbx' created
We need to generate a lot of random bytes. It is a good idea to
Thanks, Frank!
Debian has already fixed this, so we will get this in questing via the
next merge of coreutils, but I think it's fine to upload now anyways. So
I will sponsor for questing.
The plucky debdiff LGTM, too. Just a couple requests for the SRU test
plan. Looking at the coreutils source,
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
1 - 100 of 226 matches
Mail list logo
