Linux-headers-5.10.0-28-amd64 missing

I used

for a while now (to use a docking stating with 2 displays), but after I applied the last updates it stopped working.

I wanted to uninstall and reinstall but it seems it misses a package:
ā†’ linux-headers-5.10.0-28-amd64

dpkg-query: package 'linux-headers-5.10.0-28-amd64' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
linux-headers-5.10.0-28-amd64 not found! Install? [Y/n] Y
Package linux-headers-5.10.0-28-amd64 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'linux-headers-5.10.0-28-amd64' has no installation candidate
linux-headers-5.10.0-28-amd64 installation failed. Aborting.

I saw this thread Is Linux-Headers recommended to be installed? , but it did not gave my any hint how to fix it.

Any idea how to solve this?

(PureOS 10 ā€“ Byzantium)


Yes this issue seems not fixed from PureOs Forum and their Email team is also not assisting anymore :((


PuroOS 10 is based on Debian Bullseye, right (which I noted down ones)?
So the package seems to be available for Debian Bullseye: Debian -- Details of package linux-headers-amd64 in bullseye

I have to admit in detail Iā€™m always confused, but the - page.

Debian has 3 variants/versions and related repos:

  • unstable
  • testing
  • stable

Idk, on which one PureOS is based on, but afair it is testing (there is an old block article, which stated testing, but support told me it is stable in 2021 at least).

So the questions are:

  • On which debian version is PureOS really based on?
  • Is the package ( linux-headers-5.10.0-28-amd64 ) really available this debain version PureOS is based on (or maybe only in unstable :thinking: - where can I see this on )?
  • (if the answer to the two questions above is yes) Why is the package not available in PureOS repos?
1 Like

Byzantium is based on Bullseye, while Crimson is based on Bookworm.


Hi all,

issue seems to be solved now: please see here: Update showing package can be upgraded - #25 by SwissUser .



Thx a lot for sharing and linking to the other thread! @SwissUser

1 Like