https://bugs.kde.org/show_bug.cgi?id=429168
--- Comment #3 from Duncan <[email protected]> --- (In reply to Bharadwaj Raju from comment #2) > Does this happen still or on a fresh user? Yes to both. That's with git-master frameworks/plasma updated a couple hours ago. (I didn't answer immediately as I'm working on a project and hadn't updated in ~10 days or so, but I'm updated now.) While retesting the likely reason occurred to me: Unlike X's wide-open security model which lets any X app know about the windows of other X apps, wayland-native apps normally only get to know about their own windows. The wayland compositor itself (kwin_wayland in plasma's case) is the only normal exception, tho it can obviously arrange to share its knowledge with specific apps via private protocol (assuming there's no wayland-shell-specific protocol already standardized that I simply haven't seen anything on yet). My guess is that either kwin doesn't have such a private sharing arrangement for that setup with plasmashell yet, or if it does and it's working for some, for whatever reason (missing dependency?) it's not working here. By contrast, kwin's window switchers and effects such as the grid just work as they're direct kwin plugins and operate with direct compositor privileges. So plasmashell on wayland literally doesn't have and cannot get the information about other windows that it uses on X to populate the taskmanager, icons-only-taskmanager, and desktop-window-list option (configurable as a desktop mouse option). Tho one would /think/ kwin_wayland would have developed such a private protocol to share with its plasmashell desktop shell, but the evidence suggests either it hasn't yet, or I'm missing a critical dependency it normally uses for that. -- You are receiving this mail because: You are watching all bug changes.
