electron apps could be started with --no-sandbox with executableArgs = ["no-sandbox"] in build mode for AppImage or Snap https://www.electron.build/configuration/snap.html .
It is also bug opened on electron https://github.com/electron/electron/issues/41066 with merged patch for detecting such issue on runtime with testing write for such namespaces as PullRequst on Electron. This change in Ubuntu for Electron is not new and there were some attempts for AppImages for Electron to fix it because Debian and other linuxes has various policies, so was also questions about it and some js npms packages attempts https://github.com/electron-userland/electron- builder/issues/5371. So issue on Electron is opened and packagers could wait on new Electron release or decide what to do... But require for each app to have own profile is weird way to bureaucratic hell overhead of something not deeply understood. ** Bug watch added: github.com/electron/electron/issues #41066 https://github.com/electron/electron/issues/41066 ** Bug watch added: github.com/electron-userland/electron-builder/issues #5371 https://github.com/electron-userland/electron-builder/issues/5371 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072811 Title: Apparmor: New update broke flatpak with `apparmor="DENIED"` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2072811/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
