I have observed that sometimes triggering a fullscreen declarative script the dialog is not appearing at all. The focus is lost from the Desktop and it is in the Dialog but the Dialog is not appearing. No special error messages are appearing from kwin --replace. I can understand that the dialog is called but not shown because in the Dialog I have set ESC to hide it. So in order for the Desktop to regain focus and responsiveness I have to press ESC. It happes also sometimes in 4.10.x... Reproducible: Sometimes Steps to Reproduce: Unfortunately, I havent found a way to reproduce it Actual Results: The PlasmaCore.Dialog in the KWin script is not shown even though it is triggered. Expected Results: The PlasmaCore.Dialog in the KWin script should be shown
The dialog is override_redirect (bypass windowmanager hint) so kwin just ignores it. Not invalid though, since it's an OR from the kwin process. Are you sure it's not shown? (Determine the WId eg. with xwininfo) When it fails, move to VT1 and use "xwininfo -id <WId> | grep -i map" If it doesn't print "Map State: IsViewable", the window is really not shown (and not just unstacked) what means that Qt didn't map it - for what reason ever*. Otherwise this may be a stacking or compositing issue. *Just to be sure: you're no more calling KWindowSystem::self() in any way, do you? ;-)
(In reply to comment #1) > The dialog is override_redirect (bypass windowmanager hint) so kwin just > ignores it. > > Not invalid though, since it's an OR from the kwin process. > Are you sure it's not shown? (Determine the WId eg. with xwininfo) > > When it fails, move to VT1 and use "xwininfo -id <WId> | grep -i map" > If it doesn't print "Map State: IsViewable", the window is really not shown > (and not just unstacked) what means that Qt didn't map it - for what reason > ever*. unfortunately for xwininfo I get... xwininfo: error: Can't grab the mouse. // but I can find the Wid from inside the script one more info when it fails, I can not use any application and I have to press ESC which is going to restore probably the window state by telling it to really hide... > > Otherwise this may be a stacking or compositing issue. > > *Just to be sure: you're no more calling KWindowSystem::self() in any way, > do you? ;-) Hmmm, for signals definitely I have disabled them but there is a chance to have let some calls inside the plugins... I will disable all this plugins and create scripting only alternatives for the kwin script.... Thomas please give some days because some work caught me up...
(In reply to comment #2) > one more info when it fails, I can not use any application sounds like the mouse is grabbed, meaning the window is mapped (or you X11 fundamentally broken) -> ever happened w/o active compositor? > > Otherwise this may be a stacking or compositing issue. This. > Thomas please give some days because some work caught me up... Take your time, it's your project after all ;-)
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
This issue report is quite old. Can you please confirm, that it still persists with Plasma 5.23?
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 mark the bug 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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!