[SOLVED] Failure of winecfg on Multilib

arubin · 09-02-2009, 04:58 PM

I have installed mutlilib using Alien BOB's packages. I have compiled and installed wine but winecfg gives this

Quote:

alan@LavanKossot:~$ winecfg
wine: created the configuration directory '/home/alan/.wine'
Could not load wine-gecko. HTML rendering will be disabled.
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 136 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x21
Serial number of failed request: 3189
Current serial number in output stream: 3189
err

rocess:__wine_kernel_init boot event wait timed out
err:winecfg

pen_mountmgr failed to open mount manager err 2
fixme:msg

ack_message msg 14 (WM_ERASEBKGND) not supported yet
err:winecfg

pen_mountmgr failed to open mount manager err 2
alan@LavanKossot:~$

The winecfg window appears but no drives are being recognised.

Alien Bob · 09-02-2009, 05:31 PM

Quote:

Could not load wine-gecko. HTML rendering will be disabled.

This error should go away once you start winecfg for a second time.

Quote:

Major opcode of failed request: 136 (GLX)

Try disabling all 3D compositing desktop effects in KDE (assuming you are running that).

Eric

arubin · 09-03-2009, 03:17 AM

I think that the main problem is

mountmgr failed to open mount manager err 2

Wine does not see the drives and does not install programs.

samac · 09-03-2009, 06:39 AM

Winecfg working just fine with me, I am running Slackware64-13.0 multilib also. I installed wine from the latest slackbuilds using sbopkg.

samac

slackass · 09-03-2009, 09:53 AM

Wine-1.1.27 works perfect for me.
Slack64 Multi-Lib

Ramurd · 09-03-2009, 11:11 AM

The problem with wine not detecting drives has occurred to me once before; The solution seems to be somewhere in a registry setting (iirc a key in HKLM);

See if things change if you:
1) move .wine to .wine-orig
2) run winecfg

A new .wine directory should've been made, and hopefully your wine now sees drives; at least: that was the solution for me. Something either to do with a change in how wine connects to the mount manager iirc, it's a while back.

You can afterward run diff on various reg files or move the right stuff to the new .wine or otherwise "restore" wine. I can imagine this will be a bit of a mess to fix, and up to you which direction you'll head.

HTH

arubin · 09-03-2009, 12:57 PM

Well what I did was I copied the system.reg, user.red and userdef.reg files from my 12.2 wine installation into my new .wine and it now detecting drives.