I’ve been trying the COSMIC store and it looks like it killed my apt somehow. Apt says that there is a version mismatch between some libc6 packages, but I checked with dpkg and it all looks correct.

Apt says that I’ve a newer version of some packages but that is not true. Is there any way to fix this?

EDIT: Fixed formatting

  • nil@piefed.caEnglish
    3·
    6 hours ago

    I suggest you install the stable version (since stability and predictability are the main features of Debian). If you need the latest packages go Arch (or any other rolling-release distro).

    • monovergent@lemmy.ml
      10·
      12 hours ago

      Can also endorse aptitude, but hopefully OP already has it installed prior to this issue. May have to manually install using dpkg if not. Whenever I run into issues like this, aptitude solves it 95% of the time, makes regular apt look like a baby helplessly crying.

      • pewpew@feddit.itOP
        4·
        11 hours ago

        Somehow I can’t even install aptitude trough dpkg because it says that the filesystem is read-only

          • pewpew@feddit.itOP
            7·
            10 hours ago

            No, I just figured it out. I had to enable a systemd service to test Cosmic. I have disabled it and now dpkg works and I manually installed Aptitude with its dependencies.

            I tried to do an upgrade with Aptitude but it won’t do anything. I’ll look into it more later

    • pewpew@feddit.itOP
      2·
      11 hours ago

      What’s the output of apt —fix-broken install, like the big red error message suggests?

      You can see it in the post image. I’m using Debian Unstable

      • stupid_asshole69 [none/use name]@hexbear.netEnglish
        1·
        9 hours ago

        Good looking out. I only saw the one inline with your post body.

        You’re on sid, using cosmic and have a read only root filesystem. Is there anything else out of the ordinary with your computer? You replied to another post that you removed additional repos from sources but did you get the ones in sources.d/?

        E: sources.list.d, not sources.d

  • pewpew@feddit.itOP
    4·
    12 hours ago

    My best guess is that the Debian Unstable repository doesn’t have all the libc6 packages updated to the same version. I might just have to wait and see what happens

    • med@sh.itjust.worksEnglish
      1·
      3 hours ago

      Looks like that might have changed, libc-gconv-modules-extra has an i386 package for 2.42-5 added at like midnight UTC+1. Given the sources only update every 6 hours, might be you found an unlucky update in between?

      Struggled to find a time for the release, but the changelog has one, unsure how true to package-available time that is:

      glibc (2.42-5) unstable; urgency=medium

  [ Martin Bagge ]
  * Update Swedish debconf translation.  Closes: #1121991.

  [ Aurelien Jarno ]
  * debian/control.in/main: change libc-gconv-modules-extra to Multi-Arch:
    same as it contains libraries.
  * debian/libc6.symbols.i386, debian/libc6-i386.symbols.{amd64,x32}: force
    the minimum libc6 version to >= 2.42, to ensure GLIBC_ABI_GNU_TLS is
    available, given symbols in .gnu.version_r section are currently not
    handled by dpkg-shlibdeps.

 -- Aurelien Jarno <aurel32@debian.org>  Sat, 06 Dec 2025 23:02:46 +0100

glibc (2.42-4) unstable; urgency=medium

  * Upload to unstable.

 -- Aurelien Jarno <aurel32@debian.org>  Wed, 03 Dec 2025 23:03:48 +0100
  • DigitalDilemma@lemmy.mlEnglish
    5·
    13 hours ago

    Has it added repos that are conflicting with your distro’s main ones?

    Check /etc/apt/sources.list and all the files in /etc/apt/sources.list.d/

    Move anything that looks sus to somewhere else and then “apt-get clean” and retry.

    • pewpew@feddit.itOP
      4·
      12 hours ago

      Nope. Sources look good. I just removed some I don’t use anymore and then did an apt-get clean but it’s still broken

  • Black616Angel@discuss.tchncs.de
    4·
    13 hours ago

    Try all the cleanup commands, so:

    apt autoremove; apt clean; apt autoclean; apt update

    Then reboot and try again.

    But yes, it looks weird.

      • Black616Angel@discuss.tchncs.de
        7·
        12 hours ago

        Okay, I’ve read into your post a bit more and something is fishy. You have libc6 for different CPU-architectures installed.

        Programs for i368 and amd64 should not be installed on the same machine. The error probably stems from that.

        Run the following to find out the architecture:

        uname -p

        If it says ‘x86_64’ then it’s amd64 and if it’s something like 'i368’ then it’s that. Otherwise, your system might be really borked…

        And then remove the wrong one.

        • TechnoCat@piefed.socialEnglish
          6·
          12 hours ago

          FWIW, installing steam used to also install both architectures on my Fedora machine. I use the flatpak version now because it kept causing conflicts years ago.

    • pewpew@feddit.itOP
      2·
      12 hours ago

      I regularly update using a macro in the terminal that just runs sudo apt update && sudo apt upgrade but this time I decided to install an update via the COSMIC store