Summary: | Logout/shutdown stopped working in Plasma 6.1.X | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Lassi Väätämöinen <lassi.vaatamoinen> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kde, keplicz, sergio |
Priority: | NOR | ||
Version: | 6.1.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
See Also: |
https://bugzilla.redhat.com/show_bug.cgi?id=2290894 https://bugs.kde.org/show_bug.cgi?id=488187 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Lassi Väätämöinen
2024-07-16 08:32:54 UTC
Also, seeing these: heinä 16 11:45:10 mopo org.kde.LogoutPrompt[4804]: warning: queue 0x55ea706c2f90 destroyed while proxies still attached: heinä 16 11:45:10 mopo org.kde.LogoutPrompt[4804]: wl_registry@36 still attached heinä 16 11:45:10 mopo dbus-daemon[2632]: [session uid=1000 pid=2632] Successfully activated service 'org.kde.LogoutPrompt' heinä 16 11:45:10 mopo ksmserver-logout-greeter[4804]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 heinä 16 11:45:10 mopo ksmserver-logout-greeter[4804]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 heinä 16 11:45:10 mopo ksmserver-logout-greeter[4804]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. heinä 16 11:45:10 mopo kwin_wayland[2668]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target. (In reply to Lassi Väätämöinen from comment #0) > This issue seems to be of very recent occurrence, since 6.1.1 or 6.1.2. Not > sure if related to bug 490081. It looks like this is very much related to the situation in bug 490081. Logout etc. work fine on my home setup, with laptop connected to one external screen, HDMI. But, at work with Thunderbolt 4 dock (USB-C + Displayport) dual screen setup, the 2nd display remain dark 50-70% of the reboots. And also logout/shutdown/etc. do not work. But on some occasions the exit functions work OK. For example today: Boot #1: 1. Log into Plasma session 2. Observe 2nd screen dark 3. killall kwin_wayland 4. Observe picture on both screens 5. Move mouse to 2nd screen -> 2nd screen goes black 6. Application Menu -> Reboot -> reboots Boot #2 1. Log into Plasma session 2. Observe 2nd screen dark 3. Disconnect and reconnect TB4 dock data connector 4. After a while both screens on, but in wrong order 5. Reorder screens 6. 6. Application Menu -> Log out -> NO EFFECT (In reply to Lassi Väätämöinen from comment #2) > It looks like this is very much related to the situation in bug 490081. > > Logout etc. work fine on my home setup, with laptop connected to one > external screen, HDMI. Per my recent findings, these actually are not related. The logout/shutdown/reboot dialog works sporadically. It worked fine on my home setup (laptop display + HDMI external monitor) this morning, and worked once at office with my work setup: laptop + TB4 dock + 2 screens. Later in the day it did not work at my office, and now it does not work at home, either. I experience similar problems. Session doesn't end when logging out, leaves a blank screen with the mouse cursor. I'm using X11, happens with and without the external screen attached. Using KDE neon with Plasma 6.1.2, problems started after an upgrade to 6.1.0. Can I have some non-truncated logs. (In reply to David Edmundson from comment #5) > Can I have some non-truncated logs. Sure, can you provide the needed commands / env variables / other stuff needed? (In reply to Piotr Keplicz from comment #4) > Using KDE neon with Plasma 6.1.2, problems started after an upgrade to 6.1.0. I am not sure if this is very specific to KDE Neon, or particular hardware. I have another system running openSUSE Tumbleweed + Plasma 6.1.2 and there's no issue with logout. I also see this in my Fedora 40 kde X11 , I notice none of the process die and also other reports https://bugzilla.redhat.com/show_bug.cgi?id=2290894 also use gdm instead sddm doesn't help (In reply to David Edmundson from comment #5) > Can I have some non-truncated logs. @David: I can provide the logs, if I could have the needed commands / env variables / other stuff needed for producing them. from a clean boot, log in, try to log out, run: "journalctl --user -b" 🐛🧹 ⚠️ 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. please read *** This bug has been marked as a duplicate of bug 488187 *** |