4fc7df5dde
This originally started as a Linux-only improvement (support for "/etc/os-release"), but it became pretty clear that OSInfo was not in a pretty state. Please note that the auto-update system is not affected, because it doesn't rely on OSInfo. The most important change involves the OS name. Before this commit we had "Win32", "WinX64", "OSX" and "X11". The latter was particularly misleading now that Wayland is a thing. We now have "Windows", "Linux", "macOS", "FreeBSD", "NetBSD", "OpenBSD", "BSD", "UNIX" and "Unknown". The second most important change is the way we retrieve the version on OSes other than Windows and macOS. OSInfo had several methods, but none was aware of "/etc/os-release". We initially wanted to implement a new method, to be used as primary, that gathers info from that file. However, we later realized we can just use QSysInfo because it does exactly what we planned to do on our own. The reason why we're retaining our own methods for Windows and macOS is because they're MUCH more descriptive. For example, the build number is not in the strings returned by QSysInfo. In order to make the code easier to read, the parts that handled versions of Windows we no longer support is removed. The final change is about the info that is sent to our server. "is64bit" was set to the correct value on all platforms except for Windows, because IsWow64Process() returns true only when the process is 32 bit and running on a 64 bit OS. "arch" and "osarch" are introduced and represent the architecture of the program and the OS, respectively. "is64bit" is removed as it's now redundant. "osverbose" is also introduced and represents the full operating system version. |
||
|---|---|---|
| .ci | ||
| .github | ||
| .tx | ||
| 3rdparty | ||
| 3rdPartyLicenses | ||
| cmake | ||
| docs | ||
| g15helper | ||
| helpers/vcpkg/ports/zeroc-ice | ||
| icons | ||
| installer | ||
| macx | ||
| man | ||
| overlay | ||
| overlay_gl | ||
| overlay_winx64 | ||
| plugins | ||
| samples | ||
| screenshots | ||
| scripts | ||
| src | ||
| themes | ||
| .cirrus.yml | ||
| .clang-format | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| .travis.yml | ||
| AUTHORS | ||
| CHANGES | ||
| CMakeLists.txt | ||
| COMMIT_GUIDELINES.md | ||
| Dockerfile | ||
| Doxyfile | ||
| LICENSE | ||
| LICENSE.header | ||
| README.md | ||
| SECURITY.md | ||
| sonar-project.properties | ||
Mumble - Open Source voice-chat software
Mumble is an Open Source, low-latency and high-quality voice-chat program written on top of Qt and Opus.
There are two modules in Mumble; the client (mumble) and the server (murmur). The client works on Windows, Linux, FreeBSD and macOS, while the server should work on anything Qt can be installed on.
Please note that with "Windows" we mean 7 and newer. Vista may be supported, but we can't guarantee it. If you don't want to encounter potential issues, you may download Mumble 1.3.x, the last version to provide support for XP.
The documentation of the project can be found on the wiki. The FAQ can also be found there.
Contributing
We always welcome contributions to the project. If you have code that you would like to contribute, please go ahead and create a PR. While doing so, please try to make sure that you follow our commit guidelines.
Building
For information on how to build Mumble, checkout the dedicated documentation.
Reporting issues
If you want to report a bug or create a feature-request, you can open a new issue (after you have checked that there is none already) on GitHub.
Windows
Running Mumble
After installation, you should have a new Mumble folder in your Start Menu, from which you can start Mumble.
Running Murmur
Doubleclick the Murmur icon to start murmur. There will be a small icon on your taskbar from which you can view the log.
To set the superuser password, run murmur with the parameters -supw <password>.
MacOS
Running Mumble
To install Mumble, drag the application from the downloaded
disk image into your /Applications folder.
Running Murmur
Murmur is distributed separately from the Mumble client on MacOS. It is called Static OS X Server and can be downloaded from the main webpage.
Once downloaded it can be run in the same way as on any other Unix-like system. For more information please see the "Running Murmur" in the Linux/Unix section below.
Linux/Unix
Running Mumble
If you have installed Mumble through your distributon's package repostory, you should be able to find Mumble in your start menu. No additional steps necessary.
Running Murmur
Murmur should be run from the command line, so start a shell (command prompt) and go to wherever you installed Mumble. Run murmur as
murmurd [-supw <password>] [-ini <inifile>] [-fg] [v]
-supw Set a new password for the user SuperUser, which is hardcoded to
bypass ACLs. Keep this password safe. Until you set a password,
the SuperUser is disabled. If you use this option, murmur will
set the password in the database and then exit.
-ini Use an inifile other than murmur.ini, use this to run several instances
of murmur from the same directory. Make sure each instance is using
a separate database.
-fg Run in the foreground, logging to standard output.
-v More verbose logging.
OpenGL Overlay
The OpenGL overlay works by intercepting the call to switch buffers, and just before the buffer switch, we draw our nice GUI.
To load a game with the overlay enabled, start the game like this: LD_PRELOAD=/path/to/libmumble.so.1.1 gamename
If you have Mumble installed through the binary packages, this can be done by simply typing: mumble-overlay gamename