[Bug 1205863] New: Qt private API issue
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1205863 Bug ID: 1205863 Summary: Qt private API issue Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: christophe@krop.fr QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Received by email today. I'm adding a bug report for discussion: � I write to you because you changed the last revisions here: https://build.opensuse.org/package/revisions/KDE:Qt:5.15/libqt5-qtbase. To fix the issue described here: https://bugreports.qt.io/browse/QTBUG-109030 I would like to create a patch for the libqt5-qtbase package. I have a rough Idea how to use osc and how to create a patch with it. But I have absolutely no Idea to which of the many libqt5-qtbase packages found in build.opensuse.org I should apply this patch to. My goal would be that the patch appears at some point in the future in SLES15-SP4. � -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1205863 http://bugzilla.opensuse.org/show_bug.cgi?id=1205863#c1 --- Comment #1 from Christophe Giboudeaux <christophe@krop.fr> --- Both openSUSE and SLE are affected by this issue. Qt6 6.4.2 will have the fix once released. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1205863 http://bugzilla.opensuse.org/show_bug.cgi?id=1205863#c3 Michael Dluhosch <michael.dluhosch@airbus.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael.dluhosch@airbus.com --- Comment #3 from Michael Dluhosch <michael.dluhosch@airbus.com> --- I noticed the isse because we use in our application following symbol "QQuickFramebufferObject::Renderer::framebufferObject const" which causes the final binary to use the wrongly private tagged symbol "QQuickFramebufferObject::Renderer::framebufferObject() const@@Qt_5.15.2_PRIVATE_API" This binary needs now to be recompiled with every new update to the qt5declarative package. We currently have SP1 SP3 and SP4 systems, it would be nice if I could compile on SP1 and just use the binary everywhere. This bug makes it impossible so I tried to get it fixed so that we can at least use our SP4 binary when SP5 arrives. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com