-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
XPRA Disable webp #23
Comments
Would be better to post this as an issue on that repository than ama section. |
Thx - at this point, I found workarounds for all my XPRA issues.
Have a great day,
…On Wed, Oct 5, 2022 at 11:35 AM Ahsen Baig ***@***.***> wrote:
Would be better to post this as an issue on that repository than ama
section.
🐛 Bugs & feature requests should be opened on the relevant issue tracker.
—
Reply to this email directly, view it on GitHub
<#23 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKT5HEKFNAUEEKIWJPBLDELWBWU4TANCNFSM5QWOZDIA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @posquit0 - found your XPRA config @ https://github.com/posquit0/dotfiles/blob/master/X/.xpra/xpra.conf which has been helpful. Thank you.
I am trying to disable the webp/pillow errors when I attach to an xpra display as I do not want to decode using Pillow. I found XPRA_WEBP_PILLOW option in the below link. I tried to add it to the xpra.conf file but am not sure of the syntax or even if this is the correct file/option. In xpra.conf, I used XPRA_WEBP_PILLOW=0. I also tried XPRA_USE_PIL. I also tried to set these as environmental variables (no joy). Would prefer they be in a config file if possible.
https://xpra.org/trac/wiki/Usage/EnvironmentOptions
I get the error: "UserWarning: image file could not be identified because WEBP support not installed". Just a note, I am in an environment where I cannot install WEBP.
Any help is appreciated.
The text was updated successfully, but these errors were encountered: