Linux Experience: Ubuntu 24 - amd64

[pfrilling]

Putting my Linux experience below in case it helps.

1. Downloaded the x64 version from https://github.com/drupal/cms-launcher/releases/tag/0.1.8
2. Made the file executable with chmod +x Drupal.CMS.for.Linux.x64.AppImage
3. Ran the file from the terminal with: ./Drupal.CMS.for.Linux.x64.AppImage and received the error message:

You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information

4. Ran lsb_release -a

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 24.04.2 LTS
Release:	24.04
Codename:	noble

5. Browsed to https://github.com/AppImage/AppImageKit/wiki/FUSE and found FUSE installation instructions
6. Ran the following

sudo add-apt-repository universe
sudo apt install libfuse2t64

7. Ran the installer again with: ./Drupal.CMS.for.Linux.x64.AppImage and received:

[3416358:0430/083331.222767:FATAL:setuid_sandbox_host.cc(163)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_DrupaleuuAMp/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

8. Ran the installer from the GUI and the install screen opened and the loading wheel spun, but nothing actually happened.
9. Ran the following from the terminal: ./Drupal.CMS.for.Linux.x64.AppImage --no-sandbox. This launched the installer and provided the following error in the terminal output:

Error occurred in handler for 'start': Error: Command failed: /tmp/.mount_Drupalmh10VF/resources/app/bin/php -r (new Phar("composer.phar"))->extractTo("composer");
    at genericNodeError (node:internal/errors:984:15)
    at wrappedFn (node:internal/errors:538:14)
    at checkExecSyncError (node:child_process:906:11)
    at execFileSync (node:child_process:942:15)
    at func (node:electron/js2c/node_init:2:2559)
    at composer (/tmp/.mount_Drupalmh10VF/resources/app/binaries.js:19:13)
    at async module.exports (/tmp/.mount_Drupalmh10VF/resources/app/installer.js:16:23)
    at async /tmp/.mount_Drupalmh10VF/resources/app/main.js:19:5
    at async WebContents.<anonymous> (node:electron/js2c/browser_init:2:87428) {
  status: 255,
  signal: null,
  output: [
    null,
    <Buffer 0a 46 61 74 61 6c 20 65 72 72 6f 72 3a 20 55 6e 63 61 75 67 68 74 20 52 75 6e 74 69 6d 65 45 78 63 65 70 74 69 6f 6e 3a 20 55 6e 61 62 6c 65 20 74 6f ... 178 more bytes>,
    <Buffer >
  ],
  pid: 3466072,
  stdout: <Buffer 0a 46 61 74 61 6c 20 65 72 72 6f 72 3a 20 55 6e 63 61 75 67 68 74 20 52 75 6e 74 69 6d 65 45 78 63 65 70 74 69 6f 6e 3a 20 55 6e 61 62 6c 65 20 74 6f ... 178 more bytes>,
  stderr: <Buffer >
}

The permissions in the bin directory are as follows:

/tmp/.mount_Drupalmh10VF/resources/app/bin
total 24851
-rw-r--r-- 1 root root  3114082 Apr 27 21:25 composer.phar
-rwxr-xr-x 1 root root 22333488 Apr 27 21:25 php

[bircher]

I downloaded it and set it as executable and then just double clicked it
it spun forever so I clicked arround and found the dev tools

[bircher]

btw I manually ran the command that failed in the image above and php complains that it can not create the path for composer.. because the appimage filesystem is readonly :(

[gitressa]

Just tried the latest release 0.1.9, and I still just get the spinner in Debian 12 ...

Perhaps this issue can be looked at, so we can more easily help debug this?

• Inform users when an error happens #58

[sikofitt]

I still have to run this with the --no-sandbox flag. But after that it works fine.
Kubuntu 24.04.2 LTS

% ./Drupal.CMS.for.Linux.x64.AppImage
[3388329:0502/162336.130010:FATAL:setuid_sandbox_host.cc(163)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_Drupalf3DlNK/chrome-sandbox is owned by root and has mode 4755.
[1]    3388329 trace trap (core dumped)  ./Drupal.CMS.for.Linux.x64.AppImage

% ls -lh /tmp/.mount_Drupalf3DlNK/chrome-sandbox
-rwxr-xr-x 1 root root 38K May  2 14:58 /tmp/.mount_Drupalf3DlNK/chrome-sandbox

[phenaproxima]

@sikofitt It's interesting that you need to run with --no-sandbox, as that is apparently the default for AppImages generated by Electron Builder (which is what this launcher uses): https://github.com/electron-userland/electron-builder/blob/master/packages/app-builder-lib/src/targets/AppImageTarget.ts#L28

[Nao-30]

@pfrilling using --no-sandbox isn't the optimal way and not recommended!

It's a bit known issue tho for now since 23.##~

I've run through this and finally conducted an in-depth analysis of the AppImage sandbox restrictions in Ubuntu 24.04 and documented comprehensive findings across two complementary blog posts:

1. Technical Analysis: A detailed exploration of the underlying mechanisms, security implications, and system-level changes affecting AppImage execution in Ubuntu 24.04's enhanced sandbox environment.

2. Practical Solutions: A user-focused guide with step-by-step workarounds and best practices for managing AppImage applications while maintaining system security.

For a complete understanding of this issue, including technical details, implementation specifics, and practical solutions, you can take a look at:

• Technical Deep Dive
• Practical Workarounds

Both articles include thoroughly researched information, verified solutions, and relevant technical documentation to help users and developers navigate these changes effectively.

[sikofitt]

@phenaproxima That is weird. If this is helpful, I'm getting these messages for apparmor in the kernel.

sudo dmesg|grep cms-launcher
[57947.487418] audit: type=1400 audit(1747072291.043:645): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=93700 comm="cms-launcher" requested="userns_create" target="unprivileged_userns"
[57947.489979] audit: type=1400 audit(1747072291.045:646): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=93708 comm="cms-launcher" capability=21  capname="sys_admin"
[57947.508581] traps: cms-launcher[93700] trap int3 ip:63768567e20e sp:7ffc486d8270 error:0 in cms-launcher[6376815ff000+897d000]

Oops, this was answered above I think. Thanks @Nao-30.

[phenaproxima]

It's also worth mentioning that df56039, the final commit before 0.1.9, removed the need for the app to extract Composer from a phar file, and instead just ships a pre-unpacked copy of Composer. Worth trying again with HEAD, probably.

[phenaproxima]

Looking at the info @Nao-30 linked, I think we might need to document this in a "troubleshooting" section in the README. Tagging for that.

[phenaproxima]

Added this to the 1.0.0 milestone for documentation.