[Slackbuilds-users] updates to signal-desktop
J. Milgram
milgram at cgpp.com
Thu Jun 4 04:03:24 UTC 2026
Re simply upgrading to the new packages: Some might consider it living
dangerously, but as the README in the binutils-gcc-glibc directory
points out:
=====
You can always back them out by upgradepkg'ing to the older versions,
but anything that you've compiled since installing these will stop working.
=====
(https://mirrors.slackware.com/slackware/slackware64-15.0/testing/packages/binutils-gcc-glibc/README)
So basically it was 15 upgradepkg's and done. I also blacklisted them in
/etc/slackpkg/blacklist as Willy suggested. The system didn't miss a
beat. Built one large-ish numerical app just as a sanity check and it
went fine.
I did notice that slackpkg upgrade-all offered to reinstall the original
gcc-g++-11.2.0 - this, because I neglected to list it as "gcc-g\+\+" in
the blacklist file. I'm sure that would have broken lots of things but
it was easy just to uncheck it from the upgrade list.
Just a report ... not advocating any particular approach.
JM
On 6/3/26 18:55, Luveh Keraph wrote:
> Thanks. I'll take a stab at it in a sandbox over the weekend.
>
> On Wed, Jun 3, 2026 at 4:33 PM Lumin Etherlight via SlackBuilds-users
> <slackbuilds-users at slackbuilds.org> wrote:
>
> Luveh Keraph <1.41421 at gmail.com> writes:
>
> > I concur. signal-desktop is not working any more
> > under 15.0. Will it be possible to have it working
> > under 15.0 without having to use glibc testing
> > packages? Quite frankly, having to use them sounds
> > scary.
>
> You can use the following hack, which worked
> for me. Install the new testing glibc into a root
> inside /opt/ isolated from the rest of the system,
> then patch all executable and libraries inside the
> latest Signal package to use the glibc inside /opt
> instead of the system one.
>
> First, upgrade to the latest Signal package:
>
> upgradepkg --install-new
> signal-desktop-8.11.0-x86_64-1_SBo.tgz
>
> Then, get the testing glibc package:
>
> lftp
> ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/testing/packages/binutils-gcc-glibc
> \
> -e 'get -c glibc-2.42-x86_64-1_slack15.0.txz'
>
> Install it to a path in /opt (note the --root):
>
> installpkg --root /opt/glibc glibc-2.42-x86_64-1_slack15.0.txz
>
> Finally, use patchelf to update the runtime
> linker in all executable files, and use it again
> to override the linker library search path to use
> the latest installed glibc libraries:
>
> find /opt/Signal/ -type f -executable \
> -exec patchelf --set-interpreter
> /opt/glibc/lib64/ld-linux-x86-64.so.2 {} \; \
> -exec patchelf --force-rpath --set-rpath
> \$ORIGIN:/opt/glibc/lib64 {} \;
>
> The $ORIGIN path is required, as a literal
> string, with $ escaped from the shell; it is not a
> shell variable. This literal string has a special
> meaning to the linker to allow the executable, in
> this case Signal, to search its own directory for
> libraries. Additionally, do not be alarmed if you
> see errors about not finding `.interp' sections,
> they are harmless, and happen because the dynamic
> linker in shared libraries can not be updated in
> the ELF binary itself, but is set by the actual
> executable that requests the library.
>
> Now, run Signal as you usually do, it should work.
>
> Hopefully :)
>
> This is definitely a hacky path, but it is a
> much more narrow intervention than updating glibc
> for your entire system. It is also isolated from
> the rest of the system, so harm is minimized. If
> you want to revert what we did here, simply run:
>
> rm -rf /opt/glibc
> upgradepkg --reinstall signal-desktop-8.11.0-x86_64-1_SBo.tgz
>
> And you're back to a clean slate.
>
>
> Best Wishes,
> Lumin Etherlight
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
--
=====
milgram at cgpp.com
301-257-7069
More information about the SlackBuilds-users
mailing list