starred/mumble-mumble-voip

Fork 0

mirror of https://github.com/mumble-voip/mumble.git synced 2026-03-03 00:46:56 -05:00

Provide an official 'portable' Mumble for Windows #275

New issue

Open

opened 2026-02-20 19:20:09 -05:00 by deekerman · 11 comments

deekerman commented

2026-02-20 19:20:09 -05:00

Owner

Originally created by @mkrautz on GitHub (Jun 20, 2014).

Originally assigned to: @mkrautz on GitHub.

On OS X, having multiple versions of Mumble installed is easy. Simply duplicate the app bundle, and rename to 'Mumble .app'. Tada!

On Windows, it's not so.

For development purposes, it'd be very handy to have a portable version of Mumble available. And since we developers need it, it's most likely also a feature that users would want.

One problem with a portable install is the inability to gain uiAccess=true to peek at global shortcuts from elevated games such as MMOs. Perhaps we'd want to add a notice to the Shortcuts config dialog mentioning that this feature is not enabled to avoid confusion?

Technically, this could be achieved by building with CONFIG+=no-elevation, and then conditionally compiling in the notice when that CONFIG flag is set.

Originally created by @mkrautz on GitHub (Jun 20, 2014). Originally assigned to: @mkrautz on GitHub. On OS X, having multiple versions of Mumble installed is easy. Simply duplicate the app bundle, and rename to 'Mumble <version>.app'. Tada! On Windows, it's not so. For development purposes, it'd be very handy to have a portable version of Mumble available. And since we developers need it, it's most likely also a feature that users would want. One problem with a portable install is the inability to gain uiAccess=true to peek at global shortcuts from elevated games such as MMOs. Perhaps we'd want to add a notice to the Shortcuts config dialog mentioning that this feature is not enabled to avoid confusion? Technically, this could be achieved by building with CONFIG+=no-elevation, and then conditionally compiling in the notice when that CONFIG flag is set.

deekerman added the

client

windows

release-management

labels

2026-02-20 19:20:09 -05:00

deekerman commented

2026-02-20 19:20:12 -05:00

Author

Owner

@CydFSA commented on GitHub (Jul 10, 2014):

Try creating an empty Mumble.ini in the folder and using the -m argument (I think it's -m...).

@CydFSA commented on GitHub (Jul 10, 2014): Try creating an empty Mumble.ini in the folder and using the -m argument (I think it's -m...).

deekerman commented

2026-02-20 19:20:12 -05:00

Author

Owner

@mkrautz commented on GitHub (Jul 10, 2014):

Yes. That's the process.

But the point of this issue is to provide portable ZIP files for all of our Windows builds, so we can use them for tracking down regressions, security issues, and so on.

A convenient side effect is that it will provide a simple download for users who want a portable install, instead of having to know 'the INI trick'.

@mkrautz commented on GitHub (Jul 10, 2014): Yes. That's the process. But the point of this issue is to provide portable ZIP files for all of our Windows builds, so we can use them for tracking down regressions, security issues, and so on. A convenient side effect is that it will provide a simple download for users who want a portable install, instead of having to know 'the INI trick'.

deekerman commented

2026-02-20 19:20:13 -05:00

Author

Owner

@hacst commented on GitHub (Sep 20, 2014):

Imho this isn't essential to have in the 1.3.0 timeframe.

@hacst commented on GitHub (Sep 20, 2014): Imho this isn't essential to have in the 1.3.0 timeframe.

deekerman commented

2026-02-20 19:20:13 -05:00

Author

Owner

@2wayne commented on GitHub (Nov 10, 2014):

Will this feature be implemented in the near future?
I am asking because I am unsure if the installation registers something which wouldn't make it portable even if you use mumble.ini.

@2wayne commented on GitHub (Nov 10, 2014): Will this feature be implemented in the near future? I am asking because I am unsure if the installation registers something which wouldn't make it portable even if you use mumble.ini.

deekerman commented

2026-02-20 19:20:13 -05:00

Author

Owner

@jagodragon commented on GitHub (Sep 10, 2015):

The problem i've had with this is that when you use the mumble .ini, windows will periodically lock the ini file and make a new one. this results in lost settings... i was attempting to use this to push an already setup mumble to all my guildies... the problem became apparent almost immediately when the complaints started pouring in...

@jagodragon commented on GitHub (Sep 10, 2015): The problem i've had with this is that when you use the mumble .ini, windows will periodically lock the ini file and make a new one. this results in lost settings... i was attempting to use this to push an already setup mumble to all my guildies... the problem became apparent almost immediately when the complaints started pouring in...

deekerman commented

2026-02-20 19:20:13 -05:00

Author

Owner

@mkrautz commented on GitHub (Nov 28, 2015):

Reassigning to 1.4.0.

It is not critical for 1.3.0.

@mkrautz commented on GitHub (Nov 28, 2015): Reassigning to 1.4.0. It is not critical for 1.3.0.

deekerman commented

2026-02-20 19:20:13 -05:00

Author

Owner

@thejustsoul commented on GitHub (Nov 1, 2017):

Some time ago, after a sudden power outage, I was surprised to find that mumble has lost all its settings (mumble.ini). It is folded. It was first observed, generally, programs using .INI configs. It is possible to prevent in the future? But to make a backup config. Mumble 1.2.19, Win 7 x64.

@thejustsoul commented on GitHub (Nov 1, 2017): Some time ago, after a sudden power outage, I was surprised to find that mumble has lost all its settings (mumble.ini). It is folded. It was first observed, generally, programs using .INI configs. It is possible to prevent in the future? But to make a backup config. `Mumble 1.2.19`, `Win 7 x64`.

deekerman commented

2026-02-20 19:20:13 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Nov 1, 2017):

Sorry to hear that.

We already fixed the problem with #3255, it shouldn't happen anymore.

The problem is still there for 1.2.x, as we didn't release a new version after the fix.

@davidebeatrici commented on GitHub (Nov 1, 2017): Sorry to hear that. We already fixed the problem with #3255, it shouldn't happen anymore. The problem is still there for 1.2.x, as we didn't release a new version after the fix.

deekerman commented

2026-02-20 19:20:13 -05:00

Author

Owner

@thejustsoul commented on GitHub (Nov 1, 2017):

@davidebeatrici Thank you, when can we expect a new release?

@thejustsoul commented on GitHub (Nov 1, 2017): @davidebeatrici Thank you, when can we expect a new release?

deekerman commented

2026-02-20 19:20:13 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Nov 1, 2017):

We don't have an ETA yet, but for now you can use development snapshots.

@davidebeatrici commented on GitHub (Nov 1, 2017): We don't have an ETA yet, but for now you can use development snapshots.

deekerman commented

2026-02-20 19:20:13 -05:00

Author

Owner

@bilogic commented on GitHub (Oct 8, 2024):

Try creating an empty Mumble.ini in the folder and using the -m argument (I think it's -m...).

It's -c/--config, not -m. And from sleuthing, it is a JSON file, not INI.

On windows, I found it in cd %localappdata%\Mumble\Mumble

@bilogic commented on GitHub (Oct 8, 2024): > Try creating an empty Mumble.ini in the folder and using the -m argument (I think it's -m...). It's `-c`/`--config`, not `-m`. And from sleuthing, it is a JSON file, not INI. On windows, I found it in `cd %localappdata%\Mumble\Mumble`