New comments cannot be posted and votes cannot be cast. The rules however allow you to downforce the flag and ideally there will be a way to configure the blocking related to fullscreen windows (ie. backbuffering was designed for low memory chips) Fantastic work! KDE is an open community of friendly people who want to create a world in which everyone has control over their digital life and enjoys freedom and privacy. KWin also supports no compositing at all. Just click on a keyframe in tim… There doesn't seem to be a dedicated shortcut for this, and as this post suggests, the default behaviour seems to have changed in recent versions.. But yes, if we add a new standard we need to implement it in each and every application. (PowerVR should currently be the king of the hill, but they do afaik only power ARM devices) , Oh, and Martin is perfectly right about plasma. If KDE is run remotely via an XDMCP session it performance is bad, really really bad. Kill yourself. to 3: normal users don’t use remote desktops. The answer about gpus with driver problems is also bad. to 2: nothing we can do about Yes thanks Martin, for leaving that post up there so the rest of us can see the There are use cases for using compositing and there are usecases for not using compositing. My biggest concern towards GNOME Shell has been from the beginning that it requires OpenGL (I talked about that part with Owen Taylor at GCDS). Now concerning e.g. no, not at all. “Please unredirect me” Compositing is re-enabled when the last matching window terminates. Block compositing. The svg rendering on theme changing (including parsing the xml, do the svg rendering, pixmap allocation, caching & a relayout before the complete edsktop update) /is/ expensive (on the CPU and then the GPU), so turning off compositing “to save some more minutes of battery” is pretty much the worst thing one could do , 2. I can also predict that any discussion on the subject will be useless… Thats going to be fun . For powersaving one should consider to use the XRender backend (completely spares the pixmap -> texture conversion. Mozilla Firefox Disable smooth scrolling In the future people will have hardware which will run smoothly with compositing turned always on (even when watching videos or playing games fullscreen), so “Always enable desktop effects” will be the ideal choice for them. If you’ll keep the API, and also the shortcut (ctrl-alt-f12), then why remove the configuration option? with xrender compositing there is no performance impact. There’s a difference between games and games. I have a dream: a dream of an always composited desktop. This list contains the most common shortcuts supported by … KDE is an international and diverse technology team creating user-friendly free and open source software for desktop and portable computing. I look forward to see it in action . Martin, big respect for you staying so calm – I really feel sorry for what some people state here… And believe me, many many people (including me) really apreciate what you and others are doing! Also what about adding the option into special window/application settings of KWin? Another example are fullscreen applications. Since last year when i bought new pc i never used kde without compositing, altough the option to disable it manually should always be here, sometimes when you update drivers compositing can crash your xserver because of buggy driver update and without having option to disable it, that would be impossible to investigate the problem. For the user it is very difficult to know what he currently needs and can do a very bad job at deciding himself. Rules by application seem nice, but they are very undiscoverable, maybe put a default rule for all menu items which are included in “games category” in kickoff? I have not tested with compiz recently to compare but a year ago the situation seemed to be ubiquitous. My GPU is also a few years old already. Disable restoring session on Login ... but it will open with Meta if another shortcut is assigned). April 19, 2018. Removing the option to turn on/off composition isnt good idea at all. except the removal of the “Enable desktop effects” check box in the GUI. As those are pure animations. For applications like a web browser or an office suite it is completely useless, while for OpenGL applications like games just unredirction might not be enough. 4. 1. Be sure to check their shortcuts for a detailed listing. We continuously work on improving the software included in our KDE Application series, and we hope you will find all the new enhancements and bug fixes useful! The same is true for if you use, for instance, shift switcher for your default application switcher, wobbly windows when dragging windows, darkening non-focused windows, and the slide back effect when changing window focus. Here you can enable effects to more efficiently manage your windows. But maybe I am just stating my idiocy again . Even stupid people have a right to live. i dont want to wait 2 or 3 years for it to happen when i need it to do it today. That’s one of the reasons why I implemented GLES support which I hope to get as our default engine, soon. Click Global Keyboard Shortcuts on the left pane 4. So this is really a corner case for which manual switching is enough. I actually have the oposite case with my laptop. First, if buggy drivers slow down desktop when compositing is enabled and the user will want to disable it, he couldnt do that easily, and he will have a laggy desktop environment. The blocking property allows a window to block compositing e.g. So what’s the problem? When compositing is needed, it is on, when compositing is bad at the moment, it is off. This is costly and will most likely drain more battery than using compositing.”. Working GPU-decoding of videos is another corner case, sadly. So this is really a corner case for which manual switching is enough and I don’t want compositing disabled for any other case automatically whenever some random application decides it’s OK. I may be missing something, but why are having compositing on and playing an HD video incompatible? 1-mergin disabling and suspending into suspendig Note: Global Shortcuts also has shortcut information for other core aspects of KDE, like the KWin window manager, KDE Power manag… You seem to be suggesting people just shouldn’t change virtual desktop when their system is under heavy load or low on batteries, which seems to be a major loss of functionality. It is already added to the window rules framework. In order to be able to type Umlauts I have to press the compose key+shift+'+vowel. When you say that there may be a increase in power consumption with composite turned off, what support do you have for that? For example under Windows some web browser plugins always disable compositing (QuickTime and QuakeLive come to mind). for all those cases there is the windows rule frameork and there is nothing wrong about sharing those rules over collaboration services. however there’s either compositing or there is not. And there are many non open source ones too. But disabling blur causes Plasma to render a different set of SVGs, so whether there would be an advantage is not possible to be said without very good performance testing (which in case of blur depends much on hardware and drivers). Sometimes (luckily not often) it happens that compositing becomes so slow that it disables itself and then I am happy to enable it again in the systemsettings (I forget the keyboard shortcut, so I go to systemsettings to reenable compositing) after which compositing runs fluently again. This is what Thomas has been working on lately. For differences between plasma-meta and plasma reference Package group. Is there a stable API for such things or the programmer has to make up his own mind how to solve things? From the same screen, you can define a shortcut to enable/disable compositing anytime. sort people you have to deal with. But sometimes i move a window over the fullscreen video to have both visible. “Please turn compositing down (implementation is vague here, but I guess you could swap to XRender, or turn off heavy postprocessing such as blur and the like). As i am running the fullscreen most of the time it reduces to: no compositing at all. I have an US international keyboard (€ sign on key 5). KWin will suspend compositing and keep the state untill no window blocks compositing. Since you’re *clearly* not an idiot you will get the message behind this parable. Consider darkening of non-focused windows: it is just modifying the rendering of the window. I really hope that video players, games and Wine pick up our new property and we will also recommend it as an additon to the NETWM specification. Without compositing it is snappy. If you want to investigate what is causing wakeups and if we can reduce them this is highly welcome. I use Lenovo T400, Intel Integrated Graphics 4500MHD. That is, permanently enable or disable compositing, if one so wishes, despite the performance hit. kde/linux sux…”)? Everything else like Present Windows, Desktop Grid or Cube does not make sense. With the application you want to adjust in focus, press Alt+F3 to open the options window. In my case I’d rather see the CPU take over decoding the video than to have the negative side effects of disabling compositing (ugly desktop, ugly fullscreen controls, flickering). Linux kernel 2.6.37, actual and intel driver. Hoping for non kde apps to implement this is wishfull thinking, and i can name way more than 5 games from the top of my head that run under linux. does okular have a nice ascii text read mode?) If the compositor should be disabled while a fullscreen application such as games or video is used it is better to disable compositing either through the shortcut Alt + Shift + F12 or since 4.7 (Released July 2011) through a window specific rule for the window. When composite is on, I have at least 60 wakeups/second coming from the driver (measured with powertop) on idle and an increased estimate of power consumption. For games there is only one proper solution: turn off compositing. On the other hand a web browser would not block compositing as that is not what the user wants. Another big thumbs up for getting the right abstraction layers. 1-Don’t disable the shorcut (alt shift f12) I think that category is designed by packagers and game developers, so disabling compositing here might be enough. so you will have to patch every game out there to support the new standard? We only need changes for games which are demanding on GPU – let’s call it the FarCry category. The KDE Plasma Workspaces ™ provide keyboard shortcuts that allow you to perform many tasks without touching your mouse. To do it, select a clip in timeline and use the "Grab Current Item" (Shift+G) function from the Timeline menu. Tip: Disable desktop effects in KDE and Xfce for a better gaming experience Gaming Hello everyone, recently I started noticing that my games are stuttering even though they were reporting high framerates (especially in CS:GO and rocket league). In the Configure Shortcuts window, you will see a list of all the shortcuts available in the current application. These are only shortcuts for KDE, other applications have their own shortcuts. I did not see any consensus on the mailing list that we need to turn off the effects. Please stop going all gnome on us, removing configuration. Blocking compositing for “normal” clients which are esp. What, however, does affect performance on my system is GPU-accelerated HD video decoding along with compositing. all quite stress the GPU and -depending on the driver- take more or less power. Some day we have to start thinking about not supporting legacy hardware. A good example for that is turning compositing off to save some more minutes of battery. These shortcuts will allow you to use your KDE desktop without touching the mouse. It really depends on what the effect is doing and you need to know the implementation of the effect (which I know). Thanks. Not so legacy system, but with compositing it is unacceptably slow. One of the things I liked best about KDE (and linux in general) was that I could fine tune it to my hearts desire. (so you don’t have to know & press the shortcut whenever you launch gl client xyz because it’s too slow otherwise or mesa will crash KWin). KDE's software runs on GNU/Linux, BSD and other operating systems, including Windows. Click "More Actions" Configure Special Application Settings. Once you got that under control, you can provide patches to improve kwin, demonstrate your advanced skills and one day take over maintainership – what btw. This should make everything more clear to the user. Under “Component”, select “Plasma”. However, you can set compositing for specific applications. For them it’s just “KDE/Linux is slow”. How about dual monitor setups with that aproach? To view the existing shortcuts for Plasma, look in the “Global Shortcuts” window for “Component”. Disable Timeline Preview 20. I really don’t know about the use cases of the average KWin user but in my case compositing does not greatly affect the performance of QuakeLive (Linux version). Even in Windows you can disable compositing. However, there is a workaround. This means the screen is no longer composited, but the resources, that is the OpenGL context and the effect system is still running. that might be true in modern systems, but in my netbook, basically every game looks slow with compositing, even kollision, though it’s just a bit. Go to the "Appearance & Fixes" tab This doesn’t help for things like games or Full-HD videos as there the impact is the compositing and not the effects. Type "wp:kde" to open Wikipedia's page about KDE. Press question mark to learn the rest of the keyboard shortcuts. 3. If so, how can I help? Probably compositing related (happens mostly but not exclusively when I switch desktops). This day will come at least with Wayland – and we will always keep the Alt+Shift+F12 key, just not expose it in the UI anymore. The second part Thomas has been working on is allowing applications to block compositing. I think years, so manually disabling should definitely don’t die, maybe it’s use could be minimized with that wine patch and making compositing off default for (fullscreen) games in kickoff. you really need to let the user also decide, not just a developer that may never do it. The same is true for watching Full-HD videos: often graphics cards are not powerfull enough to do both compositing and GPU accelerated decoding. Also, if later you have tried this system and you find that you want to always enable or always disable compositing, you can always file a request or patch kwin — It’s probably a one-liner to ignore app requests. What do you mean by “kwin will only allow compositing on system that support it”, I don’t think kwin should be the one making the decitions, unless it’s told to, I’m the owner of the system and I decide if I can bare slow compositing on old pc because it looks nice. 2-making window based disable compisiting for apps that don’t support this api So can’t we just leave opengl compositing on and forget it? Shift Switch I think that the change in functionality (switching from shift to classic) is more a problem to the usability than some five seconds on battery. So I would expect that web browsers would routinely need to set the property since it would routinely need to display HD video. Of course we cannot demand from our users that they know about it and can handle it. I haven't changed anything lately in my system, I just update packages everyday on my Fedora 33 KDE install. Also I don’t see how with a ClientMessage it could survive a restart of the compositor or getting a nice overview of what windows currently block compositing. If GPU decoding and compositing clash, act according to a pre-set rule of either disabling compositing or or switch from GPU decoding to CPU decoding. Now with Thomas work I am confident that we will be able to remove the UI to turn on/off compositing in maybe 4.8. Open your bookmarks in a webbrowser. Turning it off, will have no impact. You say that the average user should not be aware that there is such a thing as compositing and I agree with that, but I wonder: how is that realizable when (1) compositing from time to time gets so slow that it gets disabled (and the user experience is: “suddenly the desktop looks so different and why does all of a sudden ‘present windows’ not work anymore? If not, has anyone clocked if there's even a significant performance difference when compositing is running alongside a game? So no, these effects do not take resources or hurt the battery life when they are not being used, the problem is that many of the effects will be used while doing ordinary tasks on the computer. With unredirection compositing would be started again, causing an ugly flickering and taking away important resources from VLC. This is pretty awesome. Also at runtime self checks may disable compositing and also applications can block compositing bringing KWin into this mode. 4771 19254 Fri Nov 27, 2020 9:28 am Lachu Tutorials & Tips User-submitted information on installing, configuring, and using KDE. If you disable effects it will just suspend them and the effect system will be in suspended state after a restart. People with lousy hardware will choose “Disable desktop effects” and the others will like “Smart usage of desktop effects”. if one window turns off compositing it will of course affect all screens. When you say that there may be a increase in power consumption with composite turned off, what support do you have for that? Which at least looks for me unacceptable to switch the desktop shell just because you want to watch a Full-HD video. To the naysayers: kwin will have the API to disable compositing, so you’ll always be able to do it. If you just set a normal window to fullscreen nothing will change. I don't see any bar that lists open windows. And since this is KDE there is an option to disable automatic disabling (:P) of compositing since I have four monitors and I tend to play with one only and my graphics cards can handle this, I would never want compositing to be turned off , This seems like an excellent idea. So is this sort of an API that applications can use or is it a kwin only “feature” ? Depending on how efficient the client does this, it can be “quite ok” to “horribly expensive”. With those settings in place, compositing will be disabled whenever that application is running. There’d be no big deal to turn the bool into a flag but the client should not care about “how the window wants to be composited” – it should just know: here i am, i run the show, i’m expensive, please turn expensive stuff off cause it’s pointless anyway.