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.
If you don't report the bugs of what breaks (possibly while it's in testing) nobody can help you.