| Summary: | logout menue does not pop up after "Save Session" | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Toralf Förster <toralf.foerster> |
| Component: | Session Management | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | akselmo, asturm, kdedev, keplicz, natalie_clarius, nate, notmart, winter |
| Priority: | NOR | ||
| Version First Reported In: | 6.1.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Toralf Förster
2024-09-21 15:49:28 UTC
I should add that Gentoo's plasma-workspace-6.1.5-r2 package contains two related backports:
> 4dff1973116597210cf9fb1c102e5c9433d13b1d startkde: Fix wayland session restore saving
> 9bd2dcc8a785d977cdf67a7cbb467423803e3327 startkde: Disable session management in our session management
wayland or x11? I can reproduce this 1. Open desktop session settings 2. Select "When session was manually saved" radio button 3. When settings prompts to restart, click it 4. Nothing happens 5. Nothing happens from clicking restart/logout/etc. from launcher as well Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.2 Kernel Version: 6.10.10-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 (In reply to Marco Martin from comment #2) > wayland or x11? x11 here at a stable hardened Gentoo Linux After building plasma-workspace from scratch with `kdesrc-build plasma-workspace --no-inc --refresh-build` the bug does not happen. So it might have been because of that. Will have to keep eye on this and see if it re-occurs. Setting this back to reported. Similar for me with Plasma Wayland and Fedora 41 select Leave->Save Session then Restart, Shutdown, Logout->Leave no longer work *** This bug has been marked as a duplicate of bug 449077 *** |