Version: (using KDE 4.3.0) OS: Linux Installed from: Ubuntu Packages I've found a bug within the latest release of KDE 4.3 and compiz 0.8.2. Plasma panels with auto hide does not always appear when compiz is running. When i move the mouse to the side in order to make the panel appear, a purple "halo" that intensifies for the same time duration it would take the panel to appear becomes visible instead. If i turn on kwin, then the panel appear normally. I also have several oddities with plasmoids with compiz activated, for example: the analogue clock which i had in the lowest, leftmost corner in my panel were "stuck" there and couldn't be moved. And I did not have lock plasmoids activated. I've posted this bug at compiz fusion forums: http://forum.kde.org/viewtopic.php?f=67&t=63170 And KDE forums: http://forum.compiz-fusion.org/showthread.php?p=74469
I have the same problem.
Exactly the same problem on Gentoo.
Same exact problem. Also have a report listed that lists more details at http://forum.compiz.org/showthread.php?s=ae17b5a1968a8ee7b8e421a1f56648df&t=11896 Really, I'm not sure if this would be considered a KDE problem since the issue is resolved by not enabling Compiz, but since "Desktop Effects" is built in with these later releases, perhaps it is something that the assignees could look into. Jaunty, KDE 4.3.1 This report has been posted for a month and still unconfirmed, can someone at least try to duplicate?
*** This bug has been confirmed by popular vote. ***
Same here, Fedora 11 x86_64, KDE 4.3.1 and compiz-0.8.3. Vertical panel set to auto-hide won't show itself when pointing mouse to the screen edge, instead just something what could be a shadow comes out. I'm posting a screenshot...
Created attachment 36964 [details] Bug screenshot That blue thing on the left is the screen edge, where the panel is supposed to come from. This is what I get by hovering the mouse on the screen edge.
yes, this is compiz interfering with the input only windows plasma uses to detect when your mouse touches the screen edge. probably because compiz has its own input only window overlapping it. similar to how autohide panels and "magnetic edge" desktop switching in kwin don't mix. an alternative is for plasma to poll for the mouse, which would suck (as in "battery life" ;). i've heard that x.org may eventually give us alternate ways to get at such events in specific screen regions, but that's still apparently in the future. until then, the window manager needs to be careful about apps needing screen edges (and apps not interfering with each other similarly; plasma has had to work around some things there already in fact). sadly, i have to be honest here and say that this is not something that is going to change in plasma-desktop for the forseeable future. when we have other ways of achieving this, we'll jump on it. but that will require modifications either to window managers or x.org itself. until then, we live with the situation as it is.
Impressive, I must say. There's a problem that exists on an out-of-the-box install of modern distros, but we're going to do nothing in the forseeable future to fix it... An intriguing factor to many installing Linux, is compiz, and as simple as it is to setup on modern distros, it's become even more intriguing. I'm confused as to why there are obvious problems with releases, and when the community points these out, the developers say "There's no intention to fix this (obvious) problem in the forseeable future". Really? Also, how is it that people make comments since the release of KDE4 about the autohide feature, and once it is finally released, it is built incorrectly with no intention of doing it right? Just a few thoughts to chew on...
And I just noticed the "RESOLVED as WONTFIX" designation... you've got to be kidding me right?
IT WORKED FINE IN KDE 4.1, BUT SOMEHOW YOU'RE SAYING IT'S NOT A PLASMA ISSUE? "WE BROKE IT, SO LET'S PRETEND WE DIDN'T AND SHOVE IT OFF." Very helpful indeed. I'm so fed up with this issue, I'm about to switch to Gnome until you devs start caring enough to resolve issues.
Well I gotta agree with Erik, compiz and plasma teams should work together on this and neither one should say "it's their fault, we won't do anything"
@Erik: you have crossed the line beyond which i no longer deal with a person, namely when you start "yelling" and being generally unpleasant to deal with. your behaviour is not something i am willing to put up with, nor is something i am required to put up with. i'm going to address a few of your comments here, but until you pull yourself together it will be the last comment from me on this or any other comment you leave elsewhere. "An intriguing factor to many installing Linux, is compiz, and as simple as it is to setup on modern distros, it's become even more intriguing." most KDE users use KWin which also has very capable effects. it's simply a better fit for most. so let's not oversell this issue on the one hand, and on the other hand i'll be very frank and say that KWin is my primary target. when i have to choose between a "best case" solution that works with KWin (and could work with any similarly reasonable window manager) and something that works with $OTHER_WM i will pick the best case solution. often we have implemented additional features or ways of doing things in the code to make working with window managers such as compiz, but sometimes that's not worth it given the collateral costs. compiz has already resulted in a number of things in plasma and the windowing system classes in libkdeui to be done, so it's not like we ignore it out of hand. quite the opposite, in fact. "I'm confused as to why there are obvious problems with releases, and when the community points these out, the developers say "There's no intention to fix this (obvious) problem in the forseeable future"." because some problems are not fixable from our side or the fix for that particular problem would cause other problems that are deemed even worse. "Also, how is it that people make comments since the release of KDE4 about the autohide feature, and once it is finally released, it is built incorrectly with no intention of doing it right?" the implementation is correct with what we have to work with today and i've already explained what could be done to improve it further. patches welcome. as for this tidbit: "I'm so fed up with this issue, I'm about to switch to Gnome until you devs start caring enough to resolve issues." i've been resolving issues for years in KDE, and the number of improvements we have brought with plasma in the last 1.5 years speak for themselves. as such i deeply resent your tantrum-induced accusation here of not caring about resolvin issues. and if GNOME fits you better, then please switch to it. @Martin: "Well I gotta agree with Erik, compiz and plasma teams should work together on this and neither one should say "it's their fault, we won't do anything"" we do work on a lot of issues with each other, on both sides. in this case, there are additional issues to care about, as i have already explained. i'd be happy to see patches, and i'm not personally responsible to go around and unbreak things that _should_ work in an application but which compiz interferes with. note that it is also possible to configure kwin in such a way that you can get similar problems. but given how that configuration is usually used and the extremely low frequency of it causing issues for any of our users, we (kwin and plasma developers) have chosen not to address it there either. so it's not even a compiz/plasma issue. it's really a "x doesn't currently give us very good tools to work with, and window managers therefore need to be really careful with what kinds of windows they create and how they manage application windows, which is their primary task."
Aaron, You are right, I lost my temper and was out of line. I apologize. Thank you for your response. From the end-user perspective, I presume you can see what we are seeing- An issue is brought up, and the very first response from a dev immediately makes the issue a "will not fix", not even "will eventually fix", but puts it at the bottom of the barrel. From our point of view, it makes it look as if you guys don't care and we just have to deal with it as end users. I understand completely your primary focus on Kwin. It's the default, absolutely start there first. I don't simply use Compiz, however, because I think it's cool, or I like to show it off, I use it for its functionality and it's one of the main reasons I use Linux besides many others. It can be very useful, if it's set up right. You made some very clear and concise points regarding many of the issues brought up in this report. I appreciate that, it helps with the understanding a bit more. However, I still do not see an answer regarding the question of "It worked in KDE 4.1, why does it not work now?" Were there implementations in this newest version of KDE that made this issue arise? Anyway, I apologize again. I was just not seeing any response from a non-caps posting and was starting to get progressively more irritated. Thank you again for your response.
I have the same problem described in the first paragraph of the report. Fedora 15 KDE 4.6.5 compiz-0.9.5.0-3.fc15.i686 Thanks.