Thank you for your reply.
The entry was made withi Trisquel's default kernel.
I tried Xsane, like you suggested and the outcome is the same, my scanner is not recognized.
The same happened with Trisquel though until I installed libsane.
I guess this scanner cannot function with hyperbola's kernel.

Please remember that D-Bus is also a possible point as Hyperbola do not offer any Linux-only framework. Gnuinos is offering an own bus-implementation with ubus - as far I know. So this can be also a possible point, but I have no clue how to fix that. Same also for avahi: https://packages.debian.org/bookworm/libsane1

If sane and all the scanner-frameworks are only possible with that, we will surely remove that. Yes, a first harsh proposal, but without help I can't help or debug anything here. I have no scanner to test that.

I don't think this will be solved with a printer-scanner as this a complete different combination. Thanks for the offer but this is to be solved different and would also take much longer time to explain all needed steps. The Epson Workforce DS-70 is also too expensive even second-hand beyond 100 EUR. Too much for a single test-station.

Just to make sure: You have started the service, nparafe?

doas rc-service saned start

Or otherwise:

doas rc-update add saned default

Also to clear up: With D-Bus not being part many convinience-functions are not available and so far I recommend to have a look under /etc/sane.d/ as there being examples and configurations on how to connect the devices. So after a further look now for some hours this is would be the point to follow. For the moment I'm not able to support here further. But it is clear that the connection is missing while the device is nevertheless there and connected so sane is perhaps not recognizing that device automatically and needs more manual intervention.

I don't understand why you need to use those strange comparisons and escalations, jim. Nobody has said that you need to use a different system or an "old printer" - besides I dislike that wording "old" because a system is never "old" just not that longer in a wide usage. And for the moment I don't see myself in need to clarify anything here. So I ask again to calm a bit down in the tone: I only said that D-Bus is very deep implemented and making too convinient while Hyperbola with the ground interest in common UNIX is therefore quite different and in need to more manual configuration.

You can try to install cups and see where this leads. But also you need to verify that your printer-scanner is supported by the kernel at minimum. From there you can surely configure further. Also: If you are not okay with using hardware being a bit more in the years Hyperbola is not the system for your interest. As said: Hardware should be as long in usage as even possible. Hardware will be never in any way minor damage for the environment, but we can do the best to mitigate its harm done.

To clear that up: D-Bus is used for more and therefore other systems have therefore "convinience" while Hyperbola is not offering that.

Examples:

- no automatic configuration for the touchpad on notebooks
- no automatic scanner-detection and hardware is also not always given through further

The list goes on as D-Bus is sidewise not only a bloated and error-prone framework: It is also hiding parts giving the impression of "convinience" for other questionable results. And again also: If this is not okay, there are several other systems out there. We have no intention to add D-Bus back just for solving those points. I'm quite sure this can be done also different. Yes, this will take more time and configuration. But in the end every user has full control.

nparafe has asked for possible support and help, not for a discussion why "other systems offer that", jim. So if there is interest to solve or anyone has an idea? That helps for sure.

Again: You ask now for points I have no answers for the moment. Again also: I ask for solving that together instead to await a "ready-to-be-used" article in the wiki. You have just jumped over current steps and await from one person here an answer. And I see myself not in the position to give them alone. But I can explain that also: When you build packages and have no errors in running services so far like cups and / or saned, you do not see the need to solve any errors occurred. As there are now questions: Either we give answers and find answers together, or this one is not solved here and now. I underline: WE give the answer, not I write some text in the wiki.

So a possible way:

doas pacman -S cups sane
doas rc-service cupsd start
doas rc-service saned start

The problem here: Every printer is different, every scanner is different. The ideal way forward is that we can come to a solution for nparafe here. Including also a generic solution. If you demand further a wiki-article, then I say and write: That is NOT possible for me alone as every resulting article would be for only mine perspective. I don't have the concrete scanner mentioned from nparafe and I do not know what kind of printer-scanner-solution you have, jim. So I think it is reasonable to await that working together is the best solution and this means also trying out. Nothing more, nothing less.

Just to note also how many different possible variations and support-levels are there: https://sane-project.gitlab.io/website/ … ernal.html
And if you like, you can get access to the wiki also supporting the creation of a concrete article, jim. But if you await from me that I guess about possible solutions or do the whole work alone, than you should really question your own approach on that when asking "Where can I see this on the wiki?". Right question, yes, but at the wrong step and time: We are not at this point for the moment.

And so far: We can even solve sane as the scanner is found. So the next step is to enumerate why there is no connection established. Debugging and solving is not possible on my side here, jim. That can be only done on the side where those devices are connected.

Maybe some users did not wish to have an auto detect printer-scanner with that program, so that may be why it does not work the same way, but if the wiki has information about "where it is indicated how to do this" what link did you find?

Seeing "A wiki is a single document for everyone." you than can likely update it if you think there are any mistakes.

There are no flaws in my logic on this issue, since it was not me who invented the Hyperbola!

For example, I came up with or developed some kind of product that should be used not only by me and my developer friends, but by any user. Personally, I think out of respect for my users I am obliged to make a detailed guide or wiki so that those who
interested or wants to use this product, you can configure, install, use and understand how it works!

As for your opinion about nparafe, I’m also a user who has a printer and scanner that should work and I’m asking a question on this topic - setting up a printer/scanner, since there is no information on this issue either in the wiki or here or on the forum .
I am sure that if nparafe has a question about setting up its equipment, he will ask in this topic.

I don’t understand the logic when someone developed their product and tells users, let’s set it up together??????

Regarding the cost of developing a wiki. You have already said many times that all your efforts are aimed at developing HyperbolaBSD, this is great, thank you for your work, I want to ask you since many people left the Hyperbola project, as you yourself wrote about it, where on the site you wrote:

Dear friends!

Our project is looking for a developer or several developers to help us write a wiki within 2-6 months!
Write to...@hyperbola...

You give them a technical task and they work. Why ask an ordinary user who may not know any languages and just wants to use Hyperbola to create something together, this should be done by a professional! Maybe you’re trying to save money this way, but in my opinion, with this approach, there won’t be a wiki for another 10 years! If there was a ready-made wiki and you would invite users to correct something and test it together, it would be logical.