|
Bugzilla – Full Text Bug Listing |
| Summary: | Software updates fail with error message, all previous updates installed over and over again, now can't update | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | teo teo <php4fan> |
| Component: | Upgrade Problems | Assignee: | E-mail List <screening-team-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | Andreas.Stieger |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
teo teo
2022-03-23 18:31:17 UTC
Starting from something very basic: I did "sudo zypper dup" from a terminal. It gave me the exact same error, and it gave me a choice: ignore/retry/ abort (or something). Not that that changes a lot (in order to retry I needed to try and guess what to do to remove the problem, which I did), but the fact that the Software Updates widget doesn't even give me that very basic, trivial, bare minimum of a choice that is "retry / ignore / abort" is absolutely pathetic. Note: that is not the whole issue, there's a lot to unpack here, but maybe start from there? see bug 1197365 *** This bug has been marked as a duplicate of bug 1197365 *** I am sorry you feel... challenged. Some hints: * See below for what "critical" means: "Crash, data loss or corruption, severe memory leak, etc." This bug is not critical. Don't escalate because it is important to you. https://bugzilla.opensuse.org/page.cgi?id=importance_matrix.html * Use bugzilla bug search. It would have shown bug 1197365 * If you handwave to previous bugs, mention them. You mean bug 1195810. (In reply to teo teo from comment #0) > I think there's never been a single time that I have installed updates from > the Software Updates widget without some issue. Really? > Something always goes wrong. Always? |