[Bug 2063510] [NEW] "find_java_runtime openjdk" fails to find /usr/lib/jvm/java-21-openjdk-amd64

2024-04-25 Thread tom stevens
Public bug reported: # . /usr/lib/java-wrappers/java-wrappers.sh # find_java_runtime openjdk [warning] /bin/bash: No java runtime was found # ls -l /usr/lib/jvm total 4 lrwxrwxrwx 1 root root 25 Oct 4 2023 default-java -> java-1.21.0-openjdk-amd64 lrwxrwxrwx 1 root root 21 Apr 22 19:35

[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths

2022-05-23 Thread tom stevens
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

[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths

2022-05-04 Thread tom stevens
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

[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths

2022-05-03 Thread tom stevens
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

[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths

2022-05-02 Thread tom stevens
This is another way to fix the problem. It was suggested in https://bugreports.qt.io/browse/QTBUG-82589?focusedCommentId=500548=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel#comment-500548: "or disable the relocating feature for your distro". That is what this patch does.

[Bug 1964763] Re: QtChooser doesn't support qt6

2022-04-29 Thread tom stevens
This is a debdiff for qtchooser applicable to qtchooser_66-2build1. I built this in pbuilder and it builds successfully, and I installed it, the patch works as intended. ** Patch added: "1-qtchooser_66-2ubuntu1.debdiff"

[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths

2022-04-26 Thread tom stevens
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"

[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths

2022-04-24 Thread tom stevens
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

[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths

2022-04-24 Thread tom stevens
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,

[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths

2022-04-24 Thread tom stevens
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

[Bug 1970057] [NEW] Qt6 QLibraryInfo returns wrong paths

2022-04-23 Thread tom stevens
Public bug reported: The qtdiag program can be used to find the paths returned by QLibraryInfo: qtdiag --no-vulkan --no-rhi --no-gl In this output on jammy (22.04) with qt6-base-dev (6.2.4+dfsg-2ubuntu1) I see: Library info: PrefixPath: / DocumentationPath: /share/qt6/doc HeadersPath:

[Bug 1938908] Re: Backport the container stack in Impish

2021-10-28 Thread tom stevens
This works for me: docker.io/focal-proposed,now 20.10.7-0ubuntu5~20.04.1 amd64 [installed] The original error I had during a 'docker build' was: Errors during downloading metadata for repository 'fedora': - Curl error (6): Couldn't resolve host name for

[Bug 1874832] [NEW] QCoreApplications sets QTextCodec::codecForLocale() incorrectly

2020-04-24 Thread tom stevens
Public bug reported: With ICU versions >= 61 QTextCodec::codecForLocale() always returns the utf-8 codec with mib 106 regardless of the value of the environmental variable LC_ALL or the available locales. On bionic, which included ICU 60, codecForLocale() returned the correct codec. On eoan and