[–] 1 point 1 week ago

Fair guess — I did use AI to help me write this in polished English, the same way I use a lift instead of jacking up a car by hand. The mechanic, the app, the PPA and the AUR package are real though. Feel free to check the repo and judge the work, not the grammar.

  • source
  • [–] 0 points 1 week ago (1 child)

    Replying six months late — not for OP (glad you found your way, Mint is a solid choice), but for everyone who lands here later with the same problem, the way I used to land in old threads like this one.

    1. You may not need a driver at all. The "install the driver" guides are often outdated advice. Driverless printing has been an industry standard for over a decade: Apple's AirPrint since 2010, and IPP Everywhere / Mopria since 2013, when the printer manufacturers (Canon, HP, Samsung, Xerox and others) formed the Mopria Alliance. Practically every network printer built since ~2013 speaks at least one of these — the printer itself tells the system what it can do, no vendor driver involved. And here's the proof you already own: your smartphone has been printing exactly this way all along. Nobody has ever installed a printer driver on a phone — Android and iOS simply have no other mechanism than these open standards. If your printer works from your phone, it can work driverless from Linux too, on every distro including immutable ones like Bazzite. The "garbage page + hundreds of blank pages" symptom is typically a wrong driver rendering junk — removing the vendor driver setup and re-adding the printer as a network/driverless printer (CUPS picks "IPP Everywhere" as the model) often just fixes it. That's also why the Epson story above worked in one click: that wasn't Bazzite being magic, it was driverless printing doing its job.

    2. Shameless-but-honest plug: I'm a 45-year-old car mechanic from Austria, not a dev — probably not the typical person you'd expect in these threads. Printing was my own "why is this so hard" moment on Linux, so I built a small FOSS tool for it: PrintEase (https://github.com/MrHaku81/print-ease). It's a GTK4 app that auto-discovers driverless printers/scanners on your network (IPP Everywhere + eSCL scanning) and shows you honestly what the device itself reports — capabilities, paper sizes, duplex, the lot. No vendor drivers, no config files. GPL, 34 languages.

    Install options by distro:

    • Ubuntu 24.04+ / Mint 22+ / Zorin 18+ (and other noble-based): sudo add-apt-repository ppa:haku81/printease && sudo apt install print-ease
    • Arch / CachyOS / EndeavourOS / Manjaro: paru -S print-ease (AUR)
    • Fedora / openSUSE / others: from source — git clone, pip install -e . (deps: GTK4, PyGObject, pycups; see README)
    • Bazzite / Silverblue / immutable distros: honestly, no first-class option yet — a Flatpak is in the works precisely for this case. Until then: run it in a distrobox (Ubuntu or Arch box), or just use the driverless tip above, which needs no extra software at all.

    One honest limitation: if a printer genuinely needs a legacy driver (some older Brother laser models want brlaser), or is USB-only without network, no tool talks around that — driverless only works if the printer speaks the standard. Check your printer's build year and spec for "AirPrint" or "Mopria" support; if it's from ~2013 or later and has WiFi/LAN, you're one network discovery away from never thinking about printer drivers again.

    I don't hang around social platforms much, but if you find this and have questions — issues and questions on the GitHub repo are welcome, I do answer.

  • source
  • [–] 4 points 4 weeks ago

    The biggest news here is that you can use KeePass with Firefox out of the box now, as Firefox Native Messaging is now supported in Bazzite.

    While it wasn't a huge deal, I no longer have to run Firefox and KeePassXC in a distrobox, yay!

  • source
  • [–] 1 point 1 month ago

    Yes, those are indeed problems you can face that are solved with something like flatpak

    However, as long as you aren't installing random packages which are not made to work with fedora and its update cycle (plasma big screen is in its official repos) you probably won't have any problem

  • source
  • parent
  • context
  • [–] 2 points 1 month ago* (last edited 1 month ago) (1 child)

    Yes. I think they switched to a new updater tool (that gets called by just/topgrade).

    I really hope they fix it though because the JSON stream is unreadable and just pollutes the terminal scrollback buffer.

  • source
  • [–] [S] 3 points 1 month ago

    Well, I appreciate the reminder that I can't trust KDE Discover to list packages in the Fedora repos 😂 sadly necessary in this case!

    Updated my initial post but I ran rpm-ostree install plasma-bigscreen and it worked! Will be keeping an eye on things next few times I update to see if it causes any issues.

  • source
  • parent
  • context
  • [–] 2 points 1 month ago* (last edited 1 month ago) (2 children)

    It’s in the Fedora repos. As far as I can tell, it’s a separate DE, kinda like Plasma Mobile. I would imagine that it would be possible to layer it in using RPM ostree but I don’t know for sure.

    rpm-ostree plasma-bigscreen

  • source
  • [–] 2 points 1 month ago

    I installed the Gnome version of Bazzite on my full desktop PC. Rebased to KDE after a few months and a few months later rebased back to Gnome. No issues I've found, though I haven't dug into any DE specific configs in home.

  • source
  • parent
  • context
  • [–] 1 point 1 month ago (1 child)

    Well; sometimes, the screen goes black for a second. But it's rare enough tho. Also; after a while there are the ghosts of temporary files (?) on my desktop screen. Tiny pixel sized things that you can select but not delete. And Firefox sometimes freezes up cause of a memory leak. Tho this is not be bazzites faulth.

  • source
  • parent
  • context
  • [–] 4 points 2 months ago (2 children)

    Unstable how? PC crashes? game crashes? Performance drops?

    Looks like there's an issue resolved w.r.t. AND and flickering screens. I thought my screen was just failing. Hopefully this fixes it ( even though its not always an issue for me ).

    Some issues with flickering or cutting-out displays under VRR/HDMI2.1 on AMD have been resolved!

  • source
  • parent
  • context
  • view more: next ›