I'm seeing a really weird graphic glitch in which almost the entire content of kate's window is duplicated when I move the application while it's starting up. Kate must do something different, because it's also the only application which I've seen printing Qt warnings like below. The setScreen() attempt isn't a direct cause btw, because those warnings are printed instead of any actual work being done by the function. QWidgetWindow(0x7fc40c5a4780, name="QFrameClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a3e50, name="QSplitterClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a2fa0, name="QFrameClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a2130, name="QSplitterClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a2130, name="QSplitterClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a2130, name="QSplitterClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a2fa0, name="QFrameClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a2fa0, name="QFrameClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a3e50, name="QSplitterClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a3e50, name="QSplitterClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a4780, name="QFrameClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40c5a4780, name="QFrameClassWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. QWidgetWindow(0x7fc40ce07a90, name="mainToolBarWindow") ( QScreen(0x7fc409c78760, name="BenQ GL2250H") ): Attempt to set a screen on a child window. Reproducible: Always Steps to Reproduce: 1. start Kate with a document from a terminal ("kate foo.txt") 2. move the window before the document has been opened Actual Results: See screenshot. The contents are shown twice, once where they belong, and once where they would have appeared if the window hadn't been moved. Expected Results: no such weirdness. This makes one wonder if kate always maintains 2 views, which only happen to be superimposed because the window usually doesn't move in between the successive creations. - this situation can be rectified by going into and out from fullscreen mode - moving the window moves both "areas" - kate is the only application in which I've been able to provoke this behaviour.
Created attachment 101475 [details] screenshot showing the glitch
I cannot reproduce this when starting Kate through the Finder; in that case its window also opens with the document already open. It is thus faster to start, but also faster to quit. And finally, when I start kate with a document from a shell, I'm seeing messages (when quitting) in the system.log: Oct 7 19:00:45 Portia.local WindowServer[139]: _CGXRemoveWindowFromWindowMovementGroup: Window not in group They also appear when I open a document directly in Kate
Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
I don't understand how I could ever manage to move the window before the document opened. At least in the current version of the app and frameworks there is no more delay.