Frequently Asked Questions

Currently Smuxi is available in several binary packaged flavours. More information and instructions on how to install these can be found at our download page.

If you would like to get hold of the most recent stable release of the source code for Smuxi, you can either download the source tarball from the bottom of the download page.

OR

Obtain the most up to date version of the source by pulling the source from the Git repository (git://git.qnetp.net/smuxi.git).

Before compiling Smuxi from source (using the default configure options), the following dependencies must be met:

• log4net >= 1.2
• SmartIrc4net >= 0.4.5.1 (optional if IRC support is disabled)
• Mono >= 2.2 (1.9.1 if Twitter support is disabled)
• Nini >= 1.1

Optional:

• GTK# >= 2.8

Compiling from source is a very simple process once you have the requirements in place. Smuxi compiles much like any traditional unix application but directions on how to compile are listed below just in case.

First navigate to the directory that you've downloaded Smuxi's tarball source to. For instance, if the source is in your home directory you could try the following:

Untar the the tarball to extract the source

Navigate to the extracted directory

Now run ./configure, make and make install to compile the application from source. If you would like to look at the available options for ./configure please take a look at the next section before continuing.

A permission denied error may be thrown on the make install command because this tries to write to the /usr/local directory when installing. This directory is typically protected by default on most distributions and will need root access in order to install. To solve this you'll simply have to run the command with root privileges. The easiest way this can be done is with the "sudo" command available on most versions of Linux as shown above. Alternatively you can use the "su" command to log into an user with root privileges.

If all goes to plan, you should have a fully compiled version of Smuxi installed to /usr/local/bin.

Congratulations! :)

You should be able to run Smuxi now with the 'smuxi' command from the terminal. Smuxi-server can be started with the 'smuxi-server' command.

When using ./configure you can chain the commands so that you can tailor your own version of Smuxi which only contains the functionality you require. Below are some of the options available for ./configure.

Setting install location

default location is /usr/local

Remove front-end (Server only)

Remove Twitter support

Smuxi currently requires:

Currently there is no GUI to control the smuxi-server, thus you need to define a user and password yourself in the smuxi-engine.ini file and start the smuxi-server.exe manually. For more details head to this page.

Caret Mode which can be enabled and disabled in the menu: "View -> Caret Mode" or by pressing the F7 key, allows you to navigate through the output buffer using your cursor keys. That way you don't have to move your hand from the keyboard to the mouse. It also makes the selection in general easier if you want to copy/paste a specific string from it. The idea is from the Firefox Web Browser which also has this handy feature. This feature is also explained on Wikipedia here.

When using the bouncer psyBNC, smuxi is connecting but not joining any channels. This is caused by psyBNC only supporting the obsolete IRC RFC1459 instead of RFC2812. Smuxi uses the  SmartIrc4net library to implement the IRC functionality and it only supports RFC2812. The difference between the 2 RFCs regarding this issue is that RFC1459 doesn't specify the RPL_WELCOME confirmation upon successful login, thus SmartIrc4net believes it doesn't pass the login stage. I don't have plans to implement this obsolete RFC and thus Smuxi doesn't support psyBNC as long as psyBNC doesn't support RFC2812. (this issue is tracked in TRAC ticket #143)

You can get additional help about Smuxi in smuxi's home channel #smuxi @ irc.oftc.net.

Why does smuxi crash suddenly when I try to start it, with the confusing message dialog saying:

To be honest, I have no idea what the cause of that message/crash could be, I know it's corba/orbit (GNOME) related and I never saw it on Linux. But one smuxi alpha tester had that problem on Windows and it also hit me already on my Windows box. What helps is to delete %TEMP%/orbit-* and %TEMP%/gconfd-* %TEMP% is usually pointing to C:\Windows\TEMP

Starting smuxi logs or displays the following message:

That means you either do not have the required GTK# for MS .NET installed or you installed it but you didn't reboot or re-logged on to Windows. Please install GTK# for MS .NET and/or reboot or re-log on to Windows.

This error will occur when the host of the SSH server has changed the RSA keys for SSH. This is not a Smuxi error and can be fixed by editing your ~/.ssh/known_hosts file to add the correct keys. Be careful though, the reason this error was thrown in the first place is because the RSA keys have changed, it is up to you to trust the host of the server.

The easiest way to fix this is to simply delete the known_hosts file and start over this time accepting the new key. However this will remove all your saved keys for SSH.