| Summary: | `~/.local/state/plasmasessionrestorestaterc` is not updated on logout | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Cristian Le <kde> |
| Component: | Session Management | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde, natalie_clarius, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.2.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | journalctl.log | ||
|
Description
Cristian Le
2024-11-11 18:18:00 UTC
Can you clarify what you mean when you said you "installed the tuxedo drivers"? Typically those drives would be intended to be used on TuxedoOS, but you say you're on Fedora. Installing one distro's drivers on another distro is generally not going to work unless you're a system-builder-level expert. Tuxedo also provides their drivers in a dnf form using kmod, rebuilding the kernel, similar to nvidia's. Those are available on copr [1] and on their official website [2] [1]: https://copr.fedorainfracloud.org/coprs/kallepm/tuxedo-drivers/ [2]: https://www.tuxedocomputers.com/en/Add-TUXEDO-software-package-sources.tuxedo 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! I am removing the NeedsInfo because I don't know what else to answer on this one. >how can I debug what failures are causing it to not update it?
You can run:
QT_LOGGING_RULES=org.kde.plasma-fallback-session-restore.debug=true /usr/lib/libexec/plasma-fallback-session-save
it should update the file.
Created attachment 176212 [details]
journalctl.log
Thanks David for the hint. Yes the command when executed manually does create an appropriate restore state of the current state, but this still doesn't resolve why it doesn't work properly when shutting down. I would expect either this scriplet to be run at shutdown either before all applications are closed in which case it will save the current session, or run it at the end in which case it would be clean, neither of which is what's happening here.
I've looked around on how to get the full `journalctl` log and I've used `-b -1` and found quite a lot of failures reported, although not sure if some are relevant to this symptom.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |