Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I have an older Lenovo T60 with Intel 945GM graphics. The KDE Desktop Effects work great with just the laptop display, but if I attach an external monitor, the entire desktop becomes *really* slow (it takes ~5 seconds for a mouse click to register!) If I disable the effects, everything is fine. Likewise, if I change the resolution on both monitors to something like 1024x768, the effects work fine. This is because the Intel graphics are limited to 2048x2048 virtual desktop resolution. KDE *should* auto-disable effects if the desktop is larger than 2048x2048. See also https://bugs.kde.org/show_bug.cgi?id=308439 https://git.reviewboard.kde.org/r/106917/ https://bugs.freedesktop.org/show_bug.cgi?id=57609 Version-Release number of selected component (if applicable): kde-workspace-4.10.1-1.fc18.x86_64 How reproducible: every time Steps to Reproduce: 1. use a system with Intel graphics and a multi-monitor setup with combined resolution greater than 2048x2048 2. login to KDE Actual results: desktop effects are enabled but very slow Expected results: desktop effects should be disabled automatically if the hardware cannot handle it Additional info: Gnome Shell 3.6 on this same system uses the Fallback Mode and pops up a warning that the hardware cannot handle effects
Looks fixed upstream for 4.11 (not in 4.10 due to complex string additions apparently).
And I propose we backport it, it's better to have untranslated error dialogs than to have the system silently attempt to use desktop effects with absymal performance.
This is it, https://projects.kde.org/projects/kde/kde-workspace/repository/revisions/f5e5858a1fa461f37c04fd9bfb179d9be413251f
Unfortunately that didn't fix it --kde-workspace-4.10.4-5.fc18.x86_64. It's easy to see the difference as well. With desktop effects enabled, strace -p $(pgrep kwin) shows a select on descriptor 9 continuously firing and talking to the X server (I think it's the X server). With the desktop effects disabled, the select only fires when something happens (key event, mouse event, etc) and that happens whether or not I have external monitors attached to the laptop. It also used to work just fine (pre kde-4.10) so I don't really agree with the O/P that the desktop effects should be turned off, on the other hand I do have a slightly newer graphics chipset (i965, if /var/log/Xorg.0.log is anything to go by).
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.