Post reply

Topic Summary

Posted by: nylly444

« on: April 04, 2012, 11:35:03 am »

Insert Quote

Personally I prefer to compile my own binary.
That being said you can find up to date packages for main distros here: http://www.winehq.org/download/

http://appdb.winehq.org/objectManager.php?sClass=version&iId=2844
This is the AddDB entry for winmx, if some version doesn't work you can usually find the info on there (look for familar names, hehe).
Feel free to add your own test data

Posted by: GhostShip

« on: April 03, 2012, 05:12:59 pm »

Insert Quote

From what you have posted it sounds purely to be an update issue, you can of course revert back a version or two of Wine and see if anything changes, one of the folks who know more about Wine will be along no doubt with more detailed advice but thats what I suggest you try first as it will also narrow down the potential problem scope if it makes no difference and you still see such msgs.

Posted by: dabud

« on: April 03, 2012, 04:57:29 pm »

Insert Quote

opensuse 12.1 64 bit kde 4.7 wine 1.3.30-2.1.2-x86_64 winmx 3.54b4

I haven't seen this error in quite a long while:
"Winmx has encountered a serious error and has to close..."

but have been getting it now after upgrading to opensuse 12.1 and newer wine version.

If it is going to occur, it usually happens just after I start winmx and of course I must restart winmx.
Upon restarting winmx it may occur again or not, but on a second or third restart winmx is usually OK.

Does anyone know if this stems from winmx itself or is it a wine problem?
And, of course, what can I do about it?

Thanks