Seems to be solved in the current version (vsd 3.2.0-beta178).
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 6 2023
In T5960#175318, @ikloecker wrote:Also, please retest T5960#172860 with the latest build.
I misunderstood the issue. When I created the GnuPG VS-Desktop package I did not wrote a qt.conf file which thanks to our patch https://dev.gnupg.org/source/gpg4win/browse/master/patches/qtbase/0001-Gpg4win-qstandardpaths-patch.patch caused all config files for Gpg4win to be placed under %APPDATA%\kleopatra. This was by accident since it uses NSIS FileWrite and FileWrite is not supported in our NSIS to MSI packaging.
Another customer case with "always show security-dialog" on (-> external resolver):
It might actually be useful to have an random number API in gpgme. When we do that we can also add a way t search for random numbers with an upper limit in each octet.
Bugs goes back to 2002 where we stopped checking trust for keys without any signature. This was really useful but has this strange behaviour.
Hopefully, we will soon have a Windows CI to catch such errors.
/home/aheinecke/dev/main/src/gpg4win/src/playground/build/libkleo-202309061056/src/utils/gnupg.cpp: In function 'QString Kleo::stringFromGpgOutput(const QByteArray&)':
/home/aheinecke/dev/main/src/gpg4win/src/playground/build/libkleo-202309061056/src/utils/gnupg.cpp:573:53: error: passing 'const QByteArray' as 'this' argument discards qualifiers [-fpermissive]
573 | const auto s = fromEncoding(cpno, ba.replace("\r\n", "\n").constData());
| ~~~~~~~~~~^~~~~~~~~~~~~~
In file included from /home/aheinecke/dev/main/src/gpg4win/src/playground/install/include/QtCore/qstring.h:50,
from /home/aheinecke/dev/main/src/gpg4win/src/playground/install/include/QtCore/qhashfunctions.h:44,
from /home/aheinecke/dev/main/src/gpg4win/src/playground/install/include/QtCore/qlist.h:47,
from /home/aheinecke/dev/main/src/gpg4win/src/playground/install/include/QtCore/qstringlist.h:41,
from /home/aheinecke/dev/main/src/gpg4win/src/playground/install/include/QtCore/QStringList:1,
from /home/aheinecke/dev/main/src/gpg4win/src/playground/build/libkleo-202309061056/src/utils/gnupg.h:16,
from /home/aheinecke/dev/main/src/gpg4win/src/playground/build/libkleo-202309061056/src/utils/gnupg.cpp:18:
/home/aheinecke/dev/main/src/gpg4win/src/playground/install/include/QtCore/qbytearray.h:738:20: note: in call to 'QByteArray& QByteArray::replace(const char*, const char*)'
738 | inline QByteArray &QByteArray::replace(const char *before, const char *after)BTW, with one of the recent gpgme fixes we now get
$~/b/gpgme/tests/run-keylist --extern --verbose foo run-keylist: file /home/wk/s/gpgme/tests/run-keylist.c line 414: <Dirmngr> No keyserver available
which is what users (and kleopatra) expects.
Note that for vsd we also need to change our default configuration file. The new "none" value provides a better error message than the old default of assuming that the AD carries the keyserver (which it does not in practise).
Thank you.
Backported to 2.2 branch.
Sep 5 2023
Also, please retest T5960#172860 with the latest build.
The previous two changes will hopefully fix the error output of export to server. I'm not entirely sure about the missing line breaks.
With regard to the ü-error in the error message on keytocard somebody else has to check what's going wrong because I'm convinced that we are doing everything right.
[2188] org.kde.pim.libkleo: gpgConfGetConsoleOutputCodePage starting "C:\\Program Files x86)\\GnuPG VS-Desktop\\bin\\..\\GnuPG\\bin\\gpgconf.exe" --show-codepages [2188] org.kde.pim.libkleo: gpgConfGetConsoleOutputCodePage returns 0
The debug output of libkleo is missing. Please add org.kde.pim.libkleo.debug=true to your qtlogging.ini.
[1400] org.kde.pim.kleopatra: "C:\\Program Files (x86)\\GnuPG VS-Desktop\\GnuPG\\bin\\gpg.exe --send-keys 3A12118AD7F4CBB6FF38C6B8F615AD82F702FA1F gestartet ..." [1400] org.kde.pim.kleopatra: "gpg: NOTE: THIS IS A DEVELOPMENT VERSION!\r\ngpg: It is only intended for test purposes and should NOT be\r\ngpg: used in a production environment or with production keys!\r\ngpg: enabled debug flags: memstat trust extprog\r\ngpg: enabled compatibility flags:" [1400] org.kde.pim.kleopatra: "gpg: sende Schlüssel F615AD82F702FA1F auf ldap://" [1400] org.kde.pim.kleopatra: "gpg: Senden an Schlüsselserver fehlgeschlagen: Ungültige LDAP Credentials\r\ngpg: Senden an Schlüsselserver fehlgeschlagen: Ungültige LDAP Credentials\r\ngpg: keydb: handles=1 locks=0 parse=1 get=1\r\ngpg: build=0 update=0 insert=0 delete=0\r\ngpg: reset=0 found=1 not=0 cache=0 not=0\r\ngpg: kid_not_found_cache: count=0 peak=0 flushes=0\r\ngpg: sig_cache: total=2 cached=2 good=2 bad=0\r\ngpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0\r\n outmix=0 getlvl1=0/0 getlvl2=0/0\r\ngpg: rndjent stat: collector=0x00000000 calls=0 bytes=0\r\ngpg: secmem usage: 0/32768 bytes in 0 blocks"
Please provide the debug output, so that I can see which encoding was used to decode the error message.
In T5960#175302, @ebo wrote:Found in GnuPG-VS-Desktop-3.2.0-beta178, broken ü and no linebreaks:
Setting this to high after consultation with @werner, these issues should be fixed in next release.
Found in GnuPG-VS-Desktop-3.2.0-beta178, broken ü and no linebreaks:
Sep 4 2023
This is hopefully resolved. Setting to done because the fix cannot be verified with our builds of Kleopatra.
It also doesn't occur with the AppImage (Do we build a debug or unoptimized build for the AppImage?).
The problem doesn't occur with the development build. It also doesn't seem to occur with our Windows build.
Well 5.4.2 o.O and we on Tumbleweed are at 13.x gcc
