https://bugs.kde.org/show_bug.cgi?id=459778
ryu.ketsu...@outlook.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #54 from ryu.ketsu...@outlook.com ---
(In reply to Vlad Zahorodnii from comment #53)
> (In reply to Matej Mrenica from comment #52)
> > (In reply to Vlad Zahorodnii from comment #51)
> > > Can you share your klassy config?
> >
> > [Common]
> > ActiveTitlebarOpacity=90
> > InactiveTitlebarOpacity=90
> >
> > [Default Windeco Exception 0]
> > BorderSize=1
> > Enabled=true
> > ExceptionProgramNamePattern=kdenlive
> > ExceptionWindowPropertyPattern=.*Kdenlive
> > ExceptionWindowPropertyType=1
> > HideTitleBar=false
> > Mask=0
> > OpaqueTitleBar=true
> > PreventApplyOpacityToHeader=true
>
> I applied your config but I'm still not able to reproduce the issue.
>
> My best theory is that klassy tries (or did try in the past) to change the
> shadow when kwin paints the decoration. With the current implementation,
> changing the shadow when kwin composes the output will produce
> EGL_BAD_SURFACE. On the other hand, the decoration should not mess with the
> shadow in Decoration::paint().
>
> Not sure what we can do without being able to reproduce the bug, we don't
> have enough data to act on it.
I have a similar configuration and it also doesn't happen all the time with me.
It may or not happen. But it is more often that it does happen and result in
the EGL_BAD_SURFACE error and kwin crashes. I can say I am using 5.27 Beta from
openSUSE's KDE Repos.
Here's what you can do to possibly increase the chances of it happening:
- Apply the config;
- Open the program in question;
- If it doesn't happen, restart KWin or restart session;
The way I understand it, if it is immediately applied and the program is
opened, it may not crash with that error. But if it is fresh or it hasn't been
opened for a short while, it may happen. I still don't know what causes it,
only that setting titlebar as opaque for that specific application when general
config is as transparent, will increase the chances.
Only other case it happens is with Inkscape. I didn't apply that opaque
titlebar configuration and it still happens like to the others.
--
You are receiving this mail because:
You are watching all bug changes.
