KDE

5332 readers

292 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago

MODERATORS

carlschwan@lemmy.kde.social

Bro666@lemmy.kde.social

herzenschein@pawb.social

Aniqakhokhar@lemmy.kde.social

Discover Updates tab keeps refreshing non-stop (lemy.lol)

submitted 1 month ago* (last edited 1 month ago) by QuazarOmega@lemy.lol to c/kde@lemmy.kde.social

1 comments fedilink hide all child comments

I'm using Fedora Kinoite and there's this little issue that has been bugging me to no end, whenever I want to see what updates have been found for my apps and their changelogs I start scrolling there, but every few seconds, say 20, the page will refresh and look for updates again, so it interrupts my reading and resets the scrolling position I was at, so I have to wait there to finish refreshing, jump to where I was and speed-read that piece of text before it refreshes once again and I'm thrown back to square one.
I was wondering if there is any setting to control how often Discover auto-refreshes, maybe set it to only manually refresh instead, but there doesn't seem to be anything in the Settings tab.
Is there a solution or is this a bug?

you are viewing a single comment's thread
view the rest of the comments

[–] QuazarOmega@lemy.lol 1 points 1 month ago* (last edited 1 month ago)

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