I have used Debian on my servers for years and that will never change. Debian is king for servers.

For my desktop, though, I prefer newer desktop environment versions over older ones. Because of that, I have spent time using Arch, Fedora, and NixOS. I genuinely like all of them, but Debian always seems to pull me back.

I currently have Trixie installed and am debating whether to move to Testing or Sid. I have never daily-driven either one before.

I am comfortable with Linux, have used Arch and NixOS without major issues, and do not mind troubleshooting or fixing my own system if something breaks.

For someone like me, which makes more sense as a daily desktop: Debian Testing or Sid?

Also, are apt-listbugs and apt-listchanges the main packages worth installing for either option, or are there other tools and habits you would recommend?

Does anyone know a reason?

This is a genuine question, I wasn't able to find an answer on the Debian wiki, on the mailing lists or on the Debian community forum.

I am currently sporting the 550 driver line which is considered outdated and unsupported by NVIDIA. Games both native and Proton work OK although the latest version of DXVK requires a newer version of the drivers.

Yes, I know I can use the official NVIDIA repo to install the latest drivers. Technically these drivers are meant for the Debian 13 stable release, not for Sid - but people report they work OK.

But that is not the question, I am just curious about the reason.

       _,met$$$$$gg.          lionel@mat-lio-laptop-hp
    ,g$$$$$$$$$$$$$$$P.       ------------------------
  ,g$$P""       """Y$$.".     OS: Debian GNU/Linux forky/sid (forky) x86_64
 ,$$P'              `$$$.     Host: HP Laptop 14-cm0xxx
',$$P       ,ggs.     `$$b:    Kernel: Linux 6.19.14+deb14-amd64
`d$$'     ,$P"'   .    $$$     Uptime: 12 mins
$$P      d$'     ,    $$P     Packages: 3733 (dpkg), 11 (flatpak-system), 4 (flatpak-user)
$$:      $$.   -    ,d$$'     Shell: bash 5.3.9
$$;      Y$b._   _,d$P'       Display (BOE0696): 1366x768 in 14", 60 Hz [Built-in]
Y$$.    `.`"Y$$$$P"'          DE: KDE Plasma 6.6.3
`$$b      "-.__               WM: KWin (Wayland)
 `Y$$b                        WM Theme: Win11OS-dark
  `Y$$.                       Theme: Glass (Alpha 50 Light Blue) [Qt], Breeze_Dark_Glass_50 [GTK2/3/4]
    `$$b.                     Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
      `Y$$b.                  Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
        `"Y$b._               Cursor: Bibata-Rainbow-Modern (28px)
            `""""             Terminal: konsole 25.12.1
                              CPU: AMD Ryzen 3 2200U (4) @ 2.50 GHz
                              GPU: AMD Radeon Vega 3 Graphics [Integrated]
                              Memory: 2.51 GiB / 3.29 GiB (76%)
                              Swap: 1.11 GiB / 5.10 GiB (22%)
                              Disk (/): 69.63 GiB / 105.14 GiB (66%) - ext4
                              Disk (/media/HDD): 63.12 GiB / 893.90 GiB (7%) - ext4
                              Local IP (wlp3s0): 10.164.152.67/24
                              Battery (Primary): 8% [AC Connected]
                              Locale: es_PE.UTF-8

so after a system restart the wifi randomly stopped working because of the drivers and I have no idea how to fix it

I've tried powering in and off and restarting multiple times, loading back one kernel version (not in recovery mode) did not help either

currently 7.0.10 and 7.0.12 are installed and I think its running on. 12

please help

edit: booting into recovery mode did not resolve issue

also have trouble manually reinstalling the firmware since I'm having trouble finding the Linux driver for the ax200 wifi card since Intel listed it as discontinued, and all links to the Linux driver for the card lead to an error page

bluetooth also actually seems to not work but only shows old saved devices

edit 2: issue solved turned off pc and unplugged everything from the wall and waited 5 mins and turned everything back on and it works again

xserver-xorg-core: X server 2:21.1.25-1 crashes

What to do? When apt-listbugs warns you about the bug hit p to pin the existing version, answer y when asked if you're sure and then n to bail out of the upgrade.

Exiting the upgrade is is part of the pinning process and you can run the upgrade again immediately afterward; you'll notice that your package manager doesn't offer to install the broken package.

Once the bug is cleared the package will be automatically unpinned and can upgrade as normal.

[ SOLVED ]

Hello... Suddenly I was going to update my system (mostly Niri with quickshell) on Sid and now it wants to install all from Cinnamon?

Trying to debug why is this happening, I found might be due to gir1.2-glib-2.0...? I don't think it would, but I would like if someone more experienced and knowladge could help me? I'm using apt update && apt full-upgrade (even apt upgrade pulls cinnamon)

Thanks in advance.

Edit: It seems my flatpak for some reason wanted to grab some portal I already have installed and does going into gdm3 and thus some x-session and thus bringing all Cinnamon together...

Using ```apt -o APT::Install-Recommends=false full-upgrade``` bring a much smoll and compact update to my system, actually just the dependencies was not installed (which was showing in the normal apt full-upgrade)

After spending a few hours troubleshooting Bluetooth on my ThinkPad, I finally got it working. I figured I'd post everything I tried in case it helps someone else.

Symptoms included:

Bluetooth adapter not showing up

Bluetooth service inactive/dead

Couldn't discover or pair any devices

Here's the checklist that eventually solved it.

1. Check if Bluetooth is blocked by rfkill

rfkill list

If you see Soft blocked: yes or Hard blocked: yes, run:

sudo rfkill unblock bluetooth sudo rfkill unblock all

1. Make sure the required packages are installed

sudo apt update sudo apt install bluez bluetooth rfkill

(Optional GUI)

sudo apt install blueman

1. Enable and restart the Bluetooth service

sudo systemctl enable bluetooth sudo systemctl start bluetooth sudo systemctl restart bluetooth

Then verify:

systemctl status bluetooth

1. Check that the btusb kernel module is loaded

lsmod | grep btusb

If nothing appears:

sudo modprobe btusb

1. Verify that Linux detects your adapter

lsusb

and

dmesg | grep -i bluetooth

If nothing shows up, the issue could be firmware, BIOS settings, or hardware.

1. If you're using ConnMan, check for conflicts

In my case I also checked ConnMan:

systemctl status connman

If necessary, try disabling it temporarily:

sudo systemctl stop connman sudo systemctl disable connman

Then reboot and test Bluetooth again.

1. ThinkPad-specific tip

Some ThinkPads have Bluetooth disabled through:

BIOS settings

Wireless hardware switch (older models)

Fn + F5 (or the wireless shortcut key)

Double-check those before assuming it's a Linux issue.

Final result

After going through these steps, Bluetooth started working normally again and I was able to pair my devices without any issues.

Hopefully this saves someone else a few hours of troubleshooting. If you have other fixes that worked for you, feel free to share them below.

Let me know if this is not a good place to post sid problems, but my nfs shares stopped working after libtirpc (3t64, common, and dev) upgraded to 1.3.7, reverting to 1.3.6 fixed it

systemctl status nfs-mountd.service 
× nfs-mountd.service - NFS Mount Daemon
     Loaded: loaded (/usr/lib/systemd/system/nfs-mountd.service; static)
     Active: failed (Result: exit-code) since Sat 2026-03-28 21:50:15 EDT; 13s ago
 Invocation: 160987f3911e47d28258cd5f6308bcb9
       Docs: man:rpc.mountd(8)
    Process: 54635 ExecStart=/usr/sbin/rpc.mountd (code=exited, status=127)
        CPU: 8ms

Mar 28 21:50:15 ddddd systemd[1]: Starting nfs-mountd.service - NFS Mount Daemon...
Mar 28 21:50:15 ddddd rpc.mountd[54635]: /usr/sbin/rpc.mountd: symbol lookup error: /usr/sbin/rpc.mountd: undefined symbol: rpc_gss_getcred, version TIRPC_0.3.0
Mar 28 21:50:15 ddddd systemd[1]: nfs-mountd.service: Control process exited, code=exited, status=127/n/a
Mar 28 21:50:15 ddddd systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.
Mar 28 21:50:15 ddddd systemd[1]: Failed to start nfs-mountd.service - NFS Mount Daemon.
root@ddddd:/etc# systemctl status nfs-mountd.service 
× nfs-mountd.service - NFS Mount Daemon
     Loaded: loaded (/usr/lib/systemd/system/nfs-mountd.service; static)
     Active: failed (Result: exit-code) since Sat 2026-03-28 21:50:15 EDT; 23s ago
 Invocation: 160987f3911e47d28258cd5f6308bcb9
       Docs: man:rpc.mountd(8)
    Process: 54635 ExecStart=/usr/sbin/rpc.mountd (code=exited, status=127)
        CPU: 8ms

Mar 28 21:50:15 ddddd systemd[1]: Starting nfs-mountd.service - NFS Mount Daemon...
Mar 28 21:50:15 ddddd rpc.mountd[54635]: /usr/sbin/rpc.mountd: symbol lookup error: /usr/sbin/rpc.mountd: undefined symbol: rpc_gss_getcred, version TIRPC_0.3.0
Mar 28 21:50:15 ddddd systemd[1]: nfs-mountd.service: Control process exited, code=exited, status=127/n/a
Mar 28 21:50:15 ddddd systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.
Mar 28 21:50:15 ddddd systemd[1]: Failed to start nfs-mountd.service - NFS Mount Daemon.

ii  libtirpc-common                                  1.3.7-0.1                                 all          transport-independent RPC library - common files
ii  libtirpc-dev:amd64                               1.3.7-0.1                                 amd64        transport-independent RPC library - development files
ii  libtirpc3t64:amd64                               1.3.7-0.1                                 amd64        transport-independent RPC library

Edit: bug report has been filled https://www.reddit.com/r/debian/s/bnuRG7GSKM

Caught an upgrade to qbittorrent-nox yesterday - the application works but maxes out a single CPU core even when idle. Downgrading to v5.1.4 in Testing repos resolves the issue.

Bug report here - I couldn't justify making this an RC bug so unless it gets fixed fairly quickly the issue may migrate to Testing in about 3 days - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1135745