Thanks! I didn’t have the icc profiles correctly set, which might be one of the problems with my setup.

I was initially having issues with the Raster2CanonIJS and Command2CanonIJ binaries (that I copied to /usr/lib/cups/filter): cups was raising some errors when executing the scripts. But after fixing those, I wouldn’t get any further errors or warnings, although the printer would simply be unresponsive while the job was set as “completed”. I will check if the problem was the lack of icc profiles under /usr/share/color/icc.

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 for the recommendation! I tried both, but sadly it didn’t work.

I could extract the ppd file from the MacOS driver, but I still need to substitute some OS specific paths that lead to executable files and icc profiles, like *cupsFilter: "application/vnd.cups-raster 0 /Library/Printers/Canon/BJPrinter/Filters/Raster2CanonIJ/Raster2CanonIJS.bundle/Contents/MacOS/Raster2CanonIJS". Not that many, just two or three. I will most likely try to install the drivers on a MacOS VM and see if I can extract those files and place them in a Linux-specific cups directory (/usr/lib/cups or something). I think so far the odds are even.

Update: It looks like I have all the binary files with me. Raster2CanonIJS, Command2CanonIJ, the ICC profiles and whatnot. I’m now looking for some guidance on where I should place those files on Linux, that would belong in /Library/Printers/Canon/..., etc. on MacOS.

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.

You are right, those are contradictory. I meant doing it for now and sandboxing the VM while I work on finding a solution. I’m now trying to extract the useful part of the MacOS drivers and see if I can run it natively on Linux.

Edit: I edited the original post slightly to address your point, which I fully agree with.

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

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

Indeed it looks like a bug. I finally found a solution, though. Check the main post edit for details.

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!

I did check it, yes, but the page doesn’t appear to be relevant or contain much information. Another comment above (or below) mentioned that KDE Plasma can’t run without a compositor.

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.

Tasksel seems to be correctly set,

~$ tasksel --list-tasks
i desktop       Debian desktop environment
u gnome-desktop GNOME
u xfce-desktop  Xfce
u gnome-flashback-desktop       GNOME Flashback
i kde-desktop   KDE Plasma
u cinnamon-desktop      Cinnamon
u mate-desktop  MATE
u lxde-desktop  LXDE
u lxqt-desktop  LXQt
u web-server    web server
u ssh-server    SSH server
i laptop        laptop

I tried apt reinstall kde-full, but unfortunately nothing changed.

I tried reinstalling kde-full, but sadly nothing happened (all packages were already marked as installed).

I audibly laughed at this. I actually knew I was entering treacherous waters by running apt full-upgrade in Sid, but still thought “well, we’ll see…”

Thanks! Some packages were installed, but it didn’t solve it yet (even after a reboot).

...
Install: orca:amd64 (46.0-1, automatic), libpcaudio0:amd64 (1.2-2+b2, automatic), speech-dispatcher-audio-plugins:amd64 (0.11.5-4, automatic), python3-brlapi:amd64 (6.6-5, automatic), xbrlapi:amd64 (6.6-5, automatic), speech-dispatcher-espeak-ng:amd64 (0.11.5-4, automatic), libsonic0:amd64 (0.2.0-13, automatic), sound-icons:amd64 (0.1-8, automatic), python3-speechd:amd64 (0.11.5-4, automatic), libespeak-ng1:amd64 (1.51+dfsg-12, automatic), python3-louis:amd64 (3.29.0-1, automatic), x11-session-utils:amd64 (7.7+6+b1, automatic), xkbset:amd64 (0.8-1, automatic), task-desktop:amd64 (3.75, automatic), libdotconf0:amd64 (1.3-0.3+b1, automatic), xorg:amd64 (1:7.7+23, automatic), perl-tk:amd64 (1:804.036+dfsg1-2+b1, automatic), x11-apps:amd64 (7.7+11+b1, automatic), speech-dispatcher:amd64 (0.11.5-4, automatic), espeak-ng-data:amd64 (1.51+dfsg-12, automatic), task-kde-desktop:amd64 (3.75), xinit:amd64 (1.4.2-1, automatic)
End-Date: 2024-03-26  17:42:41

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.