GUI no longer starts, possible wayland issue after switching to beta release and OS update.

[Kostrol]

Pre-Submit Checklist:

• Check applicable sources for existing issues:
  • Windows Known Issues
  • Linux Known Issues
  • Github Issues

What happened:

So I'm suddenly having an issue where the UI no longer starts, there's a combination of things where it could have gone wrong because i both decided to switch to Beta release in Portmaster and update around the same time, I'm on Tumbleweed version 20250206. I booted into the new version and noticed Portmaster did not start as usual, and I was missing the tray notifier. I can not revert to the stable to test because I cannot access the UI.

Here is what happens when i try to start manually from the terminal

[ Sat Feb 08 19:00:30 ~ ] λ /opt/safing/portmaster/portmaster-start app
[pmstart] auto-upgraded to new UI
[pmstart] starting /opt/safing/portmaster/updates/linux_amd64/app2/portmaster-app_v1-6-29 --data /opt/safing/portmaster
Gdk-Message: 19:04:12.160: Error 71 (Protocol error) dispatching to Wayland display.
ERROR: WebKit encountered an internal error. This is a WebKit bug.
/home/abuild/rpmbuild/BUILD/webkit2gtk3-2.46.5-build/webkitgtk-2.46.5/Source/WebKit/WebProcess/Network/WebLoaderStrategy.cpp(562) : internallyFailedLoadTimerFired
[pmstart] app/portmaster-app.zip failed with: error during execution: exit status 1
[pmstart] auto-upgraded to new UI
[pmstart] starting /opt/safing/portmaster/updates/linux_amd64/app2/portmaster-app_v1-6-29 --data /opt/safing/portmaster
Gdk-Message: 19:04:14.735: Error 71 (Protocol error) dispatching to Wayland display.
ERROR: WebKit encountered an internal error. This is a WebKit bug.
/home/abuild/rpmbuild/BUILD/webkit2gtk3-2.46.5-build/webkitgtk-2.46.5/Source/WebKit/WebProcess/Network/WebLoaderStrategy.cpp(562) : internallyFailedLoadTimerFired
[pmstart] app/portmaster-app.zip failed with: error during execution: exit status 1
[pmstart] updating registry index
[pmstart] auto-upgraded to new UI
[pmstart] starting /opt/safing/portmaster/updates/linux_amd64/app2/portmaster-app_v1-6-29 --data /opt/safing/portmaster
Gdk-Message: 19:04:19.255: Error 71 (Protocol error) dispatching to Wayland display.
[pmstart] app/portmaster-app.zip failed with: error during execution: exit status 1
[pmstart] updating registry index
[pmstart] auto-upgraded to new UI
[pmstart] starting /opt/safing/portmaster/updates/linux_amd64/app2/portmaster-app_v1-6-29 --data /opt/safing/portmaster
Gdk-Message: 19:04:25.833: Error 71 (Protocol error) dispatching to Wayland display.
ERROR: WebKit encountered an internal error. This is a WebKit bug.
/home/abuild/rpmbuild/BUILD/webkit2gtk3-2.46.5-build/webkitgtk-2.46.5/Source/WebKit/WebProcess/Network/WebLoaderStrategy.cpp(562) : internallyFailedLoadTimerFired
[pmstart] app/portmaster-app.zip failed with: error during execution: exit status 1
[pmstart] updating registry index
[pmstart] auto-upgraded to new UI
[pmstart] starting /opt/safing/portmaster/updates/linux_amd64/app2/portmaster-app_v1-6-29 --data /opt/safing/portmaster
Gdk-Message: 19:04:34.412: Error 71 (Protocol error) dispatching to Wayland display.
[pmstart] app/portmaster-app.zip failed with: error during execution: exit status 1
[pmstart] encountered 5 consecutive errors, giving up ...
Error: error during execution: exit status 1 

Getting errors for both Wayland and WebKit it seems.

What did you expect to happen?:

UI starts like normal

How did you reproduce it?:

Debug Information: