Rebuilt with updated spec file

Renaming to 'eternal-terminal' for clarity and to ease searching

Clean up after code review

Remove redundant build packages

Both my host machine and guest are running Plasma

1. Samba testing - pass ✅

Fixing the rebase

• Bump after glibc update

Changes to package.yml after review. Added a maintainers file

Updates from review notes

Is anything needed from me to move this forward?

@darkben The change that should hopefully fix the issue you were seeing has merged. Would you be able to test it out? Let us know if you still see issues.

@Staudey , @livingsilver94
After looking at the README.md at https://github.com/thesofproject/sof-bin, the upstream maintainers recommend moving certain files leftover from installations < 1.7 to a backup directory. Has Solus done this kind of thing in the past, and if so, what's a recommended directory path? It looks like the cp commands in the package.yml should be replaced with mv. We should also clean up files that were installed incorrectly to the wrong directory. After this is decided it should be easy enough to change the install directory to the correct place.

I'll take a look at this in the next few days. My laptop does have an Intel audio device. I don't have any errors but I can look at the folder issue.

@MechAlbatross, would you mind trying again? hplip was recently updated to 3.21.8 on 10/18 (D11915)

@oly , would you mind trying again? hplip was recently updated to 3.21.8 on 10/18 (D11915)
Let us know if the problem persists.

Updated commit after pulling in latest changes from origin/master

In D11920#200499, @JoshStrobl wrote:

Marking as pending changes per @algent's remarks.

Reset branch to origin/master and applied change

Correct revision number

Review fixes

@stalebrim - I just checked and 3.21.8 has been released recently. Would you be able to update this? I saw in another diff that you're rather busy these days & switching to Fedora. If you don't have time, I can update the package. I'm keen on having this updated in the repos, having an HP printer :)

In D11194#199626, @JoshStrobl wrote:

@TClark77 So in summary excluding the fact that the extra dependency will need to be after, once the patch lands, was there any regressions in your experience compared to previous releases?

I had asked in IRC if it would be OK to update this diff to 1.8 and received the OK

Resolves T9501

Fix line break in package.yml

Also, the systemd unit is created, but not enabled. Given that the purpose of autofs is to automatically mount a filesystem at startup, I recommend making the install of autofs enable the system unit and start autofs

On a whim I reinstalled the cups package, and that has fixed the printer settings dialog.

The python error causing hp-toolbox to fail to launch is due to a missing dependency. I saw in this thread that the .py errors were resolved by installing 'python-distro'. Adding that as a dependency should solve the issues I saw in testing.

1. Testing summary

I just saw this is waiting on me, I'll test it out tomorrow.

Adding missing files after updating common

Updating after make

Adding pspec file

Initial inclusion of purple-plugin-pack

I installed the eopkgs for hplip and hplip-driver on my main Solus install that I had tested for D11194 in a VM. They installed OK and I got the expected prompt to install the driver from hplip. I can still scan, but the Printers dialog still receives the errors described previously. I am still unable to print. I get an error "Unable to star the printer. Please check your settings and try again".

I renamed /etc/cups/cupsd.conf and copied /etc/cups/cupsd.conf.default to /etc/cups/cupsd.conf and restarted cupsd. No joy.

I've just updated to Plasma 5.22.4
KDE Frameworks 5.84.0

Out of curiosity I did a little research and found there's still no fingerprint-gui available that works
I found there's a fork of fingerprint-gui but I couldn't get it to compile on my system.

@Girtablulu The hplib patch allowed me to print in the test VM. It wasn't experiencing the same errors as the laptop, but the VM hadn't been updated in a few weeks. Can we keep this open until I can test the patch on my actual laptop? I'll update as soon as the patch lands and my laptop has it.

1. Testing summary

Thanks @Girtablulu , I'll be able to give that a try tomorrow.

Confirmed the bug still exists with the latest plasma update on unstable

So a funny thing happened on the way to the access point....

That's probably the cause.
Booting with kernel 5.11.21-179.current didn't change anything.