https://bugs.kde.org/show_bug.cgi?id=356992
Thomas Lübking changed:
What|Removed |Added
CC||devuran...@gmx.net
--- Comment #36 from Thomas
https://bugs.kde.org/show_bug.cgi?id=356992
Thomas Lübking changed:
What|Removed |Added
Latest Commit|http://commits.kde.org/kwin |http://commits.kde.org/kwin
https://bugs.kde.org/show_bug.cgi?id=356992
Thomas Lübking changed:
What|Removed |Added
Version Fixed In||5.5.4
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #33 from Uriy Zhuravlev ---
(In reply to Thomas Lübking from comment #32)
> This kinda starts to become embarrassing... :-\
It happens to everyone. The current version is going and work perfectly. I hope
it will be quick in the upstream.
-
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #32 from Thomas Lübking ---
This kinda starts to become embarrassing... :-\
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #31 from Uriy Zhuravlev ---
(In reply to AnAkkk from comment #30)
> No problem :)
>
> I don't know anything about EGL, but shouldn't the call be
> eglGetCurrentDisplay() instead of eglGetDisplay() like it is in the updated
> patched version
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #30 from AnAkkk ---
No problem :)
I don't know anything about EGL, but shouldn't the call be
eglGetCurrentDisplay() instead of eglGetDisplay() like it is in the updated
patched version? Seems like eglGetDisplay always take a parameter.
--
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #29 from Thomas Lübking ---
Hehe - many thanks for covering my ass =)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
AnAkkk changed:
What|Removed |Added
CC||anakin...@gmail.com
--- Comment #28 from AnAkkk ---
T
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #27 from Uriy Zhuravlev ---
>Let's get this off the list
Good! Patch works well.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
Thomas Lübking changed:
What|Removed |Added
Flags||ReviewRequest+
URL|
https://bugs.kde.org/show_bug.cgi?id=356992
Martin Kostolný changed:
What|Removed |Added
CC||clearmar...@zoho.com
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #25 from Martin Gräßlin ---
if it works I'm fine with it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #24 from Uriy Zhuravlev ---
> if (dpy == EGL_NO_DISPLAY)
> dpy = eglGetDisplay(EGL_DEFAULT_DISPLAY);
I will try this. Although it seems to me a very good solution.
Martin?
--
You are receiving this mail because:
You are watching all bu
https://bugs.kde.org/show_bug.cgi?id=356992
Johannes Pfrang changed:
What|Removed |Added
CC||johannespfrang+...@gmail.co
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #21 from Thomas Lübking ---
The first one looks like other debug out (on your local system, not caused by
the patch) of the client extensions and a match of EGL_EXT_buffer_age against
all three extension lists.
The second one looks promisin
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #20 from Uriy Zhuravlev ---
I have two outputs, first:
("EGL_EXT_client_extensions", "EGL_EXT_platform_base",
"EGL_EXT_platform_wayland", "EGL_EXT_platform_x11",
"EGL_KHR_client_get_all_proc_addresses", "EGL_MESA_platform_gbm")
extension "EG
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #19 from Thomas Lübking ---
No, we only want to skip that bit if we've buffer_age support anyway.
I've not looked into it, but guess the extension check requires a context, what
means we cannot depend this bit on the absence of buffer_age -
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #18 from Uriy Zhuravlev ---
EGL_WINDOW_BIT|(supportsBufferAge() ? 0 : EGL_SWAP_BEHAVIOR_PRESERVED_BIT)
maybe you mean:
EGL_WINDOW_BIT|(supportsBufferAge() ? EGL_SWAP_BEHAVIOR_PRESERVED_BIT : 0)
?
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #17 from Uriy Zhuravlev ---
1. initEGL(); insted initEgl();
2. Nope... it's not work.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #16 from Thomas Lübking ---
We need to pre-fetch egl extensions init to know wheter BA is supported,
untested patch:
diff --git a/eglonxbackend.cpp b/eglonxbackend.cpp
index 480e533..abacdaa 100644
--- a/eglonxbackend.cpp
+++ b/eglonxbacken
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #15 from Uriy Zhuravlev ---
Hey. Do you have any thoughts? I think es2 != egl.
PS Now I have to use a LXQT instead KDE. Plasma5 + kwin instability at Intel.
:(
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #14 from Uriy Zhuravlev ---
(In reply to Thomas Lübking from comment #13)
> What puzzles me is that EGL_EXT_buffer_age seems to be available, so why
> would it not be in the list of client extensions?
Because in:
void AbstractEglBackend::in
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #13 from Thomas Lübking ---
What puzzles me is that EGL_EXT_buffer_age seems to be available, so why would
it not be in the list of client extensions?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #12 from Uriy Zhuravlev ---
(In reply to Martin Gräßlin from comment #11)
> which mesa version has that new behavior? When we discussed it on the
> mailing list my mesa didn't have it yet, so I didn't look into the
> implementation.
Actual
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #11 from Martin Gräßlin ---
which mesa version has that new behavior? When we discussed it on the mailing
list my mesa didn't have it yet, so I didn't look into the implementation.
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #10 from Uriy Zhuravlev ---
(In reply to Thomas Lübking from comment #9)
> prints "false" on your side?
Yes. My past result printed after initClientExtensions. :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #9 from Thomas Lübking ---
(In reply to Uriy Zhuravlev from comment #8)
> Please:
"Here you are" ;-)
The extension seems there, to be clear, this:
diff --git a/eglonxbackend.cpp b/eglonxbackend.cpp
index 480e533..d7e2fa0 100644
--- a/eglo
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #8 from Uriy Zhuravlev ---
Please:
EGL_VERSION: 1.4 (DRI2)
EGL_VENDOR: Mesa Project
EGL_EXTENSIONS:
EGL_CHROMIUM_sync_control, EGL_EXT_buffer_age,
EGL_EXT_create_context_robustness, EGL_EXT_image_dma_buf_import,
EGL_KHR_create
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #7 from Thomas Lübking ---
Errr... *after* the "initClientExtensions()" call???
Can you in case post the output of "es2_info"?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #6 from Uriy Zhuravlev ---
(In reply to Thomas Lübking from comment #5)
> Meh. Martin simply wanted to avoid it if buffer_age is supported (what makes
> sense).
> Do you have EGL_EXT_buffer_age in the client extensions?
>
> qDebug() << "buf
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #5 from Thomas Lübking ---
Meh. Martin simply wanted to avoid it if buffer_age is supported (what makes
sense).
Do you have EGL_EXT_buffer_age in the client extensions?
qDebug() << "buffer age?" <<
hasClientExtension(QByteArrayLiteral("EGL_
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #4 from Uriy Zhuravlev ---
(In reply to Uriy Zhuravlev from comment #3)
> Created attachment 96244 [details]
> Patch for fix swap behavior problem for intel
All effects work but I don't like EGL_BAD_MATCH after EGL init...
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #3 from Uriy Zhuravlev ---
Created attachment 96244
--> https://bugs.kde.org/attachment.cgi?id=96244&action=edit
Patch for fix swap behavior problem for intel
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #2 from Uriy Zhuravlev ---
> Does this work for you?
Nope becouse EGL_BAD_CONFIG return only in eglCreatePlatformWindowSurfaceEXT
and eglChooseConfig well done.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356992
--- Comment #1 from Thomas Lübking ---
Does this work for you?
diff --git a/eglonxbackend.cpp b/eglonxbackend.cpp
index 480e533..06e5a16 100644
--- a/eglonxbackend.cpp
+++ b/eglonxbackend.cpp
@@ -266,7 +266,7 @@ EGLSurface EglOnXBackend::createSurface(
https://bugs.kde.org/show_bug.cgi?id=356992
Uriy Zhuravlev changed:
What|Removed |Added
Platform|Other |Gentoo Packages
--
You are receiving this mai
37 matches
Mail list logo
