1. Forum
  2. USENET
  3. muc.lists.freebsd.ports

  • signal-desktop not working

    From Andrea Venturoli@ml@netfence.it to muc.lists.freebsd.ports on Wed Jan 21 11:44:50 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hello.

    Is anyone able to use signal-desktop?

    7.72 (from 2025Q4) used to work, but "died" due to protocol obsolescense.

    7.84 (from 2026Q1):
    _ doesn't receive new messages;
    _ eventually "chat session refreshed" will appear under each contact
    that has new messages (which I see from my phone);
    _ sent messages are stuck there; they never leave my computer;
    _ if I clean everything up and start over, it will sync everything up to
    now, but then stay frozen at that point in time.

    Is this an upstream problem? A port problem? My problem?
    Any hint on how to debug this?
    "chat session refreshed" is the only useful keyword I have for a search,
    but it points to some bugs which are all deemed as closed.

    bye & Thanks
    av.

    P.S.
    I'm on 14.3/amd64.


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Norbert Grundmann@ngrundmann@gmx.de to muc.lists.freebsd.ports on Wed Jan 21 11:49:48 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 1/21/26 11:44, Andrea Venturoli wrote:
    Hello.

    Is anyone able to use signal-desktop?

    7.72 (from 2025Q4) used to work, but "died" due to protocol obsolescense.

    7.84 (from 2026Q1):
    _ doesn't receive new messages;
    _ eventually "chat session refreshed" will appear under each contact
    that has new messages (which I see from my phone);
    _ sent messages are stuck there; they never leave my computer;
    _ if I clean everything up and start over, it will sync everything up
    to now, but then stay frozen at that point in time.

    Is this an upstream problem? A port problem? My problem?
    Any hint on how to debug this?
    "chat session refreshed" is the only useful keyword I have for a
    search, but it points to some bugs which are all deemed as closed.

    -abye & Thanks
    -a-a-a-aav.

    P.S.
    I'm on 14.3/amd64.

    Hello,
    I upgraded on FreeBSD 14.3/amd64 to signal version 7.84.0 (from
    quaterly) and don't have any problems...
    Cheers, Norbert
    --
    I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Andrea Venturoli@ml@netfence.it to muc.lists.freebsd.ports on Wed Jan 21 18:38:42 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 1/21/26 12:03, freebsd@sysctl.cz wrote:
    Hello,
    I have signal 7.84 and no problem. FreeBSD 14.3 amd64.
    M.F

    Thanks.

    A couple of questions:
    _ do you use 2026Q1 o current port tree?

    _ do you see the following message at startup?

    [57608:0121/183620.851004:ERROR:crypto/nss_util.cc:344] After loading Root Certs, loaded==false: NSS error code: -8018
    (Of course I mean when running it from a terminal, but that's the only
    way it has worked for me since a long time).


    bye & Thanks again
    av.


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2