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

cannot suspend #4

Closed
joelburget opened this Issue Oct 4, 2011 · 6 comments

Comments

Projects
None yet
3 participants
@joelburget
Owner

joelburget commented Oct 4, 2011

"Did a quick test with the newest version and pm-suspend/s2disk continues not to do anything after slimlock has launched. It happens right on the first try so I don't think the problem was the fact that you didn't unlock it afterwards but rather the lock itself."

"Notice that I still can't hibernate while using slimlock (using i3lock for the time being)"

@DanielBaulig

This comment has been minimized.

Show comment
Hide comment
@DanielBaulig

DanielBaulig Dec 21, 2011

I'm also having trouble suspending using slimlock. All pm-utils hooks seem to be processed successfully, but the actual suspending to sleep will hang and not finish correctly. I'm happy to provide additional feedback to help fixing this issue.

DanielBaulig commented Dec 21, 2011

I'm also having trouble suspending using slimlock. All pm-utils hooks seem to be processed successfully, but the actual suspending to sleep will hang and not finish correctly. I'm happy to provide additional feedback to help fixing this issue.

@joelburget

This comment has been minimized.

Show comment
Hide comment
@joelburget

joelburget Dec 22, 2011

Owner

I'm not really sure what the problem is with suspending since I don't use it myself. Here's what I would try:

  1. Disable tty locking by setting tty_lock 0 in /etc/slimlock.conf
  2. Disable dpms by setting dpms_standby_timeout 0
  3. Slimlock is owned by root, would that cause problems with suspending?

Hopefully this is helpful.

Owner

joelburget commented Dec 22, 2011

I'm not really sure what the problem is with suspending since I don't use it myself. Here's what I would try:

  1. Disable tty locking by setting tty_lock 0 in /etc/slimlock.conf
  2. Disable dpms by setting dpms_standby_timeout 0
  3. Slimlock is owned by root, would that cause problems with suspending?

Hopefully this is helpful.

@DRiKE

This comment has been minimized.

Show comment
Hide comment
@DRiKE

DRiKE Jan 16, 2012

I'm experiencing the same issue. Tried the three suggestions Joel made but that they did not fix the problem.

Installed from aur (using kernel 3.1.9-1-ARCH):
aur/slimlock-git 20110611-1

slimlock -v gives:
slimlock-0.10.1, © 2010 Joel Burget

Slimlock is called as can be seen in the pm-utils script on the Arch wiki: https://wiki.archlinux.org/index.php/Pm-utils#Locking_the_screen_saver_on_hibernate_or_suspend

DRiKE commented Jan 16, 2012

I'm experiencing the same issue. Tried the three suggestions Joel made but that they did not fix the problem.

Installed from aur (using kernel 3.1.9-1-ARCH):
aur/slimlock-git 20110611-1

slimlock -v gives:
slimlock-0.10.1, © 2010 Joel Burget

Slimlock is called as can be seen in the pm-utils script on the Arch wiki: https://wiki.archlinux.org/index.php/Pm-utils#Locking_the_screen_saver_on_hibernate_or_suspend

@joelburget

This comment has been minimized.

Show comment
Hide comment
@joelburget

joelburget Jan 20, 2012

Owner

@DRiKE I was having the same problem and setting tty_lock 0 worked for me. Would you mind confirming it doesn't work for you?

Owner

joelburget commented Jan 20, 2012

@DRiKE I was having the same problem and setting tty_lock 0 worked for me. Would you mind confirming it doesn't work for you?

@DRiKE

This comment has been minimized.

Show comment
Hide comment
@DRiKE

DRiKE Jan 20, 2012

It works when setting dpms_standby_timeout, dpms_off_timeout and tty_lock all to 0 !

DRiKE commented Jan 20, 2012

It works when setting dpms_standby_timeout, dpms_off_timeout and tty_lock all to 0 !

@joelburget

This comment has been minimized.

Show comment
Hide comment
@joelburget

joelburget Feb 7, 2012

Owner

Fixed with version 0.11 - tty_lock 0 is now the default.

Owner

joelburget commented Feb 7, 2012

Fixed with version 0.11 - tty_lock 0 is now the default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment