Daedalus 0.11.1 and Cardano SL 1.3.1
BUG FIXES AND IMPROVEMENTS
WARNING WHEN DAEDALUS IS LAUNCHED IMPROPERLY AFTER PINNING TO WINDOWS TASKBAR
Some Windows users have been creating shortcuts for launching Daedalus from the daedalus.exe file. They usually do this by right-clicking on the Daedalus icon in the taskbar while it is running, and selecting ‘Pin this program to taskbar’ option. This is an improper way of launching Daedalus. It should be launched from cardano-launcher.exe, which configures daedalus.exe and launches a Cardano node in the background. People who were using the incorrect technique were stuck on the blue loading screen with a ‘Connecting to network’ message. An update has been made so that Daedalus now detects this situation and displays an error message with instructions to launch from the Windows start menu or from the desktop icon created by the Daedalus installer.
A BLANK SCREEN IS SHOWN INSTEAD OF THE USER INTERFACE
Some graphics card drivers were rendering a blank white screen instead of the user interface. There is now an option to restart Daedalus in safe mode without graphics acceleration, which fixes this issue. Safe mode can be activated using the ‘GPU safe mode’ option in the Daedalus system menu.
QR CODES FROM PAPER WALLET CERTIFICATES WERE SOMETIMES UNREADABLE
Some QR code readers were unable to scan QR codes from paper wallet certificates because there was too much error correction data in printed QR codes. This issue is now fixed.
INTERNET DISRUPTION WAS CAUSING BLOCKCHAIN SYNCHRONIZATION TO STOP
In some cases, after an internet connection was lost, blockchain synchronization did not continue when the link was re-established. Users who experienced this were seeing a ‘Connecting to network’ message on the loading screen. This issue has been fixed.
USERS WITH NON-LATIN CHARACTERS IN THEIR WINDOWS USERNAME WERE UNABLE TO USE DAEDALUS FOR WINDOWS
All users who have non-Latin characters (Latin characters are: a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z) in their Windows username were unable to use Daedalus. For these users, Daedalus was stuck on the blue loading screen with the “Cannot connect to network” message. This issue was affecting all previous versions of Daedalus and is now fixed.
Protocol magic number used to differentiate between networks was not taken into account when validating destination addresses for transactions. This problem would allow transactions to be accepted on one network that include destination addresses from a different network. This issue has been fixed. Any such transactions will be invalid and will be rejected by the network.
UPDATE INSTALLATIONS SOMETIMES FAIL
Sometimes, after clicking on ‘Update and restart’ Daedalus will shut down, but the installation of the update will not start. If the user then tries to launch Daedalus within 60 seconds of Daedalus shutting down, the update will fail. The way around this problem is to wait for a minute after Daedalus shuts down and then start Daedalus manually. This will begin the installation process and avoid the problem.
Alternatively, the update can be made by downloading the latest installer from the Daedalus website and installing the new version of Daedalus manually. This will cure the problem.