https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #17 from AnAkkk ---
Ok, that issue is actually related to having compositing disabled. It happens
100% of the time when I disable compositing.
It must also happen when compositing is disabled with the rule.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #16 from AnAkkk ---
(In reply to AnAkkk from comment #13)
> Writing anything in kate/konsole is very slow, it can take several seconds
> for the text to appear. Restarting kwin also fixes the issue.
This issue doesn't seem to be related to
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #15 from AnAkkk ---
(In reply to Thomas Lübking from comment #14)
> You mean *while* the compositor is suspended??
No, after it has been reenabled by closing the game, just like the other
issues.
I just tried again, and for some reason I can
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #14 from Thomas Lübking ---
(In reply to AnAkkk from comment #13)
> Found another issue, which happens as well after compositing has been
> disabled through a rule:
> Writing anything in kate/konsole is very slow, it can take several seconds
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #13 from AnAkkk ---
Found another issue, which happens as well after compositing has been disabled
through a rule:
Writing anything in kate/konsole is very slow, it can take several seconds for
the text to appear. Restarting kwin also fixes
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #12 from AnAkkk ---
(In reply to Thomas Lübking from comment #11)
> Do you have positive knowledge on the relation, ie. does killing plasmashell
> remove the window?
No, you're right, it doesn't actually remove the window. But I thought thi
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #11 from Thomas Lübking ---
xkill cuts the line between client and server. This sould remove all resources
(windows) and typically the client would exit (crash in doubt) in return.
Do you have positive knowledge on the relation, ie. does ki
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #10 from AnAkkk ---
(In reply to Thomas Lübking from comment #9)
> It would then probably belong to a crashed (and stopped) process?
> ps ax | grep T
No, nothing. xkill probably doesn't work because there is no PID attached to
the window (d
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #9 from Thomas Lübking ---
(In reply to AnAkkk from comment #8)
> xkill has no effect on it, it's still here.
Err, what?
It would then probably belong to a crashed (and stopped) process?
ps ax | grep T
> > ... "glxgears", sorry :-)
> Just
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #8 from AnAkkk ---
(In reply to Thomas Lübking from comment #7)
> Idiocracy. Seriously. Whatever it is, it's idiocracy.
> run "xkill" and click the window - the process it belongs to should die
> afterwards
> (maybe take a "ps fax" diff on b
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #7 from Thomas Lübking ---
(In reply to AnAkkk from comment #6)
> (In reply to Thomas Lübking from comment #4)
> > Can you "xprop" & "xwininfo" it?
>
> Output of xprop:
> _NET_WM_WINDOW_OPACITY(CARDINAL) = 0
Idiocracy. Seriously. Whatever
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #6 from AnAkkk ---
(In reply to Thomas Lübking from comment #4)
> Can you "xprop" & "xwininfo" it?
Output of xprop:
_NET_WM_WINDOW_OPACITY(CARDINAL) = 0
Output of xwininfo:
xwininfo: Window id: 0x246 (has no name)
Absolute upper-lef
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #5 from AnAkkk ---
Created attachment 96290
--> https://bugs.kde.org/attachment.cgi?id=96290&action=edit
Screenshot of firefox window after reenabling compositing
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #4 from Thomas Lübking ---
(In reply to AnAkkk from comment #2)
> 1) A black square in the top left corner when compositing is disabled
ie. an override_redirect (unmanaged) ARGB window. It's always above the other
windows, but you can only
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #3 from AnAkkk ---
To be more precise, I get 2) and 3) only when the compositor suspended by the
rules and reenabled.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #2 from AnAkkk ---
(In reply to Thomas Lübking from comment #1)
> Sounds like a buffer age problem. KWin still running on the intel chip?
Yes, it is. Apparently, I have 3 different issues:
1) A black square in the top left corner when compo
https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #1 from Thomas Lübking ---
Sounds like a buffer age problem. KWin still running on the intel chip?
Does it go away with
KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace &
If not , does it happen on the xrender backend as well?
Did you maybe expor
17 matches
Mail list logo
