yubikey-manager-qt
yubikey-manager-qt copied to clipboard
ykman-gui.exe crashes at startup
In Windows 7 SP1, Yubikey Manager installed from yubikey-manager-qt-1.0.0-win64.exe (or yubikey-manager-qt-1.0.0-win32.exe) crashes when being started.
If I launch it from command line: ykman-gui.exe --log-level DEBUG --log-file C:\Users\blah\Documents\ykman-gui.log, this gives me no log file at all. ykman.exe that is installed by the same binary seems to work well (at least "ykman info" is OK).
That's not much information on the origin of the problem... but I can do more tests if you have suggestions.
Thanks for the report,
Do you get any crash logs at all from the crash?
Does it make any difference to set the environment variable QT_OPENGL
to angle
or software
before launching the app?
@dagheyman Good guess! The value of QT_OPENGL matters. When set to "software", it works. When set to "angle", it opens without crashing, but the "icons" in front of the Help and About buttons are replaced by dark solid squares.
When it crashes, Windows displays a window that shows a few things:
Signature du problème :
Nom d’événement de problème: BEX64
Nom de l’application: ykman-gui.exe
Version de l’application: 1.0.0.1
Horodatage de l’application: 5ba8904b
Nom du module par défaut: StackHash_1dc2
Version du module par défaut: 0.0.0.0
Horodateur du module par défaut: 00000000
Décalage de l’exception: 0000000000000000
Code de l’exception: c0000005
Données d’exception: 0000000000000008
Version du système: 6.1.7601.2.1.0.256.48
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: 1dc2
Information supplémentaire n° 2: 1dc22fb1de37d348f27e54dbb5278e7d
Information supplémentaire n° 3: eae3
Information supplémentaire n° 4: eae36a4b5ffb27c9d33117f4125a75c2
That means the issue is related to the OpenGL rendering, I would recommend to try to see if there are any updates available for your graphics driver. What machine are you running? (hardware, graphics card, etc)
The host is a Lenovo X230 laptop with Windows 7, 64 bits. The graphics driver installed is "Intel(R) HD Graphics 4000", version 10.18.10.4425, 04/04/2016".
If I try to install the latest driver version, I get an error telling me that that version was not validated by the computer's manufacturer. By looking at the Lenovo website, there seem to be no new version validated since 2016.
Update: I took the risk to force the installation of the latest graphics driver (10.18.10.5059, 16/08/2018) by following the steps here: https://www.howtogeek.com/343287/how-to-fix-the-driver-being-installed-is-not-validated-for-this-computer-on-intel-computers/
The Yubikey Manager still crashes when being started.
Hi folks,
I had the exact same error on a Dell Latitude E5430 Win7 64 Intel® Core™ i5-3230M CPU @ 2.60GHz Intel HD Graphic 4000 driver version 10.18.10.4425
Like @instantname I was not able to install the latest driver 15.33.47.5059 from Intel because I get an error "Your computer manufacturer didn't verified that driver". Of course, version 10.18.10.4425 is the latest provided on Dell website for my pretty old laptop.
I confirm that setting QT_OPENGL=software
before running ykman-gui.exe
works as expected.
Since this bug is most probably related to https://bugreports.qt.io/browse/QTBUG-50371, upgrading Qt to version 5.12 should fix this issue. This version is currently at Beta stage and will be released at the end of this year (2018)
Latest release (1.1.1) is built with Qt 5.12, does it work better?
I have tested this install: https://developers.yubico.com/yubikey-manager-qt/Releases/yubikey-manager-qt-1.1.1-win64.exe.
Without the QT_OPENGL=software environment variable, YK Manager still crashes when starting.
Unfortunately, I dont work anymore with the hardware I used to reproduce and report the issue 5 months ago. I will not be able to test fixes.
Just like to follow up on this, I have exactly the same issue with the latest NVidia drivers (471.11) and windows updates (21H1).
Seems to work okay once i set the QT_OPENGL
environment variable to software.
I will add that its first launch seems fine, it will only crash after I have closed it at least once.
OS: Windows 10 Software version: 5.0.1
Had this same problem recently where I opened the software and it immediately closed. What worked for me finally was running Powershell in admin, navigating to the Yubikey Manager CLI folder, then running ykman.exe.
i.e. cd .. (until you hit C:/) cd Program" "Files cd Yubico cd YubiKey" "Manager" "CLI ykman.exe [whatever commands]
I'm not very technologically inclined so I couldn't follow what was going on in this thread, but this helped me a lot and hopefully it helps someone else.