Comment 51 for bug 181242

ok here is my experience, I installed a photosmart 7260 printer via USB. It auto detected perfeclly, everything fine. Printed a few pages. Then tried to print from a windows vista system on my network, and it gave a media jam error. After this, no print jobs could ever be done on the printer until I unplug the printer, unplug the USB, then replug the printer to power and then replug usb. If I tried to just cycle power on the printer it would continue to lock up the printer.

Ok, so I did this, and printing from linux seems to work fine. But after a few pages (like 3-4 pages) it stoped being responsive again. So I did the whole usb/power cord unplug thing and it works. So I would try another print from a windows sytem on my same subnet, and then thats when it crashes again. with media jam error. Every time I do a print from windows on a remote system I got this error (couldn't test with a linux system remotely tho). Does not sound like a permissions problem at all, untill i came across this bug report!!!

 ....and it definitely was a permissions problem as far as I can tell. First, let me explain what I did to "work around" the problem:

"the second solution is just go to user management unlock root then add all privileges to root to access all open a terminal and su to root when u login each time and the printer should work just fine with the original install

This is just a temp solution i recommend anybody here in touch with HP LIP to talk to them about modifying the 55 files in the rules to suit all (meaning no root privileges)"

Ok, so I followed this advice to the letter from a previous post to this bug report (not sure why opening a terminal window to root would do any good, but oh well). And now the printer prints from the windows system 100% of the time and the linux system (locally) 100% of the time... But do I need to continue to keep a root terminal opened at all time until this bug is fixed?