UPDATE I changed the title because this has nothing to do with upgrading from 22.10. I just created an fresh image installing from the 22.04 LTS live image and then installed the *deb packages. The exact same behavior happens there. This is an issue with 22.04 LTS; not sure how 22.04 LTS got to release when some pretty common apps like atom and gitkraken do not install/work. The etcher AppImage does work on the fresh install.
ORIGINAL POST
I just now upgraded from 21.10 to 22.04 LTS. I performed the upgrade via do-release-upgrade. Following are now failing after working withtout issue on 21.10:
balenaEtcher-1.7.7-x64.AppImage Error: /tmp/.mount_balenaGlYYUI/balena-etcher-electron: line 10: 3717 Trace/breakpoint trap (core dumped) "${script_dir}"/balena-etcher-electron.bin "$@"
(Likely related: AppImages won't open on Ubuntu 22.04. See also Gitkraken not working Ubuntu 22.04 and https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1944468)
gitkraken: Starts but then immediately closes; no error reported. I did sudo apt remove gitkraken. Downloaded new .deb package from the site and installed via sudo apt install ./gitkraken-amd64.deb. The install reported this error: N: Download is performed unsandboxed as root as file '/home/<user>/Downloads/atom-amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied). Same behavior; opens and immediately closes.
atom: Starts but them immediately closes. After the first open, it prompted with an error which I agreed to send. I did sudo apt remove atom which removed it. Downloaded new .deb package from the site and installed via sudo apt install ./atom-amd64.deb. The install reported this error: N: Download is performed unsandboxed as root as file '/home/<user>/Downloads/atom-amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied). Same behavior; opens and immediately closes.
For context, the brave browser opens and works fine.
I ran atom at the command line and got this:
~$ atom
~$ /usr/bin/atom: line 195: 2803 Illegal instruction (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
[2803:0429/094123.175655:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
(node:2862) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/superstring/build/Release/superstring.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
(node:2862) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/pathwatcher/build/Release/pathwatcher.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
--2022-04-29 09:41:23-- https://atom.io/crash_reports
Resolving atom.io (atom.io)... 20.119.16.4
Connecting to atom.io (atom.io)|20.119.16.4|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-04-29 09:41:24 (0.00 B/s) - ‘/dev/fd/4’ saved [0]
Unexpected crash report id length
Failed to get crash dump id.
Report Id:
--2022-04-29 09:41:24-- https://atom.io/crash_reports
Resolving atom.io (atom.io)... 20.119.16.4
Connecting to atom.io (atom.io)|20.119.16.4|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-04-29 09:41:25 (0.00 B/s) - ‘/dev/fd/4’ saved [0]
Unexpected crash report id length
Failed to get crash dump id.
Report Id:
UPDATE I left this image as it is (so we can figure out what is happening?) and installed in a different partition of the same system a fresh image of impish 21.10 (the level on which I had been working successfully). I then installed atom, gitkraken, and add the etcher AppImage. All installed successfully and run fine.
Note that, when installing both atom and gitkraken I received the same error I listed above (N: Download is performed unsandboxed as root as file '/home/<user>/Downloads/atom-amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)) -- so that doesn't seem to be related. They run fine despite this error.
