https://bugs.kde.org/show_bug.cgi?id=370257
Bug ID: 370257
Summary: [OS X] weird window "dissociation" glitch
Product: kate
Version: 16.04.1
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: application
Assignee: kwrite-bugs-n...@kde.org
Reporter: rjvber...@gmail.com
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.
--
You are receiving this mail because:
You are watching all bug changes.
