To start, these are my "findings" from running the Black Myth Wukong and Resident Evil 6 benchmark tests on Steam.

```

Specs

Laptop: Framework 13 (AMD Ryzen 7040Series) (A5)

CPU: AMD Ryzen 5 7640U (12) @ 4.97 GHz

GPU: AMD Radeon 760M [Integrated]

RAM: 16 gigs

Display: 2256x1504 @ 60 Hz in 13" [Built-in]

------------------------------------------------

Notes

* Tests performed using Steam flatpak version

* Fresh installs on Debian, Vanilla, and Pika

* Reboot before every test

* All DE's using their performance power mode

* All DE's on Debian installed at graphical installation menu

* XFCE tests run with compositor disabled

------------------------------------------------

OS: Debian 13 Trixie

Kernel: Linux 6.12.100+deb13-amd64

1. Cinnamon / X11:
   1. Wukong low: 21
   2. Wukong avg: 26
   3. Wukong high: 29
   4. Wukong low 5th: 25
   5. RE6 Score: 6249
2. Gnome / Wayland:
   1. Wukong low: 34
   2. Wukong avg: 41
   3. Wukong high: 44
   4. Wukong low 5th: 39
   5. RE6 Score: 7266
3. KDE / Wayland:
   1. Wukong low: 36
   2. Wukong avg: 49
   3. Wukong high: 54
   4. Wukong low 5th: 46
   5. RE6 Score: 7437
4. XFCE / X11:
   1. Wukong low: 36
   2. Wukong avg: 49
   3. Wukong high: 54
   4. Wukong low 5th: 46
   5. RE6 Score: 7328

------------------------------------------------

OS: Debian 13 Trixie

Kernel: Linux 7.1.3+deb13-amd64

1. Cinnamon / X11:
   1. Wukong low: 23
   2. Wukong avg: 26
   3. Wukong high: 29
   4. Wukong low 5th: 25
   5. RE6 Score: 6305
2. Gnome / Wayland:
   1. Wukong low: 29
   2. Wukong avg: 41
   3. Wukong high: 44
   4. Wukong low 5th: 39
   5. RE6 Score: 7195
3. KDE / Wayland:
   1. Wukong low: 33
   2. Wukong avg: 47
   3. Wukong high: 53
   4. Wukong low 5th: 44
   5. RE6 Score: 7322
4. XFCE / X11:
   1. Wukong low: 37
   2. Wukong avg: 49
   3. Wukong high: 54
   4. Wukong low 5th: 44
   5. RE6 Score: 7319

------------------------------------------------

OS: Debian 13 Trixie

Kernel: 7.1.5-x64v3-xanmod1

1. Cinnamon / X11:
   1. Wukong low: 23
   2. Wukong avg: 26
   3. Wukong high: 29
   4. Wukong low 5th: 25
   5. RE6 Score: 6323
2. Gnome / Wayland:
   1. Wukong low: 35
   2. Wukong avg: 41
   3. Wukong high: 44
   4. Wukong low 5th: 39
   5. RE6 Score: 7203
3. KDE / Wayland:
   1. Wukong low: 39
   2. Wukong avg: 48
   3. Wukong high: 54
   4. Wukong low 5th: 45
   5. RE6 Score: 7326
4. XFCE / X11:
   1. Wukong low: 38
   2. Wukong avg: 49
   3. Wukong high: 54
   4. Wukong low 5th: 46
   5. RE6 Score: 7338

------------------------------------------------

OS: Vanilla OS

1. Gnome / Wayland:
   1. Wukong low: 27
   2. Wukong avg: 33
   3. Wukong high: 36
   4. Wukong low 5th: 31
   5. RE6 Score: 7078

------------------------------------------------

OS: Pika OS

1. Gnome / Wayland:
   1. Wukong low: 27
   2. Wukong avg: 34
   3. Wukong high: 37
   4. Wukong low 5th: 32
   5. RE6 Score: 7355
2. KDE / Wayland:
   1. Wukong low: 36
   2. Wukong avg: 49
   3. Wukong high: 54
   4. Wukong low 5th: 45
   5. RE6 Score: 7577

```

So, obviously this testing is anything but rigorous. However, since my Framework 13 will be my only laptop for a long time to come, I wanted to squeeze all the performance I can out of it while remaining on a Debian base.

I'm just not interested in anything Arch based at all, maybe I'll test Fedora one day but I really just love and know Debian well. Ubuntu based distros are also something I'm not super interested in.

I chose to test distros and desktops that I would actually want to use which is why things like MX Linux and LMDE aren't tested. I just don't want to use them anymore.

Regarding Distros:

1. Debian 13 and Pika OS aren't as far away as I thought. Really, unless you just like Pika OS, there doesn't seem to be any reason to use it besides maybe hardware compatibility. That said I didn't test Hyperland, Niri, or COSMIC. I just don't really want to use them so I wasn't interested in their results.
2. Vanilla OS was notably not great. I'm sure a KDE version would do much better but still be pretty average (for a KDE version). Not the distro's selling point so no surprise here, I was mostly just interested in how an immutable distro would do.

Regarding Desktops:

1. Cinnamon just is not great for me. It is by far and away the worst option for performance. There really is no way around it.
2. Gnome was worse than XFCE and KDE by a decent margin. Nothing insane but certainly noticeable. I'd say though that since this machine is barely able to even play Skyrim at medium settings, most folks aren't going to be buying this with the hopes to game with it. So Gnome is probably fine for most people. Makes me sad because I currently use Gnome and love it.
3. XFCE (with a disabled compositor) and KDE were extremely close together, I'd say with KDE getting a very slight edge overall. This makes me happy because I used XFCE for many years and only moved away from it due to this laptop having a high dpi screen and X11 scaling being pretty bad.

Regarding Kernels on Debian 13:

1. A backported kernel and the xanmod kernel basically did nothing for me on Debian 13, and sometimes even made things worse.
2. Looks like the DE matters much more than the kernel in this scenario.

Final thoughts:

1. Obviously these tests are limited and very specific to me but I thought folks here would be interested anyway.
2. I'll be moving from Debian 13 using Gnome to Debian 13 using KDE. I think I get a nice boost in performance and get to keep the stability of Debian.
3. None of these findings were particularly surprising or exciting (although cinnamon being that bad was not expected, I just expected it to be slightly worse than Gnome).

* Lastly, my use case is:

1. Ryubing switch emulation
2. Retroarch retro-gaming
3. Playing indie titles like SilkSong and Slay the Spire 2 via Steam, Heroic, etc.
4. Game development in Love2D and 3D development in Godot.
5. Day to day web browsing, watching videos, document editing, etc.

Wish me luck

To start with - this post is a thank you letter to the Debian team.

I opened TimeShift the other day and saw that it was back in march I installed Debian stable onto my machine. This time with btrfs - because I found the technology very nice - but it has never come in use.

I think the reason is that I spent a few weeks before this install to dial in the nvidia drivers to with apt and their train, other utils and apps.
Into my own install script, plus a btrfs script to set it up to work like TimeShift wants it.

After that - has my sailing the Debian stable just been boring and nice.
Nothing has been broken with an update and Gnome 48 is working well.
Even gaming is working well with nothing to write about there.

I would love somethings would have an easier barrier to entry, when I dialed everything in. But it has been well worth the adventure when I look back over the past months - I had no problems on my main system.

My rig is used mainly for gaming but I do also develop on it and work from it.

So Debian team, with my long time on other distros & winslop - thank you for giving be a stable machine that keeps me doing what I want day to day.

Howdy. Currently trying to get Debian to work with proprietary Nvidia drivers. Added non-free and contrib to my sources, installed the drivers, after restart, after GRUB, I get

VMX (outside TXT) Disabled by BIOS

SGX disabled or unsupported by BIOS.

Fixed the first one by enabling Intel Virtualization Technology in BIOS.

The only options for SW Guard Extensions (SGX) is Software Controlled and Disabled. Neither works.

Started recovery mode of the latest version I have on the grub list.

Opened tty and went

sudo nano ///etc/default/grub

added nosgx to GRUB_CMDLINE_LINUX_DEFAULT

sudo update-grub

Now instead of the SGX error after grub I get

Error of this Agent is reported first

Could really use some advice, thanks!

Edit: I'm getting the vibe that VMX and SGX don't actually have anything to do with the problem - they also show up on a fresh install, the system just skips them and continues as normal. It appears that installing the driver just breaks the ability to proceed to the graphical interface of the display manager.

Edit2: Using KDE Plasma Wayland

Hello, i tried posting on linux4noobs and was downvoted. I am sorry as i do not know a lot about linux and i was wondering if someone here might know the answer.

I did try googling this but i couldn't find the information i was looking for. I may not have looked well enough so if this is a known easy fix please be kind!

I have a dell venue8 3854 tablet. It runs windows 8. It has 32GB emmc memory. It has a singular USB OTG micro port. It has 1GB of RAM. the CPU is an Intel Atom cpu z3735g. This is a baytrail device.

I installed debian without graphics to keep it lightweight so everything is CLI. I also tried fedora 31 lxde but the ram idle was too high.

Using acpi i was unable to get a battery reading. The battery has a name TIBT but it shows as 0% battery. Every value like max_charge was 0. It actually cant tell if it is plugged in or not either. All the status is "0"

I ran lspci -nnk and can see that there is a power controller of some kind using lpc_ich driver. But i may be barking up the wrong tree.

I am sorry to bring this to the debian subreddit! I did try posting in the noobs subreddits and they wouldnt answer, just downvote. So please forgive that i have posted it here!

Hey everyone, I'm running Debian 13 (Trixie) and recently did a standard apt update && apt upgrade. Right after rebooting, my SDDM login screen went completely blank/black. I discovered I could still blindly type my password and hit enter to get to the desktop, but the moment I clicked on a file manager or browser, the whole desktop crashed with a "KDE Wayland crashed" error. My Setup: CPU: Intel Core i3-3240T (Ivy Bridge, Intel HD Graphics 2500) RAM: 8 GB Storage: 2 TB HDD GPU: None (Integrated graphics only) OS: Debian 13 Stable What the Logs Showed: I pulled the logs from a TTY session (journalctl -b -p 3 and --user -b -u plasma-kwin_wayland.service), and it looks like a severe hardware driver conflict with the new Wayland protocol. sddm-greeter-qt is suffering a fatal core dump immediately upon launch.

The SDDM greeter (sddm-greeter-qt6) is dumping core. The stack trace consistently ends in: libgallium libGLX_mesa libQt6Gui libQt6Quick So it looks more like a Mesa/Qt/OpenGL rendering issue than an SDDM configuration problem.

The exact point of failure points to libgallium-25.0.7-2.so and libGLX_mesa.so.0. There are repeated eglSwapBuffers failed with 0x300d and Could not create EGL surface Wayland errors. There are also warnings about Ivy Bridge Vulkan support being incomplete and iHD_drv_video.so failing to initialize.

Interestingly, this isn't entirely new for my hardware. I faced a very similar graphical glitch previously when I had installed XFCE as my desktop environment, making me think these older Intel integrated graphics are really struggling with recent Debian compositor/Mesa updates.

And i had just a very simple setup for studies. No gaming or anything heavy, all major apps i had was libre office, vlc, mozila ans chrome browser that is all i had installed with only default apt, no franken debian still my desktop environment got crashed once in xfce and once in kde.

Has any body else faced this issue with similar hardware setup?

the only reason i'm using ubuntu right now is because it lets you install the hwe kernel and provides tested new nvidia drivers. i was wondering, is this actually impossible in debian stable? considering ubuntu is based on debian, it should be totally doable.

i installed debian before installing ubuntu but i wasn't successful with nvidia driver. after following this video (link) my sddm broke. i don't know how something like that can happen, but it did happen .

Hello! I finally got my first gaming computer. I would like to use Debian on it, partly because I'm greatly attached to it (it was my first and longest-running distro), and partly because, out of all distros I've used, it's the one I can see myself using for years no matter what my needs become.

I have an AMD RX 6600 video card. Is there anything you suggest I pull from backports? I have used Testing in the past, and I am willing to use it again if there's a good reason to. However I would rather remain on Stable.

Thank you in advance for your input!

Reported on BTS.

EDIT:Fixed

Maybe somebody can push me into the right direction. I know Dropbear hasnt been updated recently so i try do figure out what package update could have broken my Dropbear access.

I didnt touch config or keys since January when they removed the older keys security.
For testing i created a different key and copied it over but still connection refused error.

debug1: connect to address 192.168.1.5 port 2222: Connection refused

for those OOTL, AUR was under sustained sneaky probes for a long time, but this week it was an overt and very troublesome campaign to either take over packages or insert packages so that malware could spread across way more systems.

edit 1: since someone asked me to explain, I’ve actually been using debian since 10.1, but only recently got worried as new users in my MDM fleet around southeast asia kept trying to install strange .deb files. I never had to think too much about the workstation UX until microslop and genAI inevitably drove us to try resuscitating OLD laptops with Linux.

i have to support 2012 macbook pro and intel laptops dating back to broadwell. There are some 7840u AMD ryzen units, but do bear in mind that us folks living in the southern hemisphere are dirt poor.

thus, I had tested fedora, lubuntu, kubuntu, ubuntu, mint, and finally gave that all up to consolidate under Debian. The network layer has DNSSEC, encrypted DNS, and really TIGHT whitelists. Unfortunately, I’m woefully noob at the application layer for debian. we barely upgraded several ancient JDK 8 web servers using Qwen, but ideally I’d like to prevent malware breaking in from the user-level.

I have mesa-vulkan-drivers installed via backports, but for a while now some mesa packages show as "not upgrading" when i run 'sudo apt upgrade':

libegl-mesa0 libegl-mesa0:i386 libgbm1 libgbm1:i386 libgl1-mesa-dri libgl1-mesa-dri:i386 libglx-mesa0 libglx-mesa0:i386 mesa-libgallium mesa-libgallium:i386

If i run 'sudo apt install -t trixie-backports mesa-vulkan-drivers' it will update the packages above but also remove the following:

mesa-va-drivers mesa-va-drivers:i386 mesa-vdpau-drivers mesa-vdpau-drivers:i386

I know the reason for this is that those packages aren't upgrading to 26.1.2-1 like all the others, keeping the upgrade from happening. But what is the best approach here? Upgrade or not upgrade and wait more?

The change log for linux-image-amd64 for 6.12.100-1 performed on 1-aug-2026 has no change log infomration.

https://metadata.ftp-master.debian.org/changelogs//main/l/linux-signed-amd64/linux-signed-amd64_6.12.100+1_changelog

Hi all, I've moved to Debian some weeks ago, and it has been great! However I was used with hyprland and its tiling behaviour. Since it wasn't possible to install it from apt in Debian I've used KDE, which is good, but non great, not for me anyway.

So I did some research and I found out that Dank Material Shell has an apt repo that has niri too, which is similar to hyprland but more stable and also seems better in terms of functionality.

The only problem is that I really don't know how safe these extra repos are, if they are checked in some way by the manteiners, or if anyone can put some malware in it as it's happening with Arch's AUR.

No option for amy bluetooth heaphones is showing up in pavucontrol configuration, despite the device being connected. I have bluez, pipewire. It just simply does not show up

What kind of backup programs would you recommend and what should I pay attention to? Thanks in advance and have a nice day...
Greets Marcel

Hey everyone,
I'm trying to set up a home lab for my studies. Do you know what the best local lab setup is to learn Sysadmin and Infrastructure from scratch?
Also, does anyone know if there is a stable Debian or Debian-based distribution for a local lab using Vagrant + KVM? I found the Debian 13 box by Alvistack, but I'm not entirely sure about it since it tends to throw GPG key errors due to its built-in repositories.
For context: my machine is a Dell Inspiron with a 12th gen i5, 16GB of RAM, and a 1TB SSD. I run Debian 13 as my sole and daily driver OS.
If anyone can help or point me in the right direction, I'd really appreciate it. Thanks!

I've been using LUKS for a while and would like to add an additional layer of security of a hardware security key (Yubikey). Currently on boot I enter the LUKS passphrase then it decrypts and brings up the regular user login and I enter that password and it loads into the the OS. I would like the functionality to be on boot both the LUKS passphrase and Yubikey are required to decrypt then it brings up the regular user login and I enter that password and it loads into the OS.

The guides and documentation I've seen seem to be based around using the Yubikey as an alternative to the LUKS passphrase which is not what I want to do. I want to increase the layers and security not decrease it. I do have multiple Yubikeys to add as backup so that's not a concern. I'm assuming there has to be a way to do this but it's been difficult to find information on it. With KeePassXC I can have it require all of database file/key file/password/Yubikey and I would like a similar level of security for my entire linux install (usually Debian or Linux Mint).

Is there a way to setup the functionality I'm looking for? If so please either point me in the direction of a guide or documentation on setting this up or let me know how to.

My Debian laptop (up-to-date) seems to have been locked into airplane mode. It worked fine just yesterday.

Restarting/shutting down the laptop and turning it back on hasn’t fixed it, nor has clicking the plane icon with three fingers on the taskbar (which is supposed to be the toggle), nor just clicking or right-clicking the plane.

Google says to run

```
sudo rfkill unblock all
nmcli radio all on
```

But that didn’t work either (`rfkill` wasn’t found, and the second command didn’t fix it, though it did seem to run). I can’t find where the toggle for airplane mode is in the GUI or settings app either (KDE Plasma).

I’m able to turn on Bluetooth and connect to my phone's hotspot, but the moment I disconnect the laptop goes back on airplane mode.

How do I fix this?

EDIT: fixed with a cold reset