On Sat, 9 Mar 2013 18:48:47 +0100 Didier 'OdyX' Raboud o...@debian.org
wrote:
I can't disagree with that.
As far as I can read that bug:
i) running backends not as root will likely break some working behaviours;
ii) apparently a non-standard backend, not even in Debian doesn't work in
that
Ok for 'jasmine', but 'beh' is a rather ''standard'' backend, that i
use extensively for some ''broken'' printers or print servers... very
useful if you don't want to be called on saturday morning at home...
Is 'beh' not working correctly when used as printer backend?
?! Sorry, i've
Control: tags -1 +wontfix -moreinfo
Hi Marco,
Le mercredi, 6 mars 2013 17.37:12, Marco Gaiarin a écrit :
As far as I can tell, all chained configurations that go through cups are
working correctly, so that's definitely a minor issue for standard use
cases.
Ok for 'jasmine', but 'beh' is
As far as I can tell, all chained configurations that go through cups are
working correctly, so that's definitely a minor issue for standard use cases.
Ok for 'jasmine', but 'beh' is a rather ''standard'' backend, that i
use extensively for some ''broken'' printers or print servers... very
Package: cups
Version: 1.4.4-7+squeeze2
If i need to chain some backend, eg because i need the Backend Error
Handler (beh, in the package 'foomatic-filters') or the 'jasmine'
backend (http://jasmine.berlios.de/dokuwiki/doku.php, non packaged)
i've found that the second backend cannot be launched.
Control: tags -1 +moreinfo
Hi Mark,
thanks for your bugreport.
Le lundi, 4 mars 2013 11.12:31, Marco Gaiarin a écrit :
If i need to chain some backend, eg because i need the Backend Error
Handler (beh, in the package 'foomatic-filters') or the 'jasmine'
backend
6 matches
Mail list logo
