It seems this package does not seem to install with latest version of boost. I had to downgrade to boost-1.86 and boost-libs-186 to able to install this.
/usr/include/boost/none_t.hpp:24:2: error: #error “Boost.Optional requires some C++11 features since version 1.87. If you have an older C++ version use Boost.Optional version 1.86 or earlier.” 24 | #error “Boost.Optional requires some C++11 features since version 1.87. If you have an older C++ version use Boost.Optional version 1.86 or earlier.” | ^
So this is a compatibility issue? Plot thickens.
Even your output errors are in error (re: version)? Trippy.
For me AUR did not see the scanner but the Flatpak did.
You also have the variables of cable, socket, usb-2/3, type 3 connector I think, etc etc. I’ve changed them all out before til I found success.
I just switched over from Linux Mint because of the NVIDIA driver problems.
Endeavour OS with its NVIDIA drivers install & using Linux Kernel 6.12.15-1-lts has fixed that issue… but I used the EpsonScan2.deb driver on Mint without any problems.
Hopefully this issue gets sorted out. I’m very happy with Endeavour OS with KDE!
Ok, that is weird. I was just going to ask you if there was a specific reason you need to use the Epson program. I have been using xsane for years and I was going to say it works great with all my printers, including my XP-4105, but I just launched it and noticed the printer is no longer showing up. It is also no longer showing up in my print settings. I can’t connect over LPR like I was before.
I’ll check it out and see what is going on. Ever since KDE updated the print setting my printers have been acting weird, even the trusty HP Smart Tank.
My scanner uses the “utsushi” backend (yours is a different model so you’ll have to check the list, or just try them both) so I installed imagescan. To enable WiFi scanning I also installed imagescan-plugin-networkscan.
I almost forgot to say, for a frontend I also installed simple-scan.
sudo pacman -S simple-scan
simple-scan is the Gnome project’s GUI SANE frontend. It’s more or less fine and doesn’t have too many dependencies. Probably any frontend you prefer will be fine. Anyway, once I set up the SANE config stuff the scanner popped right up in simple-scan and now it Just WorksTM.
you have to find this obscure list of epson scanner or all-one-models and see what linux packages they belong to. It’s cra-cra.
you know how hplips services 95% of linux HP machines?
Epson (and brother btw) has never been that forward thinking–there is no one-size-fits-all scanner driver
When I first got my V39, on Solus, I had to crack open .deb package and and have the scr plugin in the right folder with all else and used Utsushi to glue this hack job together successfully, strangely.
some Epson models will on work with the iscan package
some Epson models will only work with utsushi
if you forgo all that stuff and solve it with sane packages, non-Epson, then you can get stuff like Gscan2pdf etc to work just fine and see your scanner.
for my V-Series, when the epsonscan2 finally came out, it has consistently worked and solved all my problems.
I figured out how to downgrade boost1.87 to boost1.86.
sudo yay -Rcns boost1.87
And
sudo yay -Rcns boost187-libs
I then installed boost186 & boost1.86-libs
Unfortunely this still results in the same error message!
/usr/include/boost/none_t.hpp:24:2: error: #error "Boost.Optional requires some C++11 features since version 1.87. If you have an older C++ version use Boost.Optional version 1.86 or earlier."
24 | #error "Boost.Optional requires some C++11 features since version 1.87. If you have an older C++ version use Boost.Optional version 1.86 or earlier."
It’s likely due to a compatibility issue with the Boost library included in the Epson Scan 2 software package you are installing from the package build where the version of Boost on your Arch system might not match the version expected by the scanner software, leading to conflicts and preventing it from running properly.
The naintainer of the AUR package would need to deal with it if tha’s the issue. Did you look at the package build to see what boost version it is using?
