[Feature Request] ARM64 #1635

FatBirdie · 2021-05-15T07:24:59Z

Hi
Would love to see an AppImage made for Arm64 so Session could be run on Raspberry, Pine etc.
I'm not sure if interest for this is very low or non existent, but if you have a need for it please give this a thumbs up.

Cheers!

ryouko-dev · 2021-05-30T01:23:15Z

As someone that has primarily ARM devices due to not being able to afford something better, this would be a huge quality of life improvement.

To my knowledge, this would be required to get it to run on a PinePhone as well since they use an Allwinner A64 SoC. The PinePhone would need additional support through proper UI scaling but that's already been mentioned in issue #1304.

BugInACode · 2021-06-25T03:25:31Z

Has any progress for this to be added as a feature been made? I own a pinephone and would really appreciate support for arm64 - either being able to build from source or as an AppImage.

Happy to help debug/contribute too.

Bilb · 2021-06-29T01:11:00Z

Hey,

I cannot test this all the way as I only have a remove raspi 4 without a display, but I get a Gtk-WARNING **: 03:01:32.435: cannot open display:

so I guess it almost start. Maybe the screen not present is the only left issue?
Here is what I did:

in package.json
change the build-release command to

    "build-release": "cross-env SIGNAL_ENV=production electron-builder --config.extraMetadata.environment=production --publish=never --config.directories.output=release --arm64",

(just add the --arm64 at the end in fact)

then run

yarn icon-gen
yarn build-release

it should build you a file release/session-desktop-linux-arm64-1.6.6.AppImage

see the arm64 in its name.
upload that to your raspberry.
try to start it, complains about missing libz.so

looks like the library is installed on raspi with the version number /usr/lib/aarch64-linux-gnu/libz.so.1
so you just need to
sudo ln -s /usr/lib/aarch64-linux-gnu/libz.so.1 /usr/lib/aarch64-linux-gnu/libz.so
and then ./session-desktop-linux-arm64-1.6.6.AppImage

At this point, it just asks on my side for a screen.
What do you get?

BugInACode · 2021-06-29T03:00:23Z

@Bilb Thanks for the response, unfortunately I could not run yarn icon-gen and got the following error. Searching online I could not find what exit code 127 was relating to.

mobian@mobian:~/session-desktop$ yarn icon-gen
yarn run v1.22.10
$ electron-icon-maker --input=images/session/session_icon_1024.png --output=./build
/bin/sh: 1: electron-icon-maker: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Can you confirm I should be building this on the pinephone, or should I do this on another linux machine (amd64) and then transfer the AppImage across?

FatBirdie · 2021-06-29T07:08:35Z

Never used Yarn before, getting this error, both on my PI and my x64:
$ yarn icon-gen
00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'icon-gen'

Bilb · 2021-06-30T05:25:23Z

@Bilb Thanks for the response, unfortunately I could not run yarn icon-gen and got the following error. Searching online I could not find what exit code 127 was relating to.
mobian@mobian:~/session-desktop$ yarn icon-gen
yarn run v1.22.10
$ electron-icon-maker --input=images/session/session_icon_1024.png --output=./build
/bin/sh: 1: electron-icon-maker: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Can you confirm I should be building this on the pinephone, or should I do this on another linux machine (amd64) and then transfer the AppImage across?

I tried on my x64 so I would recommend doing the same.

About your error. Did you run yarn install --frozen before?

Bilb · 2021-06-30T05:29:08Z

Never used Yarn before, getting this error, both on my PI and my x64:
$ yarn icon-gen
00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'icon-gen'

what is the yarn package installed? it's not supposed to be a binary you installed from your repository but an npm global binary

Before trying to build a release you should first follow those steps as seen in the Building.md file

sudo apt-get install python2
# install nvm by following their github README
nvm install # install the current node version used in this project
nvm use # use the current node version used in this project
npm install -g yarn # install yarn globally for this node version
yarn install --frozen-lockfile # install all dependecies of this project
yarn grunt # transpile and assemble files

then
which yarn should return something like ~/.nvm/versions/node/v14.17.1/bin/yarn

Only then you can try to do what I am taking about in this comment

BugInACode · 2021-06-30T13:04:00Z

@Bilb

About your error. Did you run yarn install --frozen before?

I decided to clone the repo and begin from scratch on my x64, when I run this I got this output

However I decided to continue building and created the AppImage. I moved it to the pinephone and executed ./session-desktop-linux-1.6.7.AppImage (on the pinephone, not through ssh) and got the following output, unsure whether the two are related.

EDIT: I changed the outputs to be uploaded to the pastebin so the thread is tidy

Bilb · 2021-06-30T23:23:52Z

In thr first output, you get an error here
import sys; print "%s.%s.%s" % sys.version_info[:3];
this looks very much like a python3 as default error.

Can you tell me what's returned by
which python & python --version ?

BugInACode · 2021-06-30T23:48:19Z

Ah yes, my mistake I thought it was changed to python2 after installing.

$ which python
/home/aquarius/anaconda3/bin/python
$ python --version
Python 3.7.6

~~I have two python binaries python2 and python2.7, does it matter which one is used?~~ There is a symbolic link between them

Bilb · 2021-06-30T23:58:43Z

you should be able to overide your default python temporary just with this command
alias python=/usr/bin/python2.7 (or wherever python is installed locally)

and rerun your command yarn install --frozen

BugInACode · 2021-07-01T00:07:57Z

Just reran yarn install --frozen-lockfile and did not produce any errors. yarn icon-gen and yarn build-release also completed successfully, however I still get an error after running the AppImage on the pinephone. The cause seems different to the one I mentioned earlier but seems like it produced the same error. This is the output

Bilb · 2021-07-01T00:18:31Z

before build-release you also need to compile .ts and .tsx files to js.
with
yarn grunt

BugInACode · 2021-07-01T00:32:11Z

yarn grunt had no errors but the AppImage being run on the pinephone did not change as per my last response.

peepo5 · 2021-07-03T20:29:48Z

maybe just compile on amd64 PC with electron-builder config like

electron-builder build --linux ... --arm64 --armv7l

BugInACode · 2021-07-05T05:57:04Z

When I try to install electron-builder using yarn add electron-builder [--dev] I am unable to as there is a conflict between some modules. If using nvm v10.19.0 there is an error of

error [email protected]: The engine "node" is incompatible with this module. Expected version ">=12.0.0". Got "10.19.0"
error Found incompatible module.

and if nvm v12.0.0 is used then the following error is produced

error [email protected]: The engine "node" is incompatible with this module. Expected version "^10.19.0". Got "12.0.0"
error Found incompatible module.

As with FatBirdie this too my first time using these commands and I am unsure how to move forward from here.

As with the error log from my previous comment, I am not sure where the error is coming from as on lines 6-9 it appears that in the home/mobian/.config/Session folder there is only one (empty) folder named Dictionaries/. Is this what should be expected?

BugInACode · 2021-07-08T04:17:21Z

@Bilb @peepopoggers
I have taken this a few steps back and attempted to build the AppImage for my x64 and was able to run it. I have then proceeded to create the AppImage for my own raspberry pi but I am unable to execute the AppImage as I get the error below.

I followed the below steps in order, can you let me know if I'm building correctly?

On x64

git clone <repo>
cd session-desktop/
nano package.json    # add --arm64 to the end of the build release line
alias python='/usr/bin/python2'
nvm use 10.19.0
npm install -g yarn    # make sure yarn is up to date
yarn install --frozen-lockfile
yarn generate
yarn build-release

Instead of yarn generate I have also tried yarn icon-gen then yarn grunt individually
I then copy the AppImage via USB from my x64 to the Raspberry Pi

On Raspberry Pi

pi@raspberrypi:~ $ ./session-desktop-linux-arm64-1.6.7.AppImage 
bash: ./session-desktop-linux-arm64-1.6.7.AppImage: cannot execute binary file: Exec format error
pi@raspberrypi:~ $ sudo !!
sudo ./session-desktop-linux-arm64-1.6.7.AppImage 
./session-desktop-linux-arm64-1.6.7.AppImage: 2: ./session-desktop-linux-arm64-1.6.7.AppImage: Syntax error: "(" unexpected

I've also tried [sudo] chmod [a]+x session-desktop-linux-arm64-1.6.7.AppImage and it returns the same errors.

As I have an external monitor if I can replicate your AppImage for my Raspberry Pi I can also check whether the build was successful before moving back to the pinephone.

Bilb · 2021-07-09T06:30:37Z

can you try to rebuild on your computer after having removed in package.json the

    "afterPack": "./build/afterPackHook.js"

(and the , right before it). Does that Syntax error: "(" unexpected still happens?

BugInACode · 2021-07-09T07:04:04Z

No it does not remove the error
EDIT: I assume you also meant follow all the steps I took previously and that they are correct

BugInACode · 2021-10-17T05:57:34Z

Just tried to see if the latest updates fixed this and I can only get so far as to run yarn install --frozen-lockfile and run in to the error

[1/6] Validating package.json...
error [email protected]: The engine "node" is incompatible with this module. Expected version "^14.16.0". Got "10.19.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Any updates on when this will work? The main reason I dont use my pinephone daily yet is because I dont have a secure messaging platform working yet and would really like this to work.

necro-nemesis · 2021-10-19T00:17:46Z

nvm install 14.16.0 probably giving it what it wants? The instructions I'm guessing are old and it's no longer looking for 10.19.0. Confirm it's installed with nvm --version.

BugInACode · 2021-10-19T00:35:38Z

@necro-nemesis changing the version to 14.16.0 did allow ~~it to attempt to build~~ yarn install --frozen-lockfile to execute but it failed giving this error. Unfortunately I'm not familiar with this language and am unable to debug it.

necro-nemesis · 2021-10-19T00:47:36Z

It's having a problem building sqlite3 or .. better-sqlite3 and archiving it. Try installing git-lfs sudo apt install git-lfs and build again. You may need to delete your node modules and yarn clean cache.

BugInACode · 2021-10-19T01:27:51Z

I was able to build the AppImage for the pinephone, but when I tried opening it I got this error, again not sure how to proceed but it does look like it's almost complete

necro-nemesis · 2021-10-19T01:48:34Z

You're further ahead than I am at this point. I'm trying to build on a Pi4 to see if it's feasible. Possibly someone working on Session development could throw us a bone?

necro-nemesis · 2021-10-19T01:53:03Z

One thing I discovered poking around is the annoying network timeout warnings has a an option yarn install --frozen-lockfile --network-timeout 600000

BugInACode · 2021-10-19T02:39:23Z

I don't think the timeout was a problem for me, I have been building on an x64 system if that makes any difference. Hopefully the devs pull through then!

necro-nemesis · 2021-10-19T03:05:05Z

timeout was an issue for me and that fixed the option. I've the added challenge on trying to build on 32bit but if the objective is to use on Raspberry Pi OS then I'm limited there. Not sure of the merit in supporting this build but at this point it's just the challenge to see if it will build.

The Linux build instructions could use some attention like listing current dependencies. The correct version to build on etc. I was even looking over the github Actions CI Ubuntu build to see what was there that could be missing. That's where I picked up on the timeout option.

Bilb · 2021-10-19T03:49:54Z

nvm install 14.16.0 probably giving it what it wants? The instructions I'm guessing are old and it's no longer looking for 10.19.0. Confirm it's installed with nvm --version.

nvm install without version specified, on linux should look for the .nvmrc file containing the right version of nvm to install.

zpeterg · 2022-05-12T21:51:44Z

@code-mart , I tried again - building on PinePhone Mobian:

git clone https://github.com/oxen-io/session-desktop.git
git checkout fb74a33f28c9c950932d4202493819626b9125d4
yarn install
yarn generate
USE_SYSTEM_FPM=true build-release
cd release
sudo dpkg -i session-desktop-linux-arm64-1.8.4.deb

It built and installed. But on running, it throws a "database error"

Bilb · 2022-05-13T01:45:14Z

very likely, there is an earlier error than this one. Would help to have the full logs started from the terminal

zpeterg · 2022-05-13T12:20:37Z

@Bilb

Set Windows Application User Model ID (AUMID) { appUserModelId: 'com.loki-project.messenger-desktop' }
NODE_ENV production
NODE_APP_INSTANCE undefined
NODE_CONFIG_DIR /opt/Session/resources/app.asar/config
NODE_CONFIG {}
userData: /home/mobian/.config/Session
config/get: Successfully read user config file
config/get: Did not find ephemeral config file, cache is now empty object
making app single instance
{"name":"log","hostname":"mobian","pid":7515,"level":30,"msg":"app ready","time":"2022-05-13T12:19:11.631Z","v":0}
{"name":"log","hostname":"mobian","pid":7515,"level":30,"msg":"starting version 1.8.4","time":"2022-05-13T12:19:11.634Z","v":0}
initializeSql sqlnode
{"name":"log","hostname":"mobian","pid":7515,"level":30,"msg":"migrateDatabase: Migration without cipher change failed {\"code\":\"SQLITE_NOTADB\"}","time":"2022-05-13T12:19:11.715Z","v":0}
{"name":"log","hostname":"mobian","pid":7515,"level":50,"msg":"getUserVersion error {\"code\":\"SQLITE_NOTADB\"}","time":"2022-05-13T12:19:11.734Z","v":0}
{"name":"log","hostname":"mobian","pid":7515,"level":30,"msg":"migrateDatabase: migrateSchemaVersion failed {\"code\":\"SQLITE_NOTADB\"}","time":"2022-05-13T12:19:11.737Z","v":0}
{"name":"log","hostname":"mobian","pid":7515,"level":50,"msg":"error {}","time":"2022-05-13T12:19:11.738Z","v":0}
{"name":"log","hostname":"mobian","pid":7515,"level":30,"msg":"Database startup error: Error: db is not set\n    at Object.<anonymous> ([REDACTED]/ts/node/sql.js:1306:23)\n    at Generator.next (<anonymous>)\n    at [REDACTED]/ts/node/sql.js:31:71\n    at new Promise (<anonymous>)\n    at __awaiter ([REDACTED]/ts/node/sql.js:27:12)\n    at Object.initializeSql ([REDACTED]/ts/node/sql.js:1284:12)\n    at [REDACTED]/ts/mains/main_node.js:557:29\n    at Generator.next (<anonymous>)\n    at fulfilled ([REDACTED]/ts/mains/main_node.js:28:58)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)","time":"2022-05-13T12:19:11.743Z","v":0}
[7548:0513/071912.436424:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.

BugInACode · 2022-05-18T12:46:39Z

@zpeterg perhaps electron-userland/electron-builder#6116 contains some hints on how to proceed?

Based on signalapp/better-sqlite3#1 it seems like there is indeed a problem with electron-builder not being able to build the arm64 package.

zpeterg · 2022-05-18T13:37:34Z

@BugInACode , I actually had no problems building per the above. I got the executable and all - it just has DB problems.

BugInACode · 2022-05-19T00:11:50Z

Interesting, I tried yesterday on my x64 and got the same errors as in the electron-builder issue. Did you follow same procedure as I had in my previous comment but on the pinephone? I will attempt whatever instructions you provide later today

zpeterg · 2022-05-19T01:49:07Z

@BugInACode , no, the steps I used were these #1635 (comment)
Let me know how it goes for you. I tried before compiling in Docker - I haven't tried on an amd64 machine. Figure compiling on pinephone is the most sure to match the chipset... but it is painfully slow

peepo5 · 2022-05-19T15:19:26Z

try on a pi

zpeterg · 2022-05-19T15:21:23Z

Have you tried? Does it work? Sent with [ProtonMail](https://protonmail.com/) secure email.

…

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

On Thursday, May 19th, 2022 at 10:19 AM, peepopoggers ***@***.***> wrote: try on a pi — Reply to this email directly, [view it on GitHub](#1635 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACZWS3XZ6OLO4Q2X3WDPVA3VKZLY3ANCNFSM445TT3HA). You are receiving this because you were mentioned.Message ID: ***@***.***>

Keksimus69 · 2022-09-08T14:58:49Z

I was able to compile Session-Desktop as an AppImage on my device, but I too has data base problems. Seems like there are less errors than the screenshot from above

FatBirdie · 2022-09-23T07:55:49Z

Whats the issue of publishing a ready made, working out of the box, AppImage directly under releases from Session team?

gotgot1995 · 2023-01-26T19:07:17Z

It's nice to see that some people are interested in building Session for ARM. 🙏 😄
I'd love to run it on my Llibrem 5 phone some day. ❤️

robster7674 · 2023-01-30T07:13:01Z

@zpeterg : I gave building another try using your instructions in #1635 (comment). I got this error:

error [email protected]: The engine "node" is incompatible with this module. Expected version "16.13.0". Got "19.4.0"

Editing packages.json and replacing node version under engines with 19.4.0 fixed that. But then I got network errors after running "yarn install":

...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "https://registry.yarnpkg.com/@iconify/icons-mdi/-/icons-mdi-1.0.117.tgz: ESOCKETTIMEDOUT".
...

Looking into that, tbc.

PS: to automate these instructions a bit more, let's add "cd session-desktop" after the git clone command.

robster7674 · 2023-02-03T08:43:54Z

@BugInACode : I retried your instructions, and got stuck at:

mobian@mobian:~/git/session-desktop$ yarn generate
yarn run v1.22.19
error Command "generate" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

robster7674 · 2023-02-11T15:59:37Z

@BugInACode : when using "yarn generate-lock-entry" that worked. Then, I had to install "libopenjp2-tools" to fix " ⨯ exec: "opj_decompress": executable file not found in $PATH". After that:

mobian@mobian:~/git/session-desktop$ yarn build-release
yarn run v1.22.19
$ run-script-os
$ yarn sedtoDeb; yarn build-release-non-linux && yarn sedtoAppImage && yarn build-release-non-linux && yarn sedtoDeb
$ sed -i 's/"target": "AppImage"/"target": \["deb", "rpm", "freebsd"\]/g' package.json
$ yarn build-everything && cross-env SIGNAL_ENV=production electron-builder --config.extraMetadata.environment=production --publish=never --config.directories.output=release
$ yarn clean && yarn protobuf && grunt && yarn sass && tsc && yarn parcel-util-worker
$ rimraf 'ts/**/*.js' 'ts/*.js' 'ts/*.js.map' 'ts/**/*.js.map' && rimraf tsconfig.tsbuildinfo;
$ pbjs --target static-module --wrap commonjs --out ts/protobuf/compiled.js protos/*.proto && pbts --out ts/protobuf/compiled.d.ts ts/protobuf/compiled.js --force-long
Running "gitinfo" task

Running "getCommitHash" task

Done.
$ rimraf 'stylesheets/dist/' && parcel build --target sass --no-autoinstall --no-cache
✨ Built in 18.48s

stylesheets/dist/manifest.css                         85.55 KB    2.70s
stylesheets/dist/SpaceMono-Regular.4e3c874c.ttf       91.07 KB    499ms
stylesheets/dist/Roboto-Thin.b913caf8.ttf            164.54 KB    754ms
stylesheets/dist/Roboto-ThinItalic.56d6bf8f.ttf      168.81 KB    474ms
stylesheets/dist/Roboto-Light.1695f332.ttf           163.09 KB    755ms
stylesheets/dist/Roboto-LightItalic.50b96eae.ttf     169.11 KB    481ms
stylesheets/dist/Roboto-Regular.c5f94986.ttf         164.32 KB    761ms
stylesheets/dist/Roboto-Italic.b1feadc8.ttf          166.51 KB    485ms
stylesheets/dist/Roboto-Medium.91322885.ttf          164.69 KB    764ms
stylesheets/dist/Roboto-MediumItalic.dde87bd9.ttf    169.35 KB    488ms
stylesheets/dist/Roboto-Bold.821ad6c1.ttf            163.41 KB    755ms
stylesheets/dist/Roboto-BoldItalic.696e5416.ttf      167.49 KB    480ms
stylesheets/dist/Roboto-Black.be41af2a.ttf           164.12 KB    759ms
stylesheets/dist/Roboto-BlackItalic.2263e59d.ttf     170.03 KB    487ms
stylesheets/dist/Loor.ec9bcb62.ttf                   199.16 KB    763ms
stylesheets/dist/save.1c1f2615.svg                       216 B    3.53s
stylesheets/dist/x.bd0fd4ec.svg                          190 B    3.64s
stylesheets/dist/error.9c714cbe.svg                      435 B    3.54s
stylesheets/dist/file-gradient.730f2921.svg            2.47 KB    3.64s
stylesheets/dist/timer.913613e9.svg                      530 B    3.54s
stylesheets/dist/file.2c3475f5.svg                       187 B    3.64s
stylesheets/dist/image.116a5ef1.svg                      184 B    3.54s
stylesheets/dist/play.1166c0c6.svg                       102 B    3.64s
stylesheets/dist/movie.69dd4f24.svg                      181 B    3.54s
stylesheets/dist/x-shadow-16.0880b782.svg                460 B    3.65s
stylesheets/dist/x-16.feaa908e.svg                       191 B    3.54s
stylesheets/dist/plus-36.48aac3cb.svg                    152 B    3.64s
stylesheets/dist/microphone.f300daf3.svg                 305 B    3.54s
stylesheets/dist/broken-link.cb8879c3.svg                547 B    3.64s
$ rimraf ts/webworker/workers/util.worker.js && parcel build --target util-worker --no-autoinstall --no-cache
🚨 Build failed.

@parcel/core: Failed to resolve 'curve25519-js' from './ts/webworker/workers/util.worker.ts'

  /home/mobian/git/session-desktop/ts/webworker/workers/util.worker.ts:2:52
    1 | import ByteBuffer from 'bytebuffer';
  > 2 | import { generateKeyPair, sharedKey, verify } from 'curve25519-js';
  >   |                                                    ^^^^^^^^^^^^^^^
    3 | import { default as sodiumWrappers } from 'libsodium-wrappers-sumo';
    4 | import _ from 'lodash';

@parcel/resolver-default: Could not load './lib/index.js' from module 'curve25519-js' found in package.json#main

  /home/mobian/git/session-desktop/node_modules/curve25519-js/package.json:5:11
    4 |   "description": "Javascript implementation of Curve25519",
  > 5 |   "main": "lib/index.js",
  >   |           ^^^^^^^^^^^^^^ './lib/index.js' does not exist'
    6 |   "scripts": {
    7 |     "build": "tsc",

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
mobian@mobian:~/git/session-desktop$

cc: @zpeterg

robster7674 · 2023-02-12T10:36:52Z

After installing curve25519-js I still got the error about missing index.js. I ran "npm install" to reinstall all dependencies and such. This ended with:

yarn run v1.22.19
$ cd node_modules/curve25519-js && yarn install && yarn build && cd ../../
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
$ tsc
error TS18003: No inputs were found in config file '/home/mobian/git/session-desktop/node_modules/curve25519-js/tsconfig.json'. Specified 'include' paths were '["**/*"]' and 'exclude' paths were '["node_modules","lib","examples"]'.

6uHt1G · 2023-04-27T15:56:33Z

I have a PinePhone Pro and have tried installing Session-Desktop on Kali Nethunter, Manjaro Plasma Mobile, Manjaro Phosh, postmarketOS, Mobian, and Ubuntu Touch. All have been unsuccessful. Farthest I got was with Manjaro Plasma Mobile, Session gets stuck at the splash screen.

robster7674 · 2023-04-28T12:42:26Z

@6uHt1G it's been a while since I looked at this... can you share what steps you took to get to the stuck splash screen?

Treadmill6378 · 2023-06-27T20:23:49Z

Has any progress for this to be added as a feature been made? I own a pinephone and would really appreciate support for arm64 - either being able to build from source or as an AppImage.

Happy to help debug/contribute too.

As all the backorders for the Librem 5 Linux phone are close to being delivered, a number of those users will be looking for an ARM64 version of Session as well. I don't have the expertise, but I can certainly report bugs and beta test.

Keksimus69 · 2023-07-25T22:26:35Z

I still never got it to compile but I decided to try running an emulator and it worked! PostmarketOS host running a Debian Distrobox container with Box64 (x86-64 emulator for arm64) installed in the container
and then I installed the session-desktop.deb from Github. Then just $ box64 session-desktop in the container. Next thing you know you have Session-desktop on arm64 Linux.

CaptainMorgan12 · 2023-08-25T17:49:35Z

Building the Session App in Flatpak, would that automatically enable it to work on any system since it would have to contain all required libraries etc?

altsst · 2023-09-27T16:31:39Z

bump

gotgot1995 · 2023-12-02T10:16:27Z

Anything new on this subject?

FatBirdie · 2023-12-29T15:48:39Z

"KeeJef added the enhancement label on May 17, 2021" ...

KeeJef · 2024-01-11T15:00:44Z

We haven't forgotten about this, still something we would like to do, however taking a backseat to closed group & disappearing message overhaul.

BugInACode · 2024-04-02T10:17:20Z

installed in the container and then I installed the session-desktop.deb from Github

@Keksimus69 Unfortunately this is not (my)/the intended outcome, but cool to see it on the screen nonetheless.

Building the Session App in Flatpak

@CaptainMorgan12 This does sound like a good option to try. I can give this a go on the weekend.

We haven't forgotten about this

@KeeJef appreciate it. I haven't forgotten about this either

gotgot1995 · 2024-10-16T09:12:53Z

Hi everyone 👋 I'm glad to see that the issue is still open. I can see more and more ARM64 devices running Linux (and also Windows nowadays) so this feature would totally make sense.

KeeJef added the enhancement New feature or request label May 17, 2021

KeeJef mentioned this issue Aug 11, 2022

SailfishOS simple client or base for porting #2350

Closed

KeeJef mentioned this issue Dec 5, 2023

[BUG] MAC For Arm Desktop Session Network connection error！ #2855

Closed

3 tasks

amirseyedian mentioned this issue Oct 17, 2024

Error compiling on Arm64 linux #3232

Open

[Feature Request] ARM64 #1635

[Feature Request] ARM64 #1635

Comments

FatBirdie commented May 15, 2021

ryouko-dev commented May 30, 2021

BugInACode commented Jun 25, 2021

Bilb commented Jun 29, 2021

BugInACode commented Jun 29, 2021 • edited Loading

FatBirdie commented Jun 29, 2021

Bilb commented Jun 30, 2021 • edited Loading

Bilb commented Jun 30, 2021

BugInACode commented Jun 30, 2021 • edited Loading

Bilb commented Jun 30, 2021

BugInACode commented Jun 30, 2021 • edited Loading

Bilb commented Jun 30, 2021 • edited Loading

BugInACode commented Jul 1, 2021

Bilb commented Jul 1, 2021

BugInACode commented Jul 1, 2021

peepo5 commented Jul 3, 2021

BugInACode commented Jul 5, 2021 • edited Loading

BugInACode commented Jul 8, 2021

On x64

On Raspberry Pi

Bilb commented Jul 9, 2021

BugInACode commented Jul 9, 2021 • edited Loading

BugInACode commented Oct 17, 2021

necro-nemesis commented Oct 19, 2021

BugInACode commented Oct 19, 2021 • edited Loading

necro-nemesis commented Oct 19, 2021

BugInACode commented Oct 19, 2021

necro-nemesis commented Oct 19, 2021

necro-nemesis commented Oct 19, 2021

BugInACode commented Oct 19, 2021 • edited Loading

necro-nemesis commented Oct 19, 2021

Bilb commented Oct 19, 2021

zpeterg commented May 12, 2022 • edited Loading

Bilb commented May 13, 2022

zpeterg commented May 13, 2022

BugInACode commented May 18, 2022

zpeterg commented May 18, 2022

BugInACode commented May 19, 2022

zpeterg commented May 19, 2022

peepo5 commented May 19, 2022

zpeterg commented May 19, 2022 via email

Keksimus69 commented Sep 8, 2022

FatBirdie commented Sep 23, 2022

gotgot1995 commented Jan 26, 2023

robster7674 commented Jan 30, 2023

robster7674 commented Feb 3, 2023

robster7674 commented Feb 11, 2023

robster7674 commented Feb 12, 2023

6uHt1G commented Apr 27, 2023 • edited Loading

robster7674 commented Apr 28, 2023

Treadmill6378 commented Jun 27, 2023

Keksimus69 commented Jul 25, 2023

CaptainMorgan12 commented Aug 25, 2023

altsst commented Sep 27, 2023

gotgot1995 commented Dec 2, 2023

FatBirdie commented Dec 29, 2023

KeeJef commented Jan 11, 2024

BugInACode commented Apr 2, 2024

gotgot1995 commented Oct 16, 2024

BugInACode commented Jun 29, 2021 •

edited

Loading

Bilb commented Jun 30, 2021 •

edited

Loading

BugInACode commented Jun 30, 2021 •

edited

Loading

BugInACode commented Jun 30, 2021 •

edited

Loading

Bilb commented Jun 30, 2021 •

edited

Loading

BugInACode commented Jul 5, 2021 •

edited

Loading

BugInACode commented Jul 9, 2021 •

edited

Loading

BugInACode commented Oct 19, 2021 •

edited

Loading

BugInACode commented Oct 19, 2021 •

edited

Loading

zpeterg commented May 12, 2022 •

edited

Loading

6uHt1G commented Apr 27, 2023 •

edited

Loading