• 9 Posts
  • 422 Comments
Joined 1 year ago
cake
Cake day: August 10th, 2023

help-circle


  • useless research for the curious

    Did a bit more research, was thinking it might be a systemd service, so I checked for timers there, but there was just a countme timer enabled that basically tells the server to include you in the count of active systems (how to disable, for the paranoid 🥸).
    Then I went on to look at the live logs of rpm-ostree and, as found from this website used this command:

    journalctl --follow --unit rpm-ostreed.service
    

    So that I could monitor its activity while I open Discover and so I managed to record when it happens, I also saw from the logs that there is a configuration file at this path /etc/rpm-ostreed.confand that you can configure automatic updates from there, by default there a this line about it (usage greatly explained with man rpm-ostreed.conf btw):

    [Daemon]
    #AutomaticUpdatePolicy=none
    

    but it’s commented out, so it couldn’t have been that.

    Finally there is this one thing that pops up in the logs:

    Initiated txn AutomaticUpdateTrigger for client(id:cli dbus:1.1625 unit:app-org.kde.discover@df0f43f8979843c0a34d36ad199c7eda.service uid:1000): /org/projectatomic/rpmostree1/fedora
    

    So it is something triggered by Discover, as I had known already, due to other articles that talk about the integration with Discover, but I wasn’t so sure about it anymore, since I couldn’t find any related settings in the app.

    So I found the setting that configures automatic updates in general… in the three dot menu (questionable UX decision?):

    three dot menu > Configure Updates...

    which actually just leads to the system settings:
    Update software: automatically. Update frequency: weekly
    I had this configured to be weekly, there isn’t even a setting as granular as seconds, the smallest span of time is daily, but what I’m guessing is that the “Update frequency” acts on when they should be installed automatically rather than when they should be fetched, so this is a limitation of the system as I understand it




  • Why so irritable? I’m just asking, I don’t even know German, I thought since you knew the video already, you could point me in the right direction, rather than me having to sift through it all while also passing it through a translator to hopefully (because I don’t know how well youtube’s auto-translate feature works) find the information I’m looking for in the whole presentation









  • QuazarOmega@lemy.loltoLinux@lemmy.mlFedora: GNOME or KDE?
    link
    fedilink
    English
    arrow-up
    14
    ·
    edit-2
    23 days ago

    I used to prefer GNOME, until I started using KDE daily on the desktop, I thought it would just be temporary, but I ended up liking KDE way more because of the features that are built-in, the integration is simply priceless and I’m tired of those GNOME extensions that keep breaking at the next GNOME major release and I have to wait weeks for the poor devs to catch up and fix them up to get the compatibility going again, in some ways that also happens on KDE with the widgets, but, arguably, you will need way fewer of those to extend the already wide functionality provided by the Fedora KDE experience, so you risk incurring in that issue a lot less. Note I specifically mention Fedora both because it’s the system you want and because the pool of apps included is the best for a streamlined, but not bloated, experience, which also allows me to use Kinoite without troubling myself to overlay crucial apps that aren’t provided (or don’t work fully) as Flatpak.








  • I agree, besides basic patterns to search for, that will most likely be necessary. In fact looking a bit more at this tool, it has a list of “rules” tailored to each software specifically, I guess this could be sustainable really only if a repository of third party extensions was kept so that anyone could contribute and the pool of rules expanded progressively