Re: No graphical environment with nvidia after upgrade to Trixie 13.2 due to not-installed linux headers package
On Mon 24 Nov 2025 at 09:44:31 (+0100), 94f70f3232557a51a87bcde455bd2dge@vodafonemail.de wrote:
> On 2025-11-23 21:15:49 -0600, David Wright wrote:
> > But what seems to be the main cause of it occurring is the new
> > addition of §4.8
>
> The cause is bug #1091428, dkms depending on the kernel headers without
> declaring a dependency.
There are several bugs that are meant to be closed by the change in
dkms dependencies. I can't judge their competing merits.
> The headers being autoremoved is the effect and
> it is not limited to this particular autoremove action.
If you mean that linux-headers-amd64 might not be removed immediately
with the §4.8 autoremove, but later, that's why I suggested inserting
a subsection on the dkms change somewhere before §5.1.30.
> > [ Step §4.8, ]
> > which doesn't give any warning of an undesired removal of
> > linux-headers-amd64 in this case and potentially many others
>
> Autoremove is not more dangerous than any other remove/purge action.
> Caution is always advised.
That seems to be contradicted by:
> I use autoremove frequently and it had never
> caused any undesired removals before. Perhaps that's why I didn't check
> carefully enough or I just failed to see the consequences.
> >a hint could be added at §5.1.30 about dkms's possible role, and the
> >need to manually install linux-headers-amd64
>
> I'd add this to 5.2 "Items not limited to the upgrade process" (you
> still need to mind the headers if you (un)install dkms later) or even
> 5.4 "Known severe bugs". A package that can stop working at any time
> for no obvious reason is severely buggy IMO.
I'm not sure I would call its severity "Serious or above", as it
doesn't cause data loss or make dkms unsuitable for release. It just
means you have to notice APT's messages, which is easier when you're
forewarned in the Release Notes.
Cheers,
David.
Reply to: