LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 12-17-2012, 03:28 PM   #1
cmcnutt
LQ Newbie
 
Registered: May 2012
Posts: 22

Rep: Reputation: Disabled
Snanning with Brother 3-in-one J140W gets killed by signal 11 and signal 5


Downloaded and installed the brscan 4 drivers for printer DCP-J140W. It prints fine but when I try to scan I get killed by signal 11 and killed by signal 5.
We're using Fedora 16.
Using scan tool brings up message: Failed to open device 'brother4:bus1, dev1':
Trying to scan with Scan utility brings up Error report: gnome-scan
Process/usr/flegita was killed by signal 11.

What do I do next? [Mind, I'm a new user with no code writing in my background].
Thanks!
 
Old 12-17-2012, 03:49 PM   #2
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Did you follow these instructions?

Quote:
Fedora 16, 15, 14, 13, 12
1. Open"/lib/udev/rules.d/65-libsane.rules"
2. Add the following 2 lines at the last of the device entry. (just before "# The following rule...").

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

3. Restart the OS.
Is this a 32 bit system or a 64 bit system? Did you make sure you installed the driver package that matches? 32 bit or 64 bit?
 
Old 12-17-2012, 03:59 PM   #3
cmcnutt
LQ Newbie
 
Registered: May 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by camorri View Post
Did you follow these instructions?



Is this a 32 bit system or a 64 bit system? Did you make sure you installed the driver package that matches? 32 bit or 64 bit?
It's a 64 bit system. Yep, I downloaded and installed the correct drivers from the Brother support and download site.

I have no idea what those instructions mean or are saying. How and where do write these things and what do I sub for what is in the brackets? Like I said, new user [my Dad wants to use Fedora. I could do without the headach].
Carla
 
Old 12-17-2012, 04:13 PM   #4
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
They are udev rules. You need them so the scanner is correctly recognized. The instructions are on Brothers site.

Quote:
How and where do write these things and what do I sub for what is in the brackets?
You edit the file as root, copy and paste the lines exactly as they are. You do not change anything.

The udev rules are used to match information read from the scanner hardware. Once a match is made, a device gets created in the /dev directory. Without it, the scanner doesn't work.
 
Old 12-17-2012, 04:33 PM   #5
cmcnutt
LQ Newbie
 
Registered: May 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Ok, got that.
How do I do this part "Open"/lib/udev/rules.d/65-libsane.rules"
Where do I do this, in terminal?
Thanks for your help!
C


Camorri said:
"You edit the file as root, copy and paste the lines exactly as they are. You do not change anything.

The udev rules are used to match information read from the scanner hardware. Once a match is made, a device gets created in the /dev directory. Without it, the scanner doesn't work.[/QUOTE]
 
Old 12-17-2012, 04:45 PM   #6
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Quote:
Where do I do this, in terminal?
Yes, in a terminal. You use what ever text editor you have on the system. ( Not a word processor ). If the file 65-libsane.rules doesn't exist, create it and add the lines, and save it to the path /lib/udev/rules.d/ and restart the system ( boot it ).
 
Old 12-17-2012, 04:55 PM   #7
cmcnutt
LQ Newbie
 
Registered: May 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by camorri View Post
Yes, in a terminal. You use what ever text editor you have on the system. ( Not a word processor ). If the file 65-libsane.rules doesn't exist, create it and add the lines, and save it to the path /lib/udev/rules.d/ and restart the system ( boot it ).
Ok, how do I find the file "65-libsane.rules."?
Carla
 
Old 12-17-2012, 06:09 PM   #8
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Quote:
Ok, how do I find the file "65-libsane.rules
Open a konsole. It will open in your home directory. /home/username/.

Type 'cd /lib/udev/rules.d/' ( just what is between the quotes ) and press enter.

You will be in the correct directory. You can confirm that with the 'pwd' command ( present working directory).

Type 'ls 65-libsane.rules'. If the file exists, the system will list the file.
 
Old 12-18-2012, 01:00 PM   #9
cmcnutt
LQ Newbie
 
Registered: May 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Ok, it says "no such file or directory". How do I create it.
By the way, thank you for helping me with this. Now I will know how to edit when I have to install other items].
Carla


Quote:
Originally Posted by camorri View Post
Open a konsole. It will open in your home directory. /home/username/.

Type 'cd /lib/udev/rules.d/' ( just what is between the quotes ) and press enter.

You will be in the correct directory. You can confirm that with the 'pwd' command ( present working directory).

Type 'ls 65-libsane.rules'. If the file exists, the system will list the file.
 
Old 12-18-2012, 04:01 PM   #10
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
How much of the directory structure do you have? Some distros install things to different locations.

To find out, do a 'cd /' press enter. That gets you to the root of the file system.
Then one step at a time. 'cd lib' press enter. That should work on any system.
Next, 'cd udev' note there is no forward slash used here.
Last, 'cd rules.d' press enter. Can you get here?

You can do an 'pwd' at any point, and the system will tell you where you are.

If the directory structure is there, do a 'ls -l' command, look for 65-libsane.rules file.
It may not be there. There should be several files starting with numbers, and ending with .rules extension. If that is what you see, start up the editor you want to use, type the lines as posted above ( or copy and paste them ) and save the file with the name of 65-libsane.rules. Restart the system, and try the scanner.

If you have problems, copy and paste the errors into this thread, it helps me help you faster.

BTW, you are most welcome.
 
Old 12-18-2012, 04:45 PM   #11
cmcnutt
LQ Newbie
 
Registered: May 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Ok, I dud all this and found the file '65-libsane.rules' after getting down to:
[carl@localhost rules.d]$
I did the 'ls -l' command and got a whole list of directories. The 65-libsane.rules' was in the list.
How to I get it to the command prompt so that I can cut and paste the needed 2 lines? I'm not using an editor, I'm just typing everything out that you tell me or copy and pasting from these forum postings. I don't know about saving the file.

Carla

Quote:
Originally Posted by camorri View Post
How much of the directory structure do you have? Some distros install things to different locations.

To find out, do a 'cd /' press enter. That gets you to the root of the file system.
Then one step at a time. 'cd lib' press enter. That should work on any system.
Next, 'cd udev' note there is no forward slash used here.
Last, 'cd rules.d' press enter. Can you get here?

You can do an 'pwd' at any point, and the system will tell you where you are.

If the directory structure is there, do a 'ls -l' command, look for 65-libsane.rules file.
It may not be there. There should be several files starting with numbers, and ending with .rules extension. If that is what you see, start up the editor you want to use, type the lines as posted above ( or copy and paste them ) and save the file with the name of 65-libsane.rules. Restart the system, and try the scanner.

If you have problems, copy and paste the errors into this thread, it helps me help you faster.

BTW, you are most welcome.
 
Old 12-18-2012, 05:03 PM   #12
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Quote:
The 65-libsane.rules' was in the list.
How to I get it to the command prompt so that I can cut and paste the needed 2 lines
You have to use an editor as the root user.

You will have to use the 'su' command ( switch user ), the system will prompt you for a password. Enter the root password.

Next, try the 'nano' editor. type 'nano 65-libsane.rules' and press enter. The file shold open. Once opened, you can enter the lines, and save the file. Nano shows the use of keys at the bottom of the screen. You will see the ^ symbol, followed by a letter. For example, the WriteOut is done by using the Ctrl key plus the O key ( that is the letter o, not number 0 ).

If that editor is not on your system, there is always vi, however there is a learning curve with it.

If you know of an editor you would rather use, tell me, I'll try and help if you need it.
 
Old 12-18-2012, 05:58 PM   #13
cmcnutt
LQ Newbie
 
Registered: May 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by camorri View Post
You have to use an editor as the root user.

You will have to use the 'su' command ( switch user ), the system will prompt you for a password. Enter the root password.
I did what you said and it asks for the password, but it won't allow me to type, even though there's a blinking curser there...

[carl@localhost rules.d]$ su
Password:
Hsu: incorrect password
[carl@localhost rules.d]$ Helpme
bash: Helpme: command not found...
su
[carl@localhost rules.d]$ su
Password:
su: incorrect password
[carl@localhost rules.d]$
 
Old 12-18-2012, 06:23 PM   #14
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
You will have to ask the person who installed the system to give you the root password. Without it, you can not edit files owned by root. This is normal on a linux system.

What you observed is normal. The cursor does not move, the system "sees the keystrokes" you enter, plus the enter key when you type the password. If you provide the correct password, the command prompt will change from a $ sign, to a # sign and you will have root privileges.
 
Old 12-18-2012, 06:26 PM   #15
cmcnutt
LQ Newbie
 
Registered: May 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
I'm the one that installed the system. That's the password.
I don't know why it won't let me type after I do the 'su.'
Carla

Quote:
Originally Posted by camorri View Post
You will have to ask the person who installed the system to give you the root password. Without it, you can not edit files owned by root. This is normal on a linux system.

What you observed is normal. The cursor does not move, the system "sees the keystrokes" you enter, plus the enter key when you type the password. If you provide the correct password, the command prompt will change from a $ sign, to a # sign and you will have root privileges.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ld terminated by signal 9 [killed] rustyz82 Linux - Software 3 09-15-2015 08:14 AM
fatel error with dovecot(Killed with signal 15) htshshrm2@hotmail.com Linux - Server 4 02-17-2012 06:28 AM
how did I get this? dovecot: Killed with signal 15 cshelswell Linux - Server 3 08-27-2009 04:23 AM
user-define signal handler & coredump for signal 11(SIGSEGV) Alexlun Linux - Software 2 05-24-2009 06:37 AM
Process not killed with -KILL (-9) signal hondo Linux - General 2 07-25-2007 09:23 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 06:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration