I'm on Debian 13. Gnome Software is supposed to update every two weeks except for critical updates which should be updated immediately.

https://wiki.gnome.org/Design/Apps/Software/Updates#Tentative_Design

When you run "apt changelog <package>" There is an urgency field. But isn't this field designed to indicate how fast a package should migrate from Unstable to Testing?

https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.en.html#selecting-the-upload-urgency

Is this the same field that Gnome Software uses to determine if a package is critical? If so this doesn't seem to me to be a good field to determine that since that field is used to determine how fast a package moves from Unstable to Testing.

For example, the urgency to migrate to Testing might be low because the package might be large and disruptive but it might be a critical security vulnerability that needs to be updated immediately in Stable.

Basically I'm concerned that critical updates won't happen because Gnome Software is using the wrong field to determine whether they're critical. In particular, critical security updates.

Also I'm aware that "critical" could be either security or non-security updates.

Hope I was clear and thanks in advance.

Hi, everyone!

I'd like ask for help with Nvidia drivers on Debian 13. I have RTX 4060 laptop GPU and I tried to install Nvidia drivers using Debian documentation. During dkms building there was a message that nouveu is conflicting with driver and to resolve it I need to reboot my laptop after the building is ended. So, after building I've rebooted Debian and can't boot into it because it stucks during the boot. Who had the same problem please help!

PS: I use KDE plasma

PSA: Chromium in Stable is currently way behind on security updates.

The Mods removed my previous message, assuming my post was AI.

I'm hoping some people see this and spread the word.

I have emailed the maintainers to find out why.

I hope this is useful to someone!

---

Update: It seems they have released an update to 152.0.7977.75.

This is amazing. CERN is extremely strict about the Plinth they run the collider on

I'm on Debian Forky with GNOME Flashback. I'm not sure what I did but I think it may have happened after I made myself administrator in the user settings. There's no option in the menu for shutting down or restarting. When I try from the terminal, it says "user session inhibited" as you can see. I did this on stable and was fine.

Is there a way to fix this without having to use the command "systemctl poweroff -i" every time?

Thanks in advance,

Lysandra

I was happy with Debian using Budgie. Trixie + Budgie 10.9 was perfect for me, stability, low resource usage, all the things I needed, all packed into one.

The new Budgie, though, lacks LOTS of features I loved. Specially the Desktop Taskbar, which used to let you see which apps were running in each desktop, as well as drag and drop them, which meant you could EASILY handle dozens and dozens of windows opened.

That, and the fact that it had a fully featured, modern and beautiful look for less RAM and CPU usage, paired with no instability, made me enjoy it a lot.

The issue? It wasn't preinstalled, so I think I never got all the packages right, and had some issues with it when trying to install some programs that didn't get the proper X11 settings they needed since I installed everything manually, and I don't know how to fix that. Tried going for an official Budgie distro, but most are now running the new version which I tested in Fedora and found it was TERRIBLE.

Now I'm wondering if perhaps another DE officially supported in Debian would fulfill my needs?

Does anyone know if XFCE, LXQt or MATE could help me? Cinnammon doesn't help me much, uses the same or more resources as KDE or GNOME while looking uglier (in my view).

I'm almost at the point where I'm thinking of staying with Budgie 10.9 as long as possible.

The NVIDIA Linux driver version 550.163.01 was officially released on April 17, 2025 ?

Does anyone else experience issues with Debian/KDE that weren't there like, a year ago?

I've experienced some strange differences compared to last year... For context I distro-hopped cca 4 times last year with an nVidia 1060, but then got an RX6600XT and retried most of he same distros... Mainly Fedora and Debian on KDE...

1. The remote controller app (Unified Remote) only partially working this year. I can move the mouse cursor with it but can't click. This happened on Fedora too this year, that's why it got me thinking it's maybe a KDE Plasma issue...
2. Can't get the printer (Samsung M2022) to work this year. Last year it was solved with apt install printer-driver-all.
3. Probably most annoying, my Audio Device disappearing bug is still here. (more info on my PC configuration is in that post)

I had none of these issues a year ago. Other than version, the only difference is the graphics card.

I was kinda getting tired of distro hopping, thought I'd finally settle. I've never tried an Arch distro, maybe I'll try CachyOS, but if it's a KDE issue, I'm not sure what to do... Maybe I'll try it with Cosmic and see how that goes..

Hey everyone, am I the only one who feels the need to plug in a network cable after switching to Debian, just to avoid issues with network adapters?

Hello guys.

I'm kinda new to linux and brand new to Debian but I'm liking the simplicity of it.

I have an laptop connected to external monitor and when I turn on the PC the login screen is always appearing on the laptop screen. I've done some research and found this prompt:

sudo cp ~/.config/monitors.xml /var/lib/gdm/.config/monitors.xml sudo cp ~/.config/monitors.xml /var/lib/gdm/.config/monitors.xml

Since I'm kinda new, I don't still don't understand all of what is written, is this safe to use? will it help?

My other question is about Gnome Extensions. I've installed flatpak and got Spotify to work and used flatseal to make it respect the system theme. I see now on the Gnome Software the Gnome Extension program. My question is, is it the correct way to install it on Debian? Or should I just keep to base Gnome so I don't break Debian?

Thank you all!

Edit: Made it work!! For those that may come across this i'll write down what I've done:

1º - Go to Display Settings and Mirror both screens by clicking on the button on the top left of the window that says Mirror.

2º - Open terminal and after sudo apt update write:

sudo cp ~/.config/monitors.xml /var/lib/gdm3/.config/

3º - Go back to display settings and reverse it back to what you were using.

Thank you for your help! Especially u/doc_willis

Hi, is using sudo apt install, safe for yubikey manager & yubico authenticator & krita?

Are packages using the above safe & vetted?

Cheers

Is there any way to update Debian specific packages while upgrading through terminal?

Because if I type sudo apt upgrade, it will upgrade all the packages. Yes, I can see all the Upgradable package list. But how could I upgrade specific packages and left the rest packages un-upgraded.

Hi all, I have a windows 10 pc I want to dual boot with Debian. I have tried installing from usb and live booting from dvd and get the same error both ways.

End kernel panic - not syncing: VFS: unable to mount root FS on unknown block (0,0)

It's a hp pavillion (I know 😔). Has anyone any suggestions on how I can achieve this?

Thanks in advance.

I am trying to boot the raspi images from

https://cloud.debian.org/images/cloud/trixie/

on a raspi4b-2G but they fail with loading the kernel (7x green LED).

Did I miss something or is that a bug?

Edit:

cat config.txt 
# Do not modify this file!
#
# It is automatically generated upon install or update of either the
# firmware or the Linux kernel.
#
# If you need to set boot-time parameters, do so via the
# /etc/default/raspi-firmware, /etc/default/raspi-firmware-custom or
# /etc/default/raspi-extra-cmdline files.

# Switch the CPU from ARMv7 into ARMv8 (aarch64) mode
arm_64bit=1

enable_uart=1
upstream_kernel=1

kernel=vmlinuz-6.12.90+deb13.1-arm64
# For details on the initramfs directive, see
# https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=10532
initramfs initrd.img-6.12.90+deb13.1-arm64

Kernel: 6.12.107+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0

clocksource: tsc

Desktop: Cinnamon v: 6.4.10 tk: GTK v: 3.24.49 wm: Muffin v: 6.4.1 vt: 2

dm: GDM3 v: 48.0 Distro: Debian GNU/Linux 13 (trixie)

Machine:

Type: Desktop Mobo: Gigabyte model: H410M S2H serial: <superuser required>

uuid: <superuser required> UEFI: American Megatrends v: F9a date: 07/23/2025

CPU:

Info: dual core model: Intel Pentium Gold G6400 bits: 64 type: MT MCP

smt: enabled arch: Comet Lake rev: 3 cache: L1: 128 KiB L2: 512 KiB

L3: 4 MiB

Speed (MHz): avg: 800 min/max: 800/4000 cores: 1: 800 2: 800 3: 800 4: 800

bogomips: 31999

Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx

Graphics:

Device-1: Intel CometLake-S GT1 [UHD Graphics 610] vendor: Gigabyte

driver: i915 v: kernel arch: Gen-9.5 ports: active: DP-1

empty: HDMI-A-1,HDMI-A-2,HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:9ba8

class-ID: 0300

Display: x11 server: X.Org v: 21.1.16 driver: X: loaded: modesetting

unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :1 screens: 1

Screen-1: 0 s-res: 1360x768 s-dpi: 96 s-size: 359x203mm (14.13x7.99")

s-diag: 412mm (16.24")

Monitor-1: DP-1 model: LG (GoldStar) W1943 serial: <filter> res:

mode: 1360x768 hz: 60 scale: 100% (1) dpi: 85 size: 406x229mm (15.98x9.02")

diag: 466mm (18.4") modes: max: 1360x768 min: 720x400

API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris

device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris

inactive: wayland

API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.7-2+deb13u1

glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 610 (CML

GT1) device-ID: 8086:9ba8

Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr

Audio:

Device-1: Intel Comet Lake PCH-V cAVS vendor: Gigabyte driver: snd_hda_intel

v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a3f0 class-ID: 0403

API: ALSA v: k6.12.107+deb13-amd64 status: kernel-api

Server-1: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse

status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin

4: pw-jack type: plugin

Network:

Device-1: Realtek RTL8188EE Wireless Network Adapter driver: rtl8188ee

v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 4000 bus-ID: 02:00.0

chip-ID: 10ec:8179 class-ID: 0280

IF: wlp2s0 state: down mac: <filter>

Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet

vendor: Gigabyte driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1

port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200

IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>

Drives:

Local Storage: total: 968.79 GiB used: 580.95 GiB (60.0%)

ID-1: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB

speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: J1.3 scheme: GPT

ID-2: /dev/sdb vendor: Kingston model: SA400S37480G size: 447.13 GiB

speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 60.1 scheme: GPT

ID-3: /dev/sdc vendor: Western Digital model: WD3200AAJS-07M0A0

size: 298.09 GiB speed: 3.0 Gb/s tech: N/A serial: <filter> fw-rev: 3E01

scheme: GPT

Partition:

ID-1: / size: 146.75 GiB used: 58.44 GiB (39.8%) fs: ext4 dev: /dev/sda5

ID-2: /boot/efi size: 519 MiB used: 7.1 MiB (1.4%) fs: vfat dev: /dev/sda6

Swap:

ID-1: swap-1 type: partition size: 4.37 GiB used: 0 KiB (0.0%) priority: -2

dev: /dev/sda7

Sensors:

System Temperatures: cpu: 32.0 C mobo: 29.0 C

Fan Speeds (rpm): N/A

Info:

Memory: total: 8 GiB available: 7.62 GiB used: 4.37 GiB (57.3%)

Processes: 229 Power: uptime: 3h 29m states: freeze,mem,disk suspend: deep

wakeups: 0 hibernate: platform Init: systemd v: 257 default: graphical

Packages: 2519 pm: dpkg pkgs: 2511 pm: flatpak pkgs: 8 Compilers:

gcc: 14.2.0 Shell: Bash v: 5.2.37 running-in: kitty inxi: 3.3.38

Hi, I have an audio issue on Debian 13 (Cinnamon) that I can't figure out.

SYMPTOM:

The audio crackles/skips like a "broken record", cutting out

intermittently. It happens from the moment I boot up, at random

times (it's not just something that appears after leaving the PC

off overnight). I ruled out my mouse (I use one with custom

software) - it still happens without it running.

HARDWARE:

- Audio chip: Realtek ALC897

- CPU: Intel Pentium Gold G6400

- Integrated graphics, Intel UHD 610 (no dedicated GPU)

- [paste the output of inxi -Fxxxz here]

WHAT I'VE ALREADY TRIED:

- Reinstalling/testing with PulseAudio - same issue

- Updating the kernel - same issue

- Rolling back to an older kernel (downgrade) - same issue

- Updating the BIOS - same issue

- This exact same issue happened on Linux Mint too (same

hardware), so it doesn't seem to be distro-specific

- On Windows (same machine) this NEVER happens

Any help is appreciated, thanks!

I just migrated to Linux and im having quite a hard time, I tried to download some stuff and It actually worked but then I got to the damned nvidia drivers. I tried the Debian Wiki, but i dont know if im too dumb that im missing something but every time I read I realized there were some steps missing, then I followed a thread here on Reddit to no avail, for last I watched a YouTube video which ACTUALLY downloaded the driver (Photo below) but i keep getting stuck on a login loop, I put my password, my screen flashes Black and im back at login page again. Cam somebody make me a step by step? I know im asking a lot but i just started and tbh I really want this to work, anyway thanks in advance :)

I think this is waaaay too beginner for this subreddit but atp im kinda desperate lol :P

Hi everyone! I use debian for my home server and i like it.

I have debian (no window manager, only terminal) installed on an old laptop on a micro sd (because his hdd is broken). I also have another hdd that i use to store the docker containers and the container's data.
I disabled the sleep mode when the lid is closed and I wonder: can i put the pc in sleep when i'm not using the containers so i can extend the life of the sd card and of the hdd? Then when i'm opening a container it restarts and after some inactivity it goes again into sleep mode turning the drives off.
Thanks!

Long-term support for Debian 11, codenamed "bullseye", ends today, 31 August 2026, five years after its release. Debian will no longer publish any security updates for it.

A subset of bullseye packages will continue to be supported by third parties under the Extended LTS program. Individuals and companies who want to keep running Debian 11 can contract with those providers and have the packages they depend on added to that set.

Upgrading to Debian 12, which has Long Term Support until June 2028, is free for all Debian 11 users.
https://www.debian.org/News/2026/20260831

Instalando debían a la hora de configurar el gesto de paquetes siempre me tira este pantallazo

Esto dice en el pantallazo:

debian 13
Configurar el gestor de paquetes
Réplica de Debian inválida
Se detectó un error cuando se intentó utilizar la réplica del archivo de Debian especificada.
Las posibles razones para este error son: especificación de réplica incorrecta, la réplica no está disponible (posiblemente debido a una conexión de red defectuosa), la réplica está rota (por ejemplo porque se ha encontrado un archivo «Release» inválido), o la réplica no
soporta la versión de Debian correcta.
Puede encontrar información adicional en «/var/log/syslog» o en la consola virtual número 4.
Por favor, compruebe la réplica seleccionada o utilice otra distinta.

Anyone here not upgraded yet?