You are not logged in.
EDIT 2023/12/16
A fixed kernel is now available in Debian stable-updates, which is enabled in BunsenLabs by default, so a normal apt upgrade should work normally.
See:
https://forums.bunsenlabs.org/viewtopic … 49#p130849
A bug has been found in the latest kernel in the Bookworm repository, 6.1.64-1 which might cause data coruption on ext4 filesystems! (This is the default file system.)
https://www.debian.org/News/2023/2023120902
https://bugs.debian.org/cgi-bin/bugrepo … ug=1057843
Please do not upgrade any systems at this time
On my Boron VM (using Debian bookworm of course):
john@boron-b2:~$ apt policy linux-image-amd64
linux-image-amd64:
Installed: 6.1.55-1
Candidate: 6.1.64-1
Version table:
6.5.10-1~bpo12+1 100
100 https://deb.debian.org/debian bookworm-backports/main amd64 Packages
6.1.64-1 500
500 https://deb.debian.org/debian bookworm/main amd64 Packages
*** 6.1.55-1 100
100 /var/lib/dpkg/status
6.1.52-1 500
500 https://deb.debian.org/debian-security bookworm-security/main amd64 Packages
So an apt upgrade would bring in the buggy kernel!
Please don't run 'sudo apt upgrade' on a Boron system untill the fixed kernel ( 6.1.66-1 ) has arrived in the repository and is shown as the Candidate in 'apt policy linux-image-<your architecture>'.
Last edited by johnraff (2023-12-16 02:37:44)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
Posted this over at Lilidog Linux as well
Thank's John.
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline
Debian have pushed out the new kernel for Bookworm: linux-image-amd64 and linux-image-686 are now at 6.1.66-1
It should now be safe to upgrade as normal.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
Just want to mention... the upgrade to 6.5.10 via backports, shown as available in your first post, might fix issues for those on amd64 with newer hardware...
sudo apt install -t bookworm-backports linux-img-amd64
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
^Sure the backports kernel is available to me because I enabled bookworm-backports.
That goes to 6.5.10-1 which is way out of the danger zone, and already was before this alert went out.
Some people upgrade to the backported kernel to fix hardware issues, but I never recommend backported packages unless there's an actual need. Just in case of hidden snags - backports get less testing than regular packages.
This warning was about the regular Bookworm stable kernel anyway.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
Oh Dear.
The quickly released kernel 6.1.66-1 has two new bugs!
Don't upgrade yet especially if you are using wifi or certain Lenovo machines!
These two bugs:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1057967
https://bugs.debian.org/cgi-bin/bugrepo … ug=1057969
The fixed kernel 6.1.67-1 has already entered the Debian archive, so we can expect it to arrive in Bookworm/stable very soon, I'd guess today or tonight.
Do:
sudo apt update && apt policy linux-image-amd64
(or linux-image-686 for 32 bit).
When Candidate: goes from 6.1.66-1 to 6.1.67-1 then it should be safe to upgrade.
Here's a helpful post on Debian-Users that explains the issue and also Debian kernel version numbering, which is a bit complicated:
https://lists.debian.org/debian-user/20 … 00680.html
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
workaround no longer needed
EDIT: it is no longer necessary to use the bookworm-proposed-updates repository as described in this post.
See below:
https://forums.bunsenlabs.org/viewtopic … 49#p130849
The unbugged kernel 6.1.67-1 has still not arrived in the Bookworm stable-updates repository. It might appear today, or maybe not for a month, because the two bugs, although labelled "serious" are also "Fixed in version linux/6.1.67-1", and upgrading the kernel package itself is only marked "Urgency: medium".
EDIT: don't do this:
All is not lost, however, because the 6.1.67-1 kernel is available in thebookworm-proposed-updates repository. That's for packages that will be incorporated in the next Debian point release (12.5 in this case).
So if you want to upgrade your system and move on without worrying about the buggy 6.1.66-1 kernel, you can add bookworm-proposed-updates to your Debian sources, upgrade and then comment out the apt sources entry. (There are relatively few other packages in bookworm-proposed-updates right now so the chances of pulling in unwanted guests is low.) Like this:
pkexec bl-text-editor /etc/apt/sources.list
Copy in this code snippet at the bottom:
# proposed updates for the next point release
deb https://deb.debian.org/debian bookworm-proposed-updates main contrib non-free non-free-firmware
Check that linux-image-amd64 (or 686) now has a candidate of 6.1.67-1:
sudo apt update && apt policy linux-image-amd64
If it looks OK then you can do:
sudo apt upgrade
When that's all done, comment out the bookworm-proposed-updates line you added to sources.list, and get on with your life.
EDIT: If you have bookworm backports enabled, then don't comment out the bookworm-proposed-updates line until 6.1.67-1 has arrived in the regular stable repository. Otherwise apt will prompt you to upgrade the kernel to the backports version 6.5.10-1~bpo12+1. Not the end of the world, but if you want to stay as close to the stable distro as possible, then maybe better to keep 6.1.67-1 .
EDIT2: Now the package is in stable-updates which is normally enabled anyway, the problem with backports dissapears. See: https://forums.bunsenlabs.org/viewtopic … 49#p130849
---
Reference:
https://www.debian.org/releases/proposed-updates
https://wiki.debian.org/StableProposedUpdates
Last edited by johnraff (2023-12-16 02:32:40)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
Smooth as silk:
$ apt list --upgradable
Listing... Done
libfreetype6/proposed-updates 2.12.1+dfsg-5+deb12u2 amd64 [upgradable from: 2.12.1+dfsg-5]
libpipewire-0.3-0/proposed-updates 0.3.65-3+deb12u1 amd64 [upgradable from: 0.3.65-3]
libpipewire-0.3-common/proposed-updates 0.3.65-3+deb12u1 all [upgradable from: 0.3.65-3]
libpipewire-0.3-modules/proposed-updates 0.3.65-3+deb12u1 amd64 [upgradable from: 0.3.65-3]
libspa-0.2-bluetooth/proposed-updates 0.3.65-3+deb12u1 amd64 [upgradable from: 0.3.65-3]
libspa-0.2-modules/proposed-updates 0.3.65-3+deb12u1 amd64 [upgradable from: 0.3.65-3]
linux-image-amd64/proposed-updates 6.1.67-1 amd64 [upgradable from: 6.1.66-1]
linux-libc-dev/proposed-updates 6.1.67-1 amd64 [upgradable from: 6.1.66-1]
pipewire-alsa/proposed-updates 0.3.65-3+deb12u1 amd64 [upgradable from: 0.3.65-3]
pipewire-audio/proposed-updates 0.3.65-3+deb12u1 all [upgradable from: 0.3.65-3]
pipewire-bin/proposed-updates 0.3.65-3+deb12u1 amd64 [upgradable from: 0.3.65-3]
pipewire-pulse/proposed-updates 0.3.65-3+deb12u1 amd64 [upgradable from: 0.3.65-3]
pipewire/proposed-updates 0.3.65-3+deb12u1 amd64 [upgradable from: 0.3.65-3]
15 Dec 23 @ 09:56:27 ~
$ sudo apt upgrade
$ apt policy linux-image-amd64
linux-image-amd64:
Installed: 6.1.67-1
Candidate: 6.1.67-1
Version table:
*** 6.1.67-1 100
100 /var/lib/dpkg/status
6.1.66-1 500
500 https://deb.debian.org/debian bookworm/main amd64 Packages
6.1.52-1 500
500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline
The new kernel metapackage has arrived in Debian updates
It is no longer necessary to use the Debian Proposed Updates repository as described above because the upgraded linux-image-amd64 package has arrived in Debian Updates:
https://lists.debian.org/debian-stable- … 00002.html
BunsenLabs systems have stable-updates enabled by default, so if you added bookworm-proposed-updates as above, you can delete the line, and a simple 'sudo apt update && sudo apt upgrade' should be enough to get the safe kernel.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online