Hello there. The "Restart / Shut Down / Log out" buttons no longer work after upgrading the package "plasma-workspace". I have to use the terminal to do those operations. I'm not sure if this is caused by X11 (as I use the community-mantained "plasma-workspace-x11"), but I believe it is not. Downgrading from 6.0.5 to 6.0.3 fixes the problem. From journalctl, the following may be relevant: ========================================================== jun 07 11:45:32 fedora systemd[1562]: dbus-:1.2-org.kde.LogoutPrompt: Main process exited, code=exited, status=1/FAILURE jun 07 11:45:32 fedora systemd[1562]: dbus-:1.2-org.kde.LogoutPrompt: Failed with result 'exit-code'. ========================================================== Downgrade command used: sudo dnf downgrade plasma-workspace* Versions before downgrade: https://0.jaegers.net/?b040181b0a67c5be#5yWERt12eybKqnMh9q777cPoCrwkgm1HfpS8PgFCmv7e Downgrade list: https://0.jaegers.net/?082eda515741325b#4Yrj1rKWPncSnF1jRnmGZn9BvZemykNDAo6Da8HpJXwN Versions after downgrade: https://0.jaegers.net/?4de90f838a4301fb#BwQ6tib5kmtGLteMGoEAKnWAjSjjGtY9BBUFiNuqDfwQ ========================================================== Thank you for your attention. Reproducible: Always Not sure if the version 6.0.4 exists, have not tested with it if it does exist. Also, this may be an upstream bug, but I don't know.
To be clear, the Shut Down button and etc. do their job of closing all apps, but the user log out does not happen. I have then to restart Plasma-shell with a keybind and then I open the terminal and type `systemctl [reboot/poweroff]` to be able to proceed.
If you restart the system (using the terminal or even the power or reset button) after upgrading, does logging out or shutting down work then or is the failure persistent? It can unfortunately happen that Plasma is unable to log out after it was upgraded from within the session, but this should not persist after a logout or reboot. Though if the failure is persistent, it sounds like we have a real regression. So then it would be interesting whether you can reproduce this in a Wayland session. (You don't have to USE it, just to test quickly whether it can shut down / log out.)
For my system, I only apply updates when rebooting, and I believe this is the default behavior for new Fedora installations. So there was no chance of session corruption. Anyway, I tested my system again with the latest updates applied, and I can affirm the following: What works or not under Wayland: - Restart: YES - Shut Down: YES - Lock: YES - Switch User: YES - Log Out: NO What works or not under X11: - Restart: NO - Shut Down: NO - Lock: YES - Switch User: YES - Log Out: NO Both Wayland and X11 have problems with Log Out. Only X11 has problems with Restart and Shut Down.
I guess this is a regression from the ksmserver security hardening done in plasma-workspace 6.0.5.1 (which are NOT included in the 6.0.5 tag, only in the Plasma/6.0 branch). Instead of downgrading all the way down to 6.0.3 from Fedora 40 GA, I would suggest downgrading only plasma-workspace and plasma-workspace-x11 to 6.0.5: https://koji.fedoraproject.org/koji/buildinfo?buildID=2456775 https://koji.fedoraproject.org/koji/buildinfo?buildID=2456779 If that fixes it, then it is pretty clear where the regression comes from (and in that case, my recommendation would be to just revert the broken patch / downgrade to 6.0.5 in F40 updates).
Hi there. How can I downgrade only those 2 packages without breaking the system with version mismatch? When I type "sudo dnf downgrade plasma-workspace plasma-workspace-x11", it suggests the version 6.0.3, and also downgrades some unrelated packages, such as "obs-studio" and "qbittorent". Thank you for your attention.
Use the direct links to the RPMs from the 2 Koji links I posted, i.e.: sudo rpm -Uvh --oldpackage https://kojipkgs.fedoraproject.org//packages/plasma-workspace/6.0.5/1.fc40/x86_64/libkworkspace6-6.0.5-1.fc40.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/plasma-workspace/6.0.5/1.fc40/x86_64/plasma-workspace-6.0.5-1.fc40.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/plasma-workspace/6.0.5/1.fc40/x86_64/plasma-workspace-common-6.0.5-1.fc40.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/plasma-workspace/6.0.5/1.fc40/x86_64/plasma-workspace-geolocation-6.0.5-1.fc40.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/plasma-workspace/6.0.5/1.fc40/x86_64/plasma-workspace-geolocation-libs-6.0.5-1.fc40.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/plasma-workspace/6.0.5/1.fc40/x86_64/plasma-workspace-libs-6.0.5-1.fc40.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/plasma-workspace/6.0.5/1.fc40/x86_64/plasma-workspace-wayland-6.0.5-1.fc40.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/plasma-workspace-x11/6.0.5/1.fc40/x86_64/plasma-workspace-x11-6.0.5-1.fc40.x86_64.rpm
Can't proceed due to error: error: Failed dependencies: plasma-lookandfeel-fedora = 6.0.5-1.fc40 is needed by plasma-workspace-6.0.5-1.fc40.x86_64 plasma-workspace = 6.0.5.1-2.fc40 is needed by (installed) plasma-lookandfeel-fedora-6.0.5.1-2.fc40.noarch plasma-workspace = 6.0.5.1-2.fc40 is needed by (installed) sddm-breeze-6.0.5.1-2.fc40.noarch Could you please provide me with the links for these packages too? Thanks in advance.
Ah, those are under the same Koji build link I posted above, but under "noarch": https://kojipkgs.fedoraproject.org//packages/plasma-workspace/6.0.5/1.fc40/noarch/plasma-lookandfeel-fedora-6.0.5-1.fc40.noarch.rpm https://kojipkgs.fedoraproject.org//packages/plasma-workspace/6.0.5/1.fc40/noarch/sddm-breeze-6.0.5-1.fc40.noarch.rpm
Hello there. Thanks for the links. Here's the terminal output of the command: https://0.jaegers.net/?f9fc147477981368#BUzRv25iRd1AgWLx55eXke1CgSXSih8NXNrdLmVeBt7k Then, I rebooted and tested the buttons both under Wayland and X11. While testing, I had latest system updates applied, plus your mentioned specific downgrades. Test results: everything works as it should, except "Log Out". Under Wayland, "Log Out" lets me exit the current session, but when trying to log back in the monitor image freezes and I have to turn off my PC via button. Under X11, it closes all apps (including the Plasma Shell), but does not log out. I believe the "Log Out" button problem is another issue that is not directly related to this issue. It seems your guess was correct. Thanks!
To clarify: "Then, I rebooted and tested the buttons both under Wayland and X11." "buttons" here means the GUI buttons (KDE Plasma start menu buttons). ------------ "Under Wayland, "Log Out" lets me exit the current session, but when trying to log back in the monitor image freezes and I have to turn off my PC via button." "button" here means the physical button on my PC cabinet.
Maybe we should revert the "Remove iceauth dependency" parts, keep only the actual security fix, and just add a Requires: iceauth to the package? (Though I have not verified whether that fixes it or whether the security fix alone is already enough to trigger the bug.)
Quoting the upstream report: --- Comment [https://bugs.kde.org/show_bug.cgi?id=488187#c7] from David Edmundson --- We should do some research before doing any actions. Is ICEAUTHORITY set? What are the contents of where it points? What's the stderr when we start dolphin on X11?
Hi there, what new info can I provide?
The one the upstream developer asked for. :-) In other words, in a session using plasma-workspace-6.0.5.1-2.fc40 (and its subpackages) and plasma-workspace-x11-6.0.5.1-1.fc40, open a Konsole window and copy the outputs of the following commands: echo "$ICEAUTHORITY" dolphin The former should just print the contents of the environment variable ICEAUTHORITY. The latter should start a Window with Dolphin, but it is the terminal output that we are interested in.
Hi there Kevin. Thanks for making it easier for me. Here you go: https://0.jaegers.net/?23a726b30013e7aa#5ZX2ivqqZCnpwnAu13bSxz4aeaqXMRDsw6hjZnCkowCo "dolphin" didn't output anything except if I walked through some folders. That's why there is some spam in the output. The file "/run/user/1000/iceauth_MfWxAr" points to the tmp folder as you can see in the output. "MIT-MAGIC-COOKIE 1" appears inside it many times.
*** Bug 2291334 has been marked as a duplicate of this bug. ***
Same issue for me in F40, though I was able to change to another virtual terminal (Ctrl-Alt-F4) and run "systemctl restart sddm" as root to get the sddm login screen back. From there I can choose Shutdown or Reboot (or log back in to Plasma). So that's one temporary workaround until this gets fixed.
I'm also having this exact same problem. To shutdown, reboot or logout I need to use TTY or CLI in Konsole. This only happens in the X11 session. At Wayland everything is normal.
I have the same issue with PC and notebook under X11 session. plasma-workspace-x11-6.0.5.1-1.fc40.x86_64
The issue has been fixed with the update to KDE Plasma 6.1.0. Tested on X11.
Yes, now it works for X11 too
still failing the same way for me on a fully up-to-date fedora 40 instance running on a thinkpad laptop using the x11 version of plasma, not the wayland version. is there any info i can provide that would be useful here?
Unfortunately we do not support Plasma X11 sessions. If you have issues with that you will have to open a bug against plasma-workspace-x11
I already forwarded the report upstream (see https://bugs.kde.org/show_bug.cgi?id=488187), but the thing is, both here and in the upstream report, it was claimed that this is fixed in 6.1.0, at least the users could no longer reproduce it there. So if you can still reproduce this in 6.1.x, we will likely need to reopen the upstream bug.
(I am the maintainer of plasma-workspace-x11 in Fedora.)
I have reopened the upstream bug: https://bugs.kde.org/show_bug.cgi?id=488187#c21
this bug is still in Fedora 40 (completely up-to-date as of 7/19/24). specifically kernel v6.9.9 and plasma-workspace-x11 v6.1.2-1. exists on bare metal as well as vmware VM's. one thing i've noticed (not sure if it is relevant) is that on some instances of this problem, after i choose reboot or shutdown from the kde app launcher, it will kill most things and display a dark screen *except* for some remote gkrellm processes i run via ssh and X11 forwarding. they continue to run until a command line shutdown, reboot, or sddm restart.
(In reply to Mark T. Kennedy from comment #27) > this bug is still in Fedora 40 (completely up-to-date as of 7/19/24). > specifically kernel v6.9.9 and plasma-workspace-x11 v6.1.2-1. exists on > bare metal as well as vmware VM's. > > one thing i've noticed (not sure if it is relevant) is that on some > instances of this problem, after i choose reboot or shutdown from the kde > app launcher, it will kill most things and display a dark screen *except* > for some remote gkrellm processes i run via ssh and X11 forwarding. they > continue to run until a command line shutdown, reboot, or sddm restart. I see this too, seems is sddm that crash , ctrl + alt + F3 to got to one vt terminal an ctrl + alt + del I'll investigate Thank you for the report
https://bugs.kde.org/show_bug.cgi?id=490344
still present in a fully-up-to date F40 with kernel 6.9.11-200, plasma-workspace-x11 6.1.3-2, and sdd 0.21.0-4. is there any info i could provide that we be useful in resolving this? are there any theories about the source of the problem?
sorry, 'sddm', not 'sdd'.
The problem was fixed for me with Plasma 6.1.0. I have updated my F40 system since then, and still no problems. Currently I'm using the following packages: plasma-workspace-x11-6.1.3-2.fc40.x86_64 sddm-0.21.0-4.fc40.x86_64 kernel-6.9.12-200.fc40.x86_64 So I am using X11, not Wayland. I don't know if the GPU is a factor, as I'm using an integrated Intel GPU with the i915 driver. I've seen reports of people with Nvidia cards still having the problem.
same kernel, sddm, and plasma-workspace-x11 versions - shutdown/restart still hangs with a blank screen. however... i created a brand new ID with no customization at all. sign in with a plasma-x11 session and restart/shutdown *works*. fascinating. so something in my KDE config or environment triggers the bug. anything i can provide (log file, etc) to help?