Oh, thanks a lot for the efforts! You really are one of a kind to conduct an experiment to help out a stranger on the internet. Yeah, this actually works. I just added those lines to .xsessionrc and all problems were solved.

If you don’t mind my asking. Do you work in IT as a sysadmin or a developer or a cybersecurity expert? Or something else? I am just curious as to how may have gained such knowledge.

Hi, Thanks for the response. Sorry for disturbing you. I have tried what you have suggested here. There are two files with matching timestamps but different PATHs. I am using i3wm in Debian 11. Please tell me how to deal with this issue.

Adding those lines to .bashrc, helped with the flatpak commands. I can run them without having to type “flatpak run”. I did this for nix: export XDG_DATA_DIRS=$HOME/.nix-profile/share:$HOME/.share:“${XDG_DATA_DIRS:-/usr/local/share/:/usr/share/}” However, I still cannot see the entries in rofi. The package is Chromium browser.

I have this line export XDG_DATA_DIRS=$HOME/.nix-profile/share:$HOME/.share:“${XDG_DATA_DIRS:-/usr/local/share/:/usr/share/}” Do I need to add anything else? I do have the directory you have mentioned.

Thanks for the response. I will try to as you have advised. Adding those lines to .bashrc helped with flatpaks but not with nix.

Thanks for the response. Adding those lines to .bashrc helped with flatpaks but not with nix.

Thanks, I will check it out. Adding those lines to .bashrc helped with flatpaks but not with nix.

Adding those lines to .bashrc helped with flatpaks but not with nix.

I only have .profile. Actually adding those lines as to .bashrc as suggested by @[email protected] helped for the flatpak commands. But the issue with .desktop files for programs installed using nix still persists.

Thanks, that works with the flatpaks. However, it doesn’t seem to work with nix packages. I mean rofi doesn’t detect the .desktop files for packages installed using nix.

Changed it allow execution for the owner. Still no results. Tried with both .profile and .bash_profile.

Thanks for the response. But in my case, even that does not work as well.

Thanks for the response. But that does not work as well.

That’s impossible or at least very difficult, right now. Video content is very expensive. LBRY is the only feasible option.