Fedora 36 - Flatpak install does not launch

[l0steh]

Ive found installing ModernDeck app through Flatpak does not launch. So, I tried launching this through terminal and have the following

flatpak run com.dangeredwolf.ModernDeck
{}
LaunchProcess: failed to execvp:
xdg-settings
Gtk-Message: 10:17:22.266: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:17:22.266: Failed to load module "pk-gtk-module"
Gtk-Message: 10:17:22.267: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:17:22.267: Failed to load module "pk-gtk-module"
[3:1001/101722.287786:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:1001/101722.287852:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[45:1001/101722.738182:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
(node:3) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 did-stop-loading listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
(Use `moderndeck --trace-warnings ...` to show where the warning was created)
(node:3) UnhandledPromiseRejectionWarning: Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
    at node:electron/js2c/renderer_init:93:395
    at EventEmitter.<anonymous> (node:electron/js2c/renderer_init:81:375)
    at EventEmitter.emit (node:events:390:28)
    at Object.onMessage (node:electron/js2c/renderer_init:69:746)
(node:3) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:3) UnhandledPromiseRejectionWarning: Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
    at node:electron/js2c/renderer_init:93:395
    at EventEmitter.<anonymous> (node:electron/js2c/renderer_init:81:375)
    at EventEmitter.emit (node:events:390:28)
    at Object.onMessage (node:electron/js2c/renderer_init:69:746)
(node:3) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:3) UnhandledPromiseRejectionWarning: Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
    at node:electron/js2c/renderer_init:93:395
    at EventEmitter.<anonymous> (node:electron/js2c/renderer_init:81:375)
    at EventEmitter.emit (node:events:390:28)
    at Object.onMessage (node:electron/js2c/renderer_init:69:746)
(node:3) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
(node:3) UnhandledPromiseRejectionWarning: Error: An object could not be cloned.
    at EventEmitter.t.ipcRendererInternal.send (node:electron/js2c/renderer_init:85:328)
    at EventEmitter.<anonymous> (node:electron/js2c/renderer_init:81:357)
(node:3) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[3:1001/101725.969688:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[45:1001/101742.325822:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[45:1001/101757.928847:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[45:1001/101801.987599:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!

so I tried update and there everything appears up to date. I have checked the xorg version is the current version (not sure if that is relevant here).

I also downloaded the file ModernDeck_x86_64.AppImage and if I Run this, it works! But this is not ideal, as the runs it and isnt installed…

My system details

Dell XPS 13 9365
F36 Workstation Edition
Mesa Intel HD Graphics 615 (KBL GT2)
Gnome 42.4
Wayland

Thanks

[dangeredwolf]

ModernDeck has been updated to version 10.0.0, is the issue you were facing still present in the new version?

[l0steh]

Sorry it took awhile to reply, but I wanted to let you know version 10 does work! It is such a shame that there will be no further developments, but I appreciate your hard work and understand the position. Thank you for all your years of putting this app out for everyone to enjoy! Wish you the very best for the future pal! Sent with [Proton Mail](https://proton.me/) secure email.

…

------- Original Message -------

On Sunday, February 12th, 2023 at 5:52 PM, dangered wolf ***@***.***> wrote: ModernDeck has been updated to version 10.0.0, is the issue you were facing still present in the new version? — Reply to this email directly, [view it on GitHub](#348 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/A3MA3ONXBCYUZKIAYNQ7ZXTWXEPOHANCNFSM6AAAAAAQ2QDHZY). You are receiving this because you authored the thread.Message ID: ***@***.***>