OneTrainer won't launch on Linux

[genevera]

I get the following error output from OneTrainer along with an exit code of 134.

[xcb] Unknown sequence number while appending request
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
python3: ../../src/xcb_io.c:157: append_pending_request: Assertion `!xcb_xlib_unknown_seq_number' failed.

[geonom]

For me at least, I get the error with OneTrainer at startup - but also Kohya_ss has the same issue as soon as I hit the button to load a model from a folder (or most other buttons except for "refresh"):

-------- [xcb] Unknown sequence number while appending request [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. python3: ../../src/xcb_io.c:157: append_pending_request: Assertion !xcb_xlib_unknown_seq_number' failed.`

So the first button is okay and works. All other buttons lead to the crash:

Quickly installed Kohya_ss from git directly (without Stability Matrix) - that seems to work fine.

[noidedxyz]

I'm on arch and having the same issue. I have not tried to manually install it yet, though.

[noidedxyz]

Okay I have fixed this for myself. What I did was manually install OneTrainer with python3.10 (from the AUR) and then copying and pasting that installation into Stability's "packages" folder. I think the problem here is Stability assumes your native python installation is 3.10, I might be wrong but either way it works now.

[genevera]

I wound up installing it manually using a fresh and isolated virtual env and it was def kind of a pain. I think there are conflicting packages in the SM venv that cause this one to not work. Also the pytorch it wants to install is linked to cuda 11.8 so if you have 12.X that could be a problem too maybe? Speculating.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove the stale label or comment, else this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stale for 5 days with no activity.