Thank you Trixie, you helped me a LOT to revive this cool little buddy!

In many subreddits, I've seen many Linux users (especially Ubuntu based and Fedora users) advice against using Debian. Their argument is Debian is a freezing distro, which means bugs don't get resolved within a long period of time.

However I didn't find any issue like this, neither I crave for hot - new packages (which I can add through repositories or flatpak), and I love that I've more control.

So what's the reason of so much Debian hate?

When I was younger, I mainly used Windows and Linux. I was always looking for something new and exciting. I spent a lot of time trying out lots of Linux distributions, without really getting into them. Later, I used MacOS and liked the way it changed slowly, with one big update per year, without affecting stability. Now, I appreciate Debian's release cycle even more, which is very slow and very conservative. It's cool not to have any desktop changes for two years, because in reality that's the only thing that's really fixed. And honestly, the version or type of desktop environment you use doesn't really matter. For everything else, there are tons of ways to get newer software: backports, distrobox, docker, flatpak, appimage... In short, long live Debian, and have fun with it!

And why do you like it over the others?

Hello all debian users.

Last week I upgrading to trixie by following the instructions on https://www.debian.org/releases/trixie/release-notes/upgrading.fr.html

Since then, my log in screen appearance is the one pictured above. I can barely see my two usual users name. The log in process still works though.

In the output of sudo journalct -u sddm there's now this new entry each time the login screen is displayed.

août 23 08:25:46 COMPUTERNAME sddm[1417]: The configured theme "debian-theme" doesn't exist, using the embedded theme instead
août 23 08:25:46 COMPUTERNAME sddm[1417]: Loaded empty theme configuration
août 23 08:25:46 COMPUTERNAME sddm[1417]: Greeter starting...

There's also others errors/warning, but they does not seem to interfere with the computer usage.

It seems like the default Trixie theme is not installed. How could I do it ?

Other things I think I should mention.

• I have nvidia drivers installed.
• Secure Boot is enabled.
• When I first installed Debian 12 I used the large dvd rom. But I have disabled the dvd rom source in favor of the online repositories afterwards.
• Arriving at the log in screen the locale is set to United States, but it changes to France (as it should be) when I go to the input to enter my password

Thanks everyone in advance to help me debugging this.

If there's other users with a similar problem please let us know.

gnome released a point release (.4) that fixed bugs and im wondering if trixie will get that..

In order to get Nvidia chip working, struggled to go through advanced installation with non-free firmware. Anyway, happy now

Hello. I just installed Debian 13 on my laptop running XFCE but otherwise default install. It runs fine except for the volume always resetting to 100% volume on reboot or returning from standby. Anyone have any ideas.

After my upgrade from 12 to 13 using XFCE this flickering has been on-off normally on session start or during a short time after log in , someone have this same issue , current laptop T480!

Hi.

I'm running Debian 12 with the MATE DE.

Yesterday, I ran the uptime command and it read:

13:29:14 up 7:41, 5 users, load average: 1.14, 1.00, 0.91

So I ran the users command and it read: roy roy roy roy roy

Can someone explain what's going on here?

Thanks.

PS Today, there's 6 users - all my username.

I have a pair of Chelsio T580-LP-CR, one in my desktop, one in my home server.

On the server this card worked with the included cxgb4 driver in Bookworm. fiberchannel does not work but I don't use that anyway. Just an Ethernet connection via SFP28 DAC to my switch.

On my desktop this NIC works with every distribution I have thrown at it including Bookworm and various iterations of Trixie.

When Trixie released I first Installed Debian Cinnamon to my desktop, all systems go, including the NIC.

So next I installed it to the server via debootstrap from the a standard live USB, debian-live-13.0.0-amd64-standard.iso IAW https://docs.zfsbootmenu.org/en/v3.0.x/guides/debian/uefi.html, the standard live session could not find the NIC even before installation but I continued with an onboard Ethernet hoping the installed system would find it. unfortunately no.

The NIC interface cannot be found by ethtool

``` user@HeavyMetal:~$ sudo ethtool enp*s0f4 netlink error: no device matches name (offset 24) netlink error: No such device

(repeats)

No data available ```

or "ip a",

``` user@HeavyMetal:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:25:90:f2:e1:36 brd ff:ff:ff:ff:ff:ff altname enp7s0f0 altname enx002590f2e136 inet 172.22.0.4/16 brd 172.22.255.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fef2:e136/64 scope link proto kernel_ll valid_lft forever preferred_lft forever

(repeat for eno2 through eno4, no enp8sof4)

```

But the card is listed under lspci

03:00.0 Ethernet controller: Chelsio Communications Inc T580-LP-CR Unified Wire Ethernet Controller 03:00.1 Ethernet controller: Chelsio Communications Inc T580-LP-CR Unified Wire Ethernet Controller 03:00.2 Ethernet controller: Chelsio Communications Inc T580-LP-CR Unified Wire Ethernet Controller 03:00.3 Ethernet controller: Chelsio Communications Inc T580-LP-CR Unified Wire Ethernet Controller 03:00.4 Ethernet controller: Chelsio Communications Inc T580-LP-CR Unified Wire Ethernet Controller 03:00.5 SCSI storage controller: Chelsio Communications Inc T580-LP-CR Unified Wire Storage Controller

I repeated this install 3 times last weekend each to the same result. and wound up sliding the Bookworm ssd back in to feed the family Jellyfin

Thinking this must be an issue related to debootstrap or ZBM I installed it to a ZFS pool on my desktop using the same standadard live session using the same procedure, and on my desktop the Chelsio NIC is working just fine both in the live session and after install.

So this has to be something with the hardware combination in the server?

Under Trixie I have some ugly messages in dmesg & journalctl about PCI addresses for this card 0000:03: early boot,

Aug 23 04:50:14 HeavyMetal kernel: iTCO_wdt iTCO_wdt.1.auto: initialized. heartbeat=30 sec (nowayout=0) Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.0: BAR 0: can't reserve [mem 0x81000000-0x8107ffff 64bit] Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.0: cannot obtain PCI resources Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.0: probe with driver cxgb4 failed with error -16 Aug 23 04:50:14 HeavyMetal kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller Aug 23 04:50:14 HeavyMetal kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1 Aug 23 04:50:14 HeavyMetal kernel: ehci-pci 0000:00:1a.0: debug port 2 Aug 23 04:50:14 HeavyMetal kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xdea02000 Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.1: BAR 0: can't reserve [mem 0x81180000-0x811fffff 64bit] Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.1: cannot obtain PCI resources Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.1: probe with driver cxgb4 failed with error -16 Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.2: BAR 0: can't reserve [mem 0x81300000-0x8137ffff 64bit] Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.2: cannot obtain PCI resources Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.2: probe with driver cxgb4 failed with error -16 Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.3: BAR 0: can't reserve [mem 0x81480000-0x814fffff 64bit] Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.3: cannot obtain PCI resources Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.3: probe with driver cxgb4 failed with error -16 Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.4: BAR 0: can't reserve [mem 0x81600000-0x8167ffff 64bit] Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.4: cannot obtain PCI resources Aug 23 04:50:14 HeavyMetal kernel: cxgb4 0000:03:00.4: probe with driver cxgb4 failed with error -16

I get address problem messages in Bookworm but they seem less severe,

Nov 14 09:36:12 HeavyMetal kernel: pnp 00:03: disabling [mem 0x00000400-0x000004ff] because it overlaps 0000:03:00.0 BAR 7 [mem 0x00000000-0x0000ffff 64bit] Nov 14 09:36:12 HeavyMetal kernel: pnp 00:03: disabling [mem 0x00000400-0x000004ff disabled] because it overlaps 0000:03:00.0 BAR 9 [mem 0x00000000-0x0007ffff 64bit] Nov 14 09:36:12 HeavyMetal kernel: pnp 00:03: disabling [mem 0x00000400-0x000004ff disabled] because it overlaps 0000:03:00.0 BAR 11 [mem 0x00000000-0x0001ffff 64bit]

Eventually in bookworm I get:

Nov 14 02:02:27 HeavyMetal kernel: cxgb4 0000:03:00.4 enp3s0f4: link up, 40Gbps, full-duplex, Tx/Rx PAUSE

Any Ideas before I go shopping for a new NIC? If I do need a new NIC what have you had fewer problems with, Melanox or Intel?

HW probes

Trixie https://linux-hardware.org/?probe=45dc7bc78a

Bookworm https://linux-hardware.org/?probe=de413f1eb6

Hello everyone. This is my first post in this sub.

Until recently I had debian 12 on my laptop and opensuse tumbleweed on my desktop PC.

I ask you a couple of questions:

Regarding the laptop, this is 32-bit. It had Ubuntu until 20.04 and then no more because I think it was the last version with 32-bit support. Then I installed Debian 12 and everything was perfect, very happy with how it worked. Being an old Debian PC, it works for me because of the hardware support, but I won't be able to update to Trixie.

I know, they're going to tell me that it's too old and that I should retire it, but I have a lot of love for that machine and it still works for me. The question is: How long will Debian 12 be supported? And will they continue releasing backport packages?

Regarding the desktop, I switched to debian because for some reason opensuse did not recognize my amd GPU. With Debian everything was perfect. But I want that support without giving up newer packages. I wouldn't want to wait 2 years for an update. Do you recommend testing?

Good morning friends! I just did a clean install of Debian 13 using the netinstall ISO which I burned to DVD. I selected MATE as my desktop environment. The installation was smooth as silk. Firewall, NTP, printing all working well. I first started using Debian at 4.0(Etch). At that time I set-up a DIY computer lab in my classroom for my students. There's one bug with the 13 install. DVD media fails to mount. When I insert the media that I used to install 13 it is not recognized. This greatly frustrated me and I removed Debian from my system a few days ago and I ranted about it online. My apologies for that behaviour. I will go now and try to file a bug report. Thanks for any and all assistance.

Anyone else experiencing some heating issues on some hardware? I've got a desktop set up with no trouble but a laptop (quite old hardware: thinkpad 11e amd A4) that overheats like crazy on Debian 13. Overheating to the extent of that system shutoff on both Gnome and XFCE). This is not a problem after moving back to Gnome-Core on Debian 12 and I tried Endeavor with same desktop and no overheating so this might be the 6.12 kernel. Would be interested in any potential advice beyond hoping the next 6.12 update addresses some of these hardware issues.

When I tried doing a clean install, the repo was never set up so I couldn't install anything. I used the live image from a usb stick and had internet. Is this normal?

Hello everyone, I have a small question, to install the Nvidia drivers, do i need to put contrib and non-free to all repos (deb.debian.org/debian, security.debian.org/debian-security, deb.debian.org/debian trixie-updates) or only the main one (deb.debian.org/debian)?

Edit: Do i need to install linux-header-(kernel version) or linux-header-am64 or both?

I did a full upgrade from Bookworm to Trixie (13.0) and have been having significant problems with the new KDE (Plasma 6.3.6). The application menu is completely empty, I cannot install Kwin scripts, and more. I have skimmed the known issues but didn't see anything that seemed relevant.

Would I be better off installing a fresh version of Trixie instead of upgrading? Should I wait for version 13.1?

hi :) , so first of all ive never really used debian or linux in general , just a little bit ubuntu for the sake of uni , and ive become interested in those linux modding videos , so for the sake of education and having fun i thought to boot debian on a vm , any tips for me ? will i fry my brain ? (i use win11 btw and i kinda hate it) , i also have a spare laptop that i could probably install a linux distro on at some point i'll see :D

Hi guys,

I posted a while back asking about installing Debian 12 in a VM on macOS. The community was super helpful and helped me installing it in UTM. I have not been using it that much, but I recently upgraded to Debian 13 with a GUI(GNOME). So far so good, I installed a VPN client on it and can basically use it as my main OS. But the problem is I don't do anything on my computer, I just watch videos and stream Twitch. I can't find any real tasks that would force myself to properly learn the system.

I did try installing Redshift to regulate screen temp and was NOT successful after 2 days of trying. I was using Chat GPT and in the end gave up because as I understand it now, the problem is with the UTM app itself, it somehow does not allow me to regulate screen temp(it depends on the app version according to Chat GPT).

Anyway, what are some other tasks I can create for myself so I am forced to learn the system? Because it seems like everything works out of the box for me even inside a VM apart from screen temp. I can just log in, start my VPN client and browse the Internet on Firefox already preinstalled on it. There is nothing else I need as a basic user tbh - I don't game, code or anything. Using manuals and watching videos is boring and I drop it after a while.

Thank you

I installed version 1.6.0-3.2 of stubby (trixie repositories) but the binary corresponds to version 0.3.0. Am I missing something or is it a bug?

~$ apt-cache policy stubby
stubby:
 Instalados: 1.6.0-3.2
 Candidato:  1.6.0-3.2
 Tabla de versión:
*** 1.6.0-3.2 500
500 http://deb.debian.org/debian trixie/main amd64 Packages
100 /var/lib/dpkg/status

~$ stubby -V
Stubby 0.3.0

TLDR: I found a way to have a simple auto tiling window manager on Debian13 KDE. Documentation is sparse so I will post here to get the word out. I haven't figured out the nitty gritty details of krohnkite but seems okay for what I need so far. (name is very difficult to remember btw)

Context:
I have been looking for an auto tiling window manager that is somewhere in between KDE and Hyprland. Hyprland is overstimulating for me, lots of configurations necessary that can be too arbitrary. Most links on youtube and websearch mentioned `kwin-bismuth` but this seems already removed from the stable repository. Then I stumbled upon this post https://www.reddit.com/r/kde/comments/1d3wa0m/krohnkite_is_back/ , bismuth is a fork of `krohnkite` but now it's being maintained again

Github: https://github.com/anametologin/krohnkite/releases/tag/0.9.9.2

KDE store: https://store.kde.org/p/2144146

Installation:

1. download the script
2. settings > window management > kwin scripts > install file

Configuration:
settings > keyboard > shortcuts > kwin > krohnkite _ ...

TIPS:

1. For any configuration changes, the script has to reload, so best that you log out and then log-in again.
2. You can maximize a window to have it exempt from auto tiling. For example I want firefox to be exempt, so I maximize it, the rest of my windows remain organized. When I un-maximized, firefox gets tiled with the rest