Bug 506798

Summary:	Discover takes ages if a repository is blocked
Product:	[Applications] Discover	Reporter:	Martin Tlustos <martin.tlustos>
Component:	discover	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	minor	CC:	aleixpol, sitter
Priority:	NOR
Version First Reported In:	6.4.2
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Martin Tlustos 2025-07-09 13:07:34 UTC

SUMMARY
I have proton vpn and its repositories installed on my system. The country where I currently work in has blocked access to proton vpn's website and also the repository (as well as other prominent vpns).
Now every time I start up discover, it takes ages for any step (like getting updates, displaying package information etc.), until the following error message appears:
"there was an unkown error..." etc, and then this:
E: https://repo.protonvpn.com/debian stable InRelease is not (yet) available (Could not wait for server fd - select (11: Resource temporarily unavailable) [IP: 104.26.4.35 443])

The problem probably cannot be reproduced outside of countries with such restrictions, but maybe something can be done about it?

Operating System: KDE neon User Edition
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.0
Kernel Version: 6.11.0-29-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 16 GiB of RAM (15,0 GiB usable)
Graphics Processor 1: AMD Radeon Graphics
Graphics Processor 2: AMD Radeon 550X Series
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12

Comment 1 Harald Sitter 2025-07-10 08:22:37 UTC

That seems entirely expected. It is how network timeouts work.

Comment 2 Martin Tlustos 2025-07-10 08:32:33 UTC

Yes, I know that, and that by itself is not the problem. But why would it prevent package info being displayed if the package is in another repo that's reachable?

Comment 3 Harald Sitter 2025-07-10 08:45:10 UTC

In apt, cache updates happen in one step. If something holds up that step then the cache update as a whole gets held up