Change:
After logging in using a fresh user, plasma6 showed only a black screen with a cursor. (see screenshot 1) refused to start, as it could not connect to . Full log see . However, seem started normally. Full log see . In d-spy, could be found in session dbus (see screenshot 2). dbus services complained a lot of "duplicate name". See . All logs () see . Use flake. () I have tried these modifications but nothing works (on branch ): to default kernel () without any custom patch. cuda and . all home-manager stuff and impermanence mount about directories under the user home, to keep the home directory as clean as possible. X11 instead of Wayland. between Nvidia graphic card only and amd+nvidia hybrid offload. to the kernel parameter. The same problem also exist on 's GPD (, ). Plasma started with the default wallpaper and status bar.   I am not sure which people should I notify, as I could not which part of nixpkgs led to this problem. system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Same on me
A strange thing is why plasmashell 6 tries to load qt5 plugins.
There is some guess, from it may be a race condition. Try to check this guess. If not caused by this, write in to enable debug log for KActivityManagerd (sadly, there is no debug log in KActivities library), and then open a tty/ssh and execute to monitor any request to KAMD. Then switch back to SDDM and log in to Plasma. Finally, post the and journalctl output here.
It does not work. There are only two item in Here is after reboot:
I have found the problem. Some theme packages (such as ) contain a file named whose content is some qt5 library pathes. If I add these theme packages into , the qt5 libraries listed in the file will also be to the environment, causing a conflict with qt6 and plasma6. Solution is to remove these packages from .
The problem is here: It should use instead of .
It's still a problem that should be fixed, do not close. I remember that I uses , that's probably why I met the problem, too. CC if you have any idea.

Discussion:
, fetchFromGitHub , breeze-icons , kdeclarative <del> , kirigami2 </del> <ins> , kirigami </ins> , plasma-framework , plasma-workspace }: stdenv.mkDerivation rec { pname = "utterly-nord-plasma"; <del> version = "2.1"; </del> <ins> version = "3.2"; </ins> src = fetchFromGitHub { owner = "HimDek"; repo = pname; <del> rev = "6d9ffe008f0bee47c8346c9a7ec71f206d999fd0"; hash = "sha256-B5pIwV0BHxDluKWKTy+xuBPaE3N6UOHXip1SIAm2kM8="; </del> <ins> rev = "e513b4dfeddd587a34bfdd9ba6b1d1eac8ecadf5"; hash = "sha256-moLgBFR+BgoiEBzV3y/LA6JZfLHrG1weL1+h8LN9ztA="; </ins> }; propagatedUserEnvPkgs = [ breeze-icons <del> kdeclarative.bin kirigami2 plasma-framework.bin </del> <ins> kdeclarative kirigami plasma-framework </ins> plasma-workspace ];

unscii = callPackage ../data/fonts/unscii { }; <del> utterly-nord-plasma = libsForQt5.callPackage ../data/themes/utterly-nord-plasma { }; </del> <ins> utterly-nord-plasma = kdePackages.callPackage ../data/themes/utterly-nord-plasma { # renamed in KF6 plasma-framework = kdePackages.libplasma; }; </ins> utterly-round-plasma-style = callPackage ../data/themes/utterly-round-plasma-style { };