a136a159f9
Wayland has a design philosophy of prohibiting keyloggers, which is sane. However X11 did not, and a lot of X11 apps were developed with the expectation of being able to sniff keyboard events to handle global shortcuts. When such apps are run in a Wayland session under XWayland, these features break. Historically we have prohibited this in the name of security. In Plasma 5.27, we gave users a KCM they can use to choose their preferred balance of security and unbreaking XWayland apps with global shortcuts. But we still defaulted to total 100% security, at the expense of breaking these apps by default. However today we have a compromise that unbreaks them 99% of the time while not meaningfully reducing security: we can have KWin only prohibit XWayland apps from reading alphanumeric key events that don't have a modifier key pressed at the same time. This still prevents those apps from acting as keyloggers and reading your password or all the text you type, but does allow those apps that have a legitimate need to read key events for global shortcuts do so, because global shortcuts will involve modifier keys being held down. Due to the way the security modes work, making this change will also allow XWayland apps to read non-alphanumeric keystrokes without any modifiers being held down, but that's also fine for security since you can't use any of those keys to type text or passwords. |
||
|---|---|---|
| autotests | ||
| cmake/modules | ||
| data | ||
| doc | ||
| examples | ||
| kconf_update | ||
| LICENSES | ||
| po | ||
| src | ||
| tests | ||
| .clang-format | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .kde-ci.yml | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| KWinDBusInterfaceConfig.cmake.in | ||
| logo.png | ||
| Mainpage.dox | ||
| plasma-kwin_wayland.service.in | ||
| plasma-kwin_x11.service.in | ||
| README.md | ||
KWin
KWin is an easy to use, but flexible, composited Window Manager for Xorg windowing systems (Wayland, X11) on Linux. Its primary usage is in conjunction with a Desktop Shell (e.g. KDE Plasma Desktop). KWin is designed to go out of the way; users should not notice that they use a window manager at all. Nevertheless KWin provides a steep learning curve for advanced features, which are available, if they do not conflict with the primary mission. KWin does not have a dedicated targeted user group, but follows the targeted user group of the Desktop Shell using KWin as it's window manager.
KWin is not...
- a standalone window manager (c.f. openbox, i3) and does not provide any functionality belonging to a Desktop Shell.
- a replacement for window managers designed for use with a specific Desktop Shell (e.g. GNOME Shell)
- a minimalistic window manager
- designed for use without compositing or for X11 network transparency, though both are possible.
Contributing to KWin
Please refer to the contributing document for everything you need to know to get started contributing to KWin.
Contacting KWin development team
- mailing list: kwin@kde.org
- IRC: #kde-kwin on irc.libera.chat
Support
Application Developer
If you are an application developer having questions regarding windowing systems (either X11 or Wayland) please do not hesitate to contact us. Preferable through our mailing list. Ideally subscribe to the mailing list, so that your mail doesn't get stuck in the moderation queue.
End user
Please contact the support channels of your Linux distribution for user support. The KWin development team does not provide end user support.
Reporting bugs
Please use KDE's bugtracker and report for product KWin.
Guidelines for new features
A new Feature can only be added to KWin if:
- it does not violate the primary missions as stated at the start of this document
- it does not introduce instabilities
- it is maintained, that is bugs are fixed in a timely manner (second next minor release) if it is not a corner case.
- it works together with all existing features
- it supports both single and multi screen (xrandr)
- it adds a significant advantage
- it is feature complete, that is supports at least all useful features from competitive implementations
- it is not a special case for a small user group
- it does not increase code complexity significantly
- it does not affect KWin's license (GPLv2+)
All new added features are under probation, that is if any of the non-functional requirements as listed above do not hold true in the next two feature releases, the added feature will be removed again.
The same non functional requirements hold true for any kind of plugins (effects, scripts, etc.). It is suggested to use scripted plugins and distribute them separately.