The problem you’re seeing is likely related to this bug. There seems to be a lot of overlap in issues with Wayland and slicers. I’m using the AppImage version of the Creality Print slicer, and it suffers the same issue. I have to use the following command line to launch it:
__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json WEBKIT_FORCE_COMPOSITING_MODE=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 WEBKIT_DISABLE_DMABUF_RENDERER=1 ~/.local/bin/CrealityPrint_Ubuntu2404-V6.2.1.3044-x86_64-Release.AppImage %F

That’s all on a single line. Ultimately, I created a .desktop file: ~/.local/share/applications/CrealityPrint.desktop
To run the slicer with that command in the EXEC line and everything works fine. Assuming the modified command to launch the slicer works for you, you should be able to create/modify the .desktop file to launch Orca Slicer similarly. Desktop File:

Categories=Utility;
Comment=
Exec= __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json WEBKIT_FORCE_COMPOSITING_MODE=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 WEBKIT_DISABLE_DMABUF_RENDERER=1 ~/.local/bin/CrealityPrint_Ubuntu2404-V6.2.1.3044-x86_64-Release.AppImage %F
Icon=CrealityPrint
MimeType=model/stl;application/vnd.ms-3mfdocument;application/prs.wavefront-obj;application/x-amf;
Name=CrealityPrint
NoDisplay=false
Path=
StartupNotify=true
Terminal=false
TerminalOptions=
Type=Application
X-KDE-SubstituteUID=false
X-KDE-Username=