mount manager error

[abraxa]

i am not sure this is a wine issue after all, as i have not found actual, related posts here or in the arch forum. anyway, i thought i might bring this up.

since yesterday's wine update to 5.6-1, my 64bit prefix does not display the mounting tab anymore.

Code: Select all

winecfg
000b:err:seh:setup_exception stack overflow 432 bytes in thread 000b eip 000000007bcbc023 esp 0000000000121460 stack 0x120000-0x121000-0x220000
0012:err:winecfg:open_mountmgr failed to open mount manager err 2

creating a new prefix is also not possible anymore.

Code: Select all

WINEPREFIX=~/.wine winecfg
wine: created the configuration directory '/home/user/.wine'
000b:err:seh:setup_exception stack overflow 432 bytes in thread 000b eip 000000007bcbc023 esp 0000000000131460 stack 0x130000-0x131000-0x230000
0009:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0009:err:module:LdrInitializeThunk "kernelbase.dll" failed to initialize, aborting
0009:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\system32\\winecfg.exe" failed, status c0000005

something is seriously broken, anything on my side to fix this issue?

[spoon0042]

Probably this bug or there might have been another one.

You can downgrade or wait for 5.7 which should be released shortly.

[abraxa]

ok, thank you for the input.

one quick question: will starting winecfg in such situations ruin a wineprefix? will there be some odd leftovers, so it is better to step backwards and rather import a backup.

[spoon0042]

There shouldn't be any issue, no. Always good to have a backup though.

[abraxa]

thank you again, very appreciated.

well, i was in the need to downgrade a single-package-tool only once long time ago, but with wine, you have many dependencies, which all need to be checked too, i guess.

not really ideal, but i think i'll better wait for the next version to get released.

[abraxa]

i am now on wine 5.7-1, which fixes the mount tab issue.

strangely, this terminal error message appears when opening the tab:

Code: Select all

winecfg
wine: Read access denied for device L"\\??\\F:\\", FS volume label and serial are not available.
wine: Read access denied for device L"\\??\\G:\\", FS volume label and serial are not available.
wine: Read access denied for device L"\\??\\J:\\", FS volume label and serial are not available.

and this cdrom (e:) related error can be found in syslog after starting winecfg:

Code: Select all

kernel	Buffer I/O error on dev sr0, logical block 0, async page read
kernel	Buffer I/O error on dev sr0, logical block 1, async page read
kernel	Buffer I/O error on dev sr0, logical block 2, async page read
kernel	Buffer I/O error on dev sr0, logical block 3, async page read
kernel	Buffer I/O error on dev sr0, logical block 4, async page read
kernel	Buffer I/O error on dev sr0, logical block 5, async page read
kernel	Buffer I/O error on dev sr0, logical block 6, async page read
kernel	Buffer I/O error on dev sr0, logical block 7, async page read

the interesting thing is, i have not assigned a drive f:, and g: keeps on reappearing over and over again while it is supposed to be my permanently attached usb drive at j:, which now seems unavaiable? in fact i can access it within wine.

the old drive mapping issue still seems to be relevant i guess?

[spoon0042]

Those messages are harmless, it's just trying and failing to read something. The drives wine looks for are in $WINEPREFIX/dosdevices and can get to be a mess if you switch around different USB drives or something. You can delete any extraneous entries there if you want.