Tips Tricks

From Mumble Wiki
Revision as of 22:39, 15 April 2011 by Lewellyn (talk | contribs) (Added reference to the GBS repository agreement.)
Jump to: navigation, search

Intention of this page

on this Page you can find Tips and Tricks from all kinds of sources.

The Tips on this page are just the so called nutshell solutions of those discussions. Some of these Tips are not officially supported or fully tested and should be executed at own risk.

Its likely that some of the content of this page will most likely be moved to different pages if the topic exceeds a certain level or interested.

Of course its always a good idea to search the forums or take actively part in discussion there. Even speak up on the IRC chartrooms for mumble or use a web search-engine to look for help (goggle yahoo or bing just to name a view)

Installation of Mumble on not natively supported OS


Installation of the Mumble client on Windows 2000

The Mumble-Client is only supported to be run on Windows XP or higher (VISTA/Win7 etc.). However it seams that following these steps most basic functions should work.

Here's a quick guide to get the mumble client running.

The fix is confirmed to be working for mumble 1.2.x Please read the Wrapper guide carefully and follow the fix step by step if you are having problems getting the client to work.

  • KERNEL32.dll - GetVolumePathNamesForVolumeNameW
  • ws_32.dll - getaddrinfo
  • wtsapi32.dll - WTSRegisterSessionNotification
  • psapi.dll - GetProcessImageFileNameW
  • dbghelp.dll - MiniDumpWriteDump

How to fix it: Get the KERNEL32.dll, ws_32.dll and wtsapi32.dll from the wrapper pack . Make sure you follow the instructions as the readme of the wrapper pack says.

Quick guide:

  • 1) Copy original corresponding dlls from WINNT\system32 in mumble-client main folder
  • 2) Rename them to kernel32_ORG.dll/wtsapi32_ORG.dll/ws_32_ORG.dll
  • 3) Place kernel32.dll/wtsapi32.dll/ws_32.dll from the wrapper zip file in the same folder
  • 4) Run ExcludeFromKnownDlls.reg if it's your first time using the wrapper.
  • 5) Get Dbghelp.dll, unzip and put it in the same folder.
  • 6) Get psapi.dll and put it in the same folder.
  • 7) Run the mumble Client !

WARNING: It's still strongly recommended to read the wrapper readme first and to backup your original before you start toying with your dlls.

(thanks to Akan and soma for this tip on the Forum)


Installation of murmur server on CentOS 5

Package Installation

There is an unofficial, unsupported, third-party package of (the statically linked) Murmur available for installation via yum. It has only been tested on CentOS 5.6 (i386) at this time, but should work on other RHEL 5.x versions and derivatives. If you have any problems or feedback (such as results on other distros besides Centos 5.6 i386), please find lewellyn on IRC. The package is not officially supported by anyone, but the package definition and configuration scripts derive from the Fedora 15-Alpha and Mandriva packages and the binary is the official static tarball from, the various pieces of which are known to work reliably.

(As of April 2011, the third-party GBS repository is providing Murmur 1.2.3.)

The steps are as follows:

  1. As root (such as via sudo), run: rpm -ivh
    1. Optional: Configure your new repository, for example using the priorities plugin.
  2. Install murmur from the new GBS repository you just added: (run the commands as root or via sudo)
    1. If you want to just install murmur and don't care about ensuring you have the proper dependencies for the web functions or dbus: yum install murmur
    2. Instead, if you want to make sure you have all the proper dependencies for running with dbus and the included web scripts (this package depends on murmur): yum install murmur-suggests
    3. NOTE: The first time you install a package from the GBS repository, you may/should get a prompt to accept the key. The proper ID for this key is 98b3c52e. If this matches what is on your screen, enter 'y' at the confirmation prompt.

That's it! Now you can service murmur start to start your new server. Or, if you wish, you can customize your configuration first.

Note that installing from the GBS repository indicates acceptance of the repository's agreement. Summary of the agreement is: No support nor warranty is offered, and if it breaks, you get to do what you will with the pieces.

Manual Installation

Here's the process for manually installing on CentOS 5.4, using the init script and config from a mandriva rpm and the 1.2.2 static binary release: (You can use this as the starting point for your own manual installation of the latest version.)

   yum install lzma
   cd ~/downloads
   cd ~/install
   lzcat ../downloads/murmur-static_x86-1.2.2.tar.lzma | tar -xf -
   cp murmur-static_x86-1.2.2/murmur.x86 /usr/sbin/murmurd
   rpm2cpio ../downloads/mumble-server-1.2.2-1mdv2010.1.x86_64.rpm > file.lzma
   lzma -d file.lzma
   mkdir mumble-rpm
   cd mumble-rpm
   cpio -imv --make-directories < ../file
   rm ../file
   cp etc/mumble-server.ini /etc
   cp etc/rc.d/init.d/mumble-server /etc/rc.d/init.d
   chmod a+x /etc/rc.d/init.d/mumble-server
   groupadd -g 4000 mumble-server
   useradd -g 4000 -G mumble-server -s /sbin/nologin -d / -M mumble-server
   mkdir /var/lib/mumble-server
   chown mumble-server:mumble-server /var/lib/mumble-server
   mkdir /var/log/mumble-server
   chown mumble-server:mumble-server /var/log/mumble-server
   vim /etc/rc.d/init.d/mumble-server

Change all occurrences of 'gprintf' to 'printf'

   service mumble-server start
   chkconfig --add mumble-server
   chkconfig --level 3 mumble-server on

(thanks to dominicc on the mumble forum)

Run Multiple instances of the Mumble Client

if you start the mumble client with the option -m You are allowed to start an other instance of the client on the same System. Be aware that this switch is unsupported and can cause all kinds of strange behaviours as the two clients still share the same config, database, overlay, get the idea ;-) (especially make sure you don't use volume attenuation^^)

Run Mumble Client without an active certificate

You can start Mumble with the -n command-line parameter to make it ignore the current user certificate. This way you can temporarily “disable” it for your Mumble process. In combination with the -m parameter for multiple instances you can connect twice to the same server, even though you’re registered with a certificate!