-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Freezes completely after suspend #292
Comments
Thanks for your report, could you please add information's about OS/Distro, Versions (like As Betterlockscreen is just a Bash-Script wrapping around i3lock-color, I'm not sure if this could be an i3lock-color issue (if it's not caused by invalid/wrong config e.g.). Could you maybe test switching to i3lock-color without additional config and test if it still occurs? |
Oh, sorry I forgot to add my system information... Arch Linux
By the content of my systemd service you mean the service file? I'll post the logs next time that happens (It doesn't happen every time) Thanks! |
Thanks for the additional information's.
Yes :)
Sounds good 👍🏻 |
/usr/lib/systemd/system/betterlockscreen@.service (the default systemd service):
It happened again, but I'm not sure what logs should I look at... What logs should I post? |
You can find a list of logs per boot with |
It happned again, here are the logs:
|
|
I use lightdm, will putting it in my .profile work as well? |
It should, according to the wiki here. |
Thanks! |
So the logs meaning the dbus solution worked? You can print out DBUS_SESSION_BUS_ADDRESS to make sure, plus maybe you should restart to have a fresh test. |
@AmitGolden I may have misguided you in the wrong direction with the above solution, sorry. After rechecking the Archwiki for xinit, I think the problem is my .xinitrc file not including some of the contents in the default config file, as pointed out by the wiki:
I updated my .xinitrc and the issue got eliminated this time. To be specific, the key content to add should be the following: if [ -d /etc/X11/xinit/xinitrc.d ] ; then
for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
[ -x "$f" ] && . "$f"
done
unset f
fi Which executes the scripts under #!/bin/sh
systemctl --user import-environment DISPLAY XAUTHORITY
if command -v dbus-update-activation-environment >/dev/null 2>&1; then
dbus-update-activation-environment DISPLAY XAUTHORITY
fi For you the .profile config should work but also check .xinitrc in case things work differently in LightDM. Hope this can help you. |
Thanks a lot! |
Thanks for your support and contributions to this issue :) I will leave this open until I've finished the new docs and added this case to a troubleshooting section. Or do you think there is something else, Betterlockscreen should/can improve on this except documentation? |
Welcome. Let me know if that works out for you :) |
You're welcome. The cause of this issue is actually an Arch one other than Betterlockscreen itself, so I suppose mentioning in the doc should suffice. |
Just out of curiosity, what caused the problem? |
Well, as to quote from Archwiki:
Without proper configuration, the dbus daemon may not get fully activated. In this case, In addition,
|
It happened again.
|
From the provided logs I can't see that this is related to Betterlockscreen? (Logs show warnings about corrupt data issues in chromium/brave) |
I agree with @SebTM since the logs are not related. Maybe you should refer it to the Arch Community? |
I've posted this problem on the Arch Forums |
I'm going to close this issue now as it seems resolved as far as what could be done here :) |
Hi,
I've enabled the systemd service.
Sometimes after my pc wakes up after suspend, betterlockscreen is active, but I can't type ANYTHING.
I can't even change to a different tty.
The only thing that I can do is either force reboot with the power button or use the magik SysRq.
One strange thing is that sometimes, using Alt + SysRq + R will unfreeze the pc and I could type again.
What can I do to fix this?
The text was updated successfully, but these errors were encountered: