bug: rofi not showing applications in drun

[shauryagoel]

Are you following the right branch?

• [X] My Nixpkgs and Home Manager versions are in sync

Is there an existing issue for this?

• [X] I have searched the existing issues

Issue description

I was trying rofi from home manager. I was able to enable rofi, but drun is not showing my applications like neovim, ranger, it is only showing Rofi and Rofi Theme Selector. I am using rofi -show drun for this. I have tried looking into ~/.nix-profile/share/applications, it has some .desktop entries, which maybe rofi drun is fetching the data from, but I guess it's not true as this location also has neovim and ranger desktop files. Rest of the rofi modes are working correctly like- rofi -show window and rofi -show ssh.

Maintainer CC

No response

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.2.10-arch1-1, Arch, noversion, rolling`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(root): `"nixpkgs"`
 - channels(shaurya): `"nixgl"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

[ncfavier]

rofi should look in XDG_DATA_HOME and XDG_DATA_DIRS for .desktop files. Make sure these variables are set correctly when rofi is started.

[shauryagoel]

XDG_DATA_HOME=/usr/share/applications XDG_DATA_DIRS=/usr/share/applications rofi -show drun I tried running this command in the terminal and the issue still remains. Also, I tried installing rofi outside the home manager (from pacman) and its binary is perfectly fine even without exporting the XDG_DATA_HOME and XDG_DATA_DIRS.

[ncfavier]

Could you try this?

programs.rofi.package = builtins.removeAttrs pkgs.rofi-unwrapped ["override"];

[shauryagoel]

The issue still remains after adding this.

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.