So the wayland session still quit on startup,but now it does not seem to leave any traces,whether in the journal nor in ~/.local/share/sddm/wayland-session.log `.

@worldofpeace any ideas why?

Maybe the description of #44139 will help?

The wayland entry is present in sddm,but does not work.
Still ,I need to check with QT_DEBUG_PLUGINS=1;QML_IMPORT_TRACE=1;

Also need to check for wrapQtApps

@hameerabbasi Checked with the suggested patch,still not working,got in .local/share/sddm/wayland-session.log ;

dbus-daemon[16640]: [session uid=1001 pid=16640] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1001 pid=16644 comm="/nix/store/90n7mvl7n0zl98wx0jjx2syfma34xhka-dbus-1" label="kernel")
dbus-daemon[16640]: [session uid=1001 pid=16640] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
qt.qpa.plugin: Could not load the Qt platform plugin "wayland-org.kde.kwin.qpa" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: wayland-org.kde.kwin.qpa, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

"/nix/store/bkdyka5fa5f707a6hvx8l6v2s37wvwvd-kwin-5.18.5-bin/bin/kwin_wayland" ("--xwayland", "--libinput", "--exit-with-session=/nix/store/2vqimab57z8f8cpbzkax9cwnb1rl997j-plasma-workspace-5.18.5/libexec/startplasma-waylandsession") exited with code 6
startplasmacompositor: Shutting down...
startplasmacompositor: Done.

@pasqui23 see #43757 (comment)

Specifically, env KWIN_FORCE_OWN_QPA=1 kwin_wayland --version fixes this particular error for me.

@matklad adding said variable to environment.sessionVariables still does not fix it for me

Adding KWIN_FORCE_OWN_QPA=1 and increasing limit (0004-start_kdeinit-environ-hard-limit.patch) to 1<<20 makes startplasma_wayland work for me

See #107472 #107476

For anyone wondering: plasma on wayland is not quite stable on NixOS, screenshots can't be taken because of X-KDE-DBUS-Restricted-Interfaces attribute absence, and plasmashell has some bugs (Task manager shows no apps) because of missing X-KDE-Wayland-Interfaces

Kwin even can't find desktop files for anything, because of wrappers?

KWIN_UTILS: Could not find the desktop file for "/nix/store/v24qakxc15pnj60i7ydqzsd9svdjdjp6-plasma-workspace-5.20.4/bin/.plasmashell-wrapped"
KWIN_UTILS: Could not find the desktop file for "/nix/store/0kbrkb257806lgx5q46gw59scgd2vhqm-yakuake/bin/.yakuake-wrapped"
KWIN_UTILS: Could not find the desktop file for "/nix/store/rabb2qzn14fvq4ksvd063fwcj6d9hwq8-spectacle/bin/.spectacle-wrapped"

See #107595

This change wasn't converted from markdown to docbook and broke eval on staging-next. This was already visible on the CI changes on this pull request.

https://github.com/NixOS/nixpkgs/runs/3863386514

This change wasn't converted from markdown to docbook and broke eval on staging-next. This was already visible on the CI changes on this pull request.

https://github.com/NixOS/nixpkgs/runs/3863386514

fixed in #141818

I believe this regressed the clock widget of plasma on Xorg. Can somebody verify please? I bisected to this particular PR. Will test a revert of it shortly.

Edit: Confirmed.

Specifically I reverted 763a001 and 4832352

@pasqui23 @peterhoeg @oxalica What do you think?

No regression on my side,Plasma XOrg on latest nixos unstable.

Try deleting .cache, often plasma blow out on updates

Try deleting .cache, often plasma blow out on updates

I am wondering why this is never happening on Debian. I was rocking Debian Unstable for quite a while and never needed to delete the .cache directory.

I believe this regressed the clock widget of plasma on Xorg.

You are sure that sddm did not switch you to wayland? There the clock is missing for me, not Xorg.

@mohe2015

I believe this regressed the clock widget of plasma on Xorg.

I fixed the clock widget issue by adding programs.zsh.enable = true in my system configuration since I'm using zsh as default shell but it's configured by home-manager instead of system configuration. It seems your default shell should be enabled in system so that sddm can successfully initialized you environments under wayland.
Please open a terminal under graphical session and check if you have __NIXOS_SET_ENVIRONMENT_DONE set. If not, please ensure your shell is enabled by programs.<shell_name>.enable.

Please open a terminal under graphical session and check if you have __NIXOS_SET_ENVIRONMENT_DONE set. If not, please ensure your shell is enabled by programs.<shell_name>.enable.

That might not be enough to check... the terminal may be using a login shell.

I think snooping around /proc/ and the PID of some components of the graphical session may be necessary to validate.

klauncher does not have __NIXOS_SET_ENVIRONMENT_DONE set for me on wayland.

Well, that is not working for bash.

- The option definition `programs.bash.enable' in `/etc/nixos/configuration.nix' no longer has any effect; please remove it.

We'll I would also consider that a regression. Why does it loose settings.... aargh

Should've read release notes...

So the only issue remaining is the missing clock on wayland with bash for me. That's probably not a regression though. Would be nice to get a fix as then I may even try wayland for my non-critical stuff. Any idea how to fix that. Home managers bash.enable didn't seem to work.

@mohe2015
Could you try running kwriteconfig5 --file startkderc --group General --key systemdBoot true and relogin? This enables "run with systemd mode" for plasma. Maybe it can fix environment variables.

@mohe2015 Could you try running kwriteconfig5 --file startkderc --group General --key systemdBoot true and relogin? This enables "run with systemd mode" for plasma. Maybe it can fix environment variables.

Yay, that seems to work. So now we need #117102 ?

Grafik-Plattform: Wayland
Well I would also consider that a regression. Why does it loose settings.... aargh

Should've read release notes...

Can someone clarify: was the intention here to make Wayland the default for users who were not ever specifying services.xserver.displayManager.defaultSession? There are two cases:

a) you've got defaultSession = plasma5. The release note is clear about this case: you must change it to plasma or plasmawayland (thus making an explicit decision whether to adopt Wayland now).

b) you've got no value for defaultSession in your config. The release note is vague: if I don't set a value, will i end up with X11 or Wayland?

I'm in case (b), saw the release note, looked at some of the remaining issues (incl. the missing clock issue), and didn't see anything in this issue or elsewhere explicitly saying the default was changing to Wayland. So I assumed that if I left defaultSession unspecified in my config, I'd remain on X11.

Now I've got a missing clock. :-/ Took me a while to circle back to even look at whether I was on X11 or Wayland, but sure enough, I'm on Wayland without intending to be. (In many ways that's a positive -- the switch was almost seamless, and if it hadn't been for the missing clock I probably never would've noticed!)

b) you've got no value for defaultSession in your config. The release note is vague: if I don't set a value, will i end up with X11 or Wayland?

wayland because it comes before x11 in when alphabetically sorting.

@SuperSandro2000 "plasmawayland" comes before "plasma"?
Also I thought that option errored out if it was not set and there were more than one option.

I am talking about the desktop selection in sddm.

Also I thought that option errored out if it was not set and there were more than one option.

No, it doesn't. I have only this in my config:

    services.xserver = {
      enable = true;

      desktopManager.plasma5.enable = true;
    };

Is there a final fix for missing clock on Wayland? I am using 'fish' as my shell, with 'prgrams.fish.enable = true' already in config, and it hasn't made any difference. Running kwriteconfig5 command mentioned above hasn't worked either. The clock widget is there as far as I can tell, it just doesn't render correctly.

@e3bc54b2

Is there a final fix for missing clock on Wayland?

It's introduced again by plasma5 5.23.1 #139657 (comment)
There's a separated issue for it. #143272