Search found 3 matches
- 2019-07-08T06:08:32-07:00
- Forum: Users
- Topic: "import" blocking keyboard I/O
- Replies: 3
- Views: 9626
Re: "import" blocking keyboard I/O
...
Adding a patch to get exclusive access to the X server resolved the problem, see XGrabServer(). The errant behaviour started a few years ago suggesting a recent change in the X server behaviour triggered the need for exclusive access to the X server as the capture rectangle is drawn ...
- 2019-07-03T16:52:13-07:00
- Forum: Users
- Topic: "import" blocking keyboard I/O
- Replies: 3
- Views: 9626
Re: "import" blocking keyboard I/O
Thanks for the reply!
Adding a patch to get exclusive access to the X server resolved the problem, see XGrabServer(). The errant behaviour started a few years ago suggesting a recent change in the X server behaviour triggered the need for exclusive access to the X server as the capture rectangle ...
Adding a patch to get exclusive access to the X server resolved the problem, see XGrabServer(). The errant behaviour started a few years ago suggesting a recent change in the X server behaviour triggered the need for exclusive access to the X server as the capture rectangle ...
- 2019-07-03T06:03:05-07:00
- Forum: Users
- Topic: "import" blocking keyboard I/O
- Replies: 3
- Views: 9626
"import" blocking keyboard I/O
Hi all.
For the last 15+ years, when I did a screenshot, I'd type
$ import foo.png
... and then switch virtual desktops (I have this config'd on fluxbox to be Ctrl-Alt arrow), drag a rectangle across the area I wanted to capture, and that would be that.
After recently upgrading (Slackware), this ...
For the last 15+ years, when I did a screenshot, I'd type
$ import foo.png
... and then switch virtual desktops (I have this config'd on fluxbox to be Ctrl-Alt arrow), drag a rectangle across the area I wanted to capture, and that would be that.
After recently upgrading (Slackware), this ...