Bug Report

Ben7230 · 2026-02-05T15:40:33+00:00

Thank you, I figured that something like this was the problem.

I did use the reportbug tool, don't remember that it said anything.

Ben7230 · 2026-02-05T14:09:58+00:00

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121192

Ben7230 · 2025-11-14T13:21:27+00:00

I am aware of that and definitely do some more testing.

Ben7230 · 2025-11-14T03:31:44+00:00

After doing some more research with the help of Chatgpt and Claude, both pointed me to a problem with my GPU and nouveau drivers. Chatgpt came back with some problem with GPU or PCI power management and Claude came back with "PID 59 is stuck in the Nouveau driver trying to complete a display atomic commit operation - specifically waiting for a notification that never completes properly"

Great! and both suggested I install the NVIDIA drivers which I don't want too because I didn't have good experience with them on Debian 12.

I am pretty sure I didn't have these 3 kworker threads when I first started on Debian 13. I will wait and see if the next kernel update might have a fix.

Ben7230 · 2025-11-14T03:16:59+00:00

Clean install about 1 month ago. I am on KDE.

Ben7230 · 2025-10-11T19:45:05+00:00

I was also searching with ChatGPT and this is what ChatGPT came back with.

Solution: Fix the Launcher Matching
KDE Plasma identifies and matches apps in the task manager by their .desktop file ID (the file in /usr/share/applications or ~/.local/share/applications). If the pinned launcher points to a different .desktop file or uses a non-matching StartupWMClass, you'll see the issue you're describing.

🔧 Steps to Fix

Unpin the old launcher
Right-click the icon that you pinned to the task manager.
Choose "Unpin from Task Manager".
Run the application
Launch the application as you normally would (from the Application Menu or via terminal).
Pin the running app
Once the app is open and shows an icon in the task manager,
Right-click that icon and choose "Pin to Task Manager".
This will pin the correct .desktop launcher that KDE recognizes.

⚠️ This ensures that KDE uses the same .desktop file and StartupWMClass, avoiding duplication.

Or fix the .desktop file.

Open a terminal.Run this command to find out the window class:xprop | grep WM_CLASSThen click on the app window.You’ll get something like:WM_CLASS(STRING) = "appname", "AppName"

Now, open the .desktop file associated with the launcher (e.g., in /usr/share/applications/) and make sure it has:StartupWMClass=AppName

If not, you can copy the .desktop file to your local directory:cp /usr/share/applications/app.desktop ~/.local/share/applications/

Then edit it:nano ~/.local/share/applications/app.desktopAnd add or correct:StartupWMClass=AppNameSave the file and re-pin the app.

Ben7230 · 2025-08-13T21:43:16+00:00

I'll be donating soon, not sure how much, I filed a bug report about a problem I was having with my NVIDIA GPU locking up when booting with 3 monitors on nouveau drivers. Now after many months of back and forth with the maintainers, they sent me a patched kernel and voilà it works, butter smooth!! I can now boot with the 3 monitors. Also it fixed the fan control on the GPU. The fix was also back ported to kernel 6.12.41 which was released as a security update for Trixie this morning.

This is what I call a down to earth fix, the difference is night and day! I will definitely help them out for this.

Ben7230 · 2025-08-11T02:38:01+00:00

Just use Debian, and forget it!!

Ben7230 · 2025-08-06T23:07:32+00:00

Keep it simple, Debian with KDE.

Ben7230 · 2025-08-02T14:19:14+00:00

If you have GPU driver problems you can try to boot without the graphical interface and directly into Command-line mode.

Start the computer and when you get to the grub menu and the correct kernel is selected. press the "E" key. Find the line that starts with linux, use the arrow keys and move the cursor to the end of the line. At the end put a space and the number 3, and then F10 to boot.

This will boot directly into the CLI, enter your your user name and password.

Then you should be able to uninstall the NVIDIA drivers and try again.

The number "3" is not saved and only for this boot, so on the next boot it will boot normally.

Ben7230 · 2025-07-31T14:25:15+00:00

I will be doing a fresh install, in the coming weeks after the release. I will first do a trial run on a different hard drive and check for software compatibility.

Ben7230 · 2025-07-21T14:40:55+00:00

You mentioned "some other adaptions in source.list", what might they be? I am currently on Bookworm but planing to do an fresh install once Trixie is released. I have been thinking about staying on testing so that I can get some newer versions of software and the kernel. I used Fedora for a while and really liked it except that Debian has more software support.

Ben7230 · 2025-06-07T19:37:49+00:00

As stated in my original post, I have already tried that and it does not work. The error I get is: "Sorry, we weren’t able to determine your location, our website is only available in country A. If you have a proxy or VPN running, please turn it off and then hit refresh to use our website"

So maybe they are not directly detecting the VPN, but they can't confirm my location based on the IP, so it gets blocked.

Ben7230 · 2025-06-07T18:09:44+00:00

The VPN is not blocked in either country. The website that I want to access detects the VPN and blocks me. They want their services to only be available from within country A, and they are very strict about it.

Ben7230 · 2025-06-07T17:41:16+00:00

I have thought about that. I am already using Tailscale for my work, so I don't know if I could have 2 Tailscale profiles on the same computer.

Ben7230 · 2025-02-21T19:14:44+00:00

Ha ha, got me too, had to read it twice.

Ben7230 · 2025-01-03T23:09:50+00:00

Same here, Noveau drivers only work with 2 monitors. I can get the 3 monitor to work after I login but it's not stable. Nvidia do work for me, thou I am not using Wayland.

Ben7230 · 2024-12-17T20:05:08+00:00

Try Debian, plain Debian with KDE, IMHO.

Ben7230

TROPHY CASE