Wappler Beta 7 Ubuntu Failed to Start

[Cheese]

Wappler Version : 7.7.7 Beta 2
Operating System : Ubuntu 24.04.1 LTS
Server Model: Node/Docker
Database Type: MySQL
Hosting Type: Digital Ocean

Expected behavior

What do you think should happen?

Clicking on the shortcut to start Wappler should open Wappler.

Actual behavior

Nothing happens, error reported.

How to reproduce

• Using Ubuntu 24.04.1 LTS. Install Wappler. Open Wappler.

Maybe relevant to this:

Recently updated Ubuntu to 24.04.1 LTS from 22.04 LTS. Wappler 6.7.3.1 also has the same issue on Ubuntu 24.04.1 (it fails to start). This could be specific to the new version of Ubuntu as all was fine using 22.04.

The remedy to start Wappler if anyone else has this issue...

Start by right clicking (run) the executable for Wappler 7 Beta, located:

/usr/share/wappler-beta

And for other versions, same principle but located:

/usr/share/wappler

[Cheese]

@George Unfortunately did not fix the issue but it is no hardship and may well be down to the update path I took with Ubuntu, which was with an update from 22.** to 24.** (personally I prefer to update using the latest LTS image rather than going from version to version, especially OS wise, but in this circumstance I did not).

[George]

What happens if you try to run Wappler with the following command:

gtk-launch wappler-beta

[Cheese]

@George

gtk-launch Wappler-beta

Receive the same error:

anon@anon:/usr/share/wappler-beta$ gtk-launch wappler-beta
gtk-launch: error launching application: Desktop file didn’t specify Exec field

[George]

Well this is weird as the desktop file does have a Exec in it.

It might be somehow wrongly escaped due to the new Ubuntu

You might try to edit it and put the command between double quotes instead of escaping with slash.

After edit you might need to reload the gtk desktop files.

Let me know how it goes

[Cheese]

@George

You might try to edit it and put the command between double quotes instead of escaping with slash.

This RESOLVED the issue @George

[Desktop Entry]
Name=Wappler Beta
Comment=Wappler - The Visual Web and App Creator
GenericName=Web Editor
Exec="/usr/share/wappler-beta/Wappler Beta" %u --no-sandbox
Icon=wappler-beta
Type=Application
StartupNotify=true
Categories=GNOME;GTK;Utility;TextEditor;Development;
MimeType=x-scheme-handler/x-wappler-desktop-auth;
Name[en_US]=Wappler Beta

Many thanks!

[George]

How about the stable Wappler?

Did you need to have quotes there as well?

[Cheese]

@George

Did you need to have quotes there as well?

Yes, sorry forgot to mention that. This (editing the .desktop file) also resolves the issue for the stable release.

Win-win!

[George]

Great to hear! Weird new Ubuntu 24 “requirements”

I’ve added also the —no-sandbox attribute to escape also the new AppArmor being auto turned on on Ubuntu 24 and breaking all the apps.

As you were updating from 22 you probably didn’t notice it, but it is bad and i think they are trying to revert it …

See:

[Bug]: The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now.

[Cheese]

Oh man there are numerous issues with 24.**. The worst for me is dark theme is broken in the files explorer so have a glaring white background that is destroying my retinas hahaha.

@George

AppArmor being auto turned on on Ubuntu 24

Had some issues with that but not with Wappler. Workbench lost the plot for stored passwords (for db connections) within the keyring, as did a few other tools (oh man looking up all those passwords broke my soul). This is why I hate updates (OS updates) and am now thinking I may revert back to a previous backup of Ubuntu 22.** for the meantime until all this is sorted out.

Ubuntu and Wappler really are a great combination aside from the above 'very rare' issue they play really well together.

[Cheese]

Please mark this issue resolved as of Wappler 7 Beta 5.

[Teodor]

Fixed in Wappler 7 beta 5