User Tools

Site Tools


it_services:mf:problems

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revision Both sides next revision
it_services:mf:problems [2014/06/12 17:16]
florido created
it_services:mf:problems [2016/02/22 13:07]
florido
Line 52: Line 52:
  
 then it seemed more stable to switch to nfs3. This is done in '/​etc/​nfsmount.conf'​. Please ask the administrator for such a fix. then it seemed more stable to switch to nfs3. This is done in '/​etc/​nfsmount.conf'​. Please ask the administrator for such a fix.
 +
 +==== Issues printing to the copy machine ====
 +
 +Most of the issues are due to incorrect code sent to the copy machine.
 +
 +If you experience problems printing from KDE or command line, follow these instructions:​
 +
 +== Kde: ==
 +For some reason KDE incorrectly writes the options for this printer. This is a KDE bug against Canon drivers.
 +
 +  - Edit the following file: <​code>​~/​.cups/​lpoptions</​code>​
 +  - If there is a line regarding ''​copy-t''​ or ''​copy-n'',​ remove that line. Sample correct file is as follows:<​file>​
 +Default printer
 +</​file>​
 +  - If you want to specify custom options for the printer, set them in KDE, but then check the content of ''​lpotions''​ again, it should be something like:<​file>​
 +Dest copy-n ColourModel=Colour UserID=None UserPassword=None
 +Dest copy-t ColourModel=Colour UserID=None UserPassword=None
 +Default printer
 +</​file>​
 +
 +== Commandline:​ ==
 +
 +It is good to test if printing works by command line.
 +
 +To pass the codes to the print queue (should not be needed after you do the
 +KDE thing above, but in any case) issue the following:
 +
 +''​lpr -o UserID=<​code>​ -o UserPassword=<​code>​ -Pcopy-t yourfile''​
 +
 +It seems the driver for this printer is different than the previous one
 +and KDE always tries to fallback to some weird default.
 +
 +==== Firefox won't open: another instance is running or similar errors ====
 +
 +This happens in two cases:
 +
 +== 1. You have firefox open in workstation A, and you try yo open it in workstation B ==
 +
 +**Solution**:​ It's advisable to close it in workstation A first. Each instance of firefox will write in the
 +same profile folder that might cause problems. To save your work you might want to use the [[https://​addons.mozilla.org/​en-US/​firefox/​addon/​session-manager/​|session-manager extension]]
 +
 +== 2. Your machine shut down abruptly or lost connection with the fileserver before firefox released the profile lock ==
 +
 +**Solution**:​ remove the profile lock using this simple one-liner. **OBS**: make sure you **DO NOT** have firefox already running on some other machine or you will cause severe damage to your firefox setup!!
 +
 +<code bash>​find ~/​.mozilla/​firefox/​ -iname '​.parentlock'​ -exec rm {} \;</​code>​
 +
 +And try to restart firefox again.
it_services/mf/problems.txt ยท Last modified: 2020/08/20 17:01 by florido

Accessibility Statement