--
You received this message because you are subscribed to the Google Groups "yajhfc-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to yajhfc-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Does YajHFC print any error messages?
Does CUPS show any errors?
In Version 0.6.0 I had to move the location of the named pipe from /tmp/yajhfc-$USER to /var/spool/yajhfc/printer-$USER because with systemd every daemon gets its own private /tmp directory, so the CUPS backend was no longer able to access the named pipe in /tmp
To narrow down the problem you can check the following things:
1. Can the client create the named pipe?
I.e. after starting YajHFC a file named /var/spool/yajhfc/printer-$USER (or whatever name the client is configured to create the named pipe as) should show up (replace $USER with the user's name of course)
2. If such a file shows up, does the send dialog appear if you write to that named pipe?
For example if you do a "cat /etc/passwd > /var/spool/yajhfc/printer-$USER", YajHFC should react.
If both things work, it most likely is some problem with the CUPS backend (most likely some issue with permissions).
These are a bit difficult to debug, but since the backend is a simple shell script, you may be able to track it down by editing it to output some "diagnostic information" (for example you can insert something like a "ls -l /var/spool/yajhfc > /tmp/test" to find out if the backend is able to see the directory and so on...)
Jonas