Bug 33299 - Plasma desktop session is not restored on Wayland (but on X11 it is ok)
Summary: Plasma desktop session is not restored on Wayland (but on X11 it is ok)
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-12 21:51 CEST by ylyco
Modified: 2024-06-13 08:03 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description ylyco 2024-06-12 21:51:46 CEST
Description of problem:
I open a new report, related to this one :
https://bugs.mageia.org/show_bug.cgi?id=33279

I have installed the updates for all ***.5.27.10-1.2.mga9.x86_64.rpm packages, has precised in the postid=33279.

The problem have been solved for X11, but in my case it's still present on Wayland.

Version-Release number of selected component (if applicable):
Mageia 9 / x64 / SDDM

On X11 session : LibreOffice, Gwenview, Okular, Kate, Konsole, Firefox and Thunderbird re-open successfully after reboot. This case is ok now.

But on the other side with Wayland : only Firefox and Thunderbird open successfully. Others softwares which are ok with X11n after reboot, are not with Wayland.
Comment 1 ylyco 2024-06-12 22:20:39 CEST
I have to tell that on Wayland it uses to work before versions ***.5.27.10-1.1.

I was working without any problem with Wayland since my beginning with Mageia 9.
It's only with the bug mentioned the 10th of June, that I noticed a problem.
Once the ***.5.27.10-1.2.mga9.x86_64.rpm packages where installed and Wayland in use, the problem was the same, no cure in this case.
But as soon as I switched to X11 : the problem disappeared, all was ok.

So I think there is still an issue with Wayland case.
Comment 2 Morgan Leijström 2024-06-13 08:03:25 CEST
Thank you for reporting.
Assigning to KDE team.

Assignee: bugsquad => kde
CC: (none) => fri


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