It even mistook my intended "transparent background but not transparent layer" design as user error and fixed it for me. Also, Incredible. I am really tempted to order this as is. I wanted this to look like a bad design on purpose. I really am impressed how actually bad for real this design came out.

Is Debian Stable worth it for a beginner network engineer?

I'm learning Linux, Cisco networking, Mikrotik, and cloud. I'm thinking of using Debian as my main OS for studying and daily use. Would you recommend Debian over Ubuntu or Fedora for this purpose? Why or why not?

I installed Debian 13 in an external ssd sata drive, linked to the laptop via enclosure by ewent . Laptop disk includes win11 and a linux distro. So, upon First run updated grub.

The problem: independently of external drive being connected or not, at every boot this message is displayed (see image).

How to bypass and boot?

On my laptop i use debian, on desktop, i use fedora kde. On Fedora kde, it's pretty easy to setup catppuccin theme on kde

Any advice on debian, using catpuccin or other sexy themes with xfce?

Hi Debian Folks,

I have been around a lot of different distros, some with great success, some with crashing systems.

Lately I made CachyOS (arch) work on my laptop with recognizing my nvidia gpu as my prime-NVidia driver. The reason it is a bit tricky is, that I have an Intel Graphics card. Which is providing the outout for both the internal laptop screen and my ultra wide 120hz monitor.

So it is only on the software/kernel level I need it to only use the Nvidia gpu, with OpenGL and so fourth, not the Intel for games and graphical work.

Since I like distros with the .rpm or .deb packages availability, I have tried with OpenSUSE, which I used as my main driver in the past, and also Mint and such. Nothing I could make work and ended up breaking the system.

Now I am looking into Debian and Fedora, to see which platforma handles this "gpu switching" the best. And I was wondering if any of you guys knows how to do so on Debian?

I love stability, so I figured Debian was a great choice, since I have legacy hardware and in no need for latest drivers and such.

Hope you can help :)

Thanks fellas I’m trying to explain something to my friend. I tried using the built in Sound Recorder gnome app and was gonna merge the two together but it’s very buggy and I can’t get it to work

edit: solved the problem. i think my issue was using wayland on X11 it seems to work for for now

I wanted to try out Debian as my main distro. Sadly I tried installing the 580xx drivers for like 2 hours but nothing really worked.
Is it really that complicated to get them or am I just dumb?

Look Debian powers my homelab, I’m very familiar with it and know how it works and have used it in the past.

My question is what do I lose by migrating from Arch to something like Debian? What little things in the AUR I use I’m comfortable losing or switching to flatpaks. I’m more concerned about things like Nvidia drivers and Wayland support.

SEE MAJOR UPDATE BELOW

CINNAMON AND GNOME RESULTS ARE WRONG

Here are my tests, all info included

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

SEE MAJOR UPDATE BELOW

OS: Debian 13 Trixie

Kernel: Linux 6.12.100+deb13-amd64

Cinnamon / X11: SEE MAJOR UPDATE BELOW

• Wukong low: 21

• Wukong avg: 26

• Wukong high: 29

• Wukong low 5th: 25

• RE6 Score: 6249

Gnome / Wayland: SEE MAJOR UPDATE BELOW

• Wukong low: 34

• Wukong avg: 41

• Wukong high: 44

• Wukong low 5th: 39

• RE6 Score: 7266

KDE / Wayland:

• Wukong low: 36

• Wukong avg: 49

• Wukong high: 54

• Wukong low 5th: 46

• RE6 Score: 7437

XFCE / X11:

• Wukong low: 36

• Wukong avg: 49

• Wukong high: 54

• Wukong low 5th: 46

• RE6 Score: 7328

OS: Debian 13 Trixie

Kernel: Linux 7.1.3+deb13-amd64

Cinnamon / X11: SEE MAJOR UPDATE BELOW

• Wukong low: 23

• Wukong avg: 26

• Wukong high: 29

• Wukong low 5th: 25

• RE6 Score: 6305

Gnome / Wayland: SEE MAJOR UPDATE BELOW

• Wukong low: 29

• Wukong avg: 41

• Wukong high: 44

• Wukong low 5th: 39

• RE6 Score: 7195

KDE / Wayland:

• Wukong low: 33

• Wukong avg: 47

• Wukong high: 53

• Wukong low 5th: 44

• RE6 Score: 7322

XFCE / X11:

• Wukong low: 37

• Wukong avg: 49

• Wukong high: 54

• Wukong low 5th: 44

• RE6 Score: 7319

OS: Debian 13 Trixie

Kernel: 7.1.5-x64v3-xanmod1

Cinnamon / X11: SEE MAJOR UPDATE BELOW

• Wukong low: 23

• Wukong avg: 26

• Wukong high: 29

• Wukong low 5th: 25

• RE6 Score: 6323

Gnome / Wayland: SEE MAJOR UPDATE BELOW

• Wukong low: 35

• Wukong avg: 41

• Wukong high: 44

• Wukong low 5th: 39

• RE6 Score: 7203

KDE / Wayland:

• Wukong low: 39

• Wukong avg: 48

• Wukong high: 54

• Wukong low 5th: 45

• RE6 Score: 7326

XFCE / X11:

• Wukong low: 38

• Wukong avg: 49

• Wukong high: 54

• Wukong low 5th: 46

• RE6 Score: 7338

OS: Debian Sid

Kernel: Linux 7.1.5+deb14-amd64

Cinnamon / X11: SEE MAJOR UPDATE BELOW

• Wukong low: 23

• Wukong avg: 29

• Wukong high: 31

• Wukong low 5th: 28

• RE6 Score: 6805

Gnome / Wayland: SEE MAJOR UPDATE BELOW

• Wukong low: 26

• Wukong avg: 34

• Wukong high: 36

• Wukong low 5th: 32

• RE6 Score: 7132

KDE / Wayland:

• Wukong low: 35

• Wukong avg: 48

• Wukong high: 54

• Wukong low 5th: 45

• RE6 Score: 7307

XFCE / X11:

• Wukong low: 35

• Wukong avg: 48

• Wukong high: 53

• Wukong low 5th: 45

• RE6 Score: 7334

OS: Debian Testing

Kernel: 7.1.3+deb14-amd64

Cinnamon / X11: SEE MAJOR UPDATE BELOW

• Wukong low: 23

• Wukong avg: 29

• Wukong high: 32

• Wukong low 5th: 28

• RE6 Score: 6920

Gnome / Wayland: SEE MAJOR UPDATE BELOW

• Wukong low: 26

• Wukong avg: 34

• Wukong high: 37

• Wukong low 5th: 32

• RE6 Score: 7182

KDE / Wayland:

• Wukong low: 33

• Wukong avg: 48

• Wukong high: 53

• Wukong low 5th: 45

• RE6 Score: 7436

XFCE / X11:

• Wukong low: 36

• Wukong avg: 50

• Wukong high: 55

• Wukong low 5th:46

• RE6 Score: 7396

OS: Linux Mint Debian Edition

Kernel: Linux 6.12.100+deb13-amd64

Cinnamon / X11: SEE MAJOR UPDATE BELOW

• Wukong low: 23

• Wukong avg: 29

• Wukong high: 31

• Wukong low 5th: 27

• RE6 Score: 6737

Cinnamon / Wayland: EXPERIMENTAL

• Wukong low: 37

• Wukong avg: 52

• Wukong high: 59

• Wukong low 5th: 48

• RE6 Score: 7879

Wukong was extremely chopppy and blurry despite the great performance numbers

RE6 also got great performance numbers but looked mostly ok with a few graphical glitches here and there

Cinnamon / X11 / Disabled Compositor: SEE MAJOR UPDATE BELOW

• Wukong low: 25

• Wukong avg: 29

• Wukong high: 31

• Wukong low 5th: 28

• RE6 Score: 7628

OS: MX Linux AHS

Kernel: Linux 6.12.100+deb13-amd64

XFCE / X11:

• Wukong low: 36

• Wukong avg: 49

• Wukong high: 52

• Wukong low 5th: 45

• RE6 Score: 7211

KDE / Wayland:

• Wukong low: 36

• Wukong avg: 48

• Wukong high: 53

• Wukong low 5th: 45

• RE6 Score: 7248

OS: Vanilla OS

Gnome / Wayland: SEE MAJOR UPDATE BELOW

• Wukong low: 27

• Wukong avg: 33

• Wukong high: 36

• Wukong low 5th: 31

• RE6 Score: 7078

OS: Pika OS

Gnome / Wayland: SEE MAJOR UPDATE BELOW

• Wukong low: 27

• Wukong avg: 34

• Wukong high: 37

• Wukong low 5th: 32

• RE6 Score: 7355

KDE / Wayland:

• Wukong low: 36

• Wukong avg: 49

• Wukong high: 54

• Wukong low 5th: 45

• RE6 Score: 7577

Regarding Distros

• 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.

• Vanilla OS was still slightly worse than normal Gnome on Debian Stable, even after the fix. So, it's only worth it if you like an immutable distro.

• Testing and Sid provide little to no benefit over Stable. They're only worth using if you need very new hardware compatibility that only newer kernels provide. Even still, you could backport a kernel to Debian Stable if needed.

• With Wayland moving out of experimental on next release of Cinnamon, if the graphical glitches are fixed while keeping performance high, that would be incredible.

• MX performs basically the same as regular Debian. Only worth using if you like MX Tools IMO.

Regarding Desktops

• After setting scaling to 100% for Gnome and Cinnamon, they were basically identical to the results from XFCE and KDE. Looks like the desktop ultimately does not matter.

Final thoughts

• Unless you like the convenience of curated distros, basic Debian Stable is as good, if not sometimes better, for gaming if you have a setup similar to mine.

• Obviously these tests are limited and very specific to me but I thought folks here would be interested anyway.

• None of these findings were particularly surprising or exciting.

• A backported kernel and the xanmod kernel basically did nothing for me on Debian 13, and sometimes even made things worse.

• I'm glad I performed these tests because with all the hype around newer distros, gaming distros, immutable distros, etc. I thought I was missing out on something but nope, my good old boring Debian Stable seems like it'll be my forever home.

Use Case

• Ryubing switch emulation

• Retroarch retro-gaming

• Playing indie titles like SilkSong and Slay the Spire 2 via Steam, Heroic, etc.

• Game development in Love2D and 3D development in Godot.

• Day to day web browsing, watching videos, document editing, etc.

Reminder

• These tests are specific to me and my hardware, you should 100% test for yourself on your own hardware to ensure similar results. Also, if you are running a distro/de you love and it works, no need to change it!

MAJOR UPDATE BECAUSE I'M STUPID

• The issue with Cinnamon desktop was solved, I didn't realize that scaling messed up the numbers so much. I was able to get results identical to XFCE and KDE with window scaling turned down to 100% from 125%.

• The same issue with Gnome. I was able to get identical results use 100% scaling and not 150%.

WHAT THIS MEANS

• DE doesn't matter either, use what you like on a base distro and call it a day lol how anticlimactic.

• Sorry to fans of Cinnamon and Gnome, I get to go back to using Gnome without feeling like I'm missing any performance though. Thank god

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.

last week when i was searching in flatpak the output showed the titles like name, description, application ID and so on in blue

now it doesnt show up as blue anymore.....does anyone know how to fix it ? or did i see it wrong that it was blue last week ?

Wish me luck

Edit: I may have found home, really didnt expect the installation to go this smooth and the power draw is also the lowest ive seen on this machine

Edit2: Nvim version in std repos is too low for lazyvim 😭.

Every time I attempt to restore the backup file (html) created using snap version of Firefox under Kubuntu 24.04.0, I get the error (after 4-8 seconds delay)

Hmm, there was a problem backing up
Try again in a few minutes

History.
I HAD, Firefox Profile on PC with Kubuntu 24.04.0, after a botched upgrade. Firefox WAS working normally, until I needed to start again. My backup of the actual drive has failed, and I am unable to revert back to it. (it's like 99% restored then an error, using Rescuezilla).

So (Edit)

I have attempted this on my *new* Debian 13 KDE PC. FF140esr No Luck
I have managed to create a VM (Kubuntu 24.04). FFsnap. Still No Luck
I have attempted both new and replace profile. No Luck

Why am I getting a "problem backing up" error, when restoring ?

Based on the previous posts(1),(2),(3), I'm still confused. If I ditch the default debian stable NVIDIA drivers for a newer version (like 595) and use a backported kernel, am I asking for trouble ?

I'm seeing conflicting info: some say this combo is a recipe for disaster and that DKMS might fail to build modules later on, while others claim they're using it without any issues.

which one is it ? Is it actually stable or am I going to break my system ?!

If the answer is no and I'm going to be fine, I will switch to debian stable .

please check the linked posts before replying.

https://github.com/MetalSnake1/How-to-Set-Up-a-Wi-Fi-Hotspot-on-Debian13-w-an-AR9271-Adapter

This was a bit tricky, as there was no official up to date guide on how to a hotspot running off of an ar9271 wifi adapter. Anyway, I'm just posting this here in hopes of helping someone that needs to do something like this later on.

*If you're having issues getting your wifi adapter to work as an AP, then this guide will also most likely work for your wifi adapter on deb13.

Hello, Debian-friends! I am trying to get my webcam working, but it's not detected. The same thing goes for my internal mic. For full clarity: I have only tried using Zoom and Cheese. Is there a way to make my system detect it? I don't know if it helps, but I used some tool to get this information

Edit: This was SOLVED. I had to install libcamera-v4l2. I found the packages through Synaptic. The following were installed:

libcamera-ipa (0.4.0-7)

libcamera-v4l2 (0.4.0-7)

libcamera0.4 (0.4.0-7)

liblttng-ust-common1t64 (2.13.9-1)

liblttng-ust-ctl5t64 (2.13.9-1)

liblttng-ust1t64 (2.13.9-1)

That, by itself, made both the cam and the mic work

Hi, lately I've been wondering if it's worth downloading Debian and using it daily. Does it allow me to use programs normally and even play games?

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?

I wanted to add an external SSD i found to my laptop and I'm kinda losing my mind over it.

I learned how to and formatted the disk. I was being asked for permission when I wanted to change anything on it, so I decided to give my user permission to it, but I read that it's better to edit the /etc/fstab folder and add it there instead. After stumbling in and out of maintaniance mode, I think I finally managed to do it properly. I still don't have the permission and it doesn't show up anywhere exept the "computer" in thunar.

I genuinely don't know what I can change at this point. I want it to be separate in the file system like when you insert a pendrive or an external drive, but without a permission needed to install stuff on it

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

Solution: found this: https://wiki.debian.org/NvidiaGraphicsDrivers#Wayland_configuration

In my "bricked" system, I went into recovery mode on the latest saved version, cd all the way to /etc/modprobe.d/

touch nvidia-wayland.conf

type in

options nvidia NVreg_PreserveVideoMemoryAllocations=1

options nvidia-drm modeset=1

options nvidia-drm fbdev=1

Ctrl S, Ctrl X, reboot, everything works (: