Skip to content
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

fatal IO error 11 (Resource temporarily unavailable) on X server ":0" #16

Open
AndreasBackx opened this issue Jul 14, 2017 · 7 comments

Comments

@AndreasBackx
Copy link

Whenever I use i3lock -f my monitors blur for about 1 second, then unblur, and then it seems like it's frozen for a while. I cannot use my mouse, I cannot enter my password to unlock it, nothing seems to be giving any feedback. After a while it "unfreezes" and throws the following error:

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 4920 requests (4920 known processed) with 0 events remaining.

The amount of requests (4920) differs sometimes. Note that using i3lock by itself works just fine.

Some information about my machine:

  • Arch Linux 4.11.9-1
  • GPU: Nvidia GTX 1070
  • GPU driver: Nvidia proprietary driver 318.22.
  • 2 monitors, 1 in landscape, 1 in portrait, both 1440p.

If there's anything else you'd like to know, I can provide that.

This was tested on the master branch and on the version that's on AUR as of writing this issue which is 2.9-1.

@anna328p
Copy link

Bump

@karulont
Copy link
Owner

I suggest to use the -o flag for now. This is available in the master branch. This does the blurring only once at the startup. The blurring still uses OpenGL and is fast.

@anna328p
Copy link

Still same problem.

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
      after 1121 requests (1121 known processed) with 0 events remaining.

@karulont
Copy link
Owner

There is also issue #6. To summarize the discussion there: Please try to use --nofork.

@faurehu
Copy link

faurehu commented Jan 14, 2018

--nofork works one or two times before it freezes on the blurred screenshot and I can only restore my system with a hard reboot.

@karulont
Copy link
Owner

I can only restore my system with a hard reboot.

Can't you use CTRL+ALT+FX to switch to a different tty and then issue sudo killall i3lock?

@faurehu
Copy link

faurehu commented Jan 15, 2018

@karulont yes I can, just learned about this thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants