buffy

joined 10 months ago
 

I recently bought a used Canon Pixma Pro 100 and I was trying to get it to run on Linux, given that it's the only computer OS I've been using since forever.

From what I've seen, there are no official drivers for the printer and gutenprint doesn't support it. There is an alternative, called Turboprint, which is a paid proprietary software for Linux that seems to fully support the printer.

Well, I would never settle for a proprietary software solution, even though I wouldn't mind the least paying for software if it was FOSS.

A solution is clearly within reach, since others have done it. I am just wondering how hard it would be, and what would be the steps that I could take to come up with a solution. I've done some reverse engineering before, so I know it can range from straightforward to arduous and time consuming. I wonder if this would be too complicated and if I would be better off setting up a QEMU Windows virtual machine with the drivers (that is what I've tried and it works well) while I work on finding a proper solution. I'm now trying to extract the useful part of the MacOS drivers and see if it would work using CUPS. (this part was edited from the original post to address an originally inconsistent phrasing).

I would really appreciate if you could help me with this!

Below I have some further context, some background and references:

1- A post on the Canon community forum says that:

Unfortunately the "Pro" series of printers aren't supported, but if you don't mind paying a little money then check out Turboprint for Linux.

2- The printer doesn't seem to be supported by generic drivers, according to an Arch forum user

3- Another Linux Mint Forums user confirms that it doesn't work on Linux and suggests a printer driver wrapper

4- Dpreview users unanimously say the solution is either Turboprint or Windows VM, according to this post and this other post

5- A printerknowledge user links a post that seems to contain instructions on how to get the printer working on Linux, but it appears to be a dead link

Update 1: I found this link on stack exchange explaining how to extract ppd from dmg MacOS images. I extracted the ppd file and all the resources from the official MacOS driver provided by Canon. Now I need to replace MacOS-specific paths to something valid on Linux. There are three or so entries that I need to configure. I will update this post as I make some progress on adapting the drivers to Linux.

[–] buffy@lemmy.world 3 points 7 months ago

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

[–] buffy@lemmy.world 1 points 7 months ago

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!

[–] buffy@lemmy.world 1 points 7 months ago

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.

[–] buffy@lemmy.world 4 points 7 months ago* (last edited 7 months ago) (1 children)

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.

[–] buffy@lemmy.world 1 points 7 months ago

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.

[–] buffy@lemmy.world 1 points 7 months ago (3 children)

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.

[–] buffy@lemmy.world 2 points 7 months ago (2 children)

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.

[–] buffy@lemmy.world 1 points 7 months ago

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

[–] buffy@lemmy.world 3 points 7 months ago

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

[–] buffy@lemmy.world 2 points 7 months ago* (last edited 7 months ago)

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
[–] buffy@lemmy.world 2 points 7 months ago

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.

[–] buffy@lemmy.world 2 points 7 months ago (5 children)

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.

 

Hi everyone, I ran apt full-upgrade last month and accidentally deleted a couple packages that weren't supposed to be removed, due to me not paying enough attention. I could recover most of the system just fine, since most of the missing features and related packages were obvious to me. However, I still couldn't figure out why transparency is not working on KDE, both in Wayland and X. I suspected it could be a missing compositor, but libwayland and libqt6waylandcompositor6 (and related packages) are all installed (and that wouldn't explain why it isn't also working on X).

I have attached a screenshot to illustrate what I mean.

I would appreciate if anyone could help me figure out what package might be missing that is causing this issue. Thanks in advance!

EDIT: Thank you so much everyone! I finally solved my problem. I just had to replace libqt5quick5-gles by libqt5quick5 (non gles version).

Commandline: apt install libqt5quick5
Install: libqt5quick5:amd64 (5.15.10+dfsg-2+b2)
Remove: libqt5quick5-gles:amd64 (5.15.10+dfsg-2+b2)
view more: next ›