Bug 455065

Summary: Installing a Flatpak application results in a white icon across the OS
Product: [I don't know] kde Reporter: Hari Rana (TheEvilSkeleton) <theevilskeleton>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED UPSTREAM    
Severity: normal CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Flatpak   
OS: Linux   
URL: https://github.com/flatpak/flatpak/issues/3109
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Firefox Flatpak in task manager
Firefox Flatpak in favorites
Firefox Flatpak in search field and menu

Description Hari Rana (TheEvilSkeleton) 2022-06-09 04:18:43 UTC
Created attachment 149568 [details]
Firefox Flatpak in task manager

SUMMARY
Installing any Flatpak application results in a white icon.

STEPS TO REPRODUCE
1. Install Flatpak and add the Flathub remote if haven't
2. Install an application

OBSERVED RESULT
Icons are white.

EXPECTED RESULT
The menu and panel should show the relevant icon.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (VM using GNOME Boxes)
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION
The workaround is to restart or log out and log back in.
Comment 1 Hari Rana (TheEvilSkeleton) 2022-06-09 04:19:20 UTC
Created attachment 149569 [details]
Firefox Flatpak in favorites
Comment 2 Hari Rana (TheEvilSkeleton) 2022-06-09 04:19:51 UTC
Created attachment 149570 [details]
Firefox Flatpak in search field and menu
Comment 3 Nate Graham 2022-06-09 17:19:39 UTC
Cannot reproduce. This is going to end up being a configuration issue of some sort. Are you using the fish shell, by any chance?
Comment 4 Hari Rana (TheEvilSkeleton) 2022-06-09 17:24:02 UTC
(In reply to Nate Graham from comment #3)
> Cannot reproduce. This is going to end up being a configuration issue of
> some sort. Are you using the fish shell, by any chance?

No. I only have it installed, but bash is the default.
Comment 5 Nate Graham 2022-06-10 15:36:51 UTC
Does it start working if you uninstall Fish shell completely using your distro's package manager tools?

Is there anything in your .bashrc, .profile, or .bash_profile file that references Fish shell?
Comment 6 Hari Rana (TheEvilSkeleton) 2022-06-10 16:03:04 UTC
(In reply to Nate Graham from comment #5)
> Does it start working if you uninstall Fish shell completely using your
> distro's package manager tools?
> 
> Is there anything in your .bashrc, .profile, or .bash_profile file that
> references Fish shell?

Yes, uninstalling it seems to have fixed my problem. As for my .bashrc and such, no. Nothing references fish.
Comment 7 Nate Graham 2022-06-10 16:13:56 UTC
Smells like https://github.com/flatpak/flatpak/issues/3109.

What version of flatpak do you have installed? If you have 1.13.2 or later, consider leaving a comment about the issue there.
Comment 8 Hari Rana (TheEvilSkeleton) 2022-06-10 16:53:47 UTC
Thanks.
I'm using Flatpak 1.12.7.

I'm surprised because I'm unable to reproduce the issue you linked. If I check XDG_DATA_DIRS in fish, I get this:

```
arch@arch ~> echo $XDG_DATA_DIRS
/home/arch/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
```

The author of the issue you linked however only had "/usr/local/share:/usr/share" in their XDG_DATA_DIRS. I don't know if that says anything?

Icons are blank but I can open apps. I did read the whole issue but I may have misunderstood. What do you think?
Comment 9 Nate Graham 2022-06-13 17:07:48 UTC
It may be a slightly different issue. I would encourage you to report it there.

Definitely Fish seems connected somehow. Flatpak really just doesn't like Fish shell!
Comment 10 Hari Rana (TheEvilSkeleton) 2022-07-17 21:10:33 UTC
(In reply to Nate Graham from comment #9)
> It may be a slightly different issue. I would encourage you to report it
> there.
> 
> Definitely Fish seems connected somehow. Flatpak really just doesn't like
> Fish shell!

So I may have forgotten to open an issue in Flatpak's issue tracker. However, I updated my VM today and this issue seems to be fixed itself!