News for hackers. Stuff that matters.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by mitchweaver on Monday November 16, 2026 @02:34AM (#50515040)
How do I explain this?

I upgraded to Trixie. Stuff broke.

I rolled back to Bookworm, which was extremely painful, because unlike other OSes rollback is not possible and a reinstall is necessary.

Stuff worked again.

Maybe I'll give it another go in 2028 when it goes EOL. Or maybe not. I'm not under any obligation to keep trying.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by walrus01 on Monday November 16, 2026 @02:49AM (#50515117)
I'm not going to take seriously a single person's anecdote of "I upgraded to trixie, stuff broke" when I weigh it against the large number of people I know who run debian stable with very few operating-system-base caused problems for very serious production things.

Your comment is devoid of any useful technical detail on what broke or why, and quite frankly reads like a very linux noob complaint. Leading me to think you did something wrong in the upgrade process, or failed to manually handle any basic configuration files that you were prompted with diffs/merge/install/keep existing version in the upgrade process.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by LtWorf on Monday November 16, 2026 @02:59AM (#50515176)
I mean, linux kernel broke userspace in a couple different instances between oldstable to stable. If his software happened to use those APIs it could crash. Just an example. But a normal person would fix their software (if they have the sources to do that!)
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by csdreamer7 on Monday November 16, 2026 @03:04AM (#50515202)
> Your comment is devoid of any useful technical detail on what broke or why, and quite frankly reads like a very linux noob complaint. Leading me to think you did something wrong in the upgrade process, or failed to manually handle any basic configuration files that you were prompted with diffs/merge/install/keep existing version in the upgrade process.

Why is your first reaction is to assume the person broke something in the upgrade process or did something in the config files? The parent comment is devoid of useful technical detail, but assuming the user is at fault is terrible. Debian is very conservative between releases with not upgrading packages from upstream and keeps a lot out of tree patches. It is very possible something broke between the major versions.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by zettabomb on Monday November 16, 2026 @04:50AM (#50515812)
Classic Linux bro response. Doing a very normal thing (system upgrade) leads to an abnormal result (broken software), blame the user.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by prmoustache on Monday November 16, 2026 @05:15AM (#50515971)
Sruff broke and broken software literally doesn't mean anything.

FWIW people use the very same words when they forgot to turn on the monitor or plug their desktop computer to an outlet.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by LtWorf on Monday November 16, 2026 @08:05AM (#50517194)
> blame the user

The user who is just complaining without providing any sort of useful information that could be used to help them?

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by wrappajack on Monday November 16, 2026 @08:29AM (#50517403)
It doesn’t appear the user is seeking help with the issue, they solved the problem themselves. They seem to be simply advising on their experience with the process.

Not sure how it’s any less valid than your anecdotal experience.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by LtWorf on Monday November 16, 2026 @08:40AM (#50517496)
> they solved the problem themselves

Leaving hundreds of unpatched security vulnerabilities open hardly seems "solving"

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by LtWorf on Monday November 16, 2026 @02:57AM (#50515167)
How do i explain this?

If you don't report the bugs of what breaks (possibly while it's in testing) nobody can help you.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by nbernard on Monday November 16, 2026 @03:05AM (#50515208)
Not GP, but I've been using Debian for 25+ years and, as a user, I still don't understand how to report a bug the right way when it is unclear what package is the cause for a regression...
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by LtWorf on Monday November 16, 2026 @03:24AM (#50515300)
The proper way is to figure out which package is causing a regression.

As an alternative you can report a general bug that will end up on the debian-devel mailing list where someone might reassign it to the proper place. But low effort reports sent to generals are basically a waste of everyone's time.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by LoganDark on Monday November 16, 2026 @04:30AM (#50515682)
This is only economical if you can afford the time wastage yourself. If you need a working system, you don't have the time to fix the bug yourself (hoping you won't find two more by the time you're done)
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by LtWorf on Monday November 16, 2026 @04:31AM (#50515688)
You can pay freexian to fix it for you.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by LoganDark on Monday November 16, 2026 @05:16AM (#50515980)
This is true, if you have the money, and the time to coordinate with them.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by LtWorf on Monday November 16, 2026 @08:29AM (#50517399)
Lol, everyone has a successful startup here but the second you suggest buying for a service (that unlike AI actually provides value) here come the downvotes.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by LoganDark on Monday November 16, 2026 @09:04AM (#50517708)
I don't think it's because it's paid, but because it doesn't entirely solve a time and energy issue.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by nbernard on Monday November 16, 2026 @02:59AM (#50515180)
FYI, for the next time: with Debian, while rollback is not supported, it often works.

I had issues too with Trixie on a laptop (after upgrade everything became unbearably slow, probably due to an Intel graphic chip which was dropped by Mesa or some other library) and did a rollback to bookworm. IIRC, I only had to put back the old apt source entries then apt update and apt dist-upgrade...

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by tremon on Monday November 16, 2026 @06:12AM (#50516293)
> IIRC, I only had to put back the old apt source entries then apt update and apt dist-upgrade...

The problem with rollbacks is not the packages themselves, that usually works without issues. The problem is with configuration and data items: if a package changes configuration format on upgrade (e.g. move from pkg.conf to pkg.conf.d), a downgrade will not restore the old pkg.conf.

Also, apt will not downgrade packages without prodding. At the very least, you would need --allow-downgrades.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by jeroenhd on Monday November 16, 2026 @04:03AM (#50515535)
OS rollback is possible if you've configured it. A combination of btrfs + timeshift has served me very well after a failed Ubuntu upgrade. You can just boot into the previous snapshot from Grub.

Although you can set this up after the fact (converting ext4 to btrfs is supported and you can update your mounts from any recovery distro), that's probably just something to keep in mind for your next fresh install. It's also extremely for any other kind of failed upgrade, though, not just full OS upgrades.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by pvaldes on Monday November 16, 2026 @04:19AM (#50515617)
[delayed]
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by e12e on Monday November 16, 2026 @05:37AM (#50516104)
You didn't have a backup? Or at least make a backup before upgrade?
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by NaaYYs on Monday November 16, 2026 @06:31AM (#50516407)
Was a snapshot before upgrading not possible?
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by alfiedotwtf on Monday November 16, 2026 @07:39AM (#50516976)
Why isn’t Ghost or Time Machine a thing in Linux

(I guess tar czf would work)

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by walrus01 on Monday November 16, 2026 @07:47AM (#50517046)
essentially the same idea as ghost:

https://clonezilla.org/

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by alfiedotwtf on Monday November 16, 2026 @10:52AM (#50518930)
Wow! Thanks.. TIL
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by deltoidmaximus on Monday November 16, 2026 @11:24AM (#50519372)
Linux Mint has Time Shift which you're prompted to setup by default.