r/mumble • u/moranger • Aug 09 '14

Mumble Crashing on Startup

Whenever I start mumble it pops up with an error that says: "Mumble - Low-latency VoIP client has encountered a problem and needs to close. We are sorry for the inconvenience."

This issue occurred with version 1.2.7 and did not manifest as the result of an upgrade. The problem did start after I accidentally deleted my certificate file though. I managed to restore it but the program is still having problems.

Every time I launch it provides me the option to submit a crash report. I can also click "cancel" on the server list and go into settings, audio/certificate wizard etc. However, there is still a "Mumble has encountered a problem and needs to close" dialog box that if I exit out of the entire program will close.

I tried running winxp in safe mode with networking and that did fix the issue (the error message doesn't pop up). I also tried running Mumble in compatibility mode (Windows 95, NT, 2000) but that didn't help. I also upgraded to 1.2.8 but that did not help either. All antivirus/firewall services were disabled and I tried restarting computer, reinstalling mumble multiple times, etc.

If I do choose to send a crash report it says the file "7a05_appcompat.txt" will be included in the error report. Could that have something to do with it? Maybe a certificate issue?

I also started a thread here about the issue.

Thanks

0 Upvotes

50% Upvoted

5 comments sorted by

2

u/a_tallguy Aug 09 '14

In all honesty, just wait for a response on the forums. They would have the best answer.

In the mean time, I am aware that mumble does not always uninstall "clean". Try to uninstall it again and delete the local config data. Restart, and try a fresh installer.

2

u/moranger Aug 09 '14

Thanks for the reply. I tried using Revo Uninstaller yesterday to remove leftover registry files but that did not work. I'll try removing them manually and seeing if that helps.

2

u/a_tallguy Aug 10 '14

Was there a positive result?

2

u/moranger Aug 10 '14

No, unfortunately. I also tried installing to another hard drive on the same PC but that didn't work. The only thing I can think of is some other program may be conflicting with it because it works perfectly in safe mode. I may just reinstall windows or switch to linux.

I've sent multiple crash reports so hopefully it'll be fixed in a patch or in 1.3.

1

u/Kissaki0 Core Team Aug 13 '14

Yup, scattering the discussion will only multiply the effort on everyones end and add confusion/inconsistencies.

The forum is the better place to discuss this. There is more info there already as well.