Hi.
I've just upgraded to the latest release from the previous build for Linux 64bit and whilst Veracrypt opens fine, I couldn't help but notice that this time around (installed via PPA on this occasion..) when installing in KDE (4), XTerm and UXTerm are installed also.. Listed as dependencies in fact. I was just wondering why that might be the case..
Additionally when I clicked on the 'About' under the 'Help' menu to ensure I had upgraded correctly, I receive the following assertion failed message as detailed in the attached.
Wondered whether you might be able to address either of these concerns..?
I am running Kubuntu 14.04 LTS 64bit incidentally if that helps.
Regards,
Chuck
Comments: Hi,
I asked the PPA maintainer about the XTerm dependency and I'll update this ticket with his answer. My personal opinion is that it is a dependency of wxWidgets on Ubuntu since the PPA binaries are linked against the official Ubuntu wxWidgets library and replay the system tray icon with an application indicator applet.
On the other hand, VeraCrypt official Linux binaries are linked against unmodified official wxWidgets sources with minimal dependencies in order to run on all Linux distributions. To avoid any conflicts and dependency issues, it is always advisable to use the official VeraCrypt binaries.
Concerning the assertion failed message, this is a know issue with wxWidgets and code generated by wxFormBuilder: http://trac.wxwidgets.org/ticket/14594
The official VeraCrypt binaries are linked against a static wxWidgets library where this type of harmless assertions are not displayed. So, that's why there is no such message when using them.
The PPA binaries are linked against Ubuntu wxWidgets library which is more verbose and that's why you get such messages.
I didn't address this since it doesn't manifest itself with the official binaries. The obvious solution would be to make wxFormBuilder generate calls to SetMaxLength that doen't use 0 on GTK, but this needs some work. Another way would be to turn off wxWidgets assertion programatically but this is not clean.
Anyway, I'll try to find the best solution for these assertions. For now, either ignore them or use the official VeraCrypt binary.