Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#32096 - [kdebase-workspace] no shutdown/reboot in menu
Attached to Project:
Arch Linux
Opened by Aurora (LadyAurora) - Friday, 19 October 2012, 17:50 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 25 October 2012, 08:37 GMT
Opened by Aurora (LadyAurora) - Friday, 19 October 2012, 17:50 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 25 October 2012, 08:37 GMT
|
DetailsDescription:
With kdebase-workspace 4.9.2-5 and no consolekit running, there are no shutdown and reboot options in the KDE menu. I don't use KDM. Surely this shouldn't be the case, as consolekit is supposed to not be needed anymore, right? Mounting and other things that require privileges are working fine. Steps to reproduce: * install kdebase-workspace 4.9.2-5 * remove or mask consolekit * run KDE through xinit alone |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Thursday, 25 October 2012, 08:37 GMT
Reason for closing: Not a bug
Additional comments about closing: Fix your configuration
Thursday, 25 October 2012, 08:37 GMT
Reason for closing: Not a bug
Additional comments about closing: Fix your configuration
Please paste the output of `loginctl list-sessions`, and then for each session id run `loginctl show-session <id>`
`xinit` in `.zlogin`. "Alone" as in "no login manager".
> Please paste the output of `loginctl list-sessions`, and then for each session id run `loginctl show-session <id>`
See the attachments.
@ladyaurora: please follow
FS#32206if interested, this is a configuration issue not a bug.