The messages here are mostly in German, but I’ll try to translate mist of it:

**dpkg:** Error when editing the package linux-image-6.9.7+bpo-amd64 (--configure): <<Installed posts installation script of the package linux-headers-6.9.7+bpo-amd64<<-subprocess returned error code 1 **dpgk:** dependency error hinders configuration of <that Linux header package>: linux-headers-6.9.7+bpo-amd64 depends on linux-image-6.9.7+bpo-amd64 (= 6.9.7-1~bpo12+1) | linux-image-6.9.7+bpo-amd64 -unsigned (= 6.9.7-1~bpo12+1); but: Package linux-image-6.9.7+bpo-amd64 is not configured yet. Package linux-image-6.9.7+bpo-amd64-unsigned is not installed. **dpgk:** Error while editing the Package linux-headers-6.9.7+bpo-amd64 (--configure): Dependency problem - remains unconfigured **dpkg:** Dependency problem hinder configuration of linux-headers-amd64: linux-headers-amd64 depends on linux-headers-6.9.7+bpo-amd64 (= 6.9.7-1~bpo12+1); but: Package linux-headers-6.9.7+bpo-amd64is not configured yet. **dpkg:** Errow while editing package linux-headers-amd64 (--configure): Dependency problem - remains in configured Errors occurred while editing these: linux-image-6.9.7+bpo-amd64 linux-headers-6.9.7+bpo-amd64 linux-headers-amd64

I really hope someone can help me out here…

EDIT: I kinda forgot to actually mention my problem. When booting nornall, I get stuck at a lonely white blinking cursor on a black screen, so startx seems to make some problems. I enter a TTY and run startx and this is what I get when running startx:

output of startx

SOLUTION

  • Uninstall your current nvidia driver (for example using sudo apt remove nvidia-driver on Debian)
  • Install the headers for your kernel. your kernel you can check rather easily by running neofetch
  • Install the headers required for your kernel. Do that by listing all packages with your kernel name in it. For example like this: apt list *6.9.7+bpo*
  • reboot, install your nvidia driver again and rovoot again. Should be done.
  • zelifcam@lemmy.worldEnglish
    0·
    4 months ago

    Wow. The terms “nuked” and “bricked” seem to have lost the meaning I grew up with. What you provided is just a simple error.

    It says dependency problem. Have you installed the dependency? It says:

    Package linux-image-6.9.7+bpo-amd64-unsigned is not installed. … linux-headers-6.9.7+bpo-amd64 depends on linux-image-6.9.7+bpo-amd64 (= 6.9.7-1~bpo12+1) | linux-image-6.9.7+bpo-amd64 -unsigned (= 6.9.7-1~bpo12+1);

    Maybe you’re doing too much at once. What happens when you just install the one kernel?

    sudo apt install linux-image-6.9.7+bpo-amd64

    Or maybe try to uninstall the new kernel and its headers. Make sure you have dkms installed and run the apt fix again.

    • Smorty [she/her]@lemmy.blahaj.zoneOP
      0·
      4 months ago

      When trying to install the one kernel I get exactly the same message as the first image in the post. The first error hints at an error in a posts installation script, which I have had issues with before. I used to delete these script to get over errors aaand that worked fine for some time. In case there has been some change in the error I’m getting, I haven’t picked up on it yet. Either way, here’s the output

      EDIT: At the top of the message it says " Newest version already installed" so it seems to be blocking itself? Like I’m trying to install a package and it’s like -But I need that package to build this one-

      • zelifcam@lemmy.worldEnglish
        0·
        4 months ago

        I used to delete these script to get over errors aaand that worked fine for some time.

        I can’t think of one time that I’ve done that in 20 years outside of repackaging applications for work because of crappy vendor supplied packages.

        And you’re sure dkms and the headers are installed?

        In situations like this, if bad enough I would usually temporarily remove mentioned packages until the apt fix works cleanly again and then reinstall whatever I was trying to do. But you’re saying you have removed post install scripts and manipulated packages? Hmm that seems like trouble.

        I’m positive if I was infront of the terminal I could help you out, but I’m starting work for the day. Maybe someone else has a better idea. Sorry bro. But on a positive note, your system is certainly not beyond repair. This seems trivial with a little work and maybe someone who sees the issue better than I right now.

        For others taking a look…. What was the command run before the apt fix?