Bug 1956916 - KDE Session Not restored properly
Summary: KDE Session Not restored properly
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 34
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-04 16:15 UTC by Brian Kaye
Modified: 2021-05-06 15:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)

Description Brian Kaye 2021-05-04 16:15:41 UTC
Description of problem:workspaces not restored to proper desktop

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

Fedora 34 Plasma 5.21.4-1.fc34.x86_64  using X11
How reproducible:
Every time

Steps to Reproduce:
1. Shutdown system
2. Reboot

Actual results:
All windows are started in the first desktop

Expected results:
All windows should be started in their original desktop.

Additional info:
New upgrade of fedora 34 from fedora 33.

I have 4 virtual desktops configured. On restart all the workspaces are restored to the first virtual desktop.

Comment 1 John Griffiths 2021-05-05 00:56:14 UTC
I upgraded from FC32 to FC34 and have similar problem.

I have 6 desktops. All got jammed into one. The mouse and keyboard become unresponsive.

I was using KDM. Switched to SDDM which did not actually start my desktop. Switched to GDM which also messed up when I tried to run a plasma session.

Comment 2 Brian Kaye 2021-05-05 02:45:04 UTC
I am using sddm. Did not have a problem with my mouse or keyboard. I am using X11 and not Wayland

Comment 3 John Griffiths 2021-05-05 16:13:05 UTC
I got the kde desktop to display under GDM by selecting the Plasma Wayland but after a while, the display became unresponsive; no mouse pointer movement or response to keyboard. 

I connected by ssh from a f32 system and ran top. plasmashell is running away.

296991 jrg3      20   0 2258508 215112 130524 S 100.0   1.3  36:50.27 plasmashell

Comment 4 Brian Kaye 2021-05-06 01:24:35 UTC
Sounds like a different problem. Did you try Alt+Ctrl+F3 to get a new console?

Comment 5 John Griffiths 2021-05-06 15:24:58 UTC
(In reply to Brian Kaye from comment #4)
> Sounds like a different problem. Did you try Alt+Ctrl+F3 to get a new
> console?

Yes. Like I said, the keyboard and mouse were both unresponsive.

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