tag:blogger.com,1999:blog-6009412.post4566512743918936789..comments2023-10-12T00:49:04.552-07:00Comments on Roger's Blog: CoolTerm 1.4.5Rogerhttp://www.blogger.com/profile/16042220149029071213noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6009412.post-84881269946313084202016-12-25T14:30:05.672-08:002016-12-25T14:30:05.672-08:00Newer version of CoolTerm require additional 32-bi...Newer version of CoolTerm require additional 32-bit libraries to be installed on 64-bit Linux systems as compare to older versions. Here is some information that may be helpful in getting v1.4.6 working on your system:<br /><br /><i>64-bit and Library Information<br />==============================<br /><br />CoolTerm requires these libraries:<br /><br /> GTK+ 2.20<br /> glibc-2.11<br /> libstdc++.so.6.0.13<br /> libicu 4.2+<br /><br />On 64-bit Linux distributions, you will need to ensure the appropriate 32-bit compatibility libraries are installed in order to run CoolTerm. Note that glib 2.0 might not be included in 32-bit library packages. One of these commands usually works for Ubuntu:<br /><br /> sudo apt-get install ia32-libs<br /> sudo apt-get install ia32-libs-multiarch<br /><br />Newer versions of Ubuntu may require additional steps as well:<br /><br /> sudo dpkg --add-architecture i386<br /> sudo apt-get update<br /> sudo apt-get install ia32-libs-multiarch<br /><br />For more information on Multiarch support: https://wiki.debian.org/Multiarch/HOWTO .<br /><br />For RedHat-based Linux distributions (such as CentOS), this command should install 32-bit libraries:<br /><br /> /usr/bin/yum -y install gtk2.i686 glib2.i686 libgcc.i686 libstdc++.i686 libicu.i686<br /><br />To determine which libraries are used by CoolTerm, you can use the ldd command:<br /><br /> ldd CoolTerm<br /><br />LibICU<br />======<br /><br />Users of Debian/Ubuntu derivatives, (such as Linux Mint etc…), regardless of whether they are using a 32-bit or 64-bit distribution, should also install the 32-bit version of the "International Components for Unicode" library, i.e. "libicu52:i386", as follows:<br /><br /> sudo apt-get install libicu52:i386<br /><br />For RedHat-based Linux distributions (such as CentOS), this command is used:<br /><br /> yum install libicu.i686<br /><br />Alternatively, the library can also be installed via the appropriate package manager. Search for "libicu52" and select "libicu52:i386" to install it.</i>Rogerhttps://www.blogger.com/profile/16042220149029071213noreply@blogger.comtag:blogger.com,1999:blog-6009412.post-9843859800499797102016-12-25T13:52:41.932-08:002016-12-25T13:52:41.932-08:00Roger:
I tried 1.4.6 under gnome shell in Mageia L...Roger:<br />I tried 1.4.6 under gnome shell in Mageia Linux and encountered lots of errors. Let me share the few at the beginning. Sound like a gtk issue?<br /><br />$ /usr/local/CoolTermLinux/CoolTerm<br />Runtime Error<br />Please report what caused this error along with the information below.<br />RuntimeCore/ICUStable.cpp: 148<br />Failure Condition: functionPtr<br />Could not resolve u_strFromUTF8<br /><br />(process:6330): GLib-GObject-WARNING **: invalid (NULL) pointer instance<br /><br />(process:6330): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed<br /><br />(process:6330): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed<br /><br />(process:6330): GLib-GObject-CRITICAL **: g_object_get: assertion 'G_IS_OBJECT (object)' failed<br /><br />(process:6330): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Shelandyhttps://www.blogger.com/profile/17017800014253018816noreply@blogger.comtag:blogger.com,1999:blog-6009412.post-84070874487316290332015-06-19T10:14:25.055-07:002015-06-19T10:14:25.055-07:00Thanks for reporting this. Looks like you're c...Thanks for reporting this. Looks like you're correct. A single 0x80 seems to be doing this. I'll look into this. It's possible that the textfield that displays the plain data has a hard time displaying this character. The receive buffer obviously has all the data since the hex view shows everything.Rogerhttps://www.blogger.com/profile/16042220149029071213noreply@blogger.comtag:blogger.com,1999:blog-6009412.post-881939154142343942015-06-19T07:05:31.845-07:002015-06-19T07:05:31.845-07:00Hi Roger, I think I've found a minor issue wit...Hi Roger, I think I've found a minor issue with 1.4.5 and probably older versions. Receiving an ASCII 128 character ($80 hex) appears to 'break' the view ASCII window. It stops displaying incoming text while 'View Hex' mode does display the characters.<br /><br />Using 'Clear Data' resets things and it starts working again.<br /><br />I should say I don't know if it is a single $80 or a pair which causes this - I unintentionally receive two when manipulating the settings on my Bluetooth module. I can't easily send a single one to check.Anonymoushttps://www.blogger.com/profile/10712850515639245646noreply@blogger.com