FS#5604 - Wine assertion failure on first start

Attached to Project: Arch Linux
Opened by name withheld (Gullible Jones) - Tuesday, 17 October 2006, 00:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dale Blount (dale)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The first time Wine is run (via winecfg or whatever), this console output is generated:


Failed to open the service control manager.
fixme:ole:ITypeInfo_fnRelease destroy child objects
ll,InstallHinfSection: main/renderbuffer.c:2041: _mesa_add_renderbuffer: Assertion `bufferName == BUFFER_DEPTH || bufferName == BUFFER_STENCIL || fb->Attachment[bufferName].Renderbuffer == ((void *)0)' failed.
wine: Assertion failed at address 0xb7fbc410 (thread 0009), starting debugger...


And this popup message is shown:


Assertion failed at adress 0xb7fbc410.
Do you wish to debug it?


If you hit "No", Wine exits. If you hit "Yes", it produces this console output:


fixme:dbghelp:SymLoadModule Should have successfully loaded debug information for image c:\windows\system32\imm32.dll
fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for c0000119


And starts after about 30 more seconds. After the first start, this behavior ceases.
This task depends upon

Closed by  Dale Blount (dale)
Sunday, 12 November 2006, 16:25 GMT
Reason for closing:  Fixed
Comment by Dale Blount (dale) - Tuesday, 17 October 2006, 13:11 GMT
Did you try setting vm.legacy_va_layout = 1 in sysctl.conf per wine.install ?
Comment by name withheld (Gullible Jones) - Tuesday, 17 October 2006, 20:41 GMT
The install recommended removing it actually.

>>> As of kernel 2.6.18, WINE will not work unless you disable the Legacy
>>> VM Layout, else you will get segfaults!
>>> Please remove the old entry from your /etc/sysctl.conf
>>> vm.legacy_va_layout = 1

I don't have that set to 1 in sysctl.conf and never did.
Comment by Woody Gilk (Shadowhand) - Tuesday, 17 October 2006, 22:14 GMT
Reproduction Steps:

created a new user (new_user)
add new_user to video group (to allow starting of X apps)
ssh -X new_user@localhost
run winecfg (no ~/.wine exists at this point)

Here's the console output:

wine: creating configuration directory '/home/new_user/.wine'...
Failed to open the service control manager.
fixme:ole:ITypeInfo_fnRelease destroy child objects
err:wgl:process_attach Could not create default context.
wine: '/home/new_user/.wine' created successfully.

Output of "wine --version":

Wine 0.9.22
Comment by Dale Blount (dale) - Tuesday, 17 October 2006, 22:30 GMT
same here, but I'm running the just recently upgraded version.

$ wine --version
Wine 0.9.23

We can't reproduce your error.
Comment by name withheld (Gullible Jones) - Tuesday, 17 October 2006, 22:40 GMT
Remove the configuration files and try running winecfg.
Comment by Dale Blount (dale) - Tuesday, 17 October 2006, 22:55 GMT
both Woody and I have created brand new users with no .wine dirs and don't get this problem...

wine: creating configuration directory '/home/test/.wine'...
Failed to open the service control manager.
fixme:ole:ITypeInfo_fnRelease destroy child objects
wine: '/home/test/.wine' created successfully


Is your system otherwise fully up to date?
Comment by name withheld (Gullible Jones) - Tuesday, 17 October 2006, 23:54 GMT
Yep, definitely up to date.
Comment by name withheld (Gullible Jones) - Tuesday, 17 October 2006, 23:56 GMT
Wait a minute, I am using Testing at the moment. I wonder if there's something in there that Wine doesn't like?
Comment by Dale Blount (dale) - Saturday, 11 November 2006, 20:13 GMT
0.9.25 is being posted soon, please try that and report back.
Comment by name withheld (Gullible Jones) - Sunday, 12 November 2006, 16:11 GMT
Yep, fixed in 0.9.25.

Loading...