** Also affects: qt6-base (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970057
Title:
Qt6 QLibraryInfo returns wrong paths
To manage noti
SRU request:
Please accept qt6-base 6.2.4+dfsg-8 into jammy.
[Impact]
1. QLibraryInfo can return non-existent paths.
2. This results in Qt6 QWebEngine being unusable.
[Test Plan]
1. Check the output of qtdiag from qt6-tools-dev-tools, and verify the paths
exist.
a) Run "qtdiag --no-vulkan --n
This bug was fixed in the package qt6-base - 6.2.4+dfsg-8
---
qt6-base (6.2.4+dfsg-8) unstable; urgency=medium
* Team upload.
* Disable relocatable feature, to fix paths on usr-merged systems.
Thanks to Steven Trabert for the patch! (Closes: #1010575, LP: #1970057)
* Mark on
A bug has been opened with debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1010575
** Bug watch added: Debian Bug tracker #1010575
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010575
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I note that qtbase-opensource-src-5.15.3+dfsg works correctly on jammy.
This is likely because the "-no-feature-relocatable" option is used with
configure in debian/rules. 2-qt6-base_6.2.4+dfsg-2ubuntu2.debdiff adds
the equivalent cmake option for qt6-base_6.2.4+dfsg.
--
You received this bug no
This is another way to fix the problem. It was suggested in
https://bugreports.qt.io/browse/QTBUG-82589?focusedCommentId=500548&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#comment-500548: "or disable the relocating feature for your
distro". That is what this patch does.
Here is a more complete patch. The fix is the same, but this includes
the updates to changelog, patches/series, as well.
** Patch added: "1-qt6-base_6.2.4+dfsg-2ubuntu2.dsc.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+attachment/5584085/+files/1-qt6-base_6.2.4+dfs
One could imagine a more robust solution where the cmake function
file(REAL_PATH [BASE_DIRECTORY ] [EXPAND_TILDE])
was used to guarantee that QtQmakeHelpers.cmake resolved the relative
path used to compute QT_CONFIGURE_LIBLOCATION_TO_PREFIX_PATH in the same
manner that the supplied patch works at
The attachment "qlibraryinfo_symlink.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~b
This issue appears on jammy because /lib is a symbolic link, and the
/lib/x86_64-linux-gnu entry in the loader search path is used to find
libQt6Core.
The cmake generated qconfig.cpp contains this line:
#define QT_CONFIGURE_LIBLOCATION_TO_PREFIX_PATH "../../"
So, prefixFromQtCoreLibraryHelper(
This seems to be related to the dynamic loader search path, see the
comments in https://bugreports.qt.io/browse/QTBUG-82589
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970057
Title:
Qt6 QLibraryI
11 matches
Mail list logo