[Bug 47275] New: 4.9 Staging, winecfg -> Driver tab -> showing " Failed to connect to mount manager; the drive configuration cannot be edited".
https://bugs.winehq.org/show_bug.cgi?id=47275 Bug ID: 47275 Summary: 4.9 Staging, winecfg -> Driver tab -> showing "Failed to connect to mount manager; the drive configuration cannot be edited". Product: Wine-staging Version: 4.9 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: avenjames(a)live.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Created attachment 64569 --> https://bugs.winehq.org/attachment.cgi?id=64569 log of the bug description. Platform: RMBP-mid2015 OS: Mac OS-HS 10.13.6 Bug Description: Just after update from Staging 4.7 to 4.8 or 4.9 (all staging version), the Driver tab in winecfg always showing "Failed to connect to mount manager; the drive configuration cannot be edited", googled for all solutions those no help, terminal log attached here, any idea brothers? best regards, Aven -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 Fotan <avenjames(a)live.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |avenjames(a)live.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 Gcenx <gcenx83(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gcenx83(a)gmail.com --- Comment #1 from Gcenx <gcenx83(a)gmail.com> --- Created attachment 64570 --> https://bugs.winehq.org/attachment.cgi?id=64570 Wine-Staging-4.9 64Bit winecfg log I've also got the same issue and had opened a bug-report for packaging here https://bugs.winehq.org/show_bug.cgi?id=47224 Also someone confirmed on my report with the same issue using Redhat. So without mingw wine64 doesn't build correctly anymore, this making cross-compiling even more of a headache. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #2 from Gcenx <gcenx83(a)gmail.com> --- The currently affects Wine-4.8 64Bit Wine-Staging-4.8 64Bit Wine-4.9 64Bit Wine-Staging-4.9 64Bit Without Mingw the builds will get the error reported and other PE files are not built correctly. Installing Mingw then compiling from source wine64 will be built correctly. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|4.9 Staging, winecfg -> |winecfg fails to connect to |Driver tab -> showing |mountmgr on 64-bit |"Failed to connect to mount | |manager; the drive | |configuration cannot be | |edited". | Product|Wine-staging |Wine Component|-unknown |-unknown Version|4.9 |4.8 --- Comment #3 from Zebediah Figura <z.figura12(a)gmail.com> --- Likely a duplicate of bug 47224. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #4 from Fotan <avenjames(a)live.com> --- (In reply to Gcenx from comment #1) Especially for an OSX to setup cross-compiling with MinGW, I think that's not an easy way for most users operating. Otherwise, I googled for an information mentioned the System.reg missing key with some values which might related to this happening, Locate to REGEDIT -> HKLM -> System -> CurrentControlSet -> Services, version 4.7 there's a key named "MountMgr", but after version 4.8 & 4.9 was missing this key. Tried to create and insert the value but no help. Is necessary to setup the MinGW then fixed this error tab?
Created attachment 64570 [details] Wine-Staging-4.9 64Bit winecfg log
I've also got the same issue and had opened a bug-report for packaging here https://bugs.winehq.org/show_bug.cgi?id=47224
Also someone confirmed on my report with the same issue using Redhat.
So without mingw wine64 doesn't build correctly anymore, this making cross-compiling even more of a headache.
-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #5 from Gcenx <gcenx83(a)gmail.com> --- (In reply to Fotan from comment #4)
(In reply to Gcenx from comment #1)
Especially for an OSX to setup cross-compiling with MinGW, I think that's not an easy way for most users operating.
Otherwise, I googled for an information mentioned the System.reg missing key with some values which might related to this happening,
Locate to REGEDIT -> HKLM -> System -> CurrentControlSet -> Services, version 4.7 there's a key named "MountMgr", but after version 4.8 & 4.9 was missing this key.
Tried to create and insert the value but no help.
Is necessary to setup the MinGW then fixed this error tab?
The registory key is lightly not created due to the PE file not being built correctly. Compiling wine with mingw no error. Installing mingw is easy actually, it’s on macports and homebrew. My setup is not standard as I’m running Mojave (XCode10 + 10.13SDK) I have the required development files from packages.macports and homebrew for bison, automake, mingw-w64 etc. So simply having mingw avalaible at compile time makes a working wine64, —without-mingw or not having it installed will produce a broken wine64 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 Fotan <avenjames(a)live.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|4.8 |4.9 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #6 from Fotan <avenjames(a)live.com> --- (In reply to Gcenx from comment #5)
(In reply to Fotan from comment #4)
(In reply to Gcenx from comment #1)
Especially for an OSX to setup cross-compiling with MinGW, I think that's not an easy way for most users operating.
Otherwise, I googled for an information mentioned the System.reg missing key with some values which might related to this happening,
Locate to REGEDIT -> HKLM -> System -> CurrentControlSet -> Services, version 4.7 there's a key named "MountMgr", but after version 4.8 & 4.9 was missing this key.
Tried to create and insert the value but no help.
Is necessary to setup the MinGW then fixed this error tab?
The registory key is lightly not created due to the PE file not being built correctly.
Compiling wine with mingw no error. Installing mingw is easy actually, it’s on macports and homebrew.
My setup is not standard as I’m running Mojave (XCode10 + 10.13SDK) I have the required development files from packages.macports and homebrew for bison, automake, mingw-w64 etc.
So simply having mingw avalaible at compile time makes a working wine64, —without-mingw or not having it installed will produce a broken wine64
Tried to install MinGW-W64 with home-brew then did a clean job / reboot / reinstall the staging 4.9, but still get empty tab with same error information. Anyway my setup was very normally from PKG downloaded from the site, and for the Xcode dependence I'm using Xquartz 2.7.11 instead, maybe some dependencies I have missed, still trying to see if any way could fix it. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #7 from Fotan <avenjames(a)live.com> --- Created attachment 64576 --> https://bugs.winehq.org/attachment.cgi?id=64576 Staging 4.9 with MinGW-w64 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #8 from Gcenx <gcenx83(a)gmail.com> --- (In reply to Fotan from comment #7)
Created attachment 64576 [details] Staging 4.9 with MinGW-w64
Your missing the point here, you must compile wine yourself from source. The follow packages from Winehq are broken; Wine-4.8 (64Bit) Wine-Staging-4.8 (64Bit) Wine-4.9 (64Bit) Wine-Staging-4.9 (64Bit) Installing mingw-w64 won’t help if the build is already broken. Once I’m in-front of my Mac I’ll upload working custom “Wine Stable.app” & “Wine Staging.app” builds for 4.8/4.9 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|4.9 |4.8 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 Fotan <avenjames(a)live.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #9 from Fotan <avenjames(a)live.com> --- Fixed in Staging 4.10, I think there's the same as none staging version. Good luck to everyone. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #10 from Gcenx <gcenx83(a)gmail.com> --- I can confirm the issue was resolved in Wine-4.10 The commit I believe fixed the problem was this one; winebuild: Don't even try to resolve imports for PE builds. ded2e82f16fb142c8056ba7833d139a1acc94e22 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #11 from Gcenx <gcenx83(a)gmail.com> --- The issues is not resolved. When compiling wine using —without-mingw or not having mingw installed the issue still happens -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 Rosanne DiMesio <dimesio(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #12 from Rosanne DiMesio <dimesio(a)earthlink.net> --- (In reply to Gcenx from comment #11)
The issues is not resolved.
When compiling wine using —without-mingw or not having mingw installed the issue still happens
Reopening. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 RayCaster <a34ypool3voiz(a)t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a34ypool3voiz(a)t-online.de --- Comment #13 from RayCaster <a34ypool3voiz(a)t-online.de> --- Not sure if this is related or not, but since upgrading from WINE 4.11 to 4.12 on Ubuntu 18.04 amd64 winecfg also fails to connect to mountmgr when run on a 64 bit wineprefix. With a 32 bit wineprefix it still works fine. Here's the startup of winecfg on a new prefix: $ WINEPREFIX=~/dummy winecfg wine: created the configuration directory '/home/zoom/dummy' wine: Unhandled page fault on write access to 0x0040b6e0 at address 0x402545 (thread 000b), starting debugger... 000b:err:seh:start_debugger Couldn't start debugger ("winedbg --auto 10 24") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger 0009:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 000d:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046} 000d:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa} 000d:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002 000d:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002 000d:err:ole:get_local_server_stream Failed: 80004002 0010:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) I can create a separate bug entry if deemed necessary. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net --- Comment #14 from Anastasius Focht <focht(a)gmx.net> --- Hello RayCaster --- quote --- Not sure if this is related or not, but since upgrading from WINE 4.11 to 4.12 on Ubuntu 18.04 amd64 winecfg also fails to connect to mountmgr when run on a 64 bit wineprefix. --- quote --- that's bug 47464 (and to-be-created-follow-up ones). Wine 4.12 release is broken in multiple aspects. Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 dominik(a)kuropka.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dominik(a)kuropka.net --- Comment #15 from dominik(a)kuropka.net --- This might be related to Bug 47474 as the error message is similar. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #16 from Fotan <avenjames(a)live.com> --- (In reply to RayCaster from comment #13)
Not sure if this is related or not, but since upgrading from WINE 4.11 to 4.12 on Ubuntu 18.04 amd64 winecfg also fails to connect to mountmgr when run on a 64 bit wineprefix. With a 32 bit wineprefix it still works fine.
Here's the startup of winecfg on a new prefix: $ WINEPREFIX=~/dummy winecfg wine: created the configuration directory '/home/zoom/dummy' wine: Unhandled page fault on write access to 0x0040b6e0 at address 0x402545 (thread 000b), starting debugger... 000b:err:seh:start_debugger Couldn't start debugger ("winedbg --auto 10 24") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger 0009:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 000d:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046} 000d:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa} 000d:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002 000d:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002 000d:err:ole:get_local_server_stream Failed: 80004002 0010:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
I can create a separate bug entry if deemed necessary.
I think this situation might related to what Gcenx descripted on Comment #2, MingW should be installed and then comply and build from the source. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #17 from Gcenx <gcenx83(a)gmail.com> --- (In reply to Fotan from comment #16)
(In reply to RayCaster from comment #13)
Not sure if this is related or not, but since upgrading from WINE 4.11 to 4.12 on Ubuntu 18.04 amd64 winecfg also fails to connect to mountmgr when run on a 64 bit wineprefix. With a 32 bit wineprefix it still works fine.
Here's the startup of winecfg on a new prefix: $ WINEPREFIX=~/dummy winecfg wine: created the configuration directory '/home/zoom/dummy' wine: Unhandled page fault on write access to 0x0040b6e0 at address 0x402545 (thread 000b), starting debugger... 000b:err:seh:start_debugger Couldn't start debugger ("winedbg --auto 10 24") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger 0009:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 000d:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046} 000d:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa} 000d:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002 000d:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002 000d:err:ole:get_local_server_stream Failed: 80004002 0010:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
I can create a separate bug entry if deemed necessary.
I think this situation might related to what Gcenx descripted on Comment #2, MingW should be installed and then comply and build from the source.
Not a good idea for Wine-4.12 as compiling with mingw caused an issue with wineboot https://bugs.winehq.org/show_bug.cgi?id=47467 that was resolved in Wine-4.12.1 that got pushed like 5 hours ago. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 --- Comment #18 from Gcenx <gcenx83(a)gmail.com> --- (In reply to dominik from comment #15)
This might be related to Bug 47474 as the error message is similar.
That bug is not related to that bug, that bug is caused by compiling with mingw resulting in a broken wineboot 64bit PE file resulting in upgraded prefixes or newly created prefix not being created correctly. That bug was resolved with Wine-4.12.1 This bug is caused by compiling --without-mingw and has been present since Wine-4.8 when mingw was introduced for cross-compiling windows PE files for use within Wine. Most of the bugs since swapping to using Mingw are with 64bit files when compiled --without-mingw in most cases, with the exception being 47474 when compiling with mingw caused the breakage. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #19 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- This issue has been fixed in the meantime. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47275 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #20 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 5.0-rc2. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla