• The_Decryptor@aussie.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 天前

    For all the wireless printers I’ve ever owned CUPS would recognize the printer once, do a job, and then magically act like the printer either doesn’t exist or is currently doing a job in perpetuity.

    I mean odds are it’s the printer that’s acting up. I owned a brother laser printer that I had to connect via the network, and that thing only ever configured the network on boot. If anything happened to the network connection it’d go offline until you restarted it.

    There’s a reason I’ve seen multiple people recommend using something like a Raspberry Pi connected via USB as a replacement print server rather than relying on the native printer support. And since the modern printer protocols are basically lifted from CUPS, compatibility would be improved.

    • JakoJakoJako13@piefed.social
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      5 天前

      Sure. It could be the printer, but 3 outta 4 Printers that had the same issue repeatedly is more likely to be the drivers fault. Then everybody and there mother suggests getting a Brother printer. That’s one brand out of how many? I don’t own a Brother printer. That’s the only brand you ever see Linux enthusiasts recommend. And then so top it off with Raspberry Pi. I shouldn’t have to hook up a Raspberry Pi to use my fucking printer. You can try to convince me that CUPS is improved, but my own experience is completely the opposite. I will shit on it every time.