Bug 2293151
| Summary: | Cannot update to KDE Plasma 6.1.0 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | EpicTux123 <EpicTux123> |
| Component: | plasma-workspace | Assignee: | KDE SIG <kde-sig> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 40 | CC: | jgrulich, kde-sig, kevin, perfinstals, rdieter, than |
| Target Milestone: | --- | Keywords: | Desktop, Upgrades |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-20 21:04:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
EpicTux123
2024-06-20 04:35:26 UTC
it does it to me too, if I try to update from discover, it gives me a series of errors, probably the same ones... what should I do? wait for them to fix the updates or some terminal commands? it works after giving sudo dnf upgrade --refresh --allowerasing --best Hello there. Thanks for the command. It seems to solve the issue. However, since I'm on X11, it doesn't work well for me because the "plasma-workspace-x11" package wasn't updated yet. After using the provided command, it uninstall the X11 packages (kwin and plasma-workspace), and then "sudo dnf install plasma-workspace-x11 kwin-x11" downgrades me to 6.0.3 (which is not a problem for me). I guess the problematic 6.0.5 were removed from the repositories due to the shutdown issue. I believe 6.1.0 fixes the shutdown issue. Kevin, could you provide some information/feedback? Thanks in advance for your time. > I believe 6.1.0 fixes the shutdown issue. I doubt it, because I have not seen any fix from upstream, though I have no evidence to conclude either way so far. *** This bug has been marked as a duplicate of bug 2293204 *** |