So out of the blue yesterday (no updates, nothing new) I am no longer able to log out into the sleep function. Doing so brings a loop which comes right back to the log in screen. Anyone else have this odd problem?
Mod Edit: Moved the post to below the arrow in the template
No offence but this is one weird post. Your post has no useful information while also posting a link to how to post? Are you an AI?
@rehunn
What exactly are you trying to say or ask? Your post ist pretty confusing.
It seems the post content was added prior to a standard template (which Iâve never seen at my end) instead of below the arrow.
However, the How to request support link is well worth checking out, if you havenât done so already.
It will help people to provide assistance if you provide some system details, e.g.:
inxi -zv8
â Place 3 backticks ``` on empty lines above and below your pasted output
~or~
â highlight the pasted text and click the </> button at the top of the reply window.
Cheers! 
I am not sure what is confusing here. When exiting a session instead of a full shutdown I log out and use the sleep function. I have fully updated system so
doesnât seem to be an update issue. System goes to dark screen as would be
normal for âsleepâ but instead loops back to the log in screen. Iâm not sure how to be more concise than that and Iâm certainly not an AI.
You had the template mixed up with your actual post, this was a little confusing.
See 
I fixed it for you.
Not sure how my post is the solutionâŚI only fixed your first post. Sorry for any confusion.
Iâll unmark it, as I havenât solved your actual problem. For that weâll likely need some more information.
Checking the logs after an unsuccessful sleep may help.
journalctl
But we dont know anything about your system ⌠what desktop, what kernel, etc âŚ
So please start by sharing the output from
inxi -Farz
Please use the code button </> for the formatted text and/or refer to this general guide for that and other hints:
This is new - I thought you could either log out, OR use sleep. You were using Plasma in a previous post, if thatâs the case then you should be presented with menu options for:
The term âsleepâ is used for âsystemctl suspendâ and you could try this in your terminal (to see if any errors occur).
Logging out would certainly take you straight to the log-in screen⌠we only use this to end a user session - then need to shutdown or suspend afterward from the log-in screen.
You cannot âlog out into the sleep functionâ.
So, as requested, post your Journalctl and inxi outputs.
You can format them like this:
This text will be hidden
[details="inxi"]
~~~
pasted output
~~~
[/details]
[details="Journalctl"]
~~~
pasted output
~~~
[/details]Your post overall was confusing because it contained too many things which made it hard to read.
Your wording, I imagine;
that, along with a lack of context.
You havenât given any system information that would indicate which Manjaro edition youâre using, for example. This makes it difficult for others to understand what you actually mean. No context.
Normally, one doesnât:
You clearly mean something else, but it hasnât been defined well enough by you for others to fully comprehend.
This is on you.
My best guess (from your original description) is that you clicked a âLogoutâ icon in your menu, or somewhere, and the resulting Logout screen (or dialog) doesnât contain a separate âSleepâ icon.
But, this isnât what youâve told anyone; thatâs not what âlog out and use the sleep functionâ suggests; especially without context.
What comes to mind, however, is that (at least in Plasma) the shutdown/restart/logout screen options (several months ago) were reduced to only two icons per screen (one of the options mentioned, plus a cancel icon), depending on context).
Before that change sleep might have been included as an extra icon (totaling three icons per screen), but frankly, I donât remember.
As I say, if youâre using Plasma, this might have been what you were trying to communicate; or it could be something else entirely.
Until you provide the requested System Information we canât possibly know; and you clearly ignored the request for that information (from a Moderator in post #3).
So, you tell us, how are we to help you if you donât put some thought and effort into your Support request?
As a Member of this forum since 2020, you should know better.
Your second post at least contains a little more information, and we might guess that your issue might be one of those already listed in recent Update Announcements under Known Issues and Solutions.
If you havenât already, it may be worth reading through those items to find any that seem to fit your problem.
Please help us to help you.
At minimum, post your System Information, as requested.
Please take some time to familiarise yourself with Forum requirements; in particular, the many ways to use the forum to your benefit:
Required Reading:
Resources:
Update Announcements:
The Update Announcements contain update related information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
System Information:
Output of the following command (formatted according to forum requirements) may be useful for those wishing to help:
inxi --admin --verbosity=8 --filter --no-host --width
Be prepared to provide more information and outputs from other commands when asked.
Regards.
Plus, not all forum Members are native English speakers.
This is something else for the OP to consider when composing a Support request.
Quite the conundrum, really.
Can you run this command in your terminal?
/usr/lib/ksmserver-logout-greeter --windowed
Why? No one should ever blindly run commands if they donât know what they do.
⌠if the command even runs, the DE is probably Plasma/KDE âŚ
@deroberts1 why did you recommend to run it?
/usr/lib/ksmserver-logout-greeter --windowed
will produce the regular full âsleep,hibernate,logout,restart,shutdownâ dialog on plasma.
Should be the same as the dbus call
qdbus6 org.kde.LogoutPrompt /LogoutPrompt promptAll
( ksmserver was slotted for removal at some point ⌠so far its still around 
)
Perhaps it was provided as some sort of ⌠assumed example of what the original author of this thread was referring to? That doesnt make it make much more sense though ⌠as we still do not know the DE of author, nor the actual intention behind their descriptions.
I actually knew that.
But why was he not explaining what the command was supposed to be going to achieve �
(rhetorical question)
It is the standard log out greeter screen. Trying to determine if that is what he is referring to.
OP appears to have stated that they cannot suspend the system (sleep fails and computer shows login screen again).
CSCS requests clarification, plus inxiâŚ
No further input or comment from OP.
When people fail to respond to a request for further information, the thread should be abandoned and left to close - nothing to be gained here.
Regarding this:
While we can obviously not offer anything definitive about this, without more actionable information from the OP (such as the inxi output requested several times), I will mention that I have experienced this myself on occasion.
If I impatiently perform an update from within the GUI (without having checked the list of packages to be updated), and then continue using the machine for a time, sometimes this happens; along with an inability to Logout, Restart or Shutdown via the (Plasma) GUI.
Now, I am not suggesting that this is either the cause of the OPâs issue, nor a solution to it. However, it is an opportunity to offer the following consideration for all that will entertain it:
In the case of an unresponsive shutdown/logout/end-session from the Plasma GUI I would normally perform one of these successfully
Not all that common mind you.
But sometimes the case with changes to plasma.
Something like systemctl reboot would similarly work, but the above are more graceful for ending the plasma session.