Welcome …

Posted on

Teamviewer – package architecture (i386) does not match system (amd64)

The teamviewer installation error “package architecture (i386) does not match system (amd64)” is observed on when attempting an install on 64 bit versions of either Debian or Ubuntu. This article details how to solve this quickly and easily.

This comes from using a “multiarch” or “multiple-architecture” installer as opposed to one which has been expressly compiled for wither i386 or amd64 architectures; from the Debian site:

“Multiarch is the term being used to refer to the capability of a system to install and run applications of multiple different binary targets on the same system. For example running a i386-linux-gnu application on an amd64-linux-gnu system.”

Symptoms:

The error is observed once an install is attempted with:

sudo dpkg -i teamviewer_linux.deb

Solution

Download

The latest teamviewer package for linux can always be downloaded using the following:

wget http://www.teamviewer.com/download/teamviewer_linux.deb

Download linux teamviewer installer

Add i386 Architecture to dpkg

The following command will add the i386 directives to dpkg:

sudo dpkg --add-architecture i386

Add i386 architecture to dpkg

Update Sources

We now need to update our sources so that the system knows about the new i386 packages:

sudo apt-get update

Update Package Sources

Install Teamviewer

We can now go ahead and try to install Teamviewer again. This will partially work but some of its dependencies will be unfulfilled, shown with the errors “dependency problems – leaving unconfigured” – we will address this in the next step.

sudo dpkg -i teamviewer_linux.deb

Run Teamviewer installer again

Fix Unfulfilled Dependencies

Running the apt-get with the “-f” or “–fix-broken” switch will resolve any missing dependencies for installed programs:

sudo apt-get install -f

Resolve Unfulfilled Dependencies

Start Teamviewer!

Open Teamviewer From the Menu:

From the applications menu, navigate to Internet and Teamviewer should be available for selection:

Accept the EULA ..
And Away We Go!

 

Related posts:

Posted on

Quick Reference: apt-get

apt-get is the command-line tool for handling packages for Debian Linux which is use to:

  • Install/manage individual packages
  • Upgrade packages
  • Apply security patch(s)
  • Keep Debian system up to date
  • Download source .deb files
  • Has many GUI and other utilities as front-ends

Here is quick cheat sheet you will find handy while using apt-get at shell prompt:

Syntax Description Example(s)
apt-get install {package} Install the new package. If package is installed then try to upgrade to latest version apt-get install zip
apt-get install lsof samba mysql-client
apt-get install {package} -f Install the new package and fix any broken dependencies. “-f” equates to “–fix-broken” apt-get install -f zip
apt-get install -f lsof samba mysql-client
apt-get remove {package} Remove/Delete an installed package except configuration files apt-get remove zip
apt-get –purge remove {package} Remove/Delete everything including configuration files apt-get –purge remove mysql-server
apt-get update
apt-get upgrade		 Resynchronize the package index files and Upgrade the Debian Linux system including security update (Internet access required) apt-get update
apt-get upgrade
apt-get update
apt-get dist-upgrade		 Usually use to upgrade to Debian distribution. For example Woody to Sarge upgrade. ‘dist-upgrade’ in addition to performing the function of upgrade, also intelligently handles changing dependencies with new versions of packages; apt-get has a “smart” conflict resolution system, and it will attempt to upgrade the most important packages at the expense of less important ones if necessary. apt-get update
apt-get dist-upgrade

{package} – Replace with actual package name

The full man page for apt-get can be found here: http://ss64.com/bash/apt-get.html

Related posts:

Posted on

Cannot Contact the Specified Host Error

Workaround for the Cannot contact the specified host” error

This article describes how to work around the “Cannot contact the specified host” error when connecting an ESXi host to a vCenter after upgrading it to 5.5 U3b.

” Cannot contact the specified host. The host may not be available on the network, a network configuration problem may exist, or the management service on this host is not responding “

This error comes about due to SSLv3 and its associated POODLE vulnerability being disabled in the latest update – 5.5 U3b. The vCenter tries to talk SSL v3 to the host which is dropped straight away with a FIN return packet from the host.

The ideal solution is to upgrade your vCenter to 5.5 U3b. Should this not be an option for whatever reason, you can enable SSL v3 on your ESXi host – be aware of the security implications though!

There are two parts where you need to enable SSLv3:

1. Enabling SSLv3 for Hostd – Port 443

1. Open a SSH to this ESXi host.
2. Browse to this location using the below command: 
# cd /etc/vmware/rhttpproxy

3. Backup the config file:

# cp config.xml config.xml.bak

4. Edit the file using the below command (Press i to begin edit)

# vi config.xml

Locate the <vmacore>, then locate the <ssl> Under <ssl> add the following entry:

<sslOptions>16924672</sslOptions>

5.Save the file by pressing Esc and then typing :wq!

2. Enabling SSLv3 for Port 902 (Required to connect to vCenter)

1. From the same SSH of the host, run the below command: 
# esxcli system settings advanced set -o /UserVars/VMAuthdDisabledProtocols -s ""

Restart the rhhtpproxy using the below command:

# /etc/init.d/rhttpproxy restart
That’s it, now you can connect this ESXi 5.5 U3b host to a lower version of vCenter. To reiterate: this is not a recommended practice as it will expose the host to the SSLv3 POODLE vulnerability.

No related posts.

Exit mobile version
%%footer%%