That I understand, but my problem is the ppd file includes paths like *cupsFilter: "application/vnd.cups-command 0 /Library/Printers/Canon/BJPrinter/Filters/Command2CanonIJ.bundle/Contents/MacOS/Command2CanonIJ". I extracted those binary files too, put them in a cups folder, and adapted the path to point at the correct locations, but the scripts don’t seem to work on Linux. Same thing for the turboprint thing, the commands like (canontoturboprint) are not doing anything from what I can tell

I could successfully decompress all the relevant files from the dmg file. Now I need to figure out a way of properly installing them in a cups directory. For instance, I don’t know where I should put /Library/Printers/Canon. But it seems to me that I have all the files required to make it work.

Thanks! It seems like the “dead link” is just telling us how to install any printer using CUPS, sadly. But the second link might help me, given that I can try to extract a ppd driver from the provided macOS drivers.

Haha, now I can’t unsee it! I guess the whole thing was more obvious in person.

Haha, yes, I’m glad they chose not to!

Yes, fully open aperture, long exposure (6"), and high ISO. I tried to recover the yellows that were (much) more apparent to the naked eye, and this made it look more saturated

I had to use both since I don’t own a nice camera or lenses. I think exposure time was around 6 seconds. If you darken it by 2EV, it should be close to how it looked to the naked eye

I will very likely migrate to BTRFS on my next install. I’m reading Snapora’s repo now, looks like an awesome tool. Thanks for the tip!

You are right, I should have made this clear. I am not on Nvidia, I am using an old Thinkpad on Intel Haswell.

I’m glad to know my problem isn’t completely new. I’ll look into it further online. If you ever find a link to a report of a similar issue, I would be happy to see!

Edit: I found this link, the issue reported appears to be very similar to what I’m seeing here https://libreddit.tux.pizza/r/kde/comments/jhqbnz/kde_plasma_rendering_problem_black_squares/

Edit 2: I finally solved my problem! It was indeed an old problem already reported somewhere.

You are absolutely right. I just tried apt purge kde* plasma* libkf* and apt install kde-full followed by a reboot. But sadly, the problem persists.

I agree with that. I suspect you might be right. SDDM (Breeze) is also weird with transparency. However, I just installed materia-kde but unfortunately the problem persisted (screenshot attached). Before that, I ran apt purge kde* plasma* libkf* and apt install kde-full. That too didn’t solve my problem.

If I am not mistaken, I used a Debian KDE live image from the official repository then switched the mirrors from Bookworm to Sid. The system went months without a single issue, then this happen.

Your suggestion will actually be my solution of choice if everything else fails: reinstall / and import relevant files from a backup that I already have.

Thanks for the tip! However, I tried apt reinstall kde-full and apt --fix-broken install, but no packages were installed and (unsurprisingly) the problem still persists.

The Gentoo sub had such a nice subtitle because it is indeed accurate! Definitely one of the things I like the most about “flexible” distros.

“Gentoo Linux: Because you like it when the power is in your hands”

I do store regular backups of this machine, but not of /var. I can always reinstall Debian (or whatever other distro), while keeping other relevant configs intact (stored in the backups) and not lose any critical data.

I commented below that I did check /var/log/dpkg.log, but it didn’t help much due to the high number of packages removed that day.

At this point I am more curious to learn more about KDE and what is causing the problem, since other desktop environments (I installed mate) seem to work fine.

Sadly I am not using BTRFS for my root directory on this specific system. If I end up deciding to reinstall, I will definitely go back to BTRFS to avoid such problems.

Debian actually has a KDE group named kde-full. I reinstalled it but the issue persists, which was honestly surprising to me.

~$ sudo apt install kde-full
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
kde-full is already the newest version (5:147).
0 upgraded, 0 newly installed, 0 to remove and 87 not upgraded.

The new user idea was really clever, thanks for the suggestion! I will try that now and see.

Edit: the new user also presents the same problem. Actually, it makes sense, since SDDM is affected as well (I should have mentioned that before).