05-06-2021, 04:17 AM
(This post was last modified: 05-06-2021, 04:23 AM by arno_nuehm.)
(05-06-2021, 04:08 AM)Anna Wrote: I'm not sure whether I should have openend a new thread for this topic as not to overload the Axolotl thread...
Anyway, I have the following Axolotl problem:
All of a sudden I can neither receive messages from one friend of mine nor can I send messages to her – they are marked with this triangular, red traffic sign (instead of the two circles) and never go out. Everything else works, only this particular person is affected.
I tried "reset encryption" for that chat, afterwards deleted the chat and asked her to do the same on her (Android) phone – it did not help, the problem persists.
However, I can still communicate with her via the Signal desktop app on Linux Mint. Normally these conversations would show up in Axolotl as well; in this case they don't.
I had the similar problem a few weeks ago with somebody else; in that case there was a slight difference: The messages I sent via the desktop app not only went out, they (unlike now) also showed up in Axolotl on my phone. This person's messages (just like in the new case) only reached my desktop app, not the Pinephone.
My friend's contact looks exactly the same as all other contacts in /.config/textsecure.nanuc/registeredContacts.yml -- nothing remarkable and no zeroes at the beginning or end of the UUID.
Last time I could "solve" the Problem with a complete reinstallation -- something I'd like to avoid this time. (I would not mind the reinstallation part, but connecting it to the computer again and reentering all the contacts is quite annoying especially if a likely perspective is having to do that over and over again...)
Is there any solution apart from reinstalling Axolotl?
Hey Anna,
thanks for posting it here. There are some other people reporting the same issue in the Axolotl-dev Telegram group and it is a bit unclear, what causes the problems. It seems that Signal has changed something in their server system, which results in the behaviour you described: Messages get lost even though they are sent correctly.
I will report back, when the are new insights.
Till then, don't deinstall or delete your personal data - help is on the way.
Sorry for the inconvnience!
And if you'd like to help, you can open an issue on github with the output of
axolotl > axolotl-log
attached, while trying to send a message to that particular contact.
05-06-2021, 04:44 AM
(This post was last modified: 05-06-2021, 04:47 AM by kqlnut.)
(05-06-2021, 04:08 AM)Anna Wrote: I'm not sure whether I should have openend a new thread for this topic as not to overload the Axolotl thread...
Anyway, I have the following Axolotl problem:
All of a sudden I can neither receive messages from one friend of mine nor can I send messages to her – they are marked with this triangular, red traffic sign (instead of the two circles) and never go out. Everything else works, only this particular person is affected.
I tried "reset encryption" for that chat, afterwards deleted the chat and asked her to do the same on her (Android) phone – it did not help, the problem persists.
However, I can still communicate with her via the Signal desktop app on Linux Mint. The messages I send via the desktop app not only go out, they also show up in Axolotl on my phone. Her messages on the other hand only reach my desktop app, not the Pinephone.
My friend's contact looks exactly the same as all other contacts in /.config/textsecure.nanuc/registeredContacts.yml -- nothing remarkable and no zeroes at the beginning or end of the UUID.
I had the same problem with somebody else a few weeks ago. Back then I could "solve" the problem with a complete reinstallation -- something I'd like to avoid this time. (I would not mind the reinstallation part, but connecting Axolotl to the desktop application again and reentering all the contacts is quite annoying -- especially if a likely perspective is having to do that over and over again...)
Is there any solution apart from reinstalling Axolotl? You would probably be best off reporting your problems in the project's bug tracker on Github. You could reinstall the app while keeping the $HOME/.config/textsecure.nanuc directory, that way you keep all your configuration and you wouldn't have to reenter anything. But of course it's also possible that something is botched in your configuration. In that case you could also backup the configuration directory, delete the original and reinstall the app, add just the one problematic contact and see if it works. You can always copy back your backed up configuration directory to have it back in the old state.
Edit: Sorry, didn't see arno's post before. Ignore my advice on reinstalling then.
I for one will be highly appreciative when and if the hardware gets some updates and we can all upgrade to a faster better device. I firmly believe that just having such slow hardware will be a roadblock for a lot of things.
I have been using Axelotl daily for about a month I have not noticed any recent disturbance in functionality. Sending and recieving messages on the pinephone with Axelotl without issues. If anything I am having some troubles with the keyboard as I am using a non english one (pushing a letter on my non english keybord doesnt correspond to the letter visualised on the screen). Looking forward to also being able to call with Axelotl sometime in the future! Appriciate the app and all the work thats been put into it.
05-13-2021, 05:42 PM
(This post was last modified: 05-13-2021, 05:48 PM by Avatars.)
From github it says to download using this script (i'm doing this from the phone):
git clone https://github.com/nuehm-arno/axolotl-mobian-package
That doesn't work unless you add wget to the beginning:
wget git clone https://github.com/nuehm-arno/axolotl-mobian-package
Then it says the github certificate has expired and therefore halts and goes no further.
Maybe there's an easier way but that is exactly what I was trying to do. Get it and install it in as few steps as possible.
So I entered the github page instead (more exp cert error warnings) and manually downloaded through the phone's browser.
Changed to the download directory with:
cd Downloads
Installed with:
sudo apt install ./axolotl_0.9.9-3_arm64.deb
The entry is there but it gives me a 'blank' screen. I installed cog: sudo apt install cog. No change
I'm not sure how long it takes to create folders but my guess is it's just not working at all for me. Chats work and tbqh I don't even know anybody who uses telegram. Such is the average state of most who own a 'smart'phone. The phone's smart, the problem is they aren't.
sudo apt remove --purge axolotl
better luck next time. Seriously though, I have to put it on my roomates phone just so I can get someone to use it (with me). What a waste of time. OMG
Encrypted comms should be standard across the board no matter who you are or what you do. PERIOD. 99.99% of the darn data loss, hacking BS problems are simply because this is not the case. Who knew.
05-14-2021, 05:50 AM
(This post was last modified: 05-14-2021, 05:50 AM by arno_nuehm.)
(05-13-2021, 05:42 PM)Avatars Wrote: From github it says to download using this script (i'm doing this from the phone):
git clone https://github.com/nuehm-arno/axolotl-mobian-package
That doesn't work unless you add wget to the beginning:
wget git clone https://github.com/nuehm-arno/axolotl-mobian-package
Then it says the github certificate has expired and therefore halts and goes no further.
Maybe there's an easier way but that is exactly what I was trying to do. Get it and install it in as few steps as possible.
So I entered the github page instead (more exp cert error warnings) and manually downloaded through the phone's browser.
Changed to the download directory with:
cd Downloads
Installed with:
sudo apt install ./axolotl_0.9.9-3_arm64.deb
The entry is there but it gives me a 'blank' screen. I installed cog: sudo apt install cog. No change
I'm not sure how long it takes to create folders but my guess is it's just not working at all for me. Chats work and tbqh I don't even know anybody who uses telegram. Such is the average state of most who own a 'smart'phone. The phone's smart, the problem is they aren't.
sudo apt remove --purge axolotl
better luck next time. Seriously though, I have to put it on my roomates phone just so I can get someone to use it (with me). What a waste of time. OMG
Encrypted comms should be standard across the board no matter who you are or what you do. PERIOD. 99.99% of the darn data loss, hacking BS problems are simply because this is not the case. Who knew.
It might also take some time to download the Electron binary (80MB) at first start (using the Axolotl icon).
I really think some effort should be put into either adapting session or creating a native tox client for pinephone. Private, decentralized, encryptexld onion routing, no phone number, no central server. Its pretty much unattackable, and a perfect match for the pinephone.
(05-13-2021, 05:42 PM)Avatars Wrote: Quote:From github it says to download using this script (i'm doing this from the phone):
git clone https://github.com/nuehm-arno/axolotl-mobian-package
That doesn't work unless you add wget to the beginning:
wget git clone https://github.com/nuehm-arno/axolotl-mobian-package
Then it says the github certificate has expired and therefore halts and goes no further.
Maybe there's an easier way but that is exactly what I was trying to do. Get it and install it in as few steps as possible.
You might be missing the git command. For me, I needed to install git first on Mobian, E.g.
sudo apt install git
Then
git clone https://github.com/nuehm-arno/axolotl-mobian-package
worked for me.
Rich
05-28-2021, 07:52 AM
(This post was last modified: 05-29-2021, 04:13 AM by arno_nuehm.)
Axolotl is out in v1.0.0 with rudimental Signal v2group support.
Here are more informations:
https://github.com/nuehm-arno/axolotl-mobian-package
Cheers!
Edit2: If you have trouble being added to v2groups, send a private message to the person inviting you first.
Edit: Here is the roadmap to basic v2group support
https://github.com/nanu-c/axolotl/pull/460
(05-28-2021, 07:52 AM)arno_nuehm Wrote: Axolotl is out in v1.0.0
Hi there,
I've updated from last version (already installed as .deb) to this new version (on up-to-date mobian), now Axolotl won't start anymore (nothing seems to happen when starting via icon).
I've already tried: Completely deinstall Axolotl, reboot, reinstall, start (fail), rebooted again, start (fail).
If I try to start Axolotl in terminal, these error message appears (after a strange "file is not a database" debug info):
Code: ERRO[001] '/home/mobian/.config/textsecure.nanuc/electron/vendor/electron-linux-arm64/electron' exited with code: 1
then stopping worker und
Code: [axolotl-electron] main: creating window failed: context canceled.
Any suggestions what I could try to fix this? 
Best Regards,
Dante
(BTW... THANKS FOR YOUR WORK ON THIS PROJECT ARNO!!!  )
|
