I use Paperless-ng and it’s great. Headlining feature is that it stores your documents in PDF in a plain folder which makes backing up easy. Another software that puts your documents in a database is no good unless it has its own backup method.
Plus being on a network server means I can set up my printer to scan to there as a target, my phone to scan to there, computer, I can drop emails in the consume folder, etc. Easy peasy to get stuff in there.
Set up Paperless-ng on your server, generally with Docker, and map the Consume folder to wherever you want. Expose that on the network as a Samba or FTP share depending on your printer.
Printers with a bit more than basic features allow you to “scan to target” and it’s basically designed to set up a Public share folder on windows and scan and your document just shows up on the computer. Same deal but map it to the consume folder on the server. Paperless automatically picks up and intakes anything dropped in the consume folder.
So you end up just hitting Scan on the printer, the printer will dump the output into consume share via either samba or ftp, and Paperless automatically picks it up and puts it in the Inbox for ya.
OK, many thx for the tips. Since my script in the service file is already doing some logging, i will try to use the last log entry, to find out, when it was last time running and exit the script, if it is not in the timeframe of 1 week.
I’ve been running Fedora Silverblue on nearly all of my PCs for about a year now and overall it’s been great.
Automatic and unobtrusive updates for the core OS and user apps (everything happens in the background without interaction; flatpak updates are applied immediately, and OS updates are applied at next boot)
I can choose to apply many core updates immediately, but rarely do
Atomic OS updates means that everything must be installed successfully or none of the OS updates are applied, which prevents a partially updated system
Being an image-based distro, I can and do easily rebase to Fedora’s test/beta/remix releases, and just as easily rollback, or run both stable and beta releases side by side for testing purposes
Being image-based means there’s no chance of orphaned packages or library files being left behind after an update, resulting in a cleaner system over time
In the event that anything does go sideways after a system update (hasn’t happened yet), I can easily rollback to the previous version at boot
Some elements not unique to Silverblue but part of its common workflow:
Distrobox/toolbox allow you to run any other distro as a container, and then use that distro’s apps as if they were native to your host system; this includes systemd services, locally installed RPMs, debs, etc.; I use distrobox to keep most of my dev workflow within my preferred Archlinux environment
Flatpaks are the FOSS community’s answer to Ubuntu’s Snaps, providing universal 1-click installation of sandboxed user apps (mostly GUI based); Firefox, Steam, VLC, and thousands of other apps are available to users, all without the need for root access
My only complaints about Silverblue are more to do with how Flatpaks work right now, such as:
Drag & drop doesn’t work between apps, at least not for the apps I’ve attempted to use; for example, dragging a pic into a chat window for sharing; instead, I have to browse to and select the image from within the chat app
Firefox won’t open a link clicked within Thunderbird unless the browser is already open, otherwise it just opens a blank tab
Many flatpak apps are maintained by unofficial volunteers, and this isn’t always clear on Flathub; I view this as a security risk and would prefer to see a flag or warning of some kind when a flatpak is not maintained by the official upstream developer
That said, I’m confident that these issues will be addressed over time. The platform has already come a long way these past couple of years and now that the KDE and GNOME teams are collaborating for it, things will only get better.
Like I said though, overall Silverblue has been a really great user experience, and as a nearly 20-year Linux veteran it has really changed the way I view computing.
Do you have to watch a loading screen while system updates are applied like on regular Fedora or is it in the background?
Many flatpak apps are maintained by unofficial volunteers, and this isn’t always clear on Flathub; I view this as a security risk and would prefer to see a flag or warning of some kind when a flatpak is not maintained by the official upstream developer
On flathub.org there’s a blue checkmark for apps maintained by the devs
Do you have to watch a loading screen while system updates are applied like on regular Fedora or is it in the background?
The image is downloaded and staged in the background of the active session. Upon reboot, the session seamlessly defaults to the staged image. For flatpaks, the updates happen immediately and without the need for a reboot.
On flathub.org there’s a blue checkmark for apps maintained by the devs
Aha, that must be one of the newer features implemented from the beta portal they’d been working on. I’m glad to hear it, and overall I hope to see more official upstream devs come on board with the platform (Signal, I’m looking at you).
The image is downloaded and staged in the background of the active session. Upon reboot, the session seamlessly defaults to the staged image. For flatpaks, the updates happen immediately and without the need for a reboot.
That’s great to hear. Maybe I’ll give Silverblue a try
The flatpaks will continue to be updated by the backend system, but you’ll no longer have to deal with the sluggish frontend UI to keep things up to date.
the timer has no idea if it was triggered during last boot. It only has the context of “this” boot, so it will do it right after a reboot and set a timer to start the service again after a week of uptime.
So if you reboot every day, it will trigger the service every day, even though you set it to weekly in the timer.
So it’s up to your .service file to determine if it has been run this week or not.
It’s not a problem because the update script automatically skips the other GPU packages. Uninstalling it would be an issue because some nobara packages depend on it.
I used the commands OP provided, which is also what's been posted on the official page and it seemed to have worked without issues for me. At least in regards to me not having any graphical issues.
Your systemd file looks ok, but I think it’s doing exactly what you are telling it.
The solution may lie in the backup.service. Is that code you can modify? The OnCalendar=weekly doesn’t specify when in the week the service should run so that config may be vague.
If I understand the desired function here, you will need the service up all the time. It will just wait politely and occasionally run the specific backup script. It’s up to the backup script to determine when the last backup was made and either exit early because it hasn’t been a week or run the backup and reset a flag file.
At least that’s the approach I would take. Systemd is a very vigilant, but very stupid, service manager. It just watches and triggers services based on just a few criteria. Any logic more complex needs to go in the service itself.
It all started with my own Minecraft Server and an an offer on V-Servers at my Hoster at the time. Started to learn what SSH is, how to install Java and run my own Minecraft Server. And now I am running my Homelab on Kubernetes and do it for work. Life is funny
I was 11 and had issues with bad ram sectors so Windows would shut down every few minutes.
I read up on it and used an Ubuntu live USB, back when unity was new, I loved that it wouldn’t have problems with my ram so I installed it and started distro hopping.
I now don’t have a computer so I only use Windows at work.
OP is it the 7700 non-x 65w tdp version? Asking because I’m thinking about upgrading my CPU from 5600x to the 7700non-x and have the same gpu. I was actually wondering how throwing that integrated graphics into the mix would work so thanks for asking this and looking forward to your findings if you don’t mind posting however you end up solving this.
Yes, I have the non x version. I think the one with x has a higher tdp. I’ll probably look into this this weekend. Hopefully, I’ll find something out that’s helpful to you.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.