** Tags removed: verification-needed-focal-linux-riscv-5.15
** Tags added: verification-done-focal-linux-riscv-5.15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2096917
Title:
Revert addition of dw
** Changed in: linux (Ubuntu Noble)
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/2097301
Title:
Noble update: upstream stable patchset 2025-02-03
To man
** Changed in: linux (Ubuntu Jammy)
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/2097298
Title:
Jammy update: v5.15.177 upstream stable release
To manag
** 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/2097413
Title:
Oracular update: upstream stable patchset 2025-02-05
** 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/2097531
Title:
Oracular update: upstream stable patchset 2025-02-06
The following commits are skipped (dropped):
* iommu/vt-d: Remove cache tags before disabling ATS
(Reason: CVE backport has been done and ACK-ed at the same time)
** Changed in: linux (Ubuntu Oracular)
Status: In Progress => Fix Committed
--
You received this bug notification because y
The following commits are skipped (dropped):
* selftests: net: Remove executable bits from library scripts
(Reason: Empty commit. Also, Noble innately has the original patch.)
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification
** Changed in: linux (Ubuntu Noble)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Oracular)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided =>
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Oracular)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
Importance: Undecide
** Changed in: linux (Ubuntu Focal)
Status: New => 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/2095376
Title:
net: stmmac: kernel continually prints wol unbalance irq warning
h: btusb: mediatek: change the conditions for ISO interface
ALSA: ump: Shut up truncated string warning
UBUNTU: Upstream stable to v6.6.69, v6.12.8
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Oracular)
Importance: Medium
Assignee
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
tream stable to v6.6.68, v6.12.7
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Oracular)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed
: Upstream stable to v6.6.67, v6.12.6
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Oracular)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Ch
** 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/2096744
Title:
Oracular update: upstream stable patchset 2025-01-27
** 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/2096827
Title:
Oracular update: upstream stable patchset 2025-01-28
** 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/2095594
Title:
Oracular update: upstream stable patchset 2025-01-23
** Also affects: linux-riscv-5.15 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-riscv-5.15 (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Public bug reported:
LP#2086606 introduced the use of the dwarfdump command in
debian/rules.d/2-binary-arch.mk, but on some architectures (at least
riscv64), the dwarfdump package does not appear to function as expected.
Until the issue is resolved, revert this change in
debian/rules.d/2-binary-ar
** Description changed:
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 originat
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Assignee: (unassigned) =>
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:
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
Status: Invalid
** Affects: linux (Ubuntu Oracular)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-b
** Changed in: linux (Ubuntu Oracular)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20892
** Changed in: linux (Ubuntu Jammy)
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/2095283
Title:
Jammy update: v5.15.174 upstream stable release
To manag
** Changed in: linux (Ubuntu Jammy)
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/2095327
Title:
Jammy update: v5.15.176 upstream stable release
To manag
** 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/2095145
Title:
Focal update: v5.4.287 upstream stable release
To manage
** 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/2095199
Title:
Focal update: v5.4.288 upstream stable release
To manage
** Changed in: linux (Ubuntu Jammy)
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/2095302
Title:
Jammy update: v5.15.175 upstream stable release
To manag
** 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/2095437
Title:
Focal update: v5.4.289 upstream stable release
To manage
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Oracular)
Importance: Undec
I can't seem to create an account on the freedesktop gitlab. Is there
another way to file a bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092284
Title:
[Sony Vaio VPCF11M1E] nouveau driver in
es to prevent infinite Loop in
throttle_direct_reclaim()
Linux 5.15.176
UBUNTU: Upstream stable to v5.15.176
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status:
tu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tag
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) =>
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
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Noble)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I just tried to see if a newer BIOS is available, but unfortunately for
my model no downloads are available anymore as support has been dropped.
(See https://www.sony.nl/electronics/support/laptop-pc-vpc-
series/vpcf11m1e/downloads)
What's the process from here? It probably is a quirk for this mac
No I can't select anything on the login screen, This happens during the
launch of the installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092284
Title:
[Sony Vaio VPCF11M1E] nouveau driver
When booting into Arch, you will just boot into the terminal, but here
the resolution seems to be bigger than the screen.
** Also affects: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided
Status: New
** Also affects: archlinux
Importance: Undecided
Status: New
--
Yo
That is not possible for me. The GT330M was supported by the nvidia 340
driver, but that driver is unsupported. The GT330M is not supported in
newer versions of the nvidia driver. `ubuntu-drivers` does not list any
drivers either. It does on LTS 22.04 though.
--
You received this bug notification
Public bug reported:
When booting the installation of 24.04 (LTS) I will be presented with a
nice screen. However the resolution is wrong. My screen is actually
1920x1080. However the installation uses a resolution of 2048x1536. It's
a wrong aspect ratio as well, 16:9 vs 4:3.
The weird thing is t
Thanks for the report. We'll handle to address the issue. SRU patch sent
to ML: https://lists.ubuntu.com/archives/kernel-
team/2024-December/156028.html
SRU Justification
[Impact]
Upstream commit 0bfcb7b71e73 ("netfilter: xtables: avoid NFPROTO_UNSPEC
where needed") was backported to Oracular an
Hard to understand how Canonical keeps on breaking trivial Linux things
that have been working for decades and allowing this to exist for nearly
one and a half year now without decent work arounds.
I checked the new security app, there is no way to allow these snaps
access to the directory where c
** Tags removed: verification-needed-jammy-linux-kvm
** Tags added: verification-done-jammy-linux-kvm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085082
Title:
Cannot detect audio sinks and sourc
It landed in 6.8.y (v6.8.12) and Noble has no longer been affected since
6.8.0-40.40.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067291
Title:
ftrace:test.d--dynevent--add_remove_btfarg.tc in
Patch series sent to ML: https://lists.ubuntu.com/archives/kernel-
team/2024-December/155884.html
SRU Justification
[Impact]
Since upstream commit c8bd1f7f3e61 ("virtio_net: add support for Byte Queue
Limits"), BQL crashes have been observed. One crash pattern was addressed
by upstream commit b9
The following patch series were merged to net tree:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=00301ef4b26d551141c96efeebff40904241f594
Once it reaches mainline, I'll submit backport to KTML (with opening
another bug tracker).
--
You received this bug notification
** Description changed:
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 originat
** Description changed:
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 originat
he number of concurrent async COPY operations
drm/sched: revert "Always increment correct scheduler score"
ALSA: control: Fix leftover snd_power_unref()
UBUNTU: Upstream stable to v6.6.55, v6.10.14
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects:
Public bug reported:
Next failures are reported with fwts V24.11.00:
High failures: 3
smm: Graphics Control register is not locked (GGCLCK != 1).
smm: TSEG Memory Base register is not locked.
smm: Top of Low Usable DRAM (TOLUD) register is not locked.
The registers checked do not exist on the
"Unhandled exception 6 #UD" issue which Mehmet had written in comment#4
was also seen in 2024.10.28/noble/linux-lowlatency/6.8.0-50.51.1 on
testflinger amd64 node bomberto.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
It's been a year since I have made this bug report. I no longer use this
configuration, but since there was no further activity I consider this
bug to be no longer relevant and should be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Link: https://bugs.launchpad.net/bugs/2083823
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088065
Title:
hardlink permission denied in selftests
To manage notifications about this bug go to:
http
Link: https://bugs.launchpad.net/bugs/2083819
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088064
Title:
kmem permission denied in selftest
To manage notifications about this bug go to:
https://b
v6.6.53, v6.10.12
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
** Description changed:
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 originat
or when find_module() is not available
drm/xe/display: fix compat IS_DISPLAY_STEP() range end
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Prog
I got the same error on Ubuntu 24.04 LTS as well.
This issue is very annoying once again.. And not solved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1998865
Title:
apt-cacher-ng corrupt/bad fi
Well I was trying to upgrade a Linux system connected to apt-cacher-ng,
and not just a single package upgrade, but an major distro upgrade..
Well that didn't went well.. DlMaxRetries was already set to 200, I
needed to raise DlMaxRetries to 900...
Server side:
1729628723|E|697|192.168.1.194|ubure
For f:linux-kvm, this should be an expected behavior since:
* f7e33bdbd6d1 ("fs: remove mandatory file locking support") [1] is not
backported
* CONFIG_MANDATORY_FILE_LOCKING=n
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f7e33bdbd6d1bdf9c3df8bba5abcf3399f957
Same issue indeed (also without PPAs).. Still present in 2024. First
time trying to use apt-cacher-ng. Great experience (NOT).
Hopefully increasing DlMaxRetries helps, but I have the feeling something is
wrong.. Is Apt-cacher-ng creating the 503 errors? Or the upstream repository?
That is not c
** Description changed:
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 originat
s
UBUNTU: Upstream stable to v6.6.49, v6.10.8
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed i
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) =>
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
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) =>
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
og_pipe_topology_update
UBUNTU: Upstream stable to v6.6.46, v6.10.5
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Progress
** Tags: kernel-stable-track
to v6.6.45, v6.10.4
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
@kelv No, I don't think the do-release-upgrade command allows you to by-
pass this check. So try what Mitchell just said above your comment, try
to remove rabbitmq-server instead. Try proceed with the Ubuntu upgrade
using do-release-upgrade CLI command. And finally try to install
RabbitMQ & recreat
cket
cx82310_eth: fix error return code in cx82310_bind()
Linux 5.4.284
UBUNTU: Upstream stable to v5.4.284
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Sta
UNTU: Upstream stable to v5.15.167
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Koichiro Den (koichiroden)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in:
I am also affected. And was stopped nicely by the do-release-upgrade
command. Hopefully RabbitMQ can soon fix this issue, so I can upgrade my
Ubuntu Server to 24.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
oup in
remove_power_attributes()
net: dsa: mv8e6xxx: Fix stub function parameters
scsi: aacraid: Fix double-free on probe failure
Linux 5.4.283
UBUNTU: Upstream stable to v5.4.283
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
ree on probe failure
apparmor: fix policy_unpack_test on big endian systems
Linux 5.15.166
UBUNTU: Upstream stable to v5.15.166
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Koichiro
containerd seems to have similar issues from Kubernetes... (I need to
check if a bug exists for that as well)
kubelet.go:2049] [failed to "KillContainer" for "ceph-exporter" with
KillContainerError: "rpc error: code = Unknown desc = failed to kill container
\"373f6f3fc02b903a49b6d5e330366944e9c
a: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error"
Linux 5.15.165
UBUNTU: Upstream stable to v5.15.165
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Koichiro Den (koichirod
de
media: Revert "media: dvb-usb: Fix unexpected infinite loop in
dvb_usb_read_remote_control()"
Linux 5.4.282
UBUNTU: Upstream stable to v5.4.282
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Me
There's an addititional problem though: to make mod_evasive send mails
properly it should be using mailx -t, but that'd most likely break
alternatives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/189
Disregard my issue with my second machine, it didn't have the 'UUID='
part in /etc/default/grub. Adding that solved the issues with that
machine as well. So definite +1 solved for me.
That does lead to the question, why doesn't forgetting to add 'UUID='
give a better error message, and instead giv
actually, I jumped the gun on my 2nd machine which is a laptop. It's
showing a completely wrong major/minor of: 2623:602885, the
resume_offset in /sys/power is the same as my grub/cmdline though. My
major/minor should be 259:1
--
You received this bug notification because you are a member of Ubun
enabled proposed, but the update didn't come automatically. Manually
selected the newer version with aptitude. Can confirm this works on 2
machines now. Awesome! But what a regression in the first place? I had
to search pretty hard to find this.
--
You received this bug notification because you a
This was a clear regression introduced in:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?h=master-
next&id=c30411266fd67ea3c02a05c157231654d5a3bdc9
Fixed in: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/unstable/commit/?id=3c2ea5ec1d86d073
Some issue on 24.04:
root@noble ~ # curl -s https://launchpadlibrarian.net/250515419/test.html |
html2text; echo $?
Input recoding failed due to invalid input sequence. Unconverted part of text
follows.
“Test�?)
0
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi , i have the trash not working too , impossible to put item with
externals partitions on ubuntu 22.04 :
[code]
iznobe@iznobe-PC:~$ cat /etc/os*release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LI
Yes, that backport works for me. However, we want it in Focal as well.
How do we get that fixed?
A sponsor is needed? I can say the code works, but how to resolve the
backport issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Is there a way I can help here?
The code works and we are happy with it. What else is needed to get the
packages into 22.04 Jammy?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962743
Title:
[BPO]
Public bug reported:
installer hangs when creating root partition
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.8
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5Ch
Public bug reported:
it is the installer when kubuntu 22.94 is started in a virtual machine
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.7
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Archi
See the attached file where I used the PPA from Fantu with an updated
version of freeipmi.
The Lan6_Conf section is back as expected.
And yes, this seems like a major regression to me. This all worked fine
under Ubuntu 18.04 LTS and is suddenly removed when going to a newer LTS
version.
We depen
I would love to test this with a PPA package on one of our systems.
We rely on IPv6 for our IPMI systems and have now noticed this has
broken after upgrading to 20.04
We follow a rather 'slow' process. We usually use HWE kernels for a
longer period prior to upgrading. This is now breaking many of
I tried this on two Dell R6525 machines running. One with 18.04 the
other with 20.04
On the 20.04 machine the Lan6_Conf section is missing.
** UBUNTU 18.04 **
root@hv-138-e14-25:~# dmidecode memory|grep R6525
Product Name: PowerEdge R6525
SKU Number: SKU=NotProvided;ModelName=Po
Thank you for the response!
ii freeipmi-common 1.6.4-3ubuntu1.1
all GNU implementation of the IPMI protocol - common files
ii freeipmi-tools1.6.4-3ubuntu1.1
amd64GNU implementation of the I
Public bug reported:
In bug #1645912 support for the Lan6_Conf section was added:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1645912
This also worked on our Ubuntu 18.04 systems, but does not seem to work
anymore on our Ubuntu 20.04 systems.
We use these systems:
- SuperMicro AS-11
same at 20.04.2 after an upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789544
Title:
smbd.service failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
Public bug reported:
We have recently seen seemingly random kernel panics on one of our
instances in Google Compute Engine, running the `linux-gcp-5.11` kernel
on Ubuntu 20.04.
The crashes happened weeks apart and seem to occur randomly, we have not
found a way to consistently trigger the crashes
I just installed geonkick from impish proposed and geonkick is found and makes
sound.
I did see did dpkg -l geonkick lists /usr/lib/x86_64-linux-gnu , just the dir,
no files.
Rob van den Berg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
1 - 100 of 1109 matches
Mail list logo
