[Bug] Fedora 39 - BadAlloc serial 345 error_code 11

[geolaw]

Describe the Bug Lunasea does not launch at all from the application menu I'm using the i3wm respin of Fedora 39

When trying to launch from a terminal

lunasea 
/home/glaw/Downloads was removed, reassigning DOWNLOAD to homedir
/home/glaw/Pictures was removed, reassigning PICTURES to homedir

(lunasea:6091): Gdk-CRITICAL **: 09:34:52.190: gdk_window_get_state: assertion 'GDK_IS_WINDOW (window)' failed
Fontconfig warning: "/etc/fonts/conf.d/10-sub-pixel-rgb-for-kde.conf", line 4: unknown element "description"

** (lunasea:6091): CRITICAL **: 09:34:52.959: Failed to read XDG desktop portal settings: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: startup job failed.

** (lunasea:6091): CRITICAL **: 09:34:52.961: Failed to read XDG desktop portal settings: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: startup job failed.

** (lunasea:6091): CRITICAL **: 09:34:52.963: Failed to read XDG desktop portal settings: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: startup job failed.

** (lunasea:6091): CRITICAL **: 09:34:52.964: Failed to read XDG desktop portal settings: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: startup job failed.

** (lunasea:6091): CRITICAL **: 09:34:52.965: Failed to read XDG desktop portal settings: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: startup job failed.

** (lunasea:6091): CRITICAL **: 09:34:52.965: Failed to read XDG desktop portal settings: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: startup job failed.

(lunasea:6091): Gdk-ERROR **: 09:34:52.965: The program 'lunasea' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc'.
  (Details: serial 251 error_code 11 request_code 149 (unknown) minor_code 2)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

To Reproduce launch from application menu or 'lunasea' from the command line

Expected Behaviour

Screenshots application never starts to get a screenshot, terminal output above

Versions installed via snap

lunasea 10.2.6 187 latest/stable jagandeepbrar -

Additional context Add any other context about the problem here.