![]() ![]() Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) The USB connection to the scanner from xsane specifically?ĪPT policy: (500, 'stretch'), (500, 'testing'), (500, 'stable') That's why I have used a USB connection until this point.)ĭo you have any ideas on what might have changed that is invalidating ![]() Scanimage: open of device brother4:net1 dev0 failed: Invalid argument Have no recollection of trying with scanimage before:Įrdos:~ $ scanimage -x 210mm -y 297mm > Desktop/out1.ppm With scanimage, and I have never been able to do so with xsane - I (Incidentally, I can't open the network variant of the printer even Permissions 0666 doesn't make a difference to the xsane failure. Running chmod as root to change /dev/bus/usb/002/003 to have Scanimage: rounded value of br-y from 297 to 296.973 Scanimage: rounded value of br-x from 210 to 209.981 Running the scanimage command works fine however:Įrdos:~ $ scanimage -d 'brother4:bus1 dev3' -x 210mm -y 297mm > Desktop/out.ppm xsane starts fine, butįailed to start scanner: Invalid argument That didn't help either (even after a reboot). SUBSYSTEM!="usb_device", GOTO="brother_mfp_end" SUBSYSTEM="usb", GOTO="brother_mfp_udev_1" ![]() # copy to /etc/udev/rules.d or /lib/udev/rules.d So I installed the package from Brother brother-udev-rule-type1 which Ii brscan4 0.4.3-3 amd64 Brother Scanner Driver ![]() Ii brscan-skey 0.2.4-1 amd64 Brother Linux scanner S-KEY tool I already have brscan4 and brscan-skey installed: I looked on the internet for ideas, and figured that it might be a I am a member of the lp and scanner groups: These are the same physical device, but I am trying to use the USBĬrw-rw-r-+ 1 root lp 189, 130 Jun 11 22:29 /dev/bus/usb/002/003 When I start xsane, it offers me two scanners, matching those reportedĭevice `brother4:net1 dev0' is a Brother HomePrinter DCP-9020CDWĭevice `brother4:bus1 dev3' is a Brother DCP-9020CDW USB scanner Now, I'm assuming that it is most likely to be something in one of theĬups packages which has caused the problem. Will install 57 packages, and remove 1 packages. IMPORTANT: this log only lists intended actions actions which failĭue to dpkg problems may not be completed. Last night, I scanned an image using xsane with my USB-connected ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |