Apps crashing / malfunctioning and weird Qt/wayland/xcb behaviour

[MattiBRNDMR]

POP-Os,Intel Laptop CPU, Nvidia gtx 1070 with nvidia 555 driver, popdev master, latest cosmic-comp version in popdev master

Putting my 3d software packages to the test on cosmic again, I've encountered some issues related to (what I believe) running qt based apps on cosmic. I hope this is the right place for that.

My point of reference: on pop-gnome-wayland everything works just fine.

I created to aliases in order to run the particular application:
alias run_houdini="__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms QT_QPA_PLATFORM=xcb QT_QPA_PLATFORM=xcb hindie"

alias run_nuke="__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms QT_QPA_PLATFORM=xcb /home/matti/programs/Nuke15.1v2/Nuke15.1 --nukex --nc"

Comparing executing the apps on pop-gnome-wayland vs cosmic:

1. On pop-gnome-wayland : run_houdini -> runs as expected

2. On pop-gnome-wayland: run_nuke -> runs as expected but gives a warning in the terminal on startup:
   Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.

3. On cosmic: run_houdini -> starts as expected, but opening certain windows/interface elements crash the app

4. On cosmic: run_houdini with QT_QPA_PLATFORM=wayland -> crashes (this does work on pop-gnome-wayland as well)
   Qt Error: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), linuxfb (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), minimal (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), minimalegl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), offscreen (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), vnc (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-egl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-xcomposite-egl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-xcomposite-glx (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), xcb (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, webgl, xcb.

5. On cosmic: run_nuke -> starts but has visual glitches (like ui elements overlapping in wrong order) and a bit crashy sometimes

6. On cosmic: run_nuke with QT_QPA_PLATFORM=wayland -> crashes (does as well on pop-gnome-wayland, so might be due to the application vendor)
   qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), linuxfb (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), minimal (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), minimalegl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), offscreen (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), vnc (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-egl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-xcomposite-egl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-xcomposite-glx (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), xcb (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), linuxfb, minimal, offscreen, vnc, xcb, eglfs, minimalegl, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.

7. on cosmic: run_nuke without any Qt related variables set -> starts but has visual glitches (like ui elements overlapping in wrong order) and in general crashy

Thanks in advance for reading through all this :D

[Drakulix]

Okay, a couple of remarks on this:

__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia
Please don't do this. Rather use the built-in options to make cosmic select the correct GPU. (E.g. right-click on the dock or app-library or launcher entry of the application in question and selecting "Run on GPU".

It would even already pick the correct GPU by default, if the desktop-files contained PrefersNonDefaultGPU, but unfortunately Houdini doesn't seem to do so...

In the future these flags will likely break as COSMIC shifts to an alternative implementation of GPU offloading.

opening certain windows/interface elements crash the app

That is a bug and I would love to get some logs of that, if possible.

starts but has visual glitches (like ui elements overlapping in wrong order)

That also sounds like a bug on our side. Can you provide some instructions how to reproduce this with houdini?

Qt Error: This application failed to start because no Qt platform plugin could be initialized.

This usually indicates, that the platform plugin in missing, however both wayland and wayland-egl (which are the useful targets here, not the xcomposite-variants) seem to exist here, so I'll have to assume that the plugin actually failed to initialize on cosmic.

There are very few reasons for this, one might be a missing protocol qt5 expects. Could you run the same command (with QT_QPA_PLATFORM=wayland) but also set WAYLAND_DEBUG=1 and post the logs here? (Doesn't matter if from nuke or houdini, as both behave very similarly, it is most likely the same bug.)

[MattiBRNDMR]

Okay, a couple of remarks on this:

__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia
Please don't do this. Rather use the built-in options to make cosmic select the correct GPU. (E.g. right-click on the dock or app-library or launcher entry of the application in question and selecting "Run on GPU".

It would even already pick the correct GPU by default, if the desktop-files contained PrefersNonDefaultGPU, but unfortunately Houdini doesn't seem to do so...

In the future these flags will likely break as COSMIC shifts to an alternative implementation of GPU offloading.

opening certain windows/interface elements crash the app

That is a bug and I would love to get some logs of that, if possible.

starts but has visual glitches (like ui elements overlapping in wrong order)

That also sounds like a bug on our side. Can you provide some instructions how to reproduce this with houdini?

Qt Error: This application failed to start because no Qt platform plugin could be initialized.

This usually indicates, that the platform plugin in missing, however both wayland and wayland-egl (which are the useful targets here, not the xcomposite-variants) seem to exist here, so I'll have to assume that the plugin actually failed to initialize on cosmic.

There are very few reasons for this, one might be a missing protocol qt5 expects. Could you run the same command (with QT_QPA_PLATFORM=wayland) but also set WAYLAND_DEBUG=1 and post the logs here? (Doesn't matter if from nuke or houdini, as both behave very similarly, it is most likely the same bug.)

Hey, first of all thank you for the headup - never realized one can start applications using the dGPU via right-clicking. That indeed safes me from setting these bothersome env vars, as no matter what I do, POP-OS always chooses the intel graphics unit as default and completely ignores the settings under the dropdown menu, or when setting it via system76-power.

To test your suggestions, I did the following for both houdini and nuke:

Houdini:

started houdini using an alias with a terminal (using the dGPU - right-click-technique :D ):

alias run_houdini="QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms WAYLAND_DEBUG=1 QT_QPA_PLATFORM=wayland hindie"

houdini crashed on startup, terminal saying:

matti@pop-os:~$ run_houdini
Qt Error: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), linuxfb (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), minimal (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), minimalegl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), offscreen (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), vnc (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-egl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-xcomposite-egl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-xcomposite-glx (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), xcb (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, webgl, xcb.

12232: (sent by pid 12232)
Crash log saved to /tmp/houdini_temp/crash.matti_12232_log.txt

said crash log says:

Crash report from 698869c6; Unknown App Version 20.5.299 [linux-x86_64-gcc11.2]
Uptime 0 seconds
Wed Jul 31 22:52:37 2024
Caught signal 6

Traceback from 12232 ThreadId=0x744e516db300
AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so>
AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo_t*, void*) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo_t*, void*) <libHoudiniUT.so>
__sigaction <libc.so.6>
pthread_kill <libc.so.6>
raise <libc.so.6>
abort <libc.so.6>
QMessageLogger::fatal(char const*, ...) const <libQt5Core.so.5>
QGuiApplicationPrivate::createPlatformIntegration() <libQt5Gui.so.5>
QGuiApplicationPrivate::createEventDispatcher() <libQt5Gui.so.5>
QCoreApplicationPrivate::init() <libQt5Core.so.5>
QGuiApplicationPrivate::init() <libQt5Gui.so.5>
QApplicationPrivate::init() <libQt5Widgets.so.5>
std::unique_ptr<QApplication, std::default_delete > QT_Utils::createApplication(int&, char**) <libHoudiniUI.so>
main <libHoudiniUI.so>
__libc_init_first <libc.so.6>
__libc_start_main <libc.so.6>
[0x40365c]

WAYLAND_DEBUG did not seem to pick anything up - tested with gedit, which put wayland related output to the terminal.

started houdini again with a different alias, to gather information on the crashing using xcb.
alias run_houdini="QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms WAYLAND_DEBUG=1 QT_QPA_PLATFORM=xcb hindie"

houdini starts, when trying to open a houdini ui element (a new floating window) houdini crashes with no particular message in the terminal, but creates this crash log:

Crash report from 698869c6; Houdini Version 20.5.299 [linux-x86_64-gcc11.2]
Uptime 14 seconds
Wed Jul 31 23:10:12 2024
Caught signal 11

Traceback from 13626 ThreadId=0x73fc2f3fe300
AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so>
AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo_t*, void*) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo_t*, void*) <libHoudiniUT.so>
__sigaction <libc.so.6>
RE_RenderFlush::pushMatrix(bool, RE_MatrixMode) <libHoudiniUI.so>
UI_Window::beginContext() <libHoudiniUI.so>
UI_Window::clearWindow(UT_Color const&) <libHoudiniUI.so>
UI_Window::doRedrawSubclass() <libHoudiniUI.so>
UI_Window::doRedraw() <libHoudiniUI.so>
UI_Queue::doWindowRedraws() <libHoudiniUI.so>
UI_Queue::drain() <libHoudiniUI.so>
UI_Queue::eventLoop() <libHoudiniUI.so>
main <libHoudiniUI.so>
__libc_init_first <libc.so.6>
__libc_start_main <libc.so.6>
[0x40365c]

what I've noticed: when starting houdini via a terminal that is not explicitly using the dGPU (so it defaults to the crappy old iGPU of the intel proc) it does not crash after opening the floating ui element, but when I close and re open the element, it is just a black box. unfortunately, even houdinis built in logger doesnt pick anything up on that.

Nuke:

starting nuke with an alias via dGPU terminal:
alias run_nuke="QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms QT_QPA_PLATFORM=wayland WAYLAND_DEBUG=1 FOUNDRY_LOG_LEVEL=3 /home/matti/programs/Nuke15.1v2/Nuke15.1 --nukex --nc"

crashes on startup, terminal says:

matti@pop-os:~$ run_nuke
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), linuxfb (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), minimal (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), minimalegl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), offscreen (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), vnc (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-egl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-xcomposite-egl (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), wayland-xcomposite-glx (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), xcb (from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms), linuxfb, minimal, offscreen, vnc, xcb, eglfs, minimalegl, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.

Aborted (core dumped)

xcb alias:
alias run_nuke="QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms QT_QPA_PLATFORM=xcb WAYLAND_DEBUG=1 FOUNDRY_LOG_LEVEL=3 /home/matti/programs/Nuke15.1v2/Nuke15.1 --nukex --nc"

runs as expected, but has visual bugs (even if set to terminal logging via FOUNDRY_LOG_LEVEL=3, does not seem to recognize it as an error)
Here is a picture of the bug, that cleary shows the wrong ordering of UI elements (forgive me for the picture, didnt get flameshot to work to record a delayed screenshot under cosmic)

I hope that helps in any way..

[MattiBRNDMR]

Here is the journalctl output for cosmic-comp when trying to run houdini as xcb (crashing when trying to open houdini ui elements):

-- Boot edd973f56d324482be8713ee0dc7d417 --
Aug 01 17:16:35 pop-os cosmic-comp[2279]: Failed to read config 'workspaces'
Aug 01 17:16:35 pop-os cosmic-comp[2279]: failed to read local shortcuts config 'system_actions': NoConfigDirectory
Aug 01 17:16:35 pop-os cosmic-comp[2279]: Key-Binding 'Period' only matched case insensitive for "period"
Aug 01 17:16:35 pop-os cosmic-comp[2279]: Key-Binding 'Comma' only matched case insensitive for "comma"
Aug 01 17:16:35 pop-os cosmic-comp[2279]: Key-Binding 'Period' only matched case insensitive for "period"
Aug 01 17:16:35 pop-os cosmic-comp[2279]: Key-Binding 'Comma' only matched case insensitive for "comma"
Aug 01 17:16:35 pop-os cosmic-comp[2279]: shortcuts custom config error: GetKey("custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
Aug 01 17:16:35 pop-os cosmic-comp[2279]: Unable to become drm master, assuming unprivileged mode
Aug 01 17:16:35 pop-os cosmic-comp[2279]: Unable to become drm master, assuming unprivileged mode
Aug 01 17:17:03 pop-os cosmic-comp[2279]: Unknown X11 window associated to wl_surface in commit hook
Aug 01 17:18:17 pop-os cosmic-comp[2279]: Failed to handle X11 event

[Drakulix]

POP-OS always chooses the intel graphics unit as default and completely ignores the settings under the dropdown menu, or when setting it via system76-power.

Yeah that does nothing on non-system76 laptops and is getting deprecated anyway.

QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms

Btw, why are you setting those yourself? If houdini is using your system's Qt version this shouldn't be necessary. If houdini is shipping it's own, it is very likely that the version doesn't match and it doesn't actually load them, which is what I think we are seeing here.

eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, webgl, xcb

As seen by the "normal" plugins not containing "wayland". So houdini is absolutely right to fail to launch, if you force it in wayland mode. I don't think that is supported.

linuxfb, minimal, offscreen, vnc, xcb, eglfs, minimalegl, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx

Nuke on the other hand does seem to have a wayland plugin.

What does happen if you launch that without the QT_PLUGIN_PATH and QT_QPA_PLATFORM_PLUGIN_PATH, but WAYLAND_DEBUG=1? (So QT_QPA_PLATFORM=wayland WAYLAND_DEBUG=1 FOUNDRY_LOG_LEVEL=3 /home/matti/programs/Nuke15.1v2/Nuke15.1 --nukex --nc

I would be interested in those logs, to see if it truly connects via wayland.

houdini starts, when trying to open a houdini ui element (a new floating window) houdini crashes with no particular message in the terminal, but creates this crash log:

Yeah I can reproduce that now. It looks like some weird interaction with the graphics driver, unfortunately this is really hard to debug given houdini is closed source.

Aug 01 17:18:17 pop-os cosmic-comp[2279]: Failed to handle X11 event

That kinda is the only hint, looking at a debugger these events seem to be GetGeometry-requests, which can only fail, if the window id isn't valid, so that is entirely houdini's own fault?

I am kinda lost here, I'll poke at it for a bit more, but I might have to tell you to open a ticket with sidefx.

[Drakulix]

Great it even is a heisenbug, it doesn't appear with a cosmic-comp debug build, just with release builds. Making debugging this even more difficult.

To be clear, I think there is some weird interaction between houdini and cosmic-comp going on here, that leads to the segfault. But given this is racy and crashes somewhere in houdini's UI library, I am not convinced this is our bug and it is almost impossible to track down.

[mmstick]

does nothing on non-system76 laptops and is getting deprecated anyway.

It does actually work on all laptops with hybrid NVIDIA graphics. It'll still be supported by the command line.

[Drakulix]

does nothing on non-system76 laptops and is getting deprecated anyway.

It does actually work on all laptops with hybrid NVIDIA graphics. It'll still be supported by the command line.

The Xorg configuration will not do anything useful though. It might successfully deactivate the dGPU in integrated mode, but hybrid/discrete will not have any impact on COSMIC.

[mmstick]

The integrated setting also creates a modprobe config which blacklists all nouveau and nvidia kernel drivers. Then on startup, it will probe PCI devices to unbind any identifying as NVIDIA.

[MattiBRNDMR]

POP-OS always chooses the intel graphics unit as default and completely ignores the settings under the dropdown menu, or when setting it via system76-power.

Yeah that does nothing on non-system76 laptops and is getting deprecated anyway.

QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms

Btw, why are you setting those yourself? If houdini is using your system's Qt version this shouldn't be necessary. If houdini is shipping it's own, it is very likely that the version doesn't match and it doesn't actually load them, which is what I think we are seeing here.

eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, webgl, xcb

As seen by the "normal" plugins not containing "wayland". So houdini is absolutely right to fail to launch, if you force it in wayland mode. I don't think that is supported.

linuxfb, minimal, offscreen, vnc, xcb, eglfs, minimalegl, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx

Nuke on the other hand does seem to have a wayland plugin.

What does happen if you launch that without the QT_PLUGIN_PATH and QT_QPA_PLATFORM_PLUGIN_PATH, but WAYLAND_DEBUG=1? (So QT_QPA_PLATFORM=wayland WAYLAND_DEBUG=1 FOUNDRY_LOG_LEVEL=3 /home/matti/programs/Nuke15.1v2/Nuke15.1 --nukex --nc

I would be interested in those logs, to see if it truly connects via wayland.

houdini starts, when trying to open a houdini ui element (a new floating window) houdini crashes with no particular message in the terminal, but creates this crash log:

Yeah I can reproduce that now. It looks like some weird interaction with the graphics driver, unfortunately this is really hard to debug given houdini is closed source.

Aug 01 17:18:17 pop-os cosmic-comp[2279]: Failed to handle X11 event

That kinda is the only hint, looking at a debugger these events seem to be GetGeometry-requests, which can only fail, if the window id isn't valid, so that is entirely houdini's own fault?

I am kinda lost here, I'll poke at it for a bit more, but I might have to tell you to open a ticket with sidefx.

I was setting these env vars myself to test if one of the other platform plugins, thats not being shipped with houdini, might work (for whatever reason, I dont have much experience at this level of linux :D ).
As houdini and nuke are more or less strictly following the vfx reference plattform for dependencies, I doubt that there is native wayland support in any way - but since they work perfectly fine on pop-gnome-wayland, kde-wayland etc, I thought the issue would not be on the vendors side in the first place. But yeah, I get that especially with closed-source software, it must be difficult to debug such things. So one way or another, I will file an issue to sidefx linking this thread - perhaps they have another hint.

I tried to run nuke without setting the QT_PLUGIN_PATH and QT_QPA_PLATFORM_PLUGIN_PATH, which then says:
matti@pop-os:~$ QT_QPA_PLATFORM=wayland WAYLAND_DEBUG=1 FOUNDRY_LOG_LEVEL=3 /home/matti/programs/Nuke15.1v2/Nuke15.1 --nukex --nc qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: linuxfb, minimal, offscreen, vnc, xcb. Aborted (core dumped)

I guess nuke also has no wayland plugin by default, hence providing the system's one does not work either.

[MattiBRNDMR]

Submitted an issue to sidefx, they were really quick to respond that my laptops graphics card does not meet the minimal requirements and that wayland is not official supported - in their words, it is most likely pure luck that houdini runs so well on pop-gnome-wayland. So I guess that issue is for another day.
Thank you for your efforts and taking the time anyways! :)

[Drakulix]

Submitted an issue to sidefx, they were really quick to respond that my laptops graphics card does not meet the minimal requirements and that wayland is not official supported - in their words, it is most likely pure luck that houdini runs so well on pop-gnome-wayland. So I guess that issue is for another day.

Yeah that is the most boring answer we could've possibly gotten, kinda disappointing.

Closing this for now, but feel free to ping me, should you have any new info on this issue.