• signal-desktop does not start

    From Andrea Venturoli@ml@netfence.it to muc.lists.freebsd.ports on Sat Oct 10 11:26:42 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hello.

    After being hit by #299127, I moved to 2026Q4 branch and rebuilt everything.

    So I started signal-desktop 8.29.0...

    First I was asked for a KDE wallet password: no idea why, but I created one. Then Signal started and I got a window with "Can't Open Signal" and was
    given three options:
    a) Go To Support Page;
    b) Delete data and restart;
    c) Copy error and quit.

    I tried b), but it goes in a loop.

    So I manually deleted ~/.config/Signal and tried again, but this did not
    help either.

    This is what I get in console:
    % signal-desktop
    [18674:1010/112032.728317:ERROR:crypto/nss_util.cc:377] After loading Root Certs, loaded==false: NSS error code: -8018
    NODE_ENV production
    NODE_CONFIG_DIR /usr/local/share/signal-desktop/resources/app.asar/config NODE_CONFIG {}
    ALLOW_CONFIG_MUTATIONS undefined
    HOSTNAME alamar.ventu
    NODE_APP_INSTANCE undefined
    SUPPRESS_NO_CONFIG_WARNING undefined
    SIGNAL_ENABLE_HTTP undefined
    userData: /home/andrea/.config/Signal
    couldn't lock 16384 bytes of memory (secret_value): Cannot allocate memory
    No name and/or group mapping for uid,gid:(1000,1001)
    No name and/or group mapping for uid,gid:(1000,1001)
    No name and/or group mapping for uid,gid:(1000,1001)
    No name and/or group mapping for uid,gid:(1000,1001)
    No name and/or group mapping for uid,gid:(1000,1001) [18674:1010/112039.714068:ERROR:ui/gfx/x/atom_cache.cc:236] Add application/vnd.portal.filetransfer to kAtomsToCache
    [18674:1010/112039.716217:ERROR:ui/gfx/x/atom_cache.cc:236] Add application/vnd.portal.files to kAtomsToCache
    __cxa_thread_call_dtors: dtr 0xfe1b0f35e80 from unloaded dso, skipping

    Any hint?

    bye & Thanks
    av.

    P.S.
    Not sure if "No name and/or group mapping for uid,gid:(1000,1001)" is relevant.
    I'm on an AD domain, and user/groups are resolved via NSS/Samba.
    AFAICT this works, at least for logins, for permissions on filesystems
    and for all other software; I have no idea why Signal think it doesn't.
    Then again, is that the reason it doesn't start?


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