-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Dolphin freezes when home-manager is installed #4941
Comments
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. 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. |
same issue here! Not sure whats causing it, but resetting dolphin to default settings helped:
|
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... |
hm. now I have a similar problem to @n-a-m-e :
also checkout this issue here: |
I have the same issue. With Interestingly, when I uninstall In my case, the hanging occurs in After running |
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 you are not the original author of the issue
Memorandum on closing issuesDon'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. |
Why is this stale when the bug persists? I see the same thing, and for me, running As suggested in the KDE bug linked above, this is likely due to a cycle between JSON and JavaScript/ECMAScript MIME types. |
Experiencing a similar issue after enabling the |
The `xdg-mime` module now exposes packages to determine what will be run for update-mime-database and update-desktop-database. This allows users to select a different version of these packages if the are incompatible. This should, in combination with an override to the version of `shared-mime-info` (can be found here ?????), resolve nix-community#4955, nix-community#5102 , nix-community#4682, and possibly nix-community#4941. The problem seems to stem from a mismatch in the version of `shared-mime-info` with the host.
The `xdg-mime` module now exposes packages to determine what will be run for update-mime-database and update-desktop-database. This allows users to select a different version of these packages if the are incompatible. This should, in combination with an override to the version of `shared-mime-info` (can be found here ?????), resolve nix-community#4955, nix-community#5102 , nix-community#4682, and possibly nix-community#4941. The problem seems to stem from a mismatch in the version of `shared-mime-info` with the host.
The `xdg-mime` module now exposes packages to determine what will be run for update-mime-database and update-desktop-database. This allows users to select a different version of these packages if the are incompatible. This should, in combination with an override to the version of `shared-mime-info` (can be found here notalltim/home-mananger-config#4), resolve nix-community#4955, nix-community#5102, nix-community#4682, and possibly nix-community#4941. The problem seems to stem from a mismatch in the version of `shared-mime-info` with the host.
The `xdg-mime` module now exposes packages to determine what will be run for update-mime-database and update-desktop-database. This allows users to select a different version of these packages if the are incompatible. This should, in combination with an override to the version of `shared-mime-info` (can be found here notalltim/home-manager-config#4), resolve nix-community#4955, nix-community#5102, nix-community#4682, and possibly nix-community#4941. The problem seems to stem from a mismatch in the version of `shared-mime-info` with the host. I also switched from using `buildPackages` to `pkgs` to improve cross-compilation compatibility.
* xdg-mime: allow overrides to shared-mime-info and desktop-file-utils The `xdg-mime` module now exposes packages to determine what will be run for update-mime-database and update-desktop-database. This allows users to select a different version of these packages if the are incompatible. This should, in combination with an override to the version of `shared-mime-info` (can be found here notalltim/home-manager-config#4), resolve #4955, #5102, #4682, and possibly #4941. The problem seems to stem from a mismatch in the version of `shared-mime-info` with the host. I also switched from using `buildPackages` to `pkgs` to improve cross-compilation compatibility. * xdg-mime: Add tests for xdg-mime module The xdg-mime module was missing tests so I added basic test for all the options and checked the basic behavior. It covers ensuring that the proper files/folders are created and that the package overrides work.
* xdg-mime: allow overrides to shared-mime-info and desktop-file-utils The `xdg-mime` module now exposes packages to determine what will be run for update-mime-database and update-desktop-database. This allows users to select a different version of these packages if the are incompatible. This should, in combination with an override to the version of `shared-mime-info` (can be found here notalltim/home-manager-config#4), resolve nix-community#4955, nix-community#5102, nix-community#4682, and possibly nix-community#4941. The problem seems to stem from a mismatch in the version of `shared-mime-info` with the host. I also switched from using `buildPackages` to `pkgs` to improve cross-compilation compatibility. * xdg-mime: Add tests for xdg-mime module The xdg-mime module was missing tests so I added basic test for all the options and checked the basic behavior. It covers ensuring that the proper files/folders are created and that the package overrides work.
Are you following the right branch?
Is there an existing issue for this?
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
The text was updated successfully, but these errors were encountered: