DEV Community: Michael

KDE Plasma 6.3 Didn’t Add Features—It Removed Friction

Michael — Wed, 10 Dec 2025 13:55:02 +0000

How a “boring” desktop quietly transformed my workflow, accessibility, and trust in my system

TL;DR

I didn’t switch to KDE Plasma 6.3.6 for new features—I switched as an experiment, and it immediately stopped getting in my way.

Coming from Cinnamon, I was tired of customizing like I am walking on eggshells, dated X11 behavior, and fighting my desktop to make the smallest change. Plasma surprised me with thoughtful time‑saving features: Dolphin split file views, terminals that follow directories, persistent file transfer notifications, pixel‑level zoom, excellent dark mode integration, and accessibility features that actually respect eye strain.

Even on Debian’s “older” Plasma, the experience feels smoother, and more intentional. For once, I finally stopped tweaking—not because I couldn’t, but because it was no longer necessary.

I Didn’t Upgrade for the Shiny New Thing

I’m on Debian 13 with KDE, so it's KDE Plasma 6.3.6—not the version currently in the headlines. I kept reading reviews that described recent Plasma point releases as “nothing exciting, boring,” so my expectations were low.

What I didn’t expect was that this desktop would quietly and thoroughly revolutionize the way I work.

I didn’t realize how much energy I was wasting managing my desktop until Plasma stopped demanding extra effort from me.

From Cinnamon Fatigue to Plasma Stability

I came from Cinnamon. It worked—until it broke.

Over time, every small change felt like a risk. Adjust one thing, accidentally break another. Eventually, I stopped customizing entirely, not because I was satisfied, but because I didn’t trust the system to stay stable if I touched it.

There was also the growing gap around X11. I’m not a gamer, but I couldn’t ignore how much smoother people reported Wayland to be. Cinnamon began to feel dated, and that friction showed up everywhere: animations, window behavior, small visual inconsistencies that add up over long sessions.

Plasma felt different. Predictable. Intentional.

Sure, it's busy. But it reflects that I'm a busy person.

Dolphin Is Where the Time Savings Started

The first real shift came from Dolphin, KDE’s file manager.

Pressing F3 instantly gives you a split view
The embedded terminal always opens in the current directory, no matter how deeply nested it is

That alone saved a surprising amount of typing and context switching. I stopped managing files and started moving through them.

File operations became part of my workflow instead of interruptions. It sounds small—until you realize how often you deal with files.

Pixel‑Perfect Isn’t Marketing Hype—It's Real

I heard a podcast about KDE’s “pixel‑perfect” strategy and assumed it was marketing hype.

Then I pressed Meta + + +

You can zoom anywhere on the screen down to the pixel level—instantly and smoothly. Not flashy, just helpful.

That discovery pushed me to dig out my old Wacom Intuos Pro tablet that had been collecting dust. KDE’s recent attention to designers paid off immediately: sensible defaults, excellent input handling, and none of the usual friction I expected.

At that point, the hype stopped sounding like hype.

Accessibility, Dark Mode, and a Flatpak Lesson

I’ve had three eye surgeries. Dark mode isn’t a choice—it's a necessity.

Plasma nailed this.

Scribus: perfectly themed
LibreOffice: matched the system without effort

Then I installed my must‑have email client: Evolution.

Blinding White

I had installed the Flatpak version to get newer features. On a hunch, I switched to the Debian package instead—and instantly, Evolution followed the system’s dark mode and theming perfectly.

That single change led to a few minutes of font tuning for readability and size, fractional scaling. The result was dramatic: less eye strain, more comfort, and a setup that actually respected my limits.

My workflow didn’t just improve—it became sustainable.

The Small Detail That Completely Sold Me

While cleaning up years of duplicate directories—largely created out of fear of losing something important—as soon as I discovered Dolphin, I put it to the test: a massive file operation that I knew would take hours.

Out of habit, I launched other applications and continued working, fully expecting the file transfer dialog to get buried or disappear.

But no, Plasma did something so quiet and thoughtful that it caught me off guard.

The file transfer notification moved itself to stay visible as new windows opened. No hunting. No anxiety. It simply stayed where my eyes already were while I worked away.

That sounds small on paper, but when you’re trusting the system with hours of file operations, it’s priceless. It felt less like managing a desktop and more like collaborating with one.

Hidden Gems I Didn’t Discover All at Once

One thing Plasma does exceptionally well is not advertising everything it can do. Many of its most powerful features aren’t apparent until you need them—and they have been there all the time. Check out the hotkeys in Dolphin.

A few that stood out to me over time:

KRunner (Alt + Space): Far more than an app launcher. It handles calculations, unit conversions, quick searches, clipboard access, and even system actions. Once you start using it, you will quickly discover how many tools it quietly replaces.

Window Rules: Plasma lets you define how individual applications behave—size, position, focus behavior, virtual desktop, even whether they always open maximized. This turns the window manager into something predictable instead of reactive.

Activities (not just virtual desktops): Activities allow different sets of running apps, widgets, and wallpapers for different contexts—writing, design, maintenance—without duplicating data or adding mental clutter.

Clipboard History (Meta + V): Reliable, persistent, and respectful of your workflow. It just works, and once it does, you stop thinking about it—which is precisely the point. I set my history to 100 entries, so a snippet I used a few days ago is always at my fingertips.

Global Shortcuts Everywhere: Nearly everything in Plasma can be bound to a keystroke—including scripts, window behaviors, and KRunner actions. Power is there when you want it, invisible when you don’t.

None of these features scream for attention. Together, they explain why Plasma feels capable and confident, even when it’s doing a lot.

Order from Chaos

Once I trusted the system, the rest followed.

I cleaned out remnants of old and failed experiments. Removed duplicate folders. Let go of “just in case” backups.

For the first time in years, my file structure reflected how I actually work—not how afraid I was of losing something.

Plasma didn’t force this on me. It just earned my confidence.

A Note for Non‑Debian Users: What’s New Beyond Plasma 6.3?

I have no experience with it, but I looked it up and can't wait for Debian to put it into the stable repo.

KDE hasn’t been idle. Upstream Plasma is now up to the 6.5 series, and while there's still no huge fanfare, the improvements reinforce exactly what made 6.3 work so well for me.

Highlights include automatic light/dark theme switching, continued Wayland refinements, better clipboard management, reduced memory usage, and more visual polish.

The direction is clear: less friction, more confidence, and a future strongly centered on Wayland.

Staying on Plasma 6.3.6 doesn’t feel limiting—it feels complete.

No Add‑Ons, No Tweaks—And That’s the Whole Point

I haven’t even looked at third‑party add‑ons or widgets.

Not because they aren’t there, but because I haven't come across anything that needs them.

When reviewers say “nothing exciting” happened between Plasma releases, I get what they mean now—but now I see why are so wrong.

Plasma didn’t add excitement. It removed friction. That should be whole point of a deskktop environment.

And when software quietly gets out of my way, that’s not boring, it's what I would have done manually.

*That’s life‑changing!
*

Debian First Aid Kit

Michael — Wed, 29 Oct 2025 01:10:15 +0000

Welcome to the Debian First Aid Kit!

Maybe you're completely new to the command line. Either way, you've probably discovered something: Debian help is everywhere, but it's scattered across forums, wikis, and threads—finding the right help when something breaks can feel like searching for a needle in a haystack. This guide exists to change all that. I have compiled the essential fixes and diagnostics you actually need, in one place.

"Anyone can cook." — Chef Gusteau

Well, anyone can use Debian too. You don't need to be an expert—you just need the right guidance when things go wrong. Let's get started...

How to Use This Guide

If you're new to Debian:

Start with the section that matches your problem
Try the first few commands listed
Don't worry if some commands look complicated - just copy and paste them

The sections get progressively more detailed. Start simple, go deeper only if needed.

System Freezes & Crashes

Check System Logs

# View logs from previous boot (after freeze/crash)
journalctl -b -1

# List all available boots
journalctl --list-boots

# Show only kernel messages from previous boot
journalctl -b -1 -k

# Show errors and critical messages only
journalctl -b -1 -p err

# Save logs to file for analysis
journalctl -b -1 > ~/crash-log.txt

Common Freeze Causes to Look For

Kernel panics: Search for "kernel panic" or "Oops"
Out of Memory (OOM): Search for "Out of memory" or "oom-killer"
Hardware errors: Look for "MCE" (Machine Check Exception) or "hardware error"
Driver issues: Check for module/driver failures
Overheating: Check system temperatures

Check System Resources

# View memory usage
free -h

# Check disk space
df -h

# Monitor system resources in real-time
htop
# or
top

(I prefer btop for better presentation)
It's not installed by default, so here are the steps.

sudo apt install btop

# Check for disk errors
sudo dmesg | grep -i error

These are permanent errors due to incomplete/buggy ACPI tables in the BIOS on my own system. I use them to demonstrate the error messages are nothing to worry about. They are just an example of what you may see with the varied hardware:

0.686554] ACPI Error: No handler for Region [ECRM] (00000000201accc4) [EmbeddedControl] (20250404/evregion-131)
0.686577] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20250404/exfldio-261)
0.686594] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_EXIST) (20250404/psparse-529)

Boot Problems

Check Boot Process

# View systemd boot analysis
systemd-analyze blame

# See what failed during boot
systemctl --failed

# Check specific service status
systemctl status <service-name>  # e.g. NetworkManager.service

Access Recovery Mode

Reboot and hold Shift to access GRUB menu (depending on your grub timing settings)
Select "Advanced options"
Choose recovery mode
Select "root" for root shell access

Common Boot Fixes

# Repair filesystem errors
# Once you identify a device with lsblk
sudo fsck /dev/sdXN

# Reinstall GRUB bootloader
sudo grub-install /dev/sdX
sudo update-grub

# Check fstab for mount errors
cat /etc/fstab

Network Issues

Diagnose Network Connection

# Check network interfaces
ip addr show

# Test connectivity
ping -c 4 8.8.8.8
# or
ping -c 6 2a00:1450:4007:809::200e

# Check DNS resolution
nslookup google.com

# View routing table
ip route show

# Check active connections
ss -tuln

Restart Network Service

# For systems with NetworkManager
sudo systemctl restart NetworkManager

# For systems with networking service
sudo systemctl restart networking

# Bring interface down and up
sudo ip link set eth0 down
sudo ip link set eth0 up

Network Issues

Diagnose Network Connection

# Check network interfaces
ip addr show

# Test connectivity
ping -c 4 8.8.8.8
# or
ping -c 6 2a00:1450:4007:809::200e

# Check DNS resolution
nslookup google.com

# View routing table
ip route show

# Check active connections
ss -tuln

Restart Network Service

# For systems with NetworkManager
sudo systemctl restart NetworkManager

# For systems with networking service
sudo systemctl restart networking

# Bring interface down and up
sudo ip link set eth0 down
sudo ip link set eth0 up

For advanced network path analysis and proving issues to your hosting provider, see the MTR (Advanced Network Diagnostics) section.

Package Management Issues

Fix Broken Packages

# Update package lists
sudo apt update

# Fix broken dependencies
sudo apt --fix-broken install

# Reconfigure packages
sudo dpkg --configure -a

(if no output, there is nothing to do)

# Clean package cache
sudo apt clean
sudo apt autoclean

# Remove unused packages
sudo apt autoremove

Handle Held or Locked Packages

# If apt is locked, find the process
sudo lsof /var/lib/dpkg/lock-frontend

# Force remove lock (use carefully)
sudo rm /var/lib/dpkg/lock-frontend
sudo rm /var/lib/apt/lists/lock

# Reconfigure dpkg
sudo dpkg --configure -a

Disk & Filesystem Issues

Check Disk Health

# Check disk space
df -h

# Check inode usage
df -i

# View disk I/O statistics
iostat -x 1

(Make sure you have sysstat which includes useful performance monitoring tools other than iostat - disk I/O statistics)

mpstat - CPU statistics
sar - system activity reporter
pidstat - process statistics
cifsiostat - CIFS statistics

# Show stats in MB instead of KB
iostat -xm 2

# Monitor specific device
iostat -x sda 1

# Check for disk errors in dmesg
sudo dmesg | grep -i "error\|fail"

# SMART disk health (if smartmontools installed)
sudo smartctl -a /dev/sda

Repair Filesystem

# Unmount the partition first
sudo umount /dev/sdXN

# Run filesystem check
sudo fsck /dev/sdXN

# For ext4 specifically
sudo e2fsck -f /dev/sdXN

Performance Issues

Identify Resource Hogs

# CPU usage by process
top -o %CPU

# Memory usage by process
top -o %MEM

# Disk usage by directory
du -sh /* | sort -h

# Find large files
find / -type f -size +100M 2>/dev/null

# Check running processes
ps aux --sort=-%mem | head -20

System Temperature Monitoring

# Install sensors (if not installed)
sudo apt install lm-sensors
sudo sensors-detect

# View temperatures
sensors

# Real-time temperature monitoring
watch -n 2 sensors

I have it as an alias in ~/.bashrc

Go to 11. Useful Aliases & Shortcuts

Service & Application Errors

Debug Service Problems

# Check service status
sudo systemctl status service-name

# View service logs
sudo journalctl -u service-name

# Restart a service
sudo systemctl restart service-name

# Enable service at boot
sudo systemctl enable service-name

# View recent service failures
journalctl -p err -b

Application Crash Investigation

# Check for core dumps
ls -lh /var/crash/

# View application-specific logs
ls /var/log/

# Check syslog for application errors
sudo tail -f /var/log/syslog

Permission & Access Issues

Fix Common Permission Problems

# Check file ownership
ls -l /path/to/file

# Change ownership
sudo chown michael:michael /path/to/file
# user:group

# Change permissions
sudo chmod 644 /path/to/file

# Recursively fix permissions
sudo chown -R user:group /path/to/directory

User & Authentication Issues

# Check user information
id username

# View user login history
last -a

# Check failed login attempts
sudo journalctl | grep "authentication failure"

# Reset user password
sudo passwd username

Hardware Issues

Identify Hardware

# List all hardware
sudo lshw -short

(May not be installed by default)

sudo apt install lshw

# PCI devices
lspci -v

# USB devices
lsusb -v

# CPU information
lscpu

# Memory information
sudo dmidecode --type memory

Check Hardware Errors

# Kernel ring buffer (hardware messages)
dmesg | less

(If no output, good, no errors)

q to quit

# Search for specific hardware issues
dmesg | grep -i "error\|fail\|warn"

# Check for USB issues
dmesg | grep -i usb

Quick Diagnostic Commands

System Information at a Glance

# Uptime and load average
uptime

# Kernel version
uname -r

# Debian version
cat /etc/debian_version

# System summary
sudo inxi -Fxz

Emergency Toolkit

# Create a diagnostic report
sudo journalctl -b > ~/system-report.txt
dmesg >> ~/system-report.txt
systemctl --failed >> ~/system-report.txt
df -h >> ~/system-report.txt
free -h >> ~/system-report.txt

# Watch logs in real-time
sudo journalctl -f

# Monitor system resources continuously
watch -n 1 'free -h && df -h'

Useful Aliases & Shortcuts

Add these to your ~/.bashrc for quick access to common troubleshooting commands:

# Monitor system temperatures in real-time
alias temps="watch -n 2 'for i in /sys/class/hwmon/hwmon*/; do echo -n \"\$(cat \${i}name): \"; cat \${i}temp*_input 2>/dev/null | while read temp; do echo \"scale=1; \$temp/1000\" | bc; done | tr \"\n\" \" \"; echo \"°C\"; done'"

or run the watch command in the shell without the opening and closing double quotes.

# Quick system status
alias sysstat='echo "=== CPU ===" && uptime && echo -e "\n=== Memory ===" && free -h && echo -e "\n=== Disk ===" && df -h && echo -e "\n=== Top Processes ===" && ps aux --sort=-%mem | head -10'

(It's a messy layout, but I'm terrible with awk. Feel free to improve the layout for me)

# View last boot logs
alias lastboot='journalctl -b -1'

# Check failed services
alias failedservices='systemctl --failed'

# Monitor logs in real-time
alias watchlog='sudo journalctl -f'

# Quick network status
alias netstat='ip addr show && echo -e "\n=== Routes ===" && ip route show'

After adding these, run:

source ~/.bashrc

Tips for Your Troubleshooting

First check logs: journalctl and dmesg are your best friends
Work through the sections: Change one thing at a time
Document changes: Keep notes on what you've tried
Search for error messages: Copy exact error messages into search engines or AI
Check recent changes: What you did before it happened? Install something, update packages, kernel?
Make backups: Before major changes, backup important data
Use verbose mode: Add -v or -vv flags to commands for more detail
Check forums: Debian forum, Reddit, Stack Exchange, and mailing lists

Remember: If in doubt, search for the specific error message along with "Debian" and the version number. e.g. Debian 13 or point release if needed, Debian 13.1

As usual I welcome any comments, suggestions or resources:

dev@divsmart.com or distro-nix on Debian Forum.

FIRST POST: WOW! - I Finally Found My Linux Stack-Pt 1

Michael — Thu, 23 Oct 2025 17:32:29 +0000

After years of searching through different distros, desktop environments, and configurations, I finally found my perfect Linux setup, with DEBIAN 13 (TRIXIE) as the core and btrfs as the filesystem. This is a short story of how I got here, and why I'm done searching

Desktop Evolution

1. GNOME - Started here, but grew frustrated with broken extensions
2. KDE - Too many options, too much tweaking, buggy
3. XFCE - Solid, but felt dated and limited
4. Cinnamon - Finally found my endpoint

The Breaking Points

GNOME Extensions:

Extensions breaking with every GNOME update
"This extension is incompatible with GNOME 4X" messages constantly
Half my workflow disappeared after updates
Searching for updated forks on GitHub when third-developers lost interest
Extension conflicts causing crashes - Gnome disabled extensions for some reason or another
Maintenance overhead became untenable

Fedora Silverblue: Distrohopping to Immutable Core

Immutability restrictions limiting flexibility
rpm-ostree layering complexity
Toolbox/Distrobox container workarounds for everything
Fighting the system to do simple customizations

I wanted the safety of rollback snapshots without the headaches of immutability. I saw OpenSUSE Tumbleweed did the snapshot rollback very well, but OpenSUSE is a story for another day, the nightmare to how to get peripherals working with YaST and why they suddenly disappear.

My Final Stack

I remember the day the founder of Debian, Ian Murdock, launched Debian. I was so excited to try it, so I bought the latest PC magazine with the CD, but alas, after a few days, I gave up in disgust. So many fatal errors and spitting out pages of meaningless gobbledygook. Years later I heard about a town hall Linux day, so I took my tower to see they could get Debian on it. Even the Linux gurus couldn't get it running. Eventually they convinced me to put on what everyone was raving about, something called Mandrake. At least it booted and had a desktop, but at least I now had Linux.

Fast forward today, I've had decades as a Linux administrator, and my dalliance with Windows is long purged from my system. I still have an iMac 27 inch 5K Retina, that Apple kindly declared obsolete due to it having an Intel CPU. I just put Debian 13 on that as well, and will write a tutorial on the installation, if anyone shows interest in how to get the Wifi and iMac Magic Mouse working.

*After years of experimentation, here's what I settled on:
*
Core System

OS: Debian 13 (Trixie)
Filesystem: btrfs with snapshots, grub menu with rollback
Desktop Environment: Cinnamon with zero extensions
Display Server: X11 (I'm not a gamer)
Keyboard: AZERTY/QWERTY (properly configured)

Applications
Email Client: Evolution 3.58 (via Flatpak)
Mail Server: Self-hosted (my primary email)
Package Management: Native apt packages first, minimal Flatpaks
only when needing some newer features

Infrastructure

Mirrors: OSUOSL (Oregon State University Open Source Lab) Super fast, please support this incubator of technology.
Locales: French default with instant English switching via bash aliases (That's because I live on a French island and regularly need to switch back and forth).

I'd love to hear your experiences, comments or suggestions.

Ok, that's my first contribution to dev.to platform. In the next episode, I will elaborate on the setup, and why IMHO, btrfs snapshots are the fail-safe system to have.

DEV Community: Michael

KDE Plasma 6.3 Didn’t Add Features—It Removed Friction

I Didn’t Upgrade for the Shiny New Thing

From Cinnamon Fatigue to Plasma Stability

Dolphin Is Where the Time Savings Started

Pixel‑Perfect Isn’t Marketing Hype—It's Real

Accessibility, Dark Mode, and a Flatpak Lesson

Blinding White

The Small Detail That Completely Sold Me

Hidden Gems I Didn’t Discover All at Once

Order from Chaos

A Note for Non‑Debian Users: What’s New Beyond Plasma 6.3?

No Add‑Ons, No Tweaks—And That’s the Whole Point

Debian First Aid Kit

Welcome to the Debian First Aid Kit!

How to Use This Guide

System Freezes & Crashes

Check System Logs

Common Freeze Causes to Look For

Check System Resources

Boot Problems

Check Boot Process

Access Recovery Mode

Common Boot Fixes

Network Issues

Diagnose Network Connection

Restart Network Service

Network Issues

Diagnose Network Connection

Restart Network Service

Package Management Issues

Fix Broken Packages

Handle Held or Locked Packages

Disk & Filesystem Issues

Check Disk Health

Repair Filesystem

Performance Issues

Identify Resource Hogs

System Temperature Monitoring

Service & Application Errors

Debug Service Problems

Application Crash Investigation

Permission & Access Issues

Fix Common Permission Problems

User & Authentication Issues

Hardware Issues

Identify Hardware

Check Hardware Errors

Quick Diagnostic Commands

System Information at a Glance

Emergency Toolkit

Useful Aliases & Shortcuts

Tips for Your Troubleshooting

FIRST POST: WOW! - I Finally Found My Linux Stack-Pt 1

After years of searching through different distros, desktop environments, and configurations, I finally found my perfect Linux setup, with DEBIAN 13 (TRIXIE) as the core and btrfs as the filesystem. This is a short story of how I got here, and why I'm done searching

Desktop Evolution

The Breaking Points

GNOME Extensions:

Fedora Silverblue: Distrohopping to Immutable Core

My Final Stack

Applications

Infrastructure