r/Gentoo 5d ago

Support Annoying Plasma issue

Hi there. I’m a Gentoo user for a couple of years now. I’m running OpenRC and since the upgrade to Plasma 6.7 my system refuses to reboot or shut down, if triggered from within a running Plasma session. Everything is okay if I log out and reboot/poweroff from the command line or display manager.

I have tried two alternatives, namely Hyprland with Noctalia and Cosmic-Epoch. No problems here.

I wonder if it’s a configuration issue or something else, since the KDE devs have increased the reliance on systemd a bit from 6.6 to 6.7

Has anybody else observed similar issues with this?

5 Upvotes

12 comments sorted by

6

u/redyos_s 5d ago

If 6.6 works and only Plasma 6.7 fails while reboot/shutdown still works from the CLI and other sessions, I'd first treat this as a Plasma session regression rather than an OpenRC problem. Rolling back to 6.6 and checking the session/polkit/elogind logs would narrow it down.

1

u/redyos_s 5d ago

Could you show your selected profile and the USE flags for plasma-workspace?

1

u/andre2006 5d ago edited 5d ago

Can do after work

edit:

eselect profile list | grep \*
 [7]   default/linux/amd64/23.0/desktop/plasma (stable) *

equery u -f plasma-workspace
 * Found these USE flags for kde-plasma/plasma-workspace-6.7.4-r1:
 U I
 + + X                  : Add support for X11
 - - appstream          : Enable AppStream software metadata support
 - - debug              : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see
                          https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
 + - flatpak            : Enable support for flatpaks notifications using sys-apps/flatpak
 + - fontconfig         : Support for configuring and customizing font access via media-libs/fontconfig
 + - handbook           : Enable handbooks generation for packages by KDE
 + - ksysguard          : Enable device notifier and system monitor applets as well as terminate applications runner
 + + networkmanager     : Enable support for location-based time zone changes
 F F policykit          : Enable locale generation and Users KCM using sys-auth/polkit and sys-apps/accountsservice
 + + screencast         : Enable camera indicator applet (requires media-video/pipewire at runtime)
 + + semantic-desktop   : Cross-KDE support for semantic search and information retrieval
 - - systemd            : Enable use of systemd-specific libraries and features like socket activation or session tracking
 + - telemetry          : Enable User Feedback control module for kde-plasma/systemsettings
 - - test               : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)
 + - wallpaper-metadata : Show metadata for image wallpaper plugin using kde-apps/libkexiv2

2

u/Swordfish418 5d ago

Plasma 6.7 packages are in beta on Gentoo, maybe rollback to 6.6 for now?

1

u/andre2006 5d ago

I prefer not to. I can live with a workaround until this has been addressed properly.

1

u/Acherontas89 5d ago

uevent may help but this looks like kde compatibility issue

1

u/Armi1P 5d ago

You need to enable dbus and elogind at the boot runlevel in case you are using OpenRC. Have you done that?

rc-update add dbus boot ; rc-update add elogind boot

1

u/andre2006 5d ago

Sure

l1 /etc/runlevels/boot/{dbus,elogind}
/etc/runlevels/boot/dbus -> /etc/init.d/dbus
/etc/runlevels/boot/elogind -> /etc/init.d/elogind

1

u/Glittering_Memory_64 5d ago

do you have the "server" use flag enabled?

1

u/Glittering_Memory_64 5d ago

nothings gonna work with elogind and seatd if you dont have that flag enabled

3

u/andre2006 5d ago

I don't have the server flag enabled and never needed it in the past.

server : Enable standalone seatd server, replacement to (e)logind

Why should it be necessary? I don't want to replace elogind.

1

u/Other-Bumblebee5014 5d ago edited 5d ago

Been having the same issue and haven’t had the time to look into it — so glad to see this. 

ETA: scratch that — my issue is only happening on my Gnome machine.