En fait, il y a déjà un problème avec le navigateur Netsurf.
J'ai remis Chromium. Comme sur les autre machines Linux, cups ne trouve pas l'imprimante sur le réseau mais celle-ci répond à l'adresse 192.168.1.1:9100
J'ai donc bien défini une imprimante.
Mais quand je lance une impression, les fichiers se retrouvent dans /var/spool/cups mais ne continuent par leur trajet vers l'imprimante.
With Chromium, I can define printing device, but print jobs stay in /var/spool/cups without proceedint further.
I tried to understane last paragraph of Chapter 21 of CUSP Howto. It's said :
"My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost
Do not use the existing UNIX print system spool directory for the Samba spool directory. It may seem convenient and a savings of space, but it only leads to problems. The two must be separate. The UNIX/Linux system print spool directory (e.g., /var/spool/cups) is typically owned by a non-privileged user such as cups or lp. Additionally. the permissions on the spool directory are typically restrictive to the owner and/or group. On the other hand, the Samba spool directory must be world writable, and should have the 't' bit set to ensure that only a temporary spool file owner can change or delete the file.
Depending on the type of print spooling system in use on the UNIX/Linux host, files that the spool management application finds and that are not currently part of job queue that it is managing can be deleted. This may explain the observation that jobs are spooled (by Samba) into this directory and just disappear."
Have a fine night. In which country do you live?
Cordialement
Jclaude