| Summary: | Start the update procedure per autostart | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | abillstein |
| Component: | Updates | Assignee: | Jonathan Thomas <echidnaman> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | aleixpol, johan, sitter |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
abillstein
2015-09-06 10:42:08 UTC
What do you mean by "update procedure"? You want muon-updater to just start updating as soon as your computer boots? Yes, when I put muon-updater to autostart, it starts, shows the busy-sign for a while and tells me then, that my last update is a while ago. Then I have to press e.g. ctrl-r for again let muon doing something (it shows again the busy-sign) and now, after this, i can start the actual update. At least, the first analysis of muon, that the update is a while ago, is not necessary. But an option to start muon directly with the update analysis is what I am looking for. Thanks. Achim. Is the problem perhaps due to Update-Manager starting before you have a network connection? Do you get the same problem if you start Update-Manager manually? You can start: plasma-discover --mode update You will get the updates view of Discover ready to trigger. Perfect, thanks. Achim. |