Interest in this package is not very high. I guess this can be closed. I'm also no longer on Solus.

This can be closed. I'm no longer on Solus.

Please let me know if you need even more info.

I also have this 2 drives in this machine. I was able to install Solus KDE 4.1 on the 840 when it was in another PC.
Samsung SSD 850 PRO 256GB at sdb
Samsung SSD 840 PRO Series at sda

Yeah, here is the nvme:

@kyrios123 I can confirm driverless printing works for me and all file permissions for cups and cups-filters are correct now. Thank you very much for resolving this issue!

Hi, I tried to test it. I switched to unstable, but didn't get the new 1.26.1 package. How can I test it? Or do you mean I should test it from github?
Here is a screenshot of what I tried:

Here is the commit for the cups-filters fix: https://github.com/OpenPrinting/cups-filters/commit/b3319242fbf528ba9e80c9b4287daee3d31343a1

@kyrios123 Please revert the changes to cups so we don't break Kerberos authentication. We already have a new solution that works without modifications to the cups package. I guess it will land in cups-filters 1.26.1.

Thank you @kyrios123! Sadly the cups "fix" will break Kerberized printing. I don't know if this is an issue for our users. I personally don't use it so it's ok for me.
I created a new issue for cups-filters to discuss how we can fix this otherwise.
https://github.com/OpenPrinting/cups-filters/issues/183

Thank you very much @GueGuerreiro.

I looked further into this. Ubuntu applies a distro specific patch for 755. I created a pull request for cups to fix this upstream.
Please vote/thumb up for it here:
https://github.com/apple/cups/pull/5710

This is fixed with cups-filters 1.26.0 and "sudo chmod 755 /usr/lib/cups/backend/ipp". Can someone check why we don't have the correct file permissons for /usr/lib/cups/backend/ipp?

Any more information needed?

I'm unable to use the ripcord XML-RPC client without this:
PHP Fatal error: Uncaught Ripcord_ConfigurationException: PHP XMLRPC library is not installed in ripcord_client.php:132
https://github.com/poef/ripcord

@siru :
Can you please try if this PR fixes your problem?
https://github.com/OpenPrinting/cups-filters/pull/173

I can confirm the backwards compatible problem pointed out by @ReillyBrogan. This broke my install. This was the error message:
sudo systemctl start docker.service
sudo journalctl -xe
dockerd[31412]: failed to start daemon: error initializing graphdriver: /var/lib/docker contains several valid graphdrivers: overlay, overlay2; Please cleanup or explicitly choose storage driver (-s <DRIVER>)

I guess some of these issues are related to TLP. Please try uninstalling TLP. Then do a reboot and try again.

Yeah, there are still issues.
I'm currently being mentored by one of the cups-filters devs to contribute a fix for legacy network printers. Maybe that will also help in your case because it also might be related to some old IPP stuff.

1.25.5 is better because it fixed some issues. Sadly for old network printers you still need to downgrade to 1.23 for driverless printing.

Hi, I tried 1.25.4 3 days ago. Sadly, it doesn't fix my problem.

No, the patch is not a fix. deepak0405 only provided it to gain more verbose debug output.

Never mind I did it on a VM and posted to github.
Special thanks to chax on IRC for the --disable-mutool configure option!

Hi, I'm afraid I need someone to hand-hold me here.

Oh, I see. Looks like an upstream problem: https://github.com/OpenPrinting/cups-filters/issues/124

I'm not sure what you mean? Did I make a mistake? I can provide any additional logs if needed, but please give me instructions how I can obtain them.

Yeah, I can provide that. It's kinda short, so I post it here:

Nice!

Have the same problem with rts5249.
lspci says something like Unassigned class

Wow, just got this updated. Last week I checked if other distros got this included - none of them had - seriously even on the arch aur there was just a barely working sandbox bin version of this. You guys are doing an awesome work! I really hope you get that patreon up and running soon again and give that package maintainers a fair share of that money!!!

As a workaround until we get a maintainer for pgadmin4 I recommend running it via docker.
https://hub.docker.com/r/dpage/pgadmin4/
Here is a nice full example how to use it when you are already using docker-compose for postgres:
https://stackoverflow.com/a/51172659
It runs superb for me.

Thanks for the info. I commented there as well.

So I opened it via "QT_LOGGING_RULES="*.debug=true" kdenlive" and it works. Now it also works if I open it normal. I really don't know why it works today. I tried it some weeks ago and also yesterday (even uninstalled and reinstalled several times) and it always froze. I guess we can close this. Thanks for the help!

Thanks for including. I removed the snap package and installed it via the software center.
What doesn't work for me with the software center version is clicking on links in other apps (tested with slack, vscode).
For example a coworker sends me a link in slack and I click on it. Now Brave gains focus but it doesn't open the link.

I installed mscorefonts following this http://www.fosslinux.com/1387/how-to-install-microsoft-true-type-fonts-in-solus.htm.
Now most of the fonts work again (google.com etc.).
The most annoying that this doesn't fix is when I look at the source of a website. Inspector tells me it's monospace font.

I have no problem with installing brave via snap.

Sadly I have to kinda quote lunduke here -
Recent events showed firefox (or better said the mozilla corp) is no longer trustworthy.
If you want a browser that installs extensions without telling you about it.
If you want a browser that collects (or helps collect for others) data on you without your consent or knowledge.
If you want a browser that actively works to restrict the content you can asscess via DRM.
If you want a browser from a vendor that funds organizations that specifically exclude and block you.
If you want a browser from a vendor who actively works to censor you.
...
Go with firefox.

So today I updated my solus system and tried printing again and it printed!!!!! I still got 2 printer errors, but I don't really care, it fucking printed!! Yes! Thanks solus team. You are awesome!