Bug 197659 - Scanner Tool can't find the scanner
Summary: Scanner Tool can't find the scanner
Status: RESOLVED WORKSFORME
Alias: None
Product: kooka
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Jonathan Marten
URL:
Keywords: investigated, triaged
: 197657 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-06-23 21:54 UTC by fanisatt
Modified: 2018-10-21 05:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fanisatt 2009-06-23 21:54:40 UTC
Version:           xsane 0.996-7 (using KDE 4.2.4)
OS:                Linux
Installed from:    Fedora RPMs

I have installed Fedora 11. I knew the procedure to make my scanner working with Sane (gt688xx-firmware file - etc).
I did all these and my scanner was working fine.
After I took some updates of the repositories ( I have checked the fedora 11 test updates too) I noticed that my scanner did not work.
The error report of scanner tool is : no devices available.
Comment 1 FiNeX 2009-06-23 23:47:56 UTC
*** Bug 197657 has been marked as a duplicate of this bug. ***
Comment 2 Jonathan Marten 2009-06-25 13:48:57 UTC
Can you confirm the version of Kooka that you are using - it is not included in KDE 4.2.  Please also confirm scanner model and connection type (USB, network etc) and installed SANE version.

Does the scanner work with xsane after the updates?  If it does not, then it is more likely to be a SANE or kernel problem.
Comment 3 fanisatt 2009-06-25 17:48:14 UTC
Thank's for your answer.
I can't see any cooka version. It is xsane 0.996.
I have a Mustek USB scanner. It's a local one , there is no network.
The scanner was working very good on Fedora 11 , but after some updates I noticed the problem. I remember that the first days there was an xsane option in the graphics menu. After the updates there is the "scanner tool" option in the graphics menu.
If it is a kernel problem , you believe it would be better for me to work with fedora 10 ?
I was very good with Fedora 10.
Googlearth doesn't work too in Fedora 11. 
Thanks a lot. 

--- Στις Πέμ., 25/06/09, ο/η Jonathan Marten <jjm@keelhaul.me.uk> έγραψε:

Από: Jonathan Marten <jjm@keelhaul.me.uk>
Θέμα: [Bug 197659] Scanner Tool can't find the scanner
Προς: fanisatt@yahoo.gr
Ημερομηνία: Πέμπτη, 25 Ιούνιος 2009, 14:48

https://bugs.kde.org/show_bug.cgi?id=197659


Jonathan Marten <jjm@keelhaul.me.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDSINFO
         Resolution|                            |WAITINGFORINFO




--- Comment #2 from Jonathan Marten <jjm keelhaul me uk>  2009-06-25 13:48:57 ---
Can you confirm the version of Kooka that you are using - it is not included in
KDE 4.2.  Please also confirm scanner model and connection type (USB, network
etc) and installed SANE version.

Does the scanner work with xsane after the updates?  If it does not, then it is
more likely to be a SANE or kernel problem.
Comment 4 fanisatt 2009-06-25 17:56:02 UTC
I remember , that when I installed fedora 11 there was an alert for kernel problem. The bug was automatically reported.

--- Στις Πέμ., 25/06/09, ο/η Jonathan Marten <jjm@keelhaul.me.uk> έγραψε:

Από: Jonathan Marten <jjm@keelhaul.me.uk>
Θέμα: [Bug 197659] Scanner Tool can't find the scanner
Προς: fanisatt@yahoo.gr
Ημερομηνία: Πέμπτη, 25 Ιούνιος 2009, 14:48

https://bugs.kde.org/show_bug.cgi?id=197659


Jonathan Marten <jjm@keelhaul.me.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDSINFO
         Resolution|                            |WAITINGFORINFO




--- Comment #2 from Jonathan Marten <jjm keelhaul me uk>  2009-06-25 13:48:57 ---
Can you confirm the version of Kooka that you are using - it is not included in
KDE 4.2.  Please also confirm scanner model and connection type (USB, network
etc) and installed SANE version.

Does the scanner work with xsane after the updates?  If it does not, then it is
more likely to be a SANE or kernel problem.
Comment 5 fanisatt 2009-06-26 12:02:46 UTC
Well, I am not good on Linux O.S. I don't know how to make things here.
According to the bug system report I had to declare the application with the problem. I have installed xsane 0.996-7. There is no kooka in fedora rpms. I remember that after I installed Fedora 11 and took the first updates , I installed xsane too. After that , I made a subdirectory named gt68xx into the /usr/share/sane directory (login as root). After that, I copied in this subdirectory the firmware file A1fw.usb for my Mustek Bearpow 1200 CS scanner.
After that, I checked my scanner and it was working fine. That is the initial story. During the next days I was taking updates from fedora RPMs normally.
3 days before I tried to use the scanner , but it is impossible to find it.
The sane-find-scanner command , finds my scanner.
The scanimage -L command (as root) finds the scanner too.
Comment 6 fanisatt 2009-06-26 13:56:45 UTC
I have news. My usb scanner is the device 002 on bus 008. lsusb says it.
Giving as root the command chmod a+rwx /dev/bus/usb/008/002 then the scanner works fine , BUT ...... I have to give the command every time I restart my PC.
Comment 7 Andrew Crouthamel 2018-09-19 04:28:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-21 05:00:20 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!