You are not logged in.
Pages: 1
arch x86_64 / gnome 3 / Canon Pixma MP230
scanimage -Vscanimage (sane-backends) 1.0.24; backend version 1.0.24
-> is OK
scanimage -Ldevice `v4l:/dev/video0' is a Noname BisonCam, NB Pro virtual device
device `pixma:04A9175F_315075' is a CANON Canon PIXMA MP230 multi-function peripheral
then, with
scanimage --device pixma:04A9175F_315075 --format=tiff > test.tiffno work, i must kill de process
Any Ideas? I will not work withe the Drivers from Canon, to many 32-bit Dependencies.
Last edited by dino (2015-01-17 17:49:30)
Offline
sudo scanimage --device pixma:04A9175F_315075 --format=tiff > test.tiffworks. It is a permission Problem, i am in the group "scanner". Any Ideas to solved this?
Offline
Are you in the group "lp"?
See also:
https://bbs.archlinux.org/viewtopic.php?id=78703
Last edited by hifi25nl (2015-01-16 10:16:53)
Offline
@hifi25nl
Thanks for your answer! I am a member of the group 'lp'.
In the file '/usr/lib/udev/rules.d/49-sane.rules'is the following entry for my Canon:
# Canon PIXMA MP230
ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="175f", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"I have changed "0664" to "0666" - with the same result, only sudo can scan :-(
Offline
After I 've now got me with the problem to two nights of sleep , and customize sheer and taste of udev rules and directories get a big head , I resign myself.
I scan about 3-5 times a week , as I can with
sudo scanimage --device pixma:04A9175F_315075 --format=tiff > test.tiffand then
xsanefirst time live well.
Currently I'm testing nor the commercial software VueScan ( http://www.hamrick.com/ ), which has so far worked without complaint , just click this without any configuration , and sit back. If this is so , I 'm going to set the professional license for it.
Thank you for your willingness to help in this matter , but if someone can think what we can revive the thread so happy again ...
Offline
After I 've now got me with the problem to two nights of sleep , and customize sheer and taste of udev rules and directories get a big head , I resign myself.
I scan about 3-5 times a week , as I can withsudo scanimage --device pixma:04A9175F_315075 --format=tiff > test.tiffand then
xsanefirst time live well.
Currently I'm testing nor the commercial software VueScan ( http://www.hamrick.com/ ), which has so far worked without complaint , just click this without any configuration , and sit back. If this is so , I 'm going to set the professional license for it.
Thank you for your willingness to help in this matter , but if someone can think what we can revive the thread so happy again ...
I had similar issues to you and also found that vuescan works fine - my previous investigation of this issue seemed for my system to point to a problem with a scanner plugged into a usb3 port where the same scanner plugged into a computer that only has usb2 worked fine. I wonder if your scanner is plugged into a usb3 port? You might also find that plugging your scanner into a machine with only usb2 might work - this has been the subject of a bug report in the xsane scanner bug list for quite some time without a resolution yet.
Last edited by mcloaked (2015-01-17 15:31:20)
Mike C
Offline
I wonder if your scanner is plugged into a usb3 port? You might also find that plugging your scanner into a machine with only usb2 might work ...
Ah, I'm going to test it.
Offline
@mcloaked
You are the best!
After I have the printer / scanner plugged from USB3 to USB2, and restart the PC, everything works fine!
Offline
@mcloaked
You are the best!
After I have the printer / scanner plugged from USB3 to USB2, and restart the PC, everything works fine!
There are two things here - first it is great you have it working, but secondly this really does clinch the usb3 issue as being the problem and it would be so nice to have more information for the upstream discussion at sane-devel at:
http://lists.alioth.debian.org/pipermai … 32645.html
and the followup of the thread at http://lists.alioth.debian.org/pipermai … 32781.html
If you could provide any further diagnostics then the developers might be able to progress this issue. It has been a problem for quite a long while now.
Mike C
Offline
Pages: 1