Skip to main content

CUPS: Unable to open device and permission denied

I use CUPS for my printer system and I got this error:

Unable
to open device "
hal:///org/freedesktop/Hal/devices/usb_device_3f0_217_00SGKGB09615_if0_printer_noserial": Permission denied

How to solve this problem? The settings of the printer was correct and was just a permission problem. Googling a bit, I found this site.

These steps what I did to solve it:
1. cd /usr/lib/cups/backend
2. chmod 700 hal (previously 755)
3. chmod 700 usb (previously 755)

For step 2 and 3, I found out that you have to change the mod to 700 although the file hal and usb has 'rwx' on them on the 'user' part. The culprit was the 'group' and the 'other' part of the permission. They should be chmod'ed to 0. On my system, the 'group' and 'other' part of both files was 5 (r-x) previously.

I hope this saves some people's time of head scratching.

Comments

4ebees said…
YOU MY FRIEND ARE A F*****G life saver!

I could not find the answer to this damn problem and came across your post after about two hours of screwing around with a Samsung CLP-310 which HAD been working fine until it was borked by what I think was kernel upgrade.

Your info - yes, I know you got it from somewhere else, but I didn't find it myself :)) - has just saved me from pulling the hair out of my children's heads (I'd already ripped out the hair from the head of my wife and myself) LOL

Thank you very much for taking the time to post this. My friend, your work is in the true spirit of FOSS and Gnu/Linux!

Regards,

Patrick
Sydney
Australia
zamri said…
Thanks for posting the comment. Glad you solved it. :)

yeah.. it's the spirit of FOSS and GNU/Linux.
Knight Samar said…
Hey,

Thanks a ton Zamri!

It saved us lots of hairpulling and helped us earn a point at our new job! :D

Regards,
Samar and Maninder
zamri said…
Hi Knight Samar. Glad to help you.
MonsterHOND said…
You sir - saved my day.....
MonsterHOND said…
You Sir - have saved the day today!

Thanks a million
zamri said…
Hi MonsterHOND.

Glad to help you. :)

Popular posts from this blog

mplayer-gui error : Error in skin config file

After installing mplayer-gui package, I can't start it.

$ gmplayer MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Error in skin config file on line 6: PNG read error in /usr/share/mplayer/skins/default/main Config file processing error with skin 'default'
After googling a bit, I found out that it was due to the png files in dir /usr/share/mplayer/skins/default. This is the default skin directory. To fix this error, I have to install ImageMagick package because I want to use the convert program to convert all of the png files to format png24. Thus, cd /usr/share/mplayer/skins/default; for FILE in *.png ; do sudo convert $FILE -define png:format=png24 $FILE ; done
Rerun gmplayer and all should be fine.
Have fun!
UPDATE (02-10-2017)

It doesn't work on Ubuntu 16.04 (xenial) but there's a workaround here.

You can update your syst…

Transparent proxy with squid 2.6

I have upgraded my squid from 2.5 STABLE13 to 2.6 STABLE18. Transparent proxy is setup differently in this version. You need this directives in squid.conf (usually in /etc or /usr/local/etc or /usr/local/squid/etc, check with your distro).

acl our_networks src 192.168.2.0/24 127.0.0.1
http_access allow our_networks
http_port 192.168.2.1:3128 transparent
always_direct allow all

where 192.168.2.1 is your proxy server IP address.


If you have flushed your iptables, create new rule:

iptables -t nat -A PREROUTING -i eth0 -p tcp –dport 80 -j REDIRECT –to-port 3128

where 3128 is the port where squid is running.
References:
http://www.deckle.co.za/squid-users-guide/Transparent_Caching/Proxy

postfix - mailbox size limit and message size limit

postfix is my MTA of choice. I use it for my mailserver because its simplicity , security and sendmail-compatible (the widely used smtp in the world but not as secure). It is also extensible by plugging other servers for various purposes (antispam, antivirus,database etc).

I had one problem with file attachment larger than 10MB. Users couldn't send it although I have setup squirrelmail (SM) to be able to attach files summed up more than 20MB and I had modified php settings as per here. The problem was not in SM setting. It was postfix. By default, attachment size that can be sent by postfix is 10MB ~ 10240000 byte. How did I know it? I looked in log file (for my system it is in /var/log/mail/errors. For other system, the file to look is /var/log/maillog). The line looked like this:

Feb 26 16:30:53 webmail postfix/sendmail[30775]: fatal: me@mymailserver.org(74): Message file too big


Solution
Open /etc/postfix/main.cf with a text editor of choice and find message_size_limit directive an…