Signal-desktop on F43

Ask Fedora
1

I upgraded from F42 to F43. This was only possible by erasing signal-desktop first. After the upgrade I tried to reinstall signal again. signal-desktop-7.83.0-1.1.x86_64 for Fedora 43 is available but some necessary packages are missing and not available:

Problem: package signal-desktop-7.83.0-2.1.x86_64 from network_im_signal requires signal-libringrtc(x86-64) = 2.60.7, but none of the providers can be installed

  • conflicting requests
  • nothing provides libabsl_hash.so.2407.0.0()(64bit) needed by signal-libringrtc-2.60.7-1.1.x86_64 from network_im_signal
  • nothing provides libabsl_raw_hash_set.so.2407.0.0()(64bit) needed by signal-libringrtc-2.60.7-1.1.x86_64 from network_im_signal
  • nothing provides libabsl_str_format_internal.so.2407.0.0()(64bit) needed by signal-libringrtc-2.60.7-1.1.x86_64 from network_im_signal
  • nothing provides libabsl_strings.so.2407.0.0()(64bit) needed by signal-libringrtc-2.60.7-1.1.x86_64 from network_im_signal
  • nothing provides libabsl_throw_delegate.so.2407.0.0()(64bit) needed by signal-libringrtc-2.60.7-1.1.x86_64 from network_im_signal

Any ideas how to fix the problem? Thanks in advance

Michael

2

I don’t have an answer to your issue with signal-desktop, but doing LANG=C commandtorun if you’re working in the shell usually will give you english output, just for having it in a form that might get more attention. (I don’t know that this works for everything on the planet, but it can make getting your issue in front of more eyes a bit easier sometimes)

3

Thank you. I have corrected my message accordingly.

4

On my F42 installation the missing libabsl_*.so.2407.0.0 files are provided by package abseil-cpp-20240722.1-1.fc42.x86_64 (current stable version for F42). For F43 the stable version is abseil-cpp-20250814.1-1.fc43.x86_64. AFAIS an abseil-cpp-20240722 package for F43 is not available in current Fedora repos. May be the installation of the F42 version works, i.e. something like

$ rpm -ivh https://rpmfind.net/linux/fedora/linux/releases/42/Everything/x86_64/os/Packages/a/abseil-cpp-20240722.1-1.fc42.x86_64.rpm

Of course this is only applicable if abseil-cpp was not already installed as dependency for other F43 packages and the F42 package itself has only dependencies satisfied by F43.

5

Last I checked, Fedora does not package Signal Desktop as an RPM. And I doubt that you had to remove the Flatpak, Flatpaks don’t interfere with RPMs.

I suggest you find out where you got this Signal package from and raise this issue with them.

1 Like
7

When upgrading from F42 to F43, the repository https://download.opensuse.org/repositories/network:im:signal/Fedora_42/network:im:signal.repo is not changed. You have to remove it manually and install the new repository https://download.opensuse.org/repositories/network:im:signal/Fedora_43/network:im:signal.repo. Then using the dnf install signal-desktop command everything works fine. Thanks for all the tips!

Michael

8

You could also replace 43 by $releasever and be done with it for the next upgrade.

I’m not using opensuse packages on Fedora, though, but signal from flathub. This solves dependency issues via the runtime.

9

That’s not an openSUSE package, it’s just a package built for Fedora on the openSUSE Build Service.

You can build packages for a whole bunch of different distributions and packaging formats there.

10

So it’s an OpenSuse package for Fedora, not a Fedora package.

Semantics aside, OBS allows to build packages in different buildroots similar to COPR. It does not imply that it adheres to Fedora guidelines or integrates well, for example, and neither that it does not. (COPR packages are expected to adhere to Fedora guidelines.)

11

No. It is not. It’s specifically built for Fedora, not simply rebuilding the openSUSE package.

It uses a “portable” .spec file which can build for multiple RPM based distributions.

For those of you that do packaging or are used to reading rpm SPEC files.

12

It does not matter how often you repeat that claim. It’s a package built by OpenSuse Build Service - which obviously is an OpenSuse service - for Fedora. It’s not a Fedora package. Infer from that what you will.