Error parsing JSON: X get_image failed: error 8 (73, 0, 967)

[Andy1996247]

[Self-Operating Computer]
Hello, I can help you with anything. What would you like done?
[User]
google the word HI
Error parsing JSON: X get_image failed: error 8 (73, 0, 967)
[Self-Operating Computer][Error] something went wrong :(
[Self-Operating Computer][Error] AI response
Failed take action after looking at the screenshot

what could be the problem?

[michaelhhogue]

What operating system are you on? Also, do you have multiple monitors?

[Andy1996247]

What operating system are you on? Also, do you have multiple monitors?

Ubuntu 22. And yes I run 2 monitors.

[michaelhhogue]

There are some known issues with multi-monitor setups. #57 proposes a change that uses only the active monitor on Linux.

[joshbickett]

#57 was merged, but not sure if it ever fixed the issue. Let us know if you're still having the issue which in that case a new PR would be great

[michaelhhogue]

@joshbickett @Andy1996247 #57 didn't fix this issue. The active monitor needs to be selected in the screenshot when there are multiple monitors connected. Will look into this tonight.

[SebastianHausler]

#57 was merged, but not sure if it ever fixed the issue. Let us know if you're still having the issue which in that case a new PR would be great

Same issue for me. Fresh ubuntu-22.04.3-desktop-amd64.iso VM and only one monitor, but I'm using a 4k monitor. Not sure if this is a problem. Used pip install self-operating-computer to install.

[ph47s74x]

#57 was merged, but not sure if it ever fixed the issue. Let us know if you're still having the issue which in that case a new PR would be great

Same issue for me. Fresh ubuntu-22.04.3-desktop-amd64.iso VM and only one monitor, but I'm using a 4k monitor. Not sure if this is a problem. Used pip install self-operating-computer to install.

I am using Ubuntu 20.04.2 and had a similar issue.

I used this issues responses to solve it;

issue: #80

This seems to be related to Pillow and ImageGrab on machines (possibly just virtual machines) that have Wayland enabled.

Here is the fix that worked for me on Ubuntu 22.04.3 LTS in a virtualbox.

https://stackoverflow.com/questions/75752576/pillow-imagegrab-grab-not-working-on-a-virtual-machine

# Open this file
/etc/gdm3/custom.conf

# Set this value to disable Wayland
WaylandEnable=false

then

# Restart gdm3
sudo systemctl restart gdm3

[Andy1996247]

#57 was merged, but not sure if it ever fixed the issue. Let us know if you're still having the issue which in that case a new PR would be great

Same issue for me. Fresh ubuntu-22.04.3-desktop-amd64.iso VM and only one monitor, but I'm using a 4k monitor. Not sure if this is a problem. Used pip install self-operating-computer to install.

I am using Ubuntu 20.04.2 and had a similar issue.

I used this issues responses to solve it;

issue: #80

This seems to be related to Pillow and ImageGrab on machines (possibly just virtual machines) that have Wayland enabled.
Here is the fix that worked for me on Ubuntu 22.04.3 LTS in a virtualbox.
https://stackoverflow.com/questions/75752576/pillow-imagegrab-grab-not-working-on-a-virtual-machine

# Open this file
/etc/gdm3/custom.conf

# Set this value to disable Wayland
WaylandEnable=false

then

# Restart gdm3
sudo systemctl restart gdm3

thankyou this worked

[joshbickett]

@michaelhhogue since #80 is a fix for this issue. I wonder if we could incorporate that fix into the project some how to avoid these issues in the future. Let me know if you have thoughts

[michaelhhogue]

@joshbickett It probably would be best to add this to the README or in a separate file that a link could point to. Even MSS, which I've looked into as a better screenshot solution, would still produce this error. From what I've found, it would take a lot of weird dependencies to actually add support for Wayland to resolve this issue automatically.

If no one else opens one, I'll probably do a PR for this after I'm done working on LLaVA support.

[joshbickett]

Ok sounds good. I wonder if it makes sense to create a linux-readme.md or something like that which we can link to from the readme.md for a more in-depth install? Not sure what the standard is in these situations