| Summary: | Discover's checking for updates appears to interfere with other network activity happening at the same time | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Gary <gh4wi> |
| Component: | discover | Assignee: | Dan Leinir Turthra Jensen <leinir> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | aleixpol, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.13.5 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Gary
2019-04-17 16:38:09 UTC
What do yo mean by "interferes"? What are the symptoms of this interference? 1) Discover prevents VPN from making initial connection. 2) Discover prevents login from working. User should be able to control when Discover runs. (In reply to Gary from comment #2) > 1) Discover prevents VPN from making initial connection. > 2) Discover prevents login from working. But what made you think it's Discover? The Discover Icon is on the task bar, usually blinking, when the conflict happens. When Discover is not active, there is no conflict and everything works ok. Please add a feature that allows the user to define when Discover should run. Discover shouldn't interfere with other network activities. Aleix, any idea what might be going on here? FYI --- I have several PC's, with different CPU & Mobo, which are booted daily and I see the same conflict with Discover & other network usage. Please allow the user to establish when Discover runs. Personally, I would prefer to run it via a cron job prior to shutdown (at Logout). But others may prefer to run it at a set time, say at lunch time. In any case, please end the forced interference which prevents users from working, because they must yield their PC to forced updates. Thanks. There are no "forced updates". You as the user choose to perform the updates at your leisure. Simply *checking* for updates is what's fixed right now. Regardless of whether or not we offer a configuration UI for this, the more important problem to solve is figuring out why you're seeing poor/no network connectivity during the periods when Discover is checking for updates. If Discover is the cause of that, we need to fix it. You can check how often updates are checked using software-properties. This way you can decide when your apt caches update. Should work as necessary, an update to newer Plasma could be needed, I don't remember if the behaviour was already in place by 5.13. |