suspend option disappeared and greyed in lock logout settings plasmoid

[pier_andreit]

Before I had lock/logout plasmoid on my desktop with three options, lock, stop and suspend, after the last update the suspend option disappeared in the plasmoid, and, if I go to the settings dialog the suspend option result greyed, also hibernate result greyed.
is there a way to have back the suspend option??
manythanks, ciao, pier :-)

my system is running plasma 5.6.2:
PC=Dell latitude E6510, RAM=8Gb, GPU=GT218 NVS 3100M, CPU=i7 Q 720 @ 1.60GHz

upgraded 13.2 to leap 42.1, using wolfi repos. I'm running KDE 4.14.18 and plasma 5.6.2, KDE frameworks 5.21.0, KDE applications 16.03.90, Kernel 4.1.15-8-default

[wolfi323]

Before I had lock/logout plasmoid on my desktop with three options, lock, stop and suspend, after the last update the suspend option disappeared in the plasmoid, and, if I go to the settings dialog the suspend option result greyed, also hibernate result greyed.
is there a way to have back the suspend option??

It should be available.

That option is only hidden/disabled if the user is not allowed to suspend/hibernate.
So that's where you should start looking for the problem...

Does "systemctl suspend" and/or "systemctl hibernate" work?
(run as logged in user inside the graphical session, in particular *not* as root)

[pier_andreit]

It should be available.

That option is only hidden/disabled if the user is not allowed to suspend/hibernate.
So that's where you should start looking for the problem...

Does "systemctl suspend" and/or "systemctl hibernate" work?
(run as logged in user inside the graphical session, in particular *not* as root)

I was trying your solutions and plasma hangs, login and logout and now it works
manythanks :-)

[wolfi323]

I was trying your solutions and plasma hangs, login and logout and now it works

Hm, sounds like the user session didn't correctly get registered on first login, but it did on the second login.

Are you using Autologin?
Try to disable it and it should work on first login.

If that's the case, some services (logind in particular) don't seem to be ready at the time of Autologin. There was a problem with this on some systems if autofs was enabled as well. Are you using that?

There also was a problem with the polkit shipped in Leap 42.1, that caused similar problems, but that should be fixed since months.
You do have all updates installed, right?

[pier_andreit]

Hm, sounds like the user session didn't correctly get registered on first login, but it did on the second login.

Are you using Autologin?
Try to disable it and it should work on first login.

no, I use login with password

If that's the case, some services (logind in particular) don't seem to be ready at the time of Autologin. There was a problem with this on some systems if autofs was enabled as well. Are you using that?

I don't know what autofs is, I can check if you can tell me where :-)

There also was a problem with the polkit shipped in Leap 42.1, that caused similar problems, but that should be fixed since months.
You do have all updates installed, right?

yes, all updates installed, and this happened after the reboot after the last update, may be it isn't related but was so evident that I immediately suspected the update :-)

[wolfi323]

no, I use login with password


I don't know what autofs is, I can check if you can tell me where :-)

If you don't know what it is, you don't use it.
It's not activated automatically...

Also, this only caused problems with Autologin as mentioned.

But if you want to check:

systemctl status autofs

[pier_andreit]

If you don't know what it is, you don't use it.
It's not activated automatically...

Also, this only caused problems with Autologin as mentioned.

But if you want to check:

systemctl status autofs

manythanx, ...disabled and inactive

pla@suseST-pla:~> systemctl status autofs
autofs.service - Automounts filesystems on demand
   Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)
   Active: inactive (dead)
     Docs: man:automount(8)
           man:autofs(5)

pla@suseST-pla:~>