mikshaw


Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: Nov. 13 2006,21:09 |
 |
It's possible to fix, but first you need to know which extension is causing the trouble. If an extension includes the /tmp directory (it shouldn't), and that directory is mode 755 or 775 (typical directory permissions), the directory will overwrite the system /tmp directory and break permissions. System temp directories should be 777 so any user can write to it.
If your extension is *.dsl or *.tar.gz you can see what files are in it by using the command "tar -tzf filename". It may have "tmp/mydsl.menu/something", but it should NOT have just "tmp".
I don't know for sure why printing needs a temp file, but it might be creating a postscript file from the source file before printing. In any case, your tmp directory needs fixing if any user has trouble writing to it.
-------------- http://www.tldp.org/LDP/intro-linux/html/index.html
|