Slack (flatpak) v4.15.0 fails to start on Fedora 34

[ocosta (André Costa)]

I upgraded Slack a couple of minutes ago to version 4.15.0, and now it won’t start. The last lines of stderr output show:

[snip]
(slack:2): Gtk-WARNING **: 09:53:04.282: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /run/host/share/icons/Adwaita/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)

Fedora was also upgraded, but it doesn’t seem related:

Packages Altered:
    Upgrade  nspr-4.31.0-1.fc34.x86_64               @updates
    Upgrade  nss-3.67.0-1.fc34.x86_64                @updates
    Upgrade  nss-softokn-3.67.0-1.fc34.x86_64        @updates
    Upgrade  nss-softokn-freebl-3.67.0-1.fc34.x86_64 @updates
    Upgrade  nss-sysinit-3.67.0-1.fc34.x86_64        @updates
    Upgrade  nss-tools-3.67.0-1.fc34.x86_64          @updates
    Upgrade  nss-util-3.67.0-1.fc34.x86_64           @updates
    Upgraded nspr-4.30.0-2.fc34.x86_64               @@System
    Upgraded nss-3.65.0-1.fc34.x86_64                @@System
    Upgraded nss-softokn-3.65.0-1.fc34.x86_64        @@System
    Upgraded nss-softokn-freebl-3.65.0-1.fc34.x86_64 @@System
    Upgraded nss-sysinit-3.65.0-1.fc34.x86_64        @@System
    Upgraded nss-tools-3.65.0-1.fc34.x86_64          @@System
    Upgraded nss-util-3.65.0-1.fc34.x86_64           @@System

Anyone else experiencing this?

[ankursinha]

I expect this is Slack from FlatHub (since Slack is a proprietary tool and will not be included in Fedora). It’s best to file an issue with the FlatHub maintainers here since it’s probably something they need to look into: GitHub - flathub/com.slack.Slack

[ocosta (André Costa)]

Thanks @ankursinha ! I just checked, and it has already been reported Apparently, it also affects Debian Bullseye.

[bryanmoore]

Just wondering, but is there any reason why you don’t want to use the rpm directly from Slack? It’s on 4.17.0 right now…