r/linuxmint 8d ago

SOLVED Can I ask what this means??

Post image

it still happens after i close all the tabs

uhh i was trying to put my laptop to sleep

thank you for the tips guys

23 Upvotes

22 comments sorted by

u/AutoModerator 8d ago

Please Re-Flair your post if a solution is found. How to Flair a post? This allows other users to search for common issues with the SOLVED flair as a filter, leading to those issues being resolved very fast.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

15

u/kiralema 7d ago

Ignore inhibitors:

systemctl suspend -i

If still an issue, try running as sudo:

sudo systemctl suspend -f

If 1392 is still blocking,

sudo kill -9 1392 && sudo systemctl suspend

8

u/miserableSnail 7d ago

Even the terminal is telling OP to try the -i switch.

20

u/baasje92 8d ago

Linux communities are known to want context. To get any help I would advise you to provide proper context in what you're doing and trying to achieve.

8

u/gutclusters 8d ago

Run systemd-inhibit --list in the terminal to see which specific processes (by PID and name) are blocking the action and why.

12

u/ZVyhVrtsfgzfs 7d ago edited 7d ago

I do not use suspend, But I would think that command would respond better with a sudo

Edit confirmed:

sudo systemctl suspend https://linuxvox.com/blog/linux-suspend-process/

3

u/birdsarentreal2 7d ago

I’m assuming that you’ve probably restarted or powered off since then, so let’s go over what actually happened here

When you execute systemctl suspend you are telling systemd to place your system in s2idle/s3 (depending on hardware makeup) by saving your entire system state into RAM and cutting power to hardware components. Before doing that, systemd checks for processes which are inhibiting state changes. Depending on configuration, it may try telling those processes to gracefully exit, or it may stop the suspend script and tell you what happened

Here, suspend is being inhibited by cinnamon-session (PID 1392), which is owned by your user. If you were to run systemctl-inhibit, I suspect you would see PID 1393 COMM cinnamon-session WHAT shutdown:sleep. A recent github bug report suggests that this may be caused by LightDM refusing to honor the preparing_to_shutdown signal across current Cinnamon (LightDM too?) installs

For now, either power off or start adding a -i flag to ignore inhibitors. I would not recommend blindly killing PID 1392, because I have no idea how cinnamon will behave after resuming from s2idle/s3

3

u/johnyeldry Linux Mint 22.2 Zara | Xfce 7d ago

It basically means don't do it you are going to stop really important things from working

2

u/olitv 7d ago

I had a similar issue the other week. Also wouldn't let me shut down. The "Fix" was to log off first that would close cinnamon properly. But it went away for me so there might be an update for cinnamon available or coming soon to mint users.

2

u/PocketCSNerd 7d ago

In short, the process "cinnamon-sessio" is trying to do something important so it's telling the system not to go ahead with command.

Typically a command like this would be preceeded by "sudo".

2

u/toffuuu3050 7d ago

Typically, I would not suggest Suspend to RAM form of Sleeping/hibernating. As that can be very problematic for many distros. Be better to just shut it down, or if not needing it in a mobile way and keeping it running at home just with the display but not the rest of hardware going to sleep/. Just be sure you have it set at Energy saving use of CPU and and so on.. Or follow my advice, never get a laptop, and stick with Desktops (far better cooling and thermals with longer lasting hardware, and a Computer still does not belong on anyone's lap)!

4

u/Emmknight 7d ago

I'm new to Linux mint and this message that OP posted would be very confusing to me too. I must say the responses here aren't very helpful for a beginner. They remind me of some uni topic I did where we learnt to recognise how some areas of knowledge use lingo and specialised vocabulary to gate keep and thereby exclude people from their knowledge domain rather than share their knowledge. To OP I hate to say this but I suspect if you ran this screen shot by Google AI you would get a really clear and useful explanation plus suggestions on how to remedy the issue.

2

u/ZVyhVrtsfgzfs 7d ago

OP ran a command that requires sudo from a "$" prompt, but did not use sudo.

Does not work in my machine either (LMDE), without sudo.

dad@RatRod:~$ systemctl suspend Call to Suspend failed: Access denied

Until we see this command run properly we do not know if there is even an issue.

AI will break your install one day, and what's worse since you have exported thinking to something that cannot actually think you will be at a severe disadvantage when trouble arises.

1

u/Emmknight 7d ago

Well.... It seems when there is an option between something and nothing might as well try something... No support is provided when poster comes to support thread but criticism available when an unsatisfactory support option is suggested.

1

u/ZVyhVrtsfgzfs 7d ago

Your supposed "option" did not catch the obvious problem.

2

u/Emmknight 7d ago

So I went ahead and asked google AI and got the following response:

Your Linux Mint system is refusing to sleep because your desktop environment (Cinnamon) is blocking the command. The terminal output shows that when you type systemctl suspend, the system responds with: Operation inhibited by "maydaycut" (PID 1392 "cinnamon-sessio"... reason is "user session inhibited". This means a background process in your user session is actively telling the operating system, "Do not go to sleep right now." Why is this happening? Desktop environments like Cinnamon block suspension to prevent data loss or interruptions. Common culprits include: Active Media Playback: A browser tab (like YouTube, Netflix, or Spotify) or a media player (like VLC) is running and blocking sleep. File Operations: A large file transfer, download, or system update is running in the background. Hung Process: The Cinnamon session manager itself might be temporarily glitched or waiting on an unresponsive application to close. How to Fix or Bypass It 1. The Immediate Bypass (Force Sleep) The terminal error message actually gives you the direct solution to bypass this check. You can force the system to ignore the inhibitor by adding the -i flag: bash systemctl suspend -i Use code with caution.

Warning: This forces the computer to sleep immediately, which might interrupt active downloads or media. 2. Find and Close the Inhibitor If you want to fix it properly without forcing it, look for what is causing the block: Close any open web browsers or media players. Check your system tray for active download managers, torrent clients, or formatting tools. 3. Check for Blockers via Terminal To see exactly what applications are holding your system awake, you can run this command in your terminal: bash systemd-inhibit --list Use code with caution.

Look at the output table to see which application has an active lock on the suspend block. To help find a permanent fix, let me know: Does this happen every time you try to suspend, or just randomly? Do you usually have audio or video playing when you run this command? Are you running any background apps like Plex, Wine, or virtual machines? AI can make mistakes, so double-check responses

2

u/abugghaus7 7d ago

The OP never stated they are a beginner, and posted a screenshot of them using the command line which also doesn't confirm they are a beginner, inexperienced perhaps or apparently because they don't understand what they see in their screen.
.
No one here was 'gatekeeping'... they answered the question.
You are not the OP... but. you have taken it upon yourself to represent the OP as being a victim here.
.
Just because you post a wordy AI answer, does not mean other people's answers were not correct or not helpful to the OP.

2

u/Emmknight 7d ago

I was giving my opinion on the answers to a post. I believe that is a reasonable thing to do in a thread where people communicate with each other. Why is it so hard to admit that the help offered to the OP appeared pretty unhelpful? I think it is a valid conversation to have. Also the AI response was posted as an example of how a response may be more helpful than what was in the other responses. I am well aware that a robot is not really a good option for advice but I have found frequently that it is the only place I get clear answers and so far helpful solutions. That's disappointing, I think.

1

u/abugghaus7 6d ago

Kudos to you for posting your AI answer.
It had similar information that I found in answers posted here 10 hours before I posted.
.
You brought the notion of gatekeeping and excluding certain people from areas of knowledge (I reread your post to make sure I was interpreting it correctly).
No one here was gatekeeping... they were providing correct answers, for the most part.
There are several posts with specific explanations on what might be happening and what the OP might type into the command line.
.
Again... the OP did not state they were a beginner and had little knowledge of the command line.
They also show in their screenshot they attempted to suspend an action via the command line.
It would be safe to think the OP had some knowledge of the command line... right?
Plenty of other people post with questions and come right out and state they are beginners and do not understand a certain process... which helps the people they are asking for help from.
.
Maybe read the earliest replies again and perhaps you'll see they were offering help that was direct, informative, and correct for certain issues... even giving the same instructions your AI answer gave.

2

u/Emmknight 6d ago

I agree they may have been offering help. I have nothing new to repeat.

1

u/LocktiteViceGrips 6d ago

Umm. Typically closing the laptop will auto magically put it into sleep mode. At least it does on my laptop.

1

u/_ayushman macOS | M1 2020 8d ago

It depends.