Public bug reported:
Can't update from 22.04 to 24.04
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.19
ProcVersionSignature: Ubuntu 6.5.0-44.44~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture:
** Tags added: oracular
** Summary changed:
- lock screen leaves left dock exposed and clickable
+ Ubuntu Dock appears on lock screen if Dash-to-Panel is enabled at the same
time
** Changed in: ubuntu
Importance: Undecided => Low
** Changed in: ubuntu
Status: Incomplete => Triaged
*
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
** Package changed: ubuntu-meta (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/2068904
Title:
Screen restarts and logs out when disconnecting HDMI cable
To manage no
A segfault is unexpected, otherwise I would have just assumed this was
bug 2050865...
To help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look
Maybe this is still bug 2050865, and the segfault in the log isn't from
disconnecting HDMI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068904
Title:
Screen restarts and logs out when disconnecti
If the HDMI port is connected to a secondary GPU then it might be bug
2069565.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068904
Title:
Screen restarts and logs out when disconnecting HDMI cable
*** This bug is a duplicate of bug 1966418 ***
https://bugs.launchpad.net/bugs/1966418
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evolution (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ub
*** This bug is a duplicate of bug 2009672 ***
https://bugs.launchpad.net/bugs/2009672
I reported this bug against xorg. I wonder why it is set to
xfce4-settings package? The issue is also when I use xrandr to change
modes. How could it be desktop environment specific? Well, maybe it does
not
Hi Michael,
with Swap file >2 times of MEm size, the stress test on CPU/MEM still
fail as time out. see attachment "Stress-SR950V3-0722.zip" for detailed
info reference.
besides, I do the other investigation, separate the CPU and MEM stress, till
now, CPU Stress still failed as below, MEM stress
** Attachment added: "Stress-SR950V3-0722.zip"
https://bugs.launchpad.net/ubuntu/+bug/2069674/+attachment/5799236/+files/Stress-SR950V3-0722.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/206967
I can confirm the issue as well, and can also confirm that changing TZ
from ETC to UTC fixes the issue for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070285
Title:
package tzdata 2024a-3ubu
Occurs with 5.15.0-115-generic, too. That is the current default kernel
of Xubuntu 22.04.
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009672
Title:
Regression: Unable to sh
*** This bug is a duplicate of bug 2009672 ***
https://bugs.launchpad.net/bugs/2009672
It was assigned to xfce4-settings because the attached logs suggest Xorg
and the kernel both recognise the 60Hz mode correctly. So far it only
looks like xfce4-settings failing to display or set it.
--
You
*** This bug is a duplicate of bug 2009672 ***
https://bugs.launchpad.net/bugs/2009672
But since bug 2009672 mentions older kernels work, let's go with that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Please try the latest HWE kernel by running:
sudo apt install linux-generic-hwe-22.04
** Also affects: linux (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.launchpa
Public bug reported:
tracking bug
** Affects: linuxptp (Ubuntu)
Importance: Undecided
Assignee: JP Meijers (jpm)
Status: In Progress
** Changed in: linuxptp (Ubuntu)
Assignee: (unassigned) => JP Meijers (jpm)
** Changed in: linuxptp (Ubuntu)
Status: New => In Prog
** Tags added: ansible
** Tags added: ubuntu-pro
** Tags added: python
** Also affects: ansible
Importance: Undecided
Status: New
** No longer affects: ansible
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** 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/2069140
Title:
RM: minetest [ppc64el riscv64]: no longer builds on archs
To manage notifications about this bug go to:
htt
Also I've noticed in a number of bug reports in the last few years that
more recent kernels have become more fussy about display bandwidth
requirements. So just installing a newer HDMI cable might solve it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Are you sure that this is printed by GRUB? I think it is systemd-stub
that is printing this, which isn't used in classic at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073634
Title:
Enable s
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070438
Title:
Fullscreen direct scanout is not used if you enable the hidden
ex
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068598
Title:
Mutter release 46.2
To manage notifications about this bug go to:
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066902
Title:
Night Light occasionally gets stuck
To manage notifications abou
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070437
Title:
Debug mode MUTTER_DEBUG_TRIPLE_BUFFERING=always doesn't work anymor
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064735
Title:
Update mutter to 46.1
To manage notifications about this bug go to
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063869
Title:
Missing default cursor
To manage notifications about this bug go t
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062377
Title:
Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor th
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061739
Title:
crash in meta_wayland_transaction_commit
To manage notifications a
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2050865
Title:
GNOME Wayland session crashes with
libmutter:ERROR:../src/core/w
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038801
Title:
Secondary GPU frame rates are held back by dynamic-max-render-time
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2026194
Title:
When clicking on some maximized or tiled windows, focus on roughly
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2016013
Title:
gnome-initial-setup doesn't get centered if Desktop Icons NG is loa
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967707
Title:
Nvidia Wayland sessions sometimes flood the log with
"clutter_fra
Thanks, the snap disconnect chromium:password-manager-service worked
btw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073356
Title:
Choose password for new keyring the first time chromium-browser
Public bug reported:
```
GNU Image Manipulation Program version 2.10.34
git-describe: GIMP_2_10_34
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TAR
** Changed in: linux (Ubuntu Focal)
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/2073621
Title:
Focal update: v5.4.279 upstream stable release
To manage
Public bug reported:
Please add support for:
cloud-archive:dalmation
cloud-archive:dalmation-proposed
This will also need to be SRU'd back to noble.
[Impact]
End users have to manually enable the dalmation cloud archive pockets.
[Test case]
sudo add-apt-repository cloud-archive:dalmation
Thank you Tim for continuing on this.
Thanks for all your efforts in comment #6.
I wonder how you can create a new 24.04 and trigger this while I can not.
At some point we need a third person to decide who of us has the uncommon case.
Thanks for tracking down the denial that you are seeing.
This
Hello,
do you have any update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070371
Title:
[VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch
To manage notifications about this bug go
I am also having trouble with this exact error when trying to remove python
3.11.
I am on 23.10 and trying to upgrade to 24.04.
```
~> sudo apt remove python3.11
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed.
Hi, Ubuntu
As we know, this is the platform BIOS flash on our system, why Ubuntu want to
drive the device, I mean does it offer our clients a interface to update UEFI
via OS or for some purposes need to read/write the flash?
If in the future kernel version that include this fixes that can drive t
Notice there are flash-kernel update in noble-proposed and oracular.
Update packages in ppa:ikepanhc/lp2065380 based on those.
--
https://launchpad.net/~ikepanhc/+archive/ubuntu/lp2065380/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
"um: Add winch to winch_handlers before registering winch IRQ" was added for
CVE-2024-39292
"drm/i915/gt: Fix CCS id's calculation for CCS mode setting" was added for
https://bugs.launchpad.net/bugs/2072755
"ASoC: amd: acp: fix for acp platform device creation failure" was added for
https://bug
No, this bug is about failures when using /usr/share/dpkg/buildflags.mk,
but openjdk-8 does include /usr/share/dpkg/buildflags.mk.
openjdk-8 is affected by bug #2071468 instead (which I am working on).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073707
Title:
Lack of Legacy Support information
To manage notifications about this bug go to:
https://bugs.launchpad.
The issue is NOT present in
- cyrus-imapd_3.8.1-1~bpo12+1 from Debian bookworm-backports
- cyrus-imapd-3.8.3-1 from Debian sid
As far as I can tell, this is an issue with the Ubuntu package and not
with upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Uploaded to oracular and to noble for SRU team review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073742
Title:
[SRU] Enable support for Dalmation Cloud Archive
To manage notifications about th
This works too, which is not quite as bad
owner / rw,
On Mon, 22 Jul 2024 at 18:55, Christian Ehrhardt <
2073...@bugs.launchpad.net> wrote:
> Thank you Tim for continuing on this.
>
> Thanks for all your efforts in comment #6.
> I wonder how you can create a new 24.04 and trigger this while I
You are absolutely right. I tried to reproduce this issue on my other PC
and didn't encounter this. Sorry if I bothered you. Thanks.
--
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/2073637
Title
Public bug reported:
Hello,
Since the last ubuntu upgrade, my system become partially unresponsive
(hanging networks at minimum and sometimes full desktop freeze) when I
plug an ethernet cable to the integrated ethrenet port of my laptop. I
can boot with the ethernet cable plugged-in but if I unp
This bug was fixed in the package linux-aws - 6.8.0-1011.12
---
linux-aws (6.8.0-1011.12) noble; urgency=medium
* noble/linux-aws: 6.8.0-1011.12 -proposed tracker (LP: #2070059)
* aws: Backport linear memory map change (LP: #2069352)
- arm64: mm: Don't remap pgtables per-cont
** Patch added: "bpftrace_0.21.0-1ubuntu6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2073120/+attachment/5799284/+files/bpftrace_0.21.0-1ubuntu6.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
@Alexey
Thanks for confirming that this'a hardware failure.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073061
Title:
USB keybo
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1990870
Title:
Cannot update sutton.newell OEM packages since upgrade to LTS 22.04
T
Thanks for the suggestion, but the workaround:
> snap disconnect chromium:dot-local-share-applications
> snap disconnect chromium:dot-local-share-icons
does not work here.
Starting chromium I get:
Jul 22 12:18:28 pc063 chromium_chromium.desktop[4469]:
[4469:4469:0722/121828.188355:ERROR:process_s
Public bug reported:
When running tree --help, or any other way of displaying the 'usage'
text, there is a small typo with the -H flag.
The flag [-H baseHREF] contains two spaces instead of one. This is an
extremely minor bug, but I still wanted to report it.
Tested on:
- Ubuntu 24.04.4 LTS r
Public bug reported:
i was updating my pc and i couldn't continue because of this file.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2
ProcVersionSignature: Ubuntu 6.5.0-44.44~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-44-generic x86_64
ApportV
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/walinuxagent/+git/walinuxagent/+merge/468162
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063046
Title:
build-dep
Public bug reported:
No os-prober entries are added to grub.cfg for alternates systems on
ThinLVM, because of an issue with /usr/lib/linux-boot-probes/50mounted-
tests.
Updating line 55 from :
type="$(grub-probe -d "$partition" -t fs)"
to
type="$(grub-probe -d "$partition" -t fs || echo b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: os-prober (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/1987679
Title:
Tested package on jammy VMs for around week, no gjs crashes detected.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
** Description changed:
+ [ Impact ]
+ Octavia fails to provision Amphora for load balancers.
+
+ [ Test Plan ]
+ Install Octavia as part of a Charmed OpenStack deployment for Caracal.
+ Create a loadbalancer - creation will fail with stack trace from original bug
report.
+
+ [ Where problems c
It indeed also leaves the systems mounted rw on /var/lib/os-prober/mount
: (sys2 is the alternate volume group and system)
# lsof /dev/sys2/rootfs
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
grub-moun 65856 root3r BLK 252,26 0t37912576 1107 /dev/sys2/../dm-26
# ps -ef |grep
** Description changed:
SRU Justification:
==
[Impact]
* A qeth device on a DPM-managed (HMC) IBM Z machine does not obtain its
MAC address for layer2 OSD interfaces from the OSA Network Adapter,
instead it uses a random MAC address.
* This can cause connecti
Marking it as incomplete until logs are attached. Thanks.
** Changed in: ubuntu-advantage-tools (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/2072677
Title:
1 - 100 of 253 matches
Mail list logo
