• printing multiple copies

    From Mike Scott@3:633/280.2 to All on Thu Dec 1 06:10:53 2022
    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of copies
    is ignored (whether from the print dialogue or using 'lpr -#'. The fix
    is out there on the net - change "true" to "True" (could you make it
    up?) in the "cupsManualCopies" entry in the ppd.

    The only snag is that a new ppd arrives from out of the ether whenever
    cups restarts (eg boot time): any change only stays on manually
    installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded from -
    can anyone help please?



    --
    Mike Scott
    Harlow, England

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: Scott family (3:633/280.2@fidonet)
  • From Nic@3:633/280.2 to All on Thu Dec 1 10:36:02 2022
    On 11/30/22 2:10 PM, Mike Scott wrote:
    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of
    copies is ignored (whether from the print dialogue or using 'lpr -#'.
    The fix is out there on the net - change "true" to "True" (could you
    make it up?) in the "cupsManualCopies" entry in the ppd.

    The only snag is that a new ppd arrives from out of the ether whenever
    cups restarts (eg boot time): any change only stays on manually
    installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded from
    - can anyone help please?



    Have a look for .wine/dosdevices/z/usr/share/cups/model

    Not sure about the 'z', but query .ppd in your file explorer


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: Arm Chair Observer (3:633/280.2@fidonet)
  • From Paul@3:633/280.2 to All on Thu Dec 1 11:06:18 2022
    On 11/30/2022 2:10 PM, Mike Scott wrote:
    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of copies is ignored (whether from the print dialogue or using 'lpr -#'. The fix is out there on the net - change "true" to "True" (could you make it up?) in the "cupsManualCopies" entry in the ppd.

    The only snag is that a new ppd arrives from out of the ether whenever cups restarts (eg boot time): any change only stays on manually installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded from - can anyone help please?




    https://www.openprinting.org/download/kpfeifle/LinuxKongress2002/Tutorial/VI.CUPS-Connections/VI.tutorial-handout-cups-connections.html

    https://www.openprinting.org/download/kpfeifle/LinuxKongress2002/Tutorial/VI.CUPS-Connections/CUPS-Connections.png

    "You can download the PPD files for any configured printer from the CUPS server:

    http://<host name>:631/printers/<printer queue name>.ppd
    "

    That suggests a ModelNumber.ppd is coerced before being stored as PrinterQueueName.ppd,
    making it harder to trace where it came from. It could be put where ever that is,
    when the printer is manually installed, or perhaps when some CUPS-specific software
    gets an update.

    I would want to search the machine for all the PPD files, and see if there
    is a "pattern" to their naming, hinting at the best place to be reaching
    in and adjusting them.

    I cannot check here, unless I have a printer set up, and it happens to be PostScript capable, to make for a complete test case. Your machine should
    be perfect for the research :-)

    Paul

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Mike Scott@3:633/280.2 to All on Fri Dec 2 02:55:48 2022
    On 01/12/2022 00:06, Paul wrote:
    On 11/30/2022 2:10 PM, Mike Scott wrote:
    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of
    copies is ignored (whether from the print dialogue or using 'lpr -#'.
    The fix is out there on the net - change "true" to "True" (could you
    make it up?) in the "cupsManualCopies" entry in the ppd.

    The only snag is that a new ppd arrives from out of the ether whenever
    cups restarts (eg boot time): any change only stays on manually
    installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded from
    - can anyone help please?
    ......> ÿ "

    That suggests a ModelNumber.ppd is coerced before being stored as PrinterQueueName.ppd,
    making it harder to trace where it came from. It could be put where ever that is,
    when the printer is manually installed, or perhaps when some
    CUPS-specific software
    gets an update.

    I would want to search the machine for all the PPD files, and see if there
    is a "pattern" to their naming, hinting at the best place to be reaching
    in and adjusting them.


    Bit of serendipity earlier today. There's a program 'driverless' that generates ppd files. I ran this with strace -- it seems it picks up the
    ppd from the printer itself. So no chance of simply fixing the errant
    capital letter. I'm toying with the idea of renaming this, and writing a
    shell script with the same name to call the original and edit it appropriately.

    Either local software has changed to be more case-picky, or I'm
    remembering a previous printer when I say it "used to work".

    Thanks for replying.


    --
    Mike Scott
    Harlow, England


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: Scott family (3:633/280.2@fidonet)
  • From Andrei Z.@3:633/280.2 to All on Fri Dec 2 03:52:31 2022
    Mike Scott wrote:
    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of copies
    is ignored (whether from the print dialogue or using 'lpr -#'. The fix
    is out there on the net - change "true" to "True" (could you make it
    up?) in the "cupsManualCopies" entry in the ppd.

    The only snag is that a new ppd arrives from out of the ether whenever
    cups restarts (eg boot time): any change only stays on manually
    installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded from -
    can anyone help please?



    Printers and Scanners — Linux Mint User Guide documentation https://linuxmint-user-guide.readthedocs.io/en/latest/printers.html

    Driverless Printing and Scanning (IPP)
    Since version 21, Linux Mint features driverless printing and scanning:
    ....


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: Aioe.org NNTP Server (3:633/280.2@fidonet)
  • From Nic@3:633/280.2 to All on Fri Dec 2 04:04:12 2022
    On 12/1/22 11:52 AM, Andrei Z. wrote:
    Mike Scott wrote:
    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of
    copies is ignored (whether from the print dialogue or using 'lpr -#'.
    The fix is out there on the net - change "true" to "True" (could you
    make it up?) in the "cupsManualCopies" entry in the ppd.

    The only snag is that a new ppd arrives from out of the ether
    whenever cups restarts (eg boot time): any change only stays on
    manually installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded from
    - can anyone help please?



    Printers and Scanners — Linux Mint User Guide documentation https://linuxmint-user-guide.readthedocs.io/en/latest/printers.html

    Driverless Printing and Scanning (IPP)
    Since version 21, Linux Mint features driverless printing and scanning:
    ...

    Has anybody implemented IPP in LM 19.1?


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: Arm Chair Observer (3:633/280.2@fidonet)
  • From Carlos E.R.@3:633/280.2 to All on Fri Dec 2 22:55:14 2022
    On 2022-12-01 16:55, Mike Scott wrote:
    On 01/12/2022 00:06, Paul wrote:
    On 11/30/2022 2:10 PM, Mike Scott wrote:
    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of
    copies is ignored (whether from the print dialogue or using 'lpr -#'.
    The fix is out there on the net - change "true" to "True" (could you
    make it up?) in the "cupsManualCopies" entry in the ppd.

    The only snag is that a new ppd arrives from out of the ether
    whenever cups restarts (eg boot time): any change only stays on
    manually installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded from
    - can anyone help please?
    .....>ÿ ÿ "

    That suggests a ModelNumber.ppd is coerced before being stored as
    PrinterQueueName.ppd,
    making it harder to trace where it came from. It could be put where
    ever that is,
    when the printer is manually installed, or perhaps when some
    CUPS-specific software
    gets an update.

    I would want to search the machine for all the PPD files, and see if
    there
    is a "pattern" to their naming, hinting at the best place to be reaching
    in and adjusting them.


    Bit of serendipity earlier today. There's a program 'driverless' that generates ppd files. I ran this with strace -- it seems it picks up the
    ppd from the printer itself. So no chance of simply fixing the errant capital letter. I'm toying with the idea of renaming this, and writing a shell script with the same name to call the original and edit it appropriately.

    Either local software has changed to be more case-picky, or I'm
    remembering a previous printer when I say it "used to work".

    Thanks for replying.

    You should be able to report that as a Bug to your distribution.

    Otherwise, there are things you can try:

    Remove the "w" (write) permission of the file. Maybe make it inmutable.

    A cron job replaces it (don't bother with the edit).

    If you are using Apparmor, you can deny the permission to 'driverless'
    for writing that particular file.

    --
    Cheers, Carlos.


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Scott Hemphill@3:633/280.2 to All on Sat Dec 3 09:42:57 2022
    Reply-To: hemphill@alumni.caltech.edu

    "Carlos E.R." <robin_listas@es.invalid> writes:

    On 2022-12-01 16:55, Mike Scott wrote:
    On 01/12/2022 00:06, Paul wrote:
    On 11/30/2022 2:10 PM, Mike Scott wrote:
    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of
    copies is ignored (whether from the print dialogue or using 'lpr
    -#'. The fix is out there on the net - change "true" to "True"
    (could you make it up?) in the "cupsManualCopies" entry in the
    ppd.

    The only snag is that a new ppd arrives from out of the ether
    whenever cups restarts (eg boot time): any change only stays on
    manually installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded
    from - can anyone help please?
    .....>ÿ ÿ "

    That suggests a ModelNumber.ppd is coerced before being stored as
    PrinterQueueName.ppd,
    making it harder to trace where it came from. It could be put where
    ever that is,
    when the printer is manually installed, or perhaps when some
    CUPS-specific software
    gets an update.

    I would want to search the machine for all the PPD files, and see
    if there
    is a "pattern" to their naming, hinting at the best place to be reaching >>> in and adjusting them.


    Bit of serendipity earlier today. There's a program 'driverless'
    that generates ppd files. I ran this with strace -- it seems it
    picks up the ppd from the printer itself. So no chance of simply
    fixing the errant capital letter. I'm toying with the idea of
    renaming this, and writing a shell script with the same name to call
    the original and edit it appropriately.

    Either local software has changed to be more case-picky, or I'm
    remembering a previous printer when I say it "used to work".

    Thanks for replying.

    You should be able to report that as a Bug to your distribution.

    Otherwise, there are things you can try:

    Remove the "w" (write) permission of the file. Maybe make it inmutable.

    A cron job replaces it (don't bother with the edit).

    If you are using Apparmor, you can deny the permission to 'driverless'
    for writing that particular file.

    How about a symbolic link?

    Scott
    --
    Scott Hemphill hemphill@alumni.caltech.edu
    "This isn't flying. This is falling, with style." -- Buzz Lightyear

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Carlos E.R.@3:633/280.2 to All on Sat Dec 3 10:02:24 2022
    On 2022-12-02 23:42, Scott Hemphill wrote:
    "Carlos E.R." <robin_listas@es.invalid> writes:

    On 2022-12-01 16:55, Mike Scott wrote:
    On 01/12/2022 00:06, Paul wrote:
    On 11/30/2022 2:10 PM, Mike Scott wrote:
    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of
    copies is ignored (whether from the print dialogue or using 'lpr
    -#'. The fix is out there on the net - change "true" to "True"
    (could you make it up?) in the "cupsManualCopies" entry in the
    ppd.

    The only snag is that a new ppd arrives from out of the ether
    whenever cups restarts (eg boot time): any change only stays on
    manually installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded
    from - can anyone help please?
    .....>ÿ ÿ "

    That suggests a ModelNumber.ppd is coerced before being stored as
    PrinterQueueName.ppd,
    making it harder to trace where it came from. It could be put where
    ever that is,
    when the printer is manually installed, or perhaps when some
    CUPS-specific software
    gets an update.

    I would want to search the machine for all the PPD files, and see
    if there
    is a "pattern" to their naming, hinting at the best place to be reaching >>>> in and adjusting them.


    Bit of serendipity earlier today. There's a program 'driverless'
    that generates ppd files. I ran this with strace -- it seems it
    picks up the ppd from the printer itself. So no chance of simply
    fixing the errant capital letter. I'm toying with the idea of
    renaming this, and writing a shell script with the same name to call
    the original and edit it appropriately.

    Either local software has changed to be more case-picky, or I'm
    remembering a previous printer when I say it "used to work".

    Thanks for replying.

    You should be able to report that as a Bug to your distribution.

    Otherwise, there are things you can try:

    Remove the "w" (write) permission of the file. Maybe make it inmutable.

    A cron job replaces it (don't bother with the edit).

    If you are using Apparmor, you can deny the permission to 'driverless'
    for writing that particular file.

    How about a symbolic link?

    I am afraid that will not work. Either the link is replaced, or the file
    at the other end of the link is replaced or edited.

    --
    Cheers, Carlos.


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Dan Purgert@3:633/280.2 to All on Fri Dec 23 03:17:47 2022
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA512

    ["Followup-To:" header set to comp.os.linux.networking.]
    Nic wrote:

    Has anybody implemented IPP in LM 19.1?


    IPP has been an option since as far back as like LM13. _However_, this "driverless" thing is pretty new (and usually requires a supported
    printer).

    TBH, I usually rip it out, as it is broken more often than not.


    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmOkg2IACgkQbWVw5Uzn KGB7IQ/9F4wY7UqP+0dcfFPM+rT3VHnqcvzKzCKAFv/O8aSfUFMaxT9uN/D3amot u2ZB+UyRQCk26J3E5HzHvp7tMlMGsCuw9HfFc+7WuUrVEtbwOe1hJI9tew6M7qKz 0/DpXtjQqrZ/qq8lGTteQNoZY81XpshQvzqyMM2ZOGQW2UKiYkke6C08g2D7IjrM QoDVfeK2goH5QCk7PGCkUh5orJfgLE7asXtqM5l4SDtV8MDgugmpFIsGOqrkHOzY qp61ULPOfzSDjp2pzHgQZrwXOSAQS2nLftaZ5//iVqqNgWhbOoD5GEMktyBX0jyd 30x5QEOE1GE81jEALMc4vqGIT8UUJyjTSkak/FZQU0J/PSAuNBNnssMsvvEAq+5r cZOeYZ/qht9K/fQNji0/cj/01p/jJkBe74QdE7VZ2Xsbdm3YTHQdQDk72NVWd2Jc iAyu68uCIfxexV55hrZaVdhyRIZ/c1TfS6pskyReA8UAQWmcQaVcHkDekkt6uRjn NAP0gmM+rc7cbKTMBCN+B+w9R9A+UIanHsfaCCprYi57zcIYPBn6eXMr0LZ+fcYi hHKW53SBZ6McHPzZ3fzVtIgeDhWl/H7ykkNx4H7H6KY1NcGrqpQRQaRXwfRuRNfB ysH80wIVvg5RF01pHEpxIeGwX8HN35UJWiyYId1zX63Cr7KcjQ8=
    =ChLZ
    -----END PGP SIGNATURE-----

    --
    |_|O|_|
    |_|_|O| Github: https://github.com/dpurgert
    |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Andrei Z.@3:633/280.2 to All on Fri Dec 23 22:14:08 2022
    Andrei Z. wrote:
    Mike Scott wrote:
    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of
    copies is ignored (whether from the print dialogue or using 'lpr -#'.
    The fix is out there on the net - change "true" to "True" (could you
    make it up?) in the "cupsManualCopies" entry in the ppd.

    The only snag is that a new ppd arrives from out of the ether whenever
    cups restarts (eg boot time): any change only stays on manually
    installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded from
    - can anyone help please?



    Printers and Scanners — Linux Mint User Guide documentation https://linuxmint-user-guide.readthedocs.io/en/latest/printers.html

    Driverless Printing and Scanning (IPP)
    Since version 21, Linux Mint features driverless printing and scanning:
    ...

    CUPSDriverlessPrinting - Debian Wiki

    https://wiki.debian.org/CUPSDriverlessPrinting


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: Aioe.org NNTP Server (3:633/280.2@fidonet)
  • From eternal.septemer@3:633/280.2 to All on Fri Jul 14 21:45:36 2023
    On Wed, 30 Nov 2022 19:10:53 +0000
    Mike Scott <usenet.16@scottsonline.org.uk.invalid> wrote:

    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of copies
    is ignored (whether from the print dialogue or using 'lpr -#'. The fix
    is out there on the net - change "true" to "True" (could you make it
    up?) in the "cupsManualCopies" entry in the ppd.

    The only snag is that a new ppd arrives from out of the ether whenever
    cups restarts (eg boot time): any change only stays on manually
    installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded from -
    can anyone help please?



    Years of experience with Brother printers under Linux have taught me always to go to:

    https://www.brother.co.uk/support/drivers

    Enter your model number, select .deb and continue to a happy life.

    I always save the resultant ppd from /etc/cups/ppd to a folder in my /home/me/useful-bits directory to save future hassle.

    HTH

    Regards, Alan



    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Mike Scott@3:633/280.2 to All on Sat Jul 15 20:37:45 2023
    On 14/07/2023 12:45, eternal.septemer wrote:
    On Wed, 30 Nov 2022 19:10:53 +0000
    Mike Scott <usenet.16@scottsonline.org.uk.invalid> wrote:

    A long-standing and very annoying problem here.

    With the default .ppd file for my Brother printer, the number of copies
    is ignored (whether from the print dialogue or using 'lpr -#'. The fix
    is out there on the net - change "true" to "True" (could you make it
    up?) in the "cupsManualCopies" entry in the ppd.

    The only snag is that a new ppd arrives from out of the ether whenever
    cups restarts (eg boot time): any change only stays on manually
    installed printers.

    Is there a fix for this? I can't find where the ppd's are loaded from -
    can anyone help please?



    Years of experience with Brother printers under Linux have taught me always to go to:

    https://www.brother.co.uk/support/drivers

    Enter your model number, select .deb and continue to a happy life.

    I always save the resultant ppd from /etc/cups/ppd to a folder in my /home/me/useful-bits directory to save future hassle.

    HTH

    Regards, Alan



    Thanks. I thought the thread had died a death :}

    In practice, I now ignore the cups automatically installed printer, and
    have a manually installed item, with the ppd I've corrected. Annoying,
    but it works and the ppd stays put.

    Still quite slow though to get going; an ongoing irritation I seem to
    recall from a while back when I did indeed use Brother's packaged drivers.


    --
    Mike Scott
    Harlow, England


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: Scott family (3:633/280.2@fidonet)