bug: Dolphin freezes when home-manager is installed

[andersrh]

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

When I install home-manager Dolphin freezes, when I go to my home folder. When I uninstall home-manager the issue gets resolved.

I haven't been able to find others, who have exactly the same issue.

My nixpkgs is pointed to unstable and I have added the master branch for home-manager.

Maintainer CC

No response

System information

this path will be fetched (0.00 MiB download, 0.00 MiB unpacked):
  /nix/store/v8p3m2vgkcd3ykrdylm5vi9alrxbwhip-nix-info
copying path '/nix/store/v8p3m2vgkcd3ykrdylm5vi9alrxbwhip-nix-info' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 6.7.0-cb1.0.fc39.lto.x86_64, Fedora Linux, 39.20240120.0 (Kinoite), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.19.2`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

[n-a-m-e]

Happens to me too. Running home-manager on Ubuntu.

I don't know why but any directory containing .js files crashes dolphin. If I open a Folder without any .js files it works just fine. There may be other file extensions which also cause a crash but I haven't found any.

I also can't open the KDE editor "Kate" as it also instantly crashes.

I think it is probably something to do with KDE apps

I was previously able to fix it by changing changing from master and setting nixpkgs.url to "github:nixos/nixpkgs/nixos-23.11" and home-manager url to "github:nix-community/home-manager/release-23.11"

But after the last time I updated a couple of days ago the issue is back.

[yeus]

same issue here! Not sure whats causing it, but resetting dolphin to default settings helped:

rm -r .local/share/dolphin/ .config/session/dolphin_* .config/dolphinrc

[yeus]

some more investigation shows that kate always freezes when I call the open/close dialog... trying to reset that as well right now :)

EDIT:

after doing this:

rm -r .config/katerc .config/katesyntaxhighlightingrc .config/katemetainfos .config/katevirc

this also seems to work for now...

[yeus]

hm. now I have a similar problem to @n-a-m-e :

• dolphin freezes whenever I enter a directory with a json file.
• kate and other KDE programs freeze as well, as soon as any sort of interaction with files is initiated! like open/close or with gwneview implicitly loading pics in the background

also checkout this issue here:

• https://bugs.kde.org/show_bug.cgi?id=477298

[mghesh-yseop]

I have the same issue. With home-manager, json files are not resolved (running xdg-mime query filetype foo.json hangs forever), but if I uninstall home-manager I get the expected answer application/json.

Interestingly, when I uninstall home-manager while the query is running, it eventually succeeds.

In my case, the hanging occurs in kmimetypefinder5.

After running sudo update-mime-database -V ~/.nix-profile/share/mime/, it works for now. I'm not sure about my installation, maybe I'm missing something about XDG settings :man_shrugging:

[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.