Bug 507766

Summary:	Allow user to control if update starts each time you run plasma-discover --mode browsing
Product:	[Applications] Discover	Reporter:	kdeuzver <asdf-kd>
Component:	PackageKit	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	aleixpol, kdedev, nate
Priority:	NOR	Keywords:	usability
Version First Reported In:	6.4.3
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description kdeuzver 2025-08-02 02:38:10 UTC

SUMMARY
Apt update should not be run every time Discover is launched.

Please add an option to the settings that allows you to disable apt update from running every time Discover is launched.

`--mode browsing` option doesn't works. apt update starts anyway.

Believe me, there is no need to abuse the system with such frequent updates of all repositories. After all, users may frequently run Discover, but running apt update every time is bad practice.
What if we give users the freedom to decide? How about that? Some freedom of choice.

Please be flexible in your thinking.
All you need to do is add one option to the settings to disable apt update at startup. And anyone who knows what they are doing could take advantage of this.

STEPS TO REPRODUCE
1. plasma-discover --mode browsing
2.
3.

OBSERVED RESULT
apt update starts each time you run plasma-discover --mode browsing

EXPECTED RESULT
apt update can be disabled from running every time you start plasma-discover --mode browsing

SOFTWARE/OS VERSIONS
Operating System: KDE neon User Edition
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.14.0-24-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ Ultra 7 255H
Memory: 32 ГиБ of RAM (30.8 GiB usable)
Graphics Processor: Intel® Graphics

ADDITIONAL INFORMATION
Here’s a screencast of me running Discover twice:
time stamps of interest:
4:15 - apt update timeout done.
4:54 - second Discover launch.
https://my.opendesktop.org/s/7Bk4T3aD83mDCdj

Comment 1 TraceyC 2025-08-05 21:47:29 UTC

Re-categorizing to feature request.
It's worth considering adding a checkbox to the Software Update KCM to automatically trigger an update or not. This could be beneficial in use cases where the system is mobile and doesn't currently have a network connection, the system has I/O contention or other resource considerations.

Comment 2 Nate Graham 2025-09-24 20:28:20 UTC

Can you describe what problem is caused by the status quo? Why does it not work out for you?

Comment 3 Bug Janitor Service 2025-10-09 03:46:58 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 4 Bug Janitor Service 2025-10-24 03:47:28 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.

Comment 5 kdeuzver 2025-11-24 06:36:30 UTC

(In reply to TraceyC from comment #1)
> Re-categorizing to feature request.
> It's worth considering adding a checkbox to the Software Update KCM to
> automatically trigger an update or not. This could be beneficial in use
> cases where the system is mobile and doesn't currently have a network
> connection, the system has I/O contention or other resource considerations.

This is a pretty good solution. Please add it. It will be helpful in many cases of Discover restart/crash/delay etc.

Comment 6 kdeuzver 2025-11-24 06:48:15 UTC

(In reply to Nate Graham from comment #2)
> Can you describe what problem is caused by the status quo? Why does it not
> work out for you?

ppa are often unavailable/malfunctioning, etc. Discover freezes and is not fully functional. If I don't want to update or install applications, I don't need to update all repositories every time I launch Discover. I may launch and close Discover frequently during work to search for information and install applications throughout the day. Updating all repositories each time I launch it is excessively abusive.

I am surprised that such a simple point is so hard to understood by the developers.

Comment 7 TraceyC 2025-11-24 19:04:50 UTC

(In reply to kdeuzver from comment #6)
> I am surprised that such a simple point is so hard to understood by the
> developers.

What we didn't have, that you have now helpfully explained, is why running apt update every time Discover was launched was a problem. We couldn't know that until you explained, we aren't mind readers. Please be respectful of the people you're asking to make changes for you.