https://bugs.kde.org/show_bug.cgi?id=478422
--- Comment #7 from Jakob Petsovits <jpe...@petsovits.com> --- (In reply to Arjen Hiemstra from comment #6) > What the `install-sessions.sh` script does is > purely copy a session configuration file from the self-built prefix to the > system prefix, but that session configuration file will point at the > self-built prefix. If you then run that session and launch software that is > system-installed it will fail the KWin prefix check as the system software's > prefix is `/usr` while KWin's prefix is `$HOME/kde/usr`. Thanks Arjen. I've understood the overall idea of install-sessions.sh. What I don't quite understand, though, is how KWin in Info Center identifies itself as the one I built (5.91.90) and e.g. querying D-Bus for the process that provides org.kde.kglobalaccel [1] shows that my self-built $HOME/build/kde6/prefix/bin/kwin_wayland is in charge of that interface. The old Plasma 5 kwin binary doesn't even show up in `ps aux`. So the correct KWin seems to be running, but still lacks support for e.g. zkde_screencast_unstable_v1 (and apparently also the screenshot extension for Spectacle). Could there be something wrong with plugin paths perhaps? Or how else would the right KWin leave out important Wayland protocols? [1] qdbus org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID org.kde.kglobalaccel (courtesy of another bug report) -- You are receiving this mail because: You are watching all bug changes.
