Bug 1907759 - KDE broken after recent F33 update
Summary: KDE broken after recent F33 update
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 33
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-15 07:22 UTC by Sreyan Chakravarty
Modified: 2021-11-30 17:28 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-30 17:28:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
DNF packages included in transaction (117.58 KB, text/plain)
2020-12-15 07:22 UTC, Sreyan Chakravarty
no flags Details

Description Sreyan Chakravarty 2020-12-15 07:22:38 UTC
Created attachment 1739249 [details]
DNF packages included in transaction

Description of problem:

I just did a "dnf update -y" after that KDE is completely broken.
When I reboot the workspace is not there, the wallpaper is not there, all I can open is the terminal. The entire KDE desktop and KDE workspace is not there.

After reboot I get the message:
"The application kde5 has requested to open the wallet kdewallet."

Version-Release number of selected component (if applicable):

Operating System: Fedora 33
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.1
Kernel Version: 5.9.13-200.fc33.x86_64
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520

How reproducible:

Always when I update.

Steps to Reproduce:
1. Open terminal.
2. sudo dnf update -y
3. Reboot.

Actual results:

Desktop, wallpaper and the entire KDE workspace is not present after rebooting.

Expected results:

The KDE workspace along with the desktop and wallpaper should be present after the reboot following the update.

Additional info:

Packages included in the dnf transaction included in the attachment.

Comment 1 Sreyan Chakravarty 2020-12-17 18:38:37 UTC
I have found the packages that were causing the problem:

kwayland packages
kf5-plasma

The update succeeds if I exclude them:

sudo dnf update -y --excludepkgs=kwayland*,kf5-plasma

Comment 2 Rex Dieter 2020-12-18 17:53:57 UTC
Interesting, are you using a wayland session?

Comment 3 Sreyan Chakravarty 2020-12-18 19:00:17 UTC
(In reply to Rex Dieter from comment #2)
> Interesting, are you using a wayland session?

No, I have never used it. I am always on X11.

Comment 4 Ben Cotton 2021-11-04 16:46:14 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2021-11-30 17:28:12 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.