xsane only scans as root

Probably the same problem as bug #121082 -- the udev scanner rules have been removed and whatever hal is supposed to be doing instead isn't working. Try getting a copy of /etc/udev/rules.d/45-libsane.rules from a gutsy machine (and I'll attach a copy here) -- that fixed it here.

Thanks for the suggestion. I just left my scanner in storage at school for the summer, so I won't be able to test it until late August.

Actually Brother has now posted specific instructions for Ubuntu 8.04 on their website (http://solutions.brother.com/linux/sol/printer/linux/linux_faq.html#9):

1. Open "/etc/udev/rules.d/40-basic-permissions.rules" file.
2. Edit "0664" to "0666" in "USB devices" section.

Before the edit --------------------------
# USB devices (usbfs replacement)
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0664"
SUBSYSTEM=="usb_device", MODE="0664"

After the edit --------------------------
# USB devices (usbfs replacement)
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
SUBSYSTEM=="usb_device", MODE="0666"

3. Restart the system.

I can't test it, but I'm assuming they have.

Is this symptom still reproducible in 8.10 or 9.04?

I'm still seeing it on 8.10

I am using 8.10 and it is not working.
The workaround by Brother didn't help, because the suggested changes were already done.
That is what it looked like right from the start.
    # USB devices (usbfs replacement)
    SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
    SUBSYSTEM=="usb_device", MODE="0666"
Also see my comments here: https://bugs.launchpad.net/ubuntu/+bug/324783
I am going to contact their support and maybe we can get something out of it :)

I made the change you mention (from http://solutions.brother.com/linux/en_us/instruction_scn1c.html#9) and it is working for me as a normal user.

I still have this problem with jaunty,
the above mentioned method worked for me in older Ubuntuversions, but the /etc/udev/rules.d/40-basic-permissions.rules file isn't present anymore to edit.

In /etc/udev/rules.d/README I noticed this:

[...] Packages do not generally install rules here, this directory is for
local rules. If you want to override behaviour of package-supplied
rules, which can be found in /lib/udev/rules.d, you can do one of
two things:

 1) Write your own rules in this directory that assign the name,
    symlinks, permissions, etc. that you want. Pick a number higher
    than the rules you want to override, and yours will be used.

 2) Copy the file from /lib/udev/rules.d and edit it here; you
    should generally only do this if you want to prevent a program
    from being run.
[...]

I didn't have much time to experiment with a local rules files, so I went ahead and edited directly this file:
/lib/udev/rules.d/50-udev-default.rules

And it worked for me. So my workaround for this problem is:
1) Open a terminal window
2) gksudo gedit /lib/udev/rules.d/50-udev-default.rules
3) Make sure the following line has MODE=" 0666" at the end:

# libusb device nodes
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0666"

4) Restart the computer

I am not familiar with udev rules and as such I am not sure what other problems this may introduce, I'd appreciate if anyone else can elaborate on this.

My scanner is part of a multi-function DCP 7020 Brother printer/scanner.

lsusb reports:
04f9:0183 Brother Industries, Ltd DCP-7020

[Solved for Jaunty]
My solution to only being able to use a scanner as root in Jaunty, much simpler than udev.rules, is:
  1) lsusb
.......
Bus 002 Device 002: ID 04f9:0182 Brother Industries, Ltd Composite Device

(but see also sudo xsane , where the xsane top panel says 0.996 DCP-7010:bus3;dev2 )

2) sudo pcmanfm
go to /dev/bus/usb/002/002
(Might want to try /dev/bus/usb/003/002 as well if this bus no. confusion exists)
Right mouse click > properties > permissions
Allow Run for Group and Other Users.

3) Reboot. I can now scan as a normal user.

solar3:

Your solution works of course, but it is manual work and we want to
avoid setting permissions manually to invidivual devices. Therefore the
correct solution would be to fix udev rules so that the device's
permissions are correct by default.

I hope somebody with access to the upstream udev rules would fix this
now, please.

I can also confirm that this still is a problem with Jaunty and Epson V100 scanner.

This issue has re-appeared in 9.04 release for me.

In 9.04 we must edit /lib/udev/rules.d/50-udev-default.rules and change:

# libusb device nodes
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0664"

to

# libusb device nodes
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0666"

and restart.

Fix from VPablo works well for me. Thanks!
Ubuntu 9.04 x64, Brother printer/scanner DCP 7025

The VPablos fix doesn't work for me on Ubuntu Jaunty 9.04, because it disables both of my USB mice multiseat setup. What I had to do for my Fujitsu 4120c is to add file
/etc/udev/rules.d/45-libsane.rules
with the following content

# Fujitsu fi-4120C
SYSFS{idVendor}=="04c5", SYSFS{idProduct}=="1041", MODE="664", GROUP="scanner"

I also had to add group scanner

sudo addgroup scanner

and add myself and other users which should have access to the scanner to this group

sudo adduser some_username scanner

After reboot scanning works beautifully. This rule came from
http://forum.ubuntu-fr.org/viewtopic.php?pid=2707917
but the venfor and product can by discovered simply by running

xxx@yyy:~$ sane-find-scanner
...
found USB scanner (vendor=0x04c5, product=0x1041) at libusb:002:002
...

bastafidli fix is good and I think it's the best because only acts on the device we need and allow limit users can use the scanner.
It works fine for my kubuntu 9.04
Thanks.

I'm experiencing the same problem with MFC-7820N but then as a network printer.

gscan2pdf (very nice app! covers what I do 99.999% of the time, scan
a mulitpage doc to a pdf) exhibits the same problem.

Any ideas on how to debug this problem for a network scanner?

@bastafidli thank you, your fix also works for me and I'd favor it as it allows control of who scans.

I initially suspected Policy Kit so I used polkit-gnome-authorization to set proper scanner access but it didn't have any effect.

I too have a networked Brother MFC-7440N with the same problem.. nothing Brother suggested worked.. their last suggestion was to reinstall my os. Works with sudo xsane, doesn't work with standard user.. Ubuntu 8.10 & 8.04 (two different machines.

I can confirm that his bug persists within Ubuntu 9.10 (Karmic Koala). I use a Brother DCP 7010, which is only recognized by both lsusb and sane-find-scanner when executed as root.

The solution proposed by bastafidli *does not work* in 9.10 !!!

While the minmal-invasive solution for just a single device does not work, the solution provided by VPablo works in 9.10 as well. Since there does not seem to be a default rules file anymore, I added the file /etc/udev/rules.d/95-udev-late.rules, having the following content:

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
SUBSYSTEM=="usb_device", MODE="0666"

This makes the scanner work in 9.10.

The udev rules file in 9.10 is located here: /lib/udev/rules.d/40-libsane.rules

        Thanks for this.
        Xsane works fine with HewlettPackhard multi-functions - right
        out of the box.
        Brother is waaay behind here.

        Cheers,

        wordsmyth

Alesh Slovak @avasys wrote:
> The udev rules file in 9.10 is located here:
> /lib/udev/rules.d/40-libsane.rules
>
>

I search the i-net and found on http://forum.ubuntu-nl.org/hardware-en-drivers/9-10-en-brother-dcp-135c-no-way!/msg503627/ the following for my scanner.

We gaan het bestand /lib/udev/rules.d/40-libsane.rules aanpassen met de editor nano. Gebruik geen gedit, daar deze een backup achterlaat en dit is niet de bedoeling. Dus:

We are going to ajust the file /lib/udev/rules.d/40-libsane.rules with the editor nano. Don't use gedit because it left a backup file. We don't want that.

  sudo nano /lib/udev/rules.d/40-libsane.rules

Ga met de cursor helemaal naar beneden en voeg de 2 Brother regels toe, onder "Dell 1600n" en voor "The following rule will disable USB autosuspend for the device"

Go all the way down en add the following rule under "Dell 1600n and before "The following rule will disalbe USB autosuspend for the device"

# Brother scanners
ATTRS{idVendor}=="04f9", ENV{libsane_matched}="yes"

# The following rule will disable USB autosuspend for the device
ENV{libsane_matched}=="yes", RUN+="/bin/sh -c 'test -e /sys/$env{DEVPATH}/power$
LABEL="libsane_rules_end"

Bewaar het bestand door CTRL+x te drukken, dan Y of J (naargelang de taal) en dan op Enter te drukken.
Save the file by CTRL + x, then Y or J, (Related to your langeauge) then hit Enter.

I restarted my system and the scanner works without have to use root.

Herstart je systeem en probeer te scannen en te printen.

I use Ubuntu 9.10 with a Brother DCP 357c
Also lsusb let me see the printer without the use of sudo.

I just upgraded to Ubuntu 9.10 and I can not even scan as root(Brother MFC-7820N) anymore.

1. when I run "sudo xsane" => no devices are found

2. when I try just "xsane" I get a SEGFAULT

I'll try to reinstall the drivers to see if that helps...

Here's what I had to do to get scanning working again after upgrading from Ubuntu 9.04 to Ubuntu 9.10:

- uninstall drivers (sudo apt-get remove brscan2)
- reinstall

=> voila! I can scan as root using "sudo gscan2pdf"

When I try to run "gscan2pdf" as non-root, it never completes the "Fetching list of scanners" operation...

In contrast to what wordsmyth2 says, it doesn't work in karmic with my HP F4280 multifunction (details in bug 121082). It's not just a Brother problem.

9.10, here's how i got my MFC-7820N to work again
1.) I uninstalled brscan2 (NOTE: apt-get remove complained about missing directories so i created them so it could finish uninstall)
2.) ran brsaneconfig2
 see http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/instruction_scn1b.html
3.) launch xsane and now it found the device

I am a big fan of brother, there linux support has been great

oops. i forgot a step.
1.5) Reinstall brscan2 after downloading from here
   http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/download_scn.html

HEllo,

Same issue in Karmic : all worked fine in Jaunty, but I was unable to install Brother Scanner DCP-7030 on a fresh Karmic Koala (printing and driver are OK).

I donwloaded sane-utils / Brscan3 : http://solutions.brother.com/linux/en_us/download_scn.html#brscan3
Scanner Driver USB scan-key-tool : http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/instruction_scn3.html

I did : sudo gedit /lib/udev/rules.d/50-udev-default.rules
in section "libusb device nodes", I replaced 0664 by 0666

But no scanner was identified by xsane.

I used "sudo lsusb" command to see my scanner, it was on Bus 004 Device 003: Brother Industries, Ltd DCP-130C

Reason of impossible use was that device 3 was root owned.

So I opened Nautilus as root, went to dev/bus/usb/004 and device 3 (003 file) was with root permission only.
I modified it for my user name and now xsane works well, scanner is recognized.

Fix from Dave Grape works well on Karmic 9.10 amd64, with a Brother DCP-7025 printer/scanner.

Brother has new instructions and a .deb for Ubuntu. It's not the easiest thing to wade through their instructions to piece everything together for a distro and for each function. I recently did a fresh install of Kubuntu 9.10 and installed the driver(s). So far printing and scanning work like a charm. I've yet to get the faxing to work. I've attached step by step instructions as to what I did to get things working.. This should work the same on ubuntu as it does on kubuntu. I should note that in Brothers instructions there is mention that Ubuntu releases prior to (one I forgot) need to follow the instructions differently.

Same problem here with xubuntu 9.10 and a Mustek 600 II N scanner. I'm able to scan when doing a sudo xsane but not as normal user. Creating such a rules file (as mentioned in former posts) is not an option for me because the scanner is not a USB scanner (it has on own ISA card which seems to be a kind of parallel port - the scanner is also powered by this card). At least I don't have an idea which kind of port numbers or vendor numbers I need to add.

same problem here with Kubuntu 10.10 and a microtek scanmaker V6UPL.

creating /lib/udev/rules.d/50-scanner.rules with the line: ATTRS{idVendor}=="05da", ATTRS{idProduct}=="00b6", MODE="664",GROUP="scanner" and creating the group "scanner" and adding myself to that group fixed it.

Problem still exists :
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/701856

This bug still persist in ubuntu 12.10 amd64.

I had to change the following lines of "/lib/udev/rules.d/50-udev-default.rules"
from

# 'libusb' device nodes
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0664"

to
# 'libusb' device nodes
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"

Now the Borther DCP 7065 DN Scanner connected via usb is working.

Aaron Sarna, thank you for reporting this and helping make Ubuntu better.

As per https://wiki.ubuntu.com/Releases your release is EOL.

If you have an issue in a supported release (ex. 16.04) please file a new report, and feel free to subscribe me to it.