I also tried to fix the printer location to match the documentation: beh:/1/0/120/socket://myprinter:9100, however, that did not work either.
Presumably beh writes its temporary file into an invalid location (/ instead or /var/spool/cups/...). Till, how can I find out with which parameters it calls the beh backend? Can I put an strace in between to see which files it creates?
Till, maybe the problem is also that beh is run as user 'lp', not user 'root'? If it does need root, beh needs to be installed 744, not 755. It might be that this was the case previously, and thus the wrong temporary file path was just hidden.
I also tried to fix the printer location to match the documentation: beh:/1/ 0/120/socket: //myprinter: 9100, however, that did not work either.
Presumably beh writes its temporary file into an invalid location (/ instead or /var/spool/ cups/.. .). Till, how can I find out with which parameters it calls the beh backend? Can I put an strace in between to see which files it creates?
Till, maybe the problem is also that beh is run as user 'lp', not user 'root'? If it does need root, beh needs to be installed 744, not 755. It might be that this was the case previously, and thus the wrong temporary file path was just hidden.