| Summary: | kooka complains about no SANE installation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | T J McKenzie <tjm1983> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
T J McKenzie
2005-11-18 18:47:19 UTC
Setting up a scanner with sane can be tricky, I can only suggest to look at this project: http://hpinkjet.sourceforge.net/ (in portage as net-print/hplip) and to experiment with the 'sane-find-scanner' utility shipped with sane-backends. Apart from that, you can find more help for these issue in the forums, as this a support request more than a bug. Let's forget for a moment about the problem of getting my scanner working. The reason I put this in a bug report is that I think there's a bug. I don't know whether it's a problem that you guys can fix or whether it's a problem the Kooka developers need to fix, but all the same, something seems to be wrong: portage installed sane-backends, but kooka complains that sane isn't there. As far as I can tell, there are two broad possibilities: 1. When I re-emerged kdegraphics with the "scanner" USE-flag set, portage didn't install sane properly where Kooka could find it. OR 2. Sane is there properly, but when Kooka is opened with the -d command-line option, it gives a misleading error message (or possibly the wrong error message entirely). Remember, it claims that sane is not there at all. The fact that going to Settings --> Select Scan Device in Kooka does absolutely nothing (no error message; no message saying "I can't find any scanners"; etc.) is also arguably a bug. At the very least, it's got to be bad practice. I didn't originally make a big point of that one, though, because it's fairly clearly Kooka's fault, not the fault of the Gentoo developers. kooka indeed has various problems, as documented here for instance: https://bugs.kde.org/show_bug.cgi?id=110338 https://bugs.kde.org/show_bug.cgi?id=107390 https://bugs.kde.org/show_bug.cgi?id=93612 There could be other problems, but then you should help by doing some investigations, otherwise this bug is not really useful. Have you tried with other programs (e.g. xsane)? Have you tried to experiment with net-print/hplip and with sane-find-scanner? You are of course free to reopen and give more details. |
