HELP! Can't Keep a Scanner Install on Ubuntu Mint

[David Kaye]

I hesitate to post here because this isn't a Linux newsgroup, but my
attempts at posting other places has landed me nothing. I know that many of
the people here are Linux geeks, so maybe I've come to the right place. If
not, please excuse me.

Here it goes:

HELP! Brother Scanner Won't Stay Connected on Ubuntu Mint Box
Okay, one part of it was a permissions issue, so here's the device list:

lsusb

Bus 003 Device 002: ID 046d:c016 Logitech, M-UV69a Optical Wheel Mouse
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 05d8:4002 Brother DCP-7065DN Scanner
Bus 002 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 005 Device 002: ID 0a12:0001 Bluetooth Dongle (HCI mode)
Bus 005 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

sudo chmod a+w /dev/bus/usb/002/002 gets the scanner working just fine.
BUT, this works ONLY while the computer is turned on. Reboot it and the
chmod reverts and/or the bus and/or device numbers change.

Does anybody know of a way to KEEP this connection from disappearing?

People have posted elsewhere asking for the OS version, but it's obviously
armchair quarterbacking because either a person has had experience with this
problem or they haven't. I'm looking for a real-world solution, not a
guess. I'm sure I'm leaving out something. Ideas?

Thanks, everyone!

--dk

[vallor]

Post by David Kaye
I hesitate to post here because this isn't a Linux newsgroup, but my
attempts at posting other places has landed me nothing. I know that
many of the people here are Linux geeks, so maybe I've come to the right
place. If not, please excuse me.
HELP! Brother Scanner Won't Stay Connected on Ubuntu Mint Box Okay, one
lsusb
Bus 003 Device 002: ID 046d:c016 Logitech, M-UV69a Optical Wheel Mouse
Bus 003 Device 001: ID 0000:0000 Bus 002 Device 002: ID 05d8:4002
Brother DCP-7065DN Scanner Bus 002 Device 001: ID 0000:0000 Bus 004
Device 001: ID 0000:0000 Bus 005 Device 002: ID 0a12:0001 Bluetooth
Dongle (HCI mode)
Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000
sudo chmod a+w /dev/bus/usb/002/002 gets the scanner working just fine.
BUT, this works ONLY while the computer is turned on. Reboot it and the
chmod reverts and/or the bus and/or device numbers change.
Does anybody know of a way to KEEP this connection from disappearing?
People have posted elsewhere asking for the OS version, but it's
obviously armchair quarterbacking because either a person has had
experience with this problem or they haven't. I'm looking for a
real-world solution, not a guess. I'm sure I'm leaving out something.
Ideas?
Thanks, everyone!
--dk

It sounds like you need some kind of udev rule to set the permissions on
the device.

This would be a file in /etc/udev/rules.d called "something.rules" with
the magic incantation to set up the device when it is detected being
plugged in, or at boot.

It would say something like (all on one line):

SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2832",
MODE:="0666"

Where you would substitute the vendor and product code for the device.
Based on your lsusb, it would probably look like:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="05d8", ATTRS{idProduct}=="4002",
MODE:="0666"

However, I am by no means a udev expert, and I probably don't have the
expertise you were looking for. But it seemed like I should probably say
something, because it looks very similar to a problem I had with my 3d
mouse.

Hope this helps,

[David Kaye]

Post by vallor
It sounds like you need some kind of udev rule to set the permissions on
the device.

Thank you. I think you're on to something. It's a pro bono situation and I
only have access to their office once a week, so I'll try this next time I'm
there.

[David Kaye]

Post by vallor
Hope this helps,

Since you have experience with this problem I'm sure it'll work just fine.
Wish me luck. Today at 5pm.

[David Kaye]

Post by vallor
SUBSYSTEMS=="usb", ATTRS{idVendor}=="05d8", ATTRS{idProduct}=="4002",
MODE:="0666"

It worked after some playing around. Thanks for your help!

[vallor]

Post by David Kaye

Post by vallor
SUBSYSTEMS=="usb", ATTRS{idVendor}=="05d8", ATTRS{idProduct}=="4002",
MODE:="0666"

It worked after some playing around. Thanks for your help!

Excellent! I'm glad it worked!

Thank you for posting about the results -- otherwise, would have been
left guessing. ;)

[Julian Macassey]

Post by vallor

Post by David Kaye
It worked after some playing around. Thanks for your help!

Excellent! I'm glad it worked!
Thank you for posting about the results -- otherwise, would have been
left guessing. ;)

I can't say how helpful it is when someone responds to a help
suggestion. You either can continue to help, or know that the fix/solution
works.

[Jeff Liebermann]

On Thu, 2 Feb 2017 01:15:15 -0800, "David Kaye"

Post by David Kaye
People have posted elsewhere asking for the OS version, but it's obviously
armchair quarterbacking because either a person has had experience with this
problem or they haven't. I'm looking for a real-world solution, not a
guess. I'm sure I'm leaving out something. Ideas?

You certainly know how to piss me off. You expect someone to spend
the time figuring out YOUR problem, yet you intentionally refuse to
supply basic information needed to untangle the mess or do a basic
Google search for anyone else with the same problem. Little things
like OS version, 32/64 bit, Mate or Cinnamon, update status, scanner
model number, driver version, are missing. Where did you get the
scanner driver? Here?
<http://support.brother.com/g/s/id/linux/en/download_scn.html>
Are you trying to make things harder for me, or merely limit the
number of responses you'll get? Please explain your rational.

Meanwhile, I dug this up:
<https://forums.linuxmint.com/viewtopic.php?t=223372>
Looks like there are scanning issues in Mint 18, but it works with 17.
Also, please notice how everyone in the Linux Mint forum includes
their hardware and software configuration to make questions easier to
answer.

Also, run dmesg or try digging through:
/var/log/boot.msg
/var/log/syslog
and see if there are any boot time error messages involving the
scanner driver.

Jeff "Armchair 1/4 back" Liebermann

[Jeff Liebermann]

Post by Jeff Liebermann
Where did you get the
scanner driver? Here?
<http://support.brother.com/g/s/id/linux/en/download_scn.html>

I forgot to mumble that the Brother DCP-7065DN is a brscan4 model.
<http://support.brother.com/g/s/id/linux/en/download_scn.html#brscan4>

More on scanning from Brother:
<http://support.brother.com/g/s/id/linux/en/instruction_scn2.html>

If you're running Scan-key-tool:
<http://support.brother.com/g/s/id/linux/en/instruction_scn5.html>

[David Kaye]

Post by Jeff Liebermann
You certainly know how to piss me off. You expect someone to spend
the time figuring out YOUR problem, yet you intentionally refuse to
supply basic information needed to untangle the mess or do a basic
Google search for anyone else with the same problem.

(1) I HAVE done lots of Google and Bing searches and not come up with
anything that works. (2) What we're talking about is basic Linux, which
should work with any distro. It looks to me like something was missing in
Brother's original installation file, and that's what I'm looking for. (3)
The computer is only accessible to me once a week, and I mislaid the note
with the driver details, OS version, etc.
This is a charity comp, so I'm trying to shuffle this among my paid work.

[David Kaye]

Post by Jeff Liebermann
<https://forums.linuxmint.com/viewtopic.php?t=223372>
Looks like there are scanning issues in Mint 18, but it works with 17.

Thanks. I apparently didn't see it because I'd entered the Brother model
number in my search, and this link refers to other models.