I can edit cups's window, whats the command line you used to change the printer.s permissionpa_mcclamrock wrote:Something changes the permissions. As I said in the Beta2 thread, the /dev/lp0 connection starts out with "777" (execute) permissions, like /dev/lp1. After I try to print, /dev/lp0 shows "660" (no execute) permissions, unlike /dev/lp1.ttuuxxx wrote:finding out why your permissions isn't working when it works out of the box for others would be helpful.
No, parallel port.is your printer usb??
Except to indicate that whatever is making the printing not work on my system is something that's different from how it was in Puppy 4.1.1.[ . . . ]bringing up older cups models that didn't work for others doesn't help [ . . . ]
EDIT 2009 Feb 26 9:25 PM EST: Hmm, yes, let me think . . . what's different? Well, it's that something changes the permissions on the printer connection, /dev/lp0. So, um, what if I manually change the permissions of /dev/lp0 back to 777? Guess what . . .
Printing Works !!!
And when do the permissions get messed up? Looking at them each step of the way, I find that it's right when the CUPS window opens up, before I've done anything about adding a printer. After that happens, if I change them back to 777, they stay that way.
And so the solution is . . . either (1) find and fix the bug that makes CUPS (sometimes) change the permissions when it opens up, or (2) add in a bit of code to determine whether the permissions on the connected device are OK after that point, and to change them if they're not. Right?
Somebody who knows a lot more about CUPS than I do will have to provide the solution, which presumably isn't to tell every user "If you can't print, just try manually changing the permissions on /dev/lp0, or whatever device file stands for your printer connection." (Huh?) Me, I can now proceed to hunt for comparatively little bugs to report in this RC, because . . . with just a bit of non-obvious manual tweaking . . .
Printing Works !!!
And here's the first comparatively little bug I've found: when I closed the ROX-Filer window in which I was examining the permissions of /dev/lp0, I found that the Pwidgets clock now had a picturesque but incongruous background consisting of hard-disk icons and device names from ROX-Filer!
say if you opened a terminal from the desktop and typed ?????
I'll add that line to cups. and then package a fix for you to test, hows that sound?
ttuuxxx