| Summary: | Compositing is disabled without proper explanation | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Yuri <yuri> |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED LATER | ||
| Severity: | normal | Keywords: | investigated, triaged |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | FreeBSD Ports | ||
| OS: | FreeBSD | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Yuri
2010-11-19 19:38:47 UTC
if it is another application, it really is another application. If kwin turns it off, it does not say that it is another app. The only two applications I know turning off compositing is our configuration interface and the power management system. So could it be that you come from suspend? In general the problems we reported about do not affect nvidia, though I do not know how that works on freebsd. No, there is no suspend. Its a desktop. kwin cannot provide the requested information, since it doesn't know itself. compositing was in this case suspended through an open dbus (IPC) interface - this could have been some shell (init) script, so there'S nothing we could do to fix the problem (but extend the dbus interface and allow callers to pass a reason, this would however have to remain optional and the application that deactivated compositing could do that by itself if it feels this is necessary, kde has various message systems, eg. just "wall 'xyz deactivated compositing because the author thinks that shadows suck'" or so would do) -> is compositing successfully resumed by pressing shift+alt+f12? -> what's the output of: * "kreadconfig --file kwinrc --group Compositing --key OpenGLIsUnsafe" * "kreadconfig --file kwinrc --group Compositing --key CheckIsSafe" shift+alt+f12 doesn't resume compositing and no such message appears like the one I described in my OP. Also this message for some reason only comes up intermittently, about every other time when I press the button "Resume Compositing". Shouldn't the effects of pressing "Resume Compositing" and shift+alt+f12 be the same and this message show up every time in case of failure? > kreadconfig --file kwinrc --group Compositing --key OpenGLIsUnsafe false > kreadconfig --file kwinrc --group Compositing --key CheckIsSafe true (In reply to comment #4) > shift+alt+f12 doesn't resume compositing this is no good, is the shortcut un/rebound ("kcmshell4 keys"), do kwin shortcuts (like switching the virtual desktop etc.) work in general & does resuming compositing from the config dialog work (on the second or third attempt - sounds like kwin messes up the internal suspension state)? > and no such message appears like the one I described in my OP. this is expected (the shortcut is a kwin internal) > Also this message for some reason only comes up intermittently, about every > other time when I press the button "Resume Compositing". So the config dialog is the source then. > Shouldn't the effects of pressing "Resume Compositing" and shift+alt+f12 be the > same and this message show up every time in case of failure? No. the shortcut is part of kwin, the dialog is not and has to use the (general) dbus interface (you can btw. disable the notion in "kcmshell4 notify") > false, true 'key - that's not it then either. shift+alt+f12 is assigned to 'Suspend Compositing' in "kcmshell4 keys". BTW This should say 'Toggle Compositing' if that's what is really meant. Other shortcuts (like ctrl-alt-f11: enable tiling) work. Switching virtual desktops also works. Resuming compositing doesn't work from both System Settings and Configure Window Behavior. is this still an issue with 4.7? This bug was reported for FreeBSD. And FreeBSD didn't adopt 4.7.0 yet. They only plan on adopting 4.7.1 or 4.7.2 (http://mail.kde.org/pipermail/kde-freebsd/2011-August/011286.html) waiting for FreeBSD to catch up Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I have no idea now what this was about. |