Github messages for voidlinux
 help / color / mirror / Atom feed
From: artenaki <artenaki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Signal-Desktop for i686
Date: Sun, 21 Nov 2021 10:35:51 +0100	[thread overview]
Message-ID: <20211121093551.ZHBuuZWytEWKgcSFiBaGfwmyZk9itq9Kgcts_50w61k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34126@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

New comment by artenaki on void-packages repository

https://github.com/void-linux/void-packages/issues/34126#issuecomment-974781711

Comment:
I checked now. Signal-Desktop 1.14.4 does not start on Void Linux i686 at all. Segfault. The build was in August 2018 and apparently incompatible with modern libraries. There is also an error when running Kadu.
https://alpha.de.repo.voidlinux.org/current/Signal-Desktop-1.14.4_1.i686.xbps
https://voidlinux.org/packages/?arch=i686&q=kadu

Signal-Desktop-1.14.4_1.i686.xbps works in Ubuntu 16.04 32 bit (2016) however (runs but does not connect).

UPD (Offtop): I prefer to use wire-desktop instead of Signal. Package from Void Linux i686 also works in Ubuntu 16.04 32 bit (only need to install electron 10). There is a web version. No phone number required, no Google captcha.

  parent reply	other threads:[~2021-11-21  9:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18  3:30 [ISSUE] " artenaki
2021-11-19 16:15 ` mikoxyz
2021-11-20  1:23 ` artenaki
2021-11-20 10:29 ` mikoxyz
2021-11-20 12:20 ` Johnnynator
2021-11-20 12:25 ` ericonr
2021-11-20 13:15 ` mikoxyz
2021-11-20 16:38 ` Johnnynator
2021-11-20 16:38 ` [ISSUE] [CLOSED] " Johnnynator
2021-11-21  9:22 ` artenaki
2021-11-21  9:33 ` artenaki
2021-11-21  9:35 ` artenaki [this message]
2022-02-09  1:32 ` artenaki
2022-02-09  1:37 ` artenaki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211121093551.ZHBuuZWytEWKgcSFiBaGfwmyZk9itq9Kgcts_50w61k@z \
    --to=artenaki@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).