Hi!
I just updated my wine from the CVS and now word is refusing to work.
It starts up as usual, but after typing 2 - 3 characters it stucks, and
the following is written to the console (beginning with fixme:nls, the former
is written during startup and seems harmless):
I think that the last two lines are the ones describing the problem. They
appear almost together. Sometimes there are other places blocked.
Waiting 60 seconds obviously tries to start the debugger...
With regards, Pavel Troller
patrol@arcus:/opt/samba-dir/Program Files/Microsoft Office/Office$ wine
WINWORD.EXE
Could not stat /mnt/fd0d (No such file or directory), ignoring drive A:
Could not stat /mnt/cd (No such file or directory), ignoring drive D:
fixme:x11drv:X11DRV_GetDeviceCaps (0x734): CAPS1 is unimplemented, will return 0
fixme:icon:DrawIconEx no flags set? setting to DI_NORMAL
fixme:nls:EnumDateFormatsW (0x3013618f, 1029, 2): stub
fixme:nls:EnumDateFormatsW (0x3013618f, 5, 2): stub
fixme:nls:EnumDateFormatsW (0x3013618f, 1029, 2): stub
fixme:nls:EnumDateFormatsW (0x301361da, 1029, 1): stub
fixme:nls:EnumDateFormatsW (0x301361da, 5, 1): stub
fixme:nls:EnumDateFormatsW (0x301361da, 1029, 1): stub
fixme:nls:EnumTimeFormatsW (0x301361f6,1029,0): stub
fixme:nls:EnumTimeFormatsW (0x301361f6,5,0): stub
fixme:nls:EnumTimeFormatsW (0x301361f6,1029,0): stub
err:ntdll:RtlpWaitForCriticalSection section 0x40b26180
"../../objects/gdiobj.c: GDI_level" wait timed out in thread 000e,
blocked by 000f, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x40b26180
"../../objects/gdiobj.c: GDI_level" wait timed out in thread 0009,
blocked by 000f, retrying (60 sec)
Killed