https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #21 from caulier.gil...@gmail.com ---
Hi Maik,
With the Qt 5.15 LTS (annotated 5.15.3 in help/component dialog), we inherit of
qtWebEngine 5.15.8.
Qt detect iconv APi (from glib) and can compile with it but not qtWebEngine as
it expect libx
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #20 from Maik Qualmann ---
I confirm that the sorting in the AppImage is now correct.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410980
caulier.gil...@gmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #18 from caulier.gil...@gmail.com ---
Git commit 00e4d5da2948ccdc101cdeeb23f7b05405812436 by Gilles Caulier.
Committed on 19/01/2022 at 19:04.
Pushed by cgilles into branch 'master'.
Great news : AppImage with Qt 5.15.2 compiled under Mageia
https://bugs.kde.org/show_bug.cgi?id=410980
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||iwannaber...@gmail.com
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #16 from Maik Qualmann ---
If I understand the instructions to compile the libicu correctly, the path to
the data must be specified during compilation. It is also possible to disable
with an option that the path can be set via an environment
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #15 from Maik Qualmann ---
I have now also played with the paths to the ICU data here and have no solution
yet...
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #14 from caulier.gil...@gmail.com ---
Maik,
I advance more and more in locale support problem with AppImage.
Now i can reproduce the problem with the digiKam compiled for the AppImage but
installed and executed on the compilation system.
T
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #13 from caulier.gil...@gmail.com ---
Maik,
I progressed a little bit with AppImage and locale system support.
1/ I recompiled AppImage with last Qt 5.13.1 and problem still reproducible.
2/ When i run the digiKam version installed under th
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #12 from caulier.gil...@gmail.com ---
Maik,
AppImage is re-built with Qt 5.12.5 and ICU support. This time, at startup, the
warning on the console is different :
= "Digikam")
Digikam::DPluginLoader::registerGenericPlugins: Generic plugin n
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #11 from caulier.gil...@gmail.com ---
Here export from bash report this from my account:
declare -x LANG="en_US.UTF-8"
declare -x LANGUAGE="en_US.UTF-8:en_GB:en"
So LANG is present, and there is nothing special in RunApp bash script from
A
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #10 from Maik Qualmann ---
QLocale reads the environment variables. We have to put these from the real
system into the AppImage.
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/tools/qlocale_unix.cpp#n75
Maik
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #9 from caulier.gil...@gmail.com ---
No idea. The Qt code relevant is complex, but QLocale is used in background.
With iconv dependency, Qt 5.12.5 LTS report now these messages on the console
at digiKam startup :
Digikam::DPluginLoader::reg
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #8 from Maik Qualmann ---
Interesting. My guess is that the library can not determine the correct locale
because we're inside the AppImage. The only question is, where does she get the
information from? From "/etc/locale.conf" or from the en
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #7 from caulier.gil...@gmail.com ---
Maik,
I found something important about AppImage and LANG=C stuff.
In fact the dysfunction described here (and certainly other ones in bugzilla),
depend of the options used to compile Qt5 for AppImage.
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #6 from caulier.gil...@gmail.com ---
Daniel,
You can hack yourself the startup shell script inside AppImage to try a work
around with the locale problem.
In fact, AppImage is something like ISO9600 disk mounted in virtual disk in
memory and
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #5 from Daniel Laidig ---
Thanks for your amazingly fast reaction! :)
I can verify that this is indeed a locale issue, but the behavior of your
workaround is not exactly the same. On the two systems I tested (Fedora 30,
Kubuntu 19.04), sett
https://bugs.kde.org/show_bug.cgi?id=410980
Maik Qualmann changed:
What|Removed |Added
CC||janmaj...@seznam.cz
--- Comment #4 from Maik Qu
https://bugs.kde.org/show_bug.cgi?id=410980
--- Comment #3 from Maik Qualmann ---
The QCollator depends on the locale used. I could imagine that there is no
locale in the AppImage and therefore the QCollator is not working properly.
Maik
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=410980
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=410980
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #2 from Maik
21 matches
Mail list logo
