Bug 373807 - Feature request: a refresh button and a config button
Summary: Feature request: a refresh button and a config button
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: PK Updates widget (other bugs)
Version First Reported In: 6.2.4
Platform: Other Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-18 09:26 UTC by Guo Yunhe
Modified: 2025-02-15 03:46 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshot of plasma-pk-updates widget offline but internet is available (14.90 KB, image/png)
2016-12-18 09:26 UTC, Guo Yunhe
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Guo Yunhe 2016-12-18 09:26:12 UTC
Created attachment 102850 [details]
Screenshot of plasma-pk-updates widget offline but internet is available

Currently, the plasma-pk-updates widget doesn't have any button to do a manual update.

Sometimes, even if I connected to internet, the plasma-pk-updates widget still thinks it is offline. Sometimes, available update list is quite old and some packages have been changed. In these situations, users need a way to manually refresh updates.

So I suggest to add a refresh button on the widget. In addition, a configuration button is also helpful. Thanks!
Comment 1 Jan Grulich 2017-01-02 11:48:21 UTC
The information about whether you are online or not is coming from PackageKit itself, so you are either connected through something what PackageKit doesn't check or there is a bug in PackageKit itself. If you are online you will see a button to refresh packages.
Comment 2 Maxime Corteel 2017-01-19 10:06:14 UTC
I don't have a refresh button when a list of packages has been loaded. But this list can be 23 hours old (refreshed every 24 hours).
Which means that if I launch the update, it might fail (if the packages have changed) without refreshing the repositories (there is still no button and it doesn't refresh automatically).
This means that I have to wait until the 24 hours are over to make the update (and not miss the target by too long if I don't want the packages list to be out of sync again).
When using a distro like OpenSUSE Tumbleweed, it's a real day-to-day issue.
Or am I missing something?
Comment 3 Guo Yunhe 2017-01-19 10:26:26 UTC
(In reply to Maxime Corteel from comment #2)
> I don't have a refresh button when a list of packages has been loaded. But
> this list can be 23 hours old (refreshed every 24 hours).
> Which means that if I launch the update, it might fail (if the packages have
> changed) without refreshing the repositories (there is still no button and
> it doesn't refresh automatically).
> This means that I have to wait until the 24 hours are over to make the
> update (and not miss the target by too long if I don't want the packages
> list to be out of sync again).
> When using a distro like OpenSUSE Tumbleweed, it's a real day-to-day issue.
> Or am I missing something?

I have the same problem with you. I also use openSUSE Tumbleweed. Zypper will check latest repo data every time you update. But plasma-pk-updates will keep old result for 24 hours. When you update with old result, these packages might not exist anymore.
Comment 4 TraceyC 2025-01-16 16:50:26 UTC
Thank you for the bug report. Unfortunately we were not able to get to it yet. If your system is still running Plasma 5, can we ask you to please check if this is still an issue with Plasma 5.27.12 (the current LTS version)? The PK Updates Widget has not been ported to Plasma 6, so if your system has updated to that, this report isn't relevant anymore.

If you can still reproduce the bug, please change the Status to "CONFIRMED". Thanks.
Comment 5 Bug Janitor Service 2025-01-31 03:47:19 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2025-02-15 03:46:30 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.