Open isparks-tg opened 8 months ago
I seem to be getting a similar issue. I started getting it after the latest update of xvfb so I am suspecting it is an issue with xvfb.
Are you using the latest version in ubuntu too? Could you share your xvfb version (apt-cache policy xvfb | grep Installed
)?
$ apt-cache policy xvfb | grep Installed
Installed: 2:21.1.4-2ubuntu1.7~22.04.7
Well I can confirm that my issue or at least part of my issue was in the latest version of xvfb
on ubuntu.
I don't get any issue if I downgrade.
Since it is not available on the official repo anymore. I did:
wget -O /tmp/xvfb.deb http://launchpadlibrarian.net/702315346/xvfb_1.20.13-1ubuntu1~20.04.12_amd64.deb
apt install -y --allow-downgrades /tmp/xvfb.deb
But since I see you are on jammy, your last package is probably this instead:
http://launchpadlibrarian.net/702313861/xvfb_21.1.4-2ubuntu1.7~22.04.5_amd64.deb
If it works for you too it should confirm that we had the same issue and that there is something weird going on with the latest version of xvfb
.
Thanks for the pointers. Downgrading xvfb worked for visibility=0 so your diagnosis looks good but I still get same failure at 89 with visible=1 suggesting there is also an issue in xephyr? (Not that I need visibility=1 got my use case)
display.py backend selection:
if self._visible:
self._backend = "xephyr"
else:
self._backend = "xvfb"
I am not 100% sure this is a pyVirtualDisplay problem (could be chrome or underlying libraries) but the following code fails for me at a count of 90 when visible=0 and 89 when visible=1. If I don't create Display it will run to 99, so something about the virtual display seems to be involved (hence the bug report here).
with traceback:
Some information:
selenium==4.14.0 pyvirtualdisplay==3.0
I know the above are not an exact match, I get the same with chrome 121 and a matching chromedriver.