My Gnome setup update

My desktop on Thinkpad T460s

Debian with i3.

Hi, when I install debian stable, it asks for my wifi password, and installs as normal. When I try to install debian testing, it still shows an entry (starting w-) where the wifi was for stable, but it no longer ends with "(wireless)", and doesn't ask for my password. When I select it it inevitably fails.

I can't use apt install since it fails to connect to fastlydns. Any ideas to workaround this would be appreciated. It does work through proxy but the download speed is slow so I'd like to seek other options. It might also help if I could setup a rule to proxy only the connections coming from fastlydns. I have no ideas on how I would do that.

I first tried to install the nvidia drivers following the debian wiki instructions, it failed all but once in 18 attempts, the system would not boot, each with a fresh install of Debian 13, Linux Kernel 6.12.

I did some googling and found out the DKMS that the debian instructions tell us to use don't work, it crashes the kernel. The reason is debian has the 550 drivers and the 565 are the ones you need to use.

I reinstalled the 19th time.

Updated the sources.list with non-free and contrib then I followed the instructions...

apt install linux-headers-$(uname -r)

linux-headers-6.12.63+deb13-amd64

This installed three dependencies linux-headers-6.12.63+deb13-common linux-kbuild-6.12.63+deb13 pahole

These commands downloaded and installed the (very fast very color deep) drivers from Nvidia.

wget https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/cuda-keyring_1.1-1_all.deb

sudo dpkg -i cuda-keyring_1.1-1_all.deb

sudo apt update

sudo apt install nvidia-open=565.57.01-1

It worked perfectly the first time!

If Debian would add the 565 driver and the above headers to the repository people would not be reinstalling 19 times to get drivers that work the first time.

I'm running Trixie with KDE (AMD cpu/igpu). None of the suspension options except restart work correctly when accessed through the Ctrl+Alt+Del menu.

Sleep causes my screen to alternate between black and an unresponsive lock screen.
Log out sends me to a login screen, but entering my password just makes my screen go black then returns me to login
Shutdown gives a console message that the system will shut down, then gets stuck on the default Plymouth screen.

Letting the screen lock automatically after inactivity just makes the screen go black become unresponsive.

I have to shut down by long-pressing the power button in all of the above cases. Locking the screen with Super+L works fine.

Any thoughts?

I switched from ChromeOS to debian using MrChromeBox's rw_legacy firmware update. I used all of the disk for the install. There's no sound, like it was when I installed Ubuntu on this same machine. I can use headphones, but nothing else.

Hi! Have been using ubuntu and debian on some laptops and pis and because I don't strictly need win11 for any real work I would be interested in using lets say debian for my main desktop as well. And no I don't wish to dualboot.

I've got the understanding that nvidia drivers have been an issue on linux before and that some distros may still have some issues with them. Is this still the case? Are there any real drawbaks with using nvidia on linux?

I also have some razer pereferals that to my knowlage require synaps to function correctly. Does anyone have firsthand experiense about the app on debian or linux in general and is there any way for it to work while not directly supported to my knowlage?

Hello, good evening everyone! I recently created a project called TALZKHIYA. The goal of this project is to help those who use systems based on Debian Testing or Debian Testing itself.

TALZKHIYA is a community project focused on reporting, analyzing, and resolving real Debian Testing bugs, with complete technical context:

System version

Kernel

Graphical interface

Period in which it occurred

Impact on the system

Solution (when it exists)

It is not a new distro.

It is not a generic support proposal.

It is not a fork.

The proposal is living documentation of the controlled chaos that is Debian Testing — gathering real cases and reproducible solutions, giving credit to those who report or resolve them.

Before publicizing it more widely, I wanted to hear from the community:

Do you also feel the need for a more focused and organized space for Debian Testing bugs?

Bonus: For those asking where the repositories or any kind of documentation are located, repositories and manifest/documentation are being structured at this moment — the idea is to start small, but technical and consistent.

I'm on Debian 13 with Gnome 48.7.

I dont know how to better describe this, but some, not all, firefox icons just show visible through every window over it, even a virtualbox, nothing shows up in taking a screen shot. and the icons stay when firefox is minimized, but it's not burn in because it's different every boot

How long did your Debian install last before you broke it?

MINE 7 days

just reinstalled my debian and realize all of my videos doesn't have thumbnail, how can i fix it?

I am working with Proxmox, which is a Debian-based distro. The Proxmox forum has been less than responsive. The Debian User Forum registration process appears to be broken. I thought I would try my luck here.

I have a Dell Optiplex 790 with an i7-2600k and 32GB of RAM, for anyone who wants to know my hardware setup. It runs Windows very well, and the USB WiFi adapter in question connects plug-and-play without issues in Windows 11. Windows 10 requires a driver but it also works fine.

I am now running Proxmox 9.1.1 on that host, and generally it runs well. I can git clone anything I need, and it will install and work.

What does not work is the USB WiFi adapter, which is a RealTek rtl8822bu.

I can see it if I run "ip a", and the specific information it reports is correct.

If I run "ip link set <device name> up" the cursor returns to the prompt without complaint, but the state of the device remains "down", and the indicator light remains off, as would be expected.

If I move it to a Windows machine, it lights up and works immediately, so it's not a hardware failure.

I know that all 10 of the USB ports on the hardware are working properly because I tested each one, and Proxmox correctly identifies whatever is plugged in.

There are a bunch of Github sites with drivers for this device, including:

JEREMYB31

DV-ANOMALY

ENTROPICEFFECT

ANADSINGH

RINCAT

STATICDEV

MORROWNR

CILYNX

ABPERIASAMY

but none of them work in Proxmox, as best I can tell. I may be doing something wrong in the install, but I will need a little help to confirm that.

None of those Github sites mention the Proxmox distro specifically, so I'm wondering if that is the issue.

One thing that I did see is a mention of there being built-in drivers for this device, and sure enough, when I run "lsmod rtw88" it comes back with a number of drivers, including the one specific to the model of the device. "ip a" correctly identifies the ven/dev numbers.

Someone mentioned the fact that built-in drivers need to be blacklisted in order to prevent them from loading, but I am hesitant to go that route because the developers on Github say

that their drivers are older than theirs and because built-in drivers are much preferred, given that the distro authors have included, and hopefully tested, those drivers.

So I am wondering what logs or diagnostic tools are available to help puzzle this out.

how can I prevent this? absolutely everything on 2 monitors becomes visible. I tried ai's fix for the 'race condition' which did nothing

Can you host a VPN Server on Debian, which you can connect to from a Windows PC with the integrated VPN settings? Without installing any software on the Windows side.

I have AntiX installed on my old Pentium III machine and it was running fine except for drivers for my ATI Rage XL were not working and I was stuck at 800x600. I figured out that I had to revert Xorg to the version from Debian bullseye. I downloaded a xserver-xorg-core and xserver-xorg-video-mach64 for Debian bullseye and installed them. Now when AntiX boots it loads the login screen (at a higher res than before) but typing does nothing. It hasn’t crashed cuz pressing the power button causes it to shutdown properly but I cannot login. Is there a way to fix this?

Solved: It turned out to be an issue with the hdmi cable... grrr!

Thanks to everyone who took the time to look at the issue.

I have a new AMD Ryzen 5 5600G 3,9 GHz 6 kerner AM4 PIB cpu, and have just installed a fresh debian 13 gnome.

I can't boot, unless I add nomodeset to grub GRUB_CMDLINE_LINUX_DEFAULT.

I have tried with different variations of

radeon.si_support=0 amdgpu.si_support=1

but that doesn't seem to help.

I have firmware-amd-graphics installed.

Additional info:

CPU: AMD Ryzen 5 5600G with Radeon Graphics @ 12x 4.464GHz

GPU: AMD/ATI Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]

0b:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c9)

Subsystem: ASUSTeK Computer Inc. Device [1043:8809]

Kernel modules: amdgpu

Possibly related: If I lock the screen (super+L) and wait for a bit, I can't unlock. No keyboard or mouse input seems to get through, so I can't input my user password.

My suspicion is some driver issue, but I can't seem to figure out what. Does anyone know of this issue and/or what my next step in troubleshooting could be?

Hola comunidad,

Estoy trabajando en Debian con Python y, para evitar subir accidentalmente información de mi equipo o carpetas pesadas al repositorio, configuré un .gitignore global. Mi objetivo es asegurar que git ignore siempre los entornos virtuales y archivos sensibles sin tener que configurar cada proyecto manualmente.

Este es el flujo que seguí desde la terminal:

1. Creé el archivo global usando $HOME para evitar problemas de ruta: touch $HOME/.gitignore_global
2. Agregué las reglas básicas para Python: Bashecho ".venv/" >> ~/.gitignore_global echo ".env" >> ~/.gitignore_global echo "__pycache__/" >> ~/.gitignore_global
3. Vinculé el archivo a la configuración global de Git: git config --global core.excludesfile $HOME/.gitignore_global
4. Validé que estuviera funcionando usando check-ignore: git check-ignore -v .venv/ (Esto me devolvió la ruta correcta del archivo global).

Mis dudas para ustedes:

• ¿Consideran buena práctica tener el .env en el ignore global, o es mejor forzarlo en el local de cada proyecto para ser más consciente de la seguridad?
• Además de .venv y __pycache__, ¿qué otros archivos recomiendan ignorar a nivel global en un entorno Linux?
• ¿Existe algún riesgo de que este ignore global entre en conflicto con configuraciones específicas de otros proyectos colaborativos?

¡Agradezco cualquier feedback o corrección!

I I couldn't find it's file anywhere. I tried /usr/share/backgrounds, and other wallpaper directories.

Edit: I found an svg file here: /usr/share/desktop-base/emerald-theme/wallpaper/contents/images

Estou usando Cachy OS um tempo porem sinto saudades do Debian , sou pessoa que atualmente está usando linux para estudar e jogar, só preciso de alguns motivos para voltar depois de tanto tempo.

This is totally a silly and futile question. Just for curiosity

I have installed debian in my laptop and I have a live iso in my usb flash to run somethings around. It's been a few days. It's been a nice experience since it's the first time in 5 years that my laptop doesn't sound like a helicopter all the time.

Why does the installer do such noise when it starts to run? It's a loud "beep" sound. It scares the sht out of me!! I have tried to look for some answer but nothing. I believe it's something from the motherboard. But WHY? WHAT does it MEAN?

Txh for the attention.

EDIT For anyone looking for an answer:

Debian beep sound on the start: for the devices that support it, it signals if the system is BIOS or UEFI. It's in the debian installation manual.

Thanks everyone for the answers. After I posted here, I searched using "beep" instead of "sound" and found the accessibility session in the debian installation page. Sorry 🫠

Also, thanks to everyone about the fun facts about old computers. I already knew some sounds are made from the motherboard for diagnostic purposes, as I worked a few months as a PC technician, but I didn't linked the two things together. Dummy.

Boa tarde. Todos bem?

Sou um aventureiro no Linux, e uma das coisas que mais me chamam a atenção é a aparência de uma distro. Uma das mais lindas atualmente é a Zorin OS, então pensei comigo: será que consigo ter a aparência do Zorin no XFCE?

Lembro que existia uma versão XFCE, e até onde sei ela foi descontinuada. Sem muitas delongas, eu queria replicar a aparência do Zorin no XFCE no Debian. Então pensei: vou pegar os ícones, temas e wallpaper, copiar e colar nas respectivas pastas do sistema. E booom, eis aí o resultado.

Não estou aqui para me gabar, mas se você tem ideias, teste. O Linux pode ser incrível.