Hey guys. I’m new to Linux. I’m trying to make the transition from Windows to Linux and decided to go with Manjaro Gnome for my distribution. So far, I’m loving it. After lots of google and reddit I’ve gotten most everything up and running. This is primarily a gaming machine and I was even able to get most of the games that I’m currently playing up and running! It’s been great so far! However, there is one problem that no matter how much I search, I can not find a solution to it. That is that I can’t get my system to hibernate. If I turn on the auto suspend feature it will lock up my system every single time. Only fix is to hold the power button and force it to restart.
I have 32 gigabytes of RAM and I created a swap partition that is 64 gigabytes. I followed a guide that I found that had me edit grub to point the kernel to the swap partition and had me edit initramfs file to add the resume hook and it’s still not working.
I’m running a Ryzen 5600x on a Asus B550i motherboard. Latest bios on the motherboard and I’m running kernel 5.13. Also using an EVGA RTX 3080 graphics card. If anyone has any ideas I would greatly appreciate it because I have no clue where to go from here. Thank you!
Please read this: How to provide good information
and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.
There’s the info I get from running that command in terminal. I switched to the 5.10 kernel but still having issues with system freezing. Any ideas what to do next? Thank you.
-- Journal begins at Tue 2021-07-27 13:36:37 CDT, ends at Mon 2021-08-09 08:34:06 CDT. --
Aug 06 16:51:39 adam-systemproductname kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Aug 06 16:51:39 adam-systemproductname kernel:
Aug 06 16:51:39 adam-systemproductname kernel: kvm: disabled by bios
Aug 06 16:51:39 adam-systemproductname kernel: kvm: disabled by bios
Aug 06 16:51:39 adam-systemproductname kernel: kvm: disabled by bios
Aug 06 16:51:39 adam-systemproductname kernel: kvm: disabled by bios
Aug 06 16:51:39 adam-systemproductname kernel: kvm: disabled by bios
Aug 06 16:51:39 adam-systemproductname kernel: kvm: disabled by bios
Aug 06 16:51:39 adam-systemproductname gnome-session-binary[676]: Unrecoverable failure in required component org.gnome.Shell.desktop
Aug 06 16:51:39 adam-systemproductname gdm-launch-environment][603]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 06 16:51:40 adam-systemproductname kernel: kvm: disabled by bios
Aug 06 16:51:40 adam-systemproductname kernel: kvm: disabled by bios
Aug 06 16:51:40 adam-systemproductname kernel: kvm: disabled by bios
Aug 06 16:51:40 adam-systemproductname kernel: kvm: disabled by bios
Aug 06 16:51:41 adam-systemproductname systemd-udevd[369]: could not find module by name='xow_blacklist'
Aug 06 16:51:47 adam-systemproductname gdm-password][1417]: gkr-pam: unable to locate daemon control file
Aug 06 16:51:49 adam-systemproductname gnome-session-binary[1112]: GLib-CRITICAL: g_hash_table_foreach_remove_or_steal: assertion 'version == hash_table->version' failed
Aug 06 16:51:50 adam-systemproductname gdm-launch-environment][737]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 06 17:23:09 adam-systemproductname gdm[539]: GLib: Source ID 115 was not found when attempting to remove it
Aug 06 17:25:02 adam-systemproductname gdm[539]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.10 was not provided by any .service files
This is what I got from running that command. It didn’t completely lock up to where I had to use the REISUB command. But I did have to press the power button to wake it up. Keyboard and mouse wouldn’t do anything at all.
That seems to be a Gnome issue and as I’m on KDE, I can’t do much more for you except:
Reclassify your support request to the Gnome category and adding the Gnome tag (Done!)
Asking you to create a new user (E.G. aj53108_2), log in there and see whether it happens there too! If it doesn’t, I might have a possible workaround for you.
So you have an issue in your user profile and finding out which exact setting you changed is going to take weeks if not months, therefore, we’re going to do the following:
Verify that the new user has access to the same groups as your old one by executing groups and comparing the output of both users.
groups twitty
groups twitty2
(Where obviously, twitty is your old user and twitty2 is your new one.)
E.G. if twitty is a member of operator and twitty2 isn’t, execute:
usermod --append --groups operator twitty2
Copy all data files from your old profile into your new one
If that worked and you had no errors, remove the documents from your old user:
rm --recursive /home/twitty/Documents/*
repeat for:
Pictures
Videos
Music
.thunderbird
.mozilla/firefox/
Templates, and everything else that is important to you.
Linux games like Battle of Wesnoth have their game data stored under ~/.local/share/ E.G. ~/.local/share/wesnoth/
After everything has been copied over, disable the old user so you cannot accidentally log on to it any more:
usermod --lock twitty
If you would have theming going on, don’t do everything in one day but do this at the rate of 1 application / theme / whatever per day and if the same issue crops up again, roll back your last change and thus you’ve now pinpointed the exact setting that made your old user misbehave.
in 1 month delete the entire home directory of your old user, but don’t delete the user itself so that in 6 months time files still owned by that user will still show up under its username.
If you ever migrate to a new machine, just don’t migrate the old user: only the new one.
From now on, start making backups so you can roll back and never have to do this again:
As I haven’t heard anything after 12 hours, I’ve marked this answer as the solution to your question as it is by far the best answer you’ll get.
However, if you disagree with my choice, please feel free to take any other answer as the solution to your question or even remove the solution altogether: You are in control! (If you disagree with my choice, just send me a personal message and explain why I shouldn’t have done this or or if you agree)
P.S. In the future, please don’t forget to come back and click the 3 dots below the answer to mark a solution like this below the answer that helped you most:
so that the next person that has the exact same problem you just had will benefit from your post as well as your question will now be in the “solved” status.