SC on Wayland + Pipewire

[ape_din]

Qt apps use native Wayland by default, which gives plain window borders. Forcing the X11 backend makes GNOME draw the title bar and shadows:

QT_QPA_PLATFORM=xcb pw-jack scide

This runs the app through XWayland instead of native Wayland. Also notice the pw-jack which will make it run through pipewire. I hope SC will run natively on pipewire and wayland soon.

[jamshark70]

Hi,

Two issue reports that may be of interest:

• Wayland support: Support for pure-Wayland environments · Issue #4544 · supercollider/supercollider · GitHub – I’m not sure of the current status. AFAICS MouseX and MouseY in Wayland are hampered by a security requirement on the Wayland side, where mouse capture has to go through an application window and can’t be free like in X11. IDE Wayland issues, I don’t know.
• Pipewire: [RFC] Native PipeWire audio backend for scsynth (Linux) - experimental, looking for feedback · Issue #7499 · supercollider/supercollider · GitHub – An experimental Pipewire backend exists but hasn’t been pulled into the main line. GitHub - lucdoebereiner/supercollider at pipewire-backend-experiment · GitHub appears to be the newer version of this experimental backend. If you can build SC yourself, you could give it a try. I’m not sure what needs to happen to move it forward into the main SC repository.

hjh

[ape_din]

yes im aware of these, that why for the moment being running SC with the above command in a Wayland environment with pipewire is the only solution.

[bad-numbers]

I was about to ask a question about Linux and Qt and saw this question - it might be related.

In general Kubuntu 26.04 which I am using has tons of problems with user interface stuff which I believe is to do with Wayland - and sorry, I don’t even know what that is.

Quite a bit of GUI-related stuff in SuperCollider is heavily buggy for me. In particular, Buffer.loadDialog causes the interpreter to crash about 50% of the time. I see errors like this when using it:

ERROR: X Error of failed request:  BadValue (integer parameter out of range for operation)

Do you think this is related to the issue @ape_din raised? Is the thing he quoted a build parameter I can use when building from source?