winecfg does not work on 32 bit wine directory

Bug #1665408 reported by John Rose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wine1.6 (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

On standard 64 bit wine directory, winecfg works OK:
WINEARCH=win64 WINEPREFIX=~/.wine winecfg

After creating 32 bit wine directory, winecfg fails:
john@NewDesktop:~$ WINEARCH=win32 WINEPREFIX=~/.wine32 wine wineboot
wine: created the configuration directory '/home/john/.wine32'
fixme:storage:create_storagefile Storage share mode not implemented.
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot fixme:storage:create_storagefile Storage share mode not implemented. fixme:iphlpapi:NotifyAddrChange (Handle 0x11fe8a0, overlapped 0x11fe8ac): stub
wine: configuration in '/home/john/.wine32' has been updated.
john@NewDesktop:~$ winecfg
fixme:shell:SIC_Initialize Failed to load IDI_SHELL_DOCUMENT icon! err:ole:apartment_createwindowifneeded CreateWindow failed with error 127

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: wine 1:1.6.2-0ubuntu14
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Feb 16 16:53:02 2017
InstallationDate: Installed on 2016-12-08 (70 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: wine1.6
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
John Rose (johnaaronrose) wrote :
Revision history for this message
jre (jre-phoenix) wrote :

With these commands you were still using ~/.wine. You have to either export WINEPREFIX or specify it for every command.
Further I think I've seen Wine complaining about "~" in the past, so maybe either use $HOME or the path directly.

To rule out any issues with existing profiles, let's start fresh again, and make sure that the first command is done and the wineserver had time to shut down between the commands. So what happens for:

WINEARCH=win32 WINEPREFIX=/home/john/.wine32-test wine wineboot
sleep 10
WINEPREFIX=/home/john/.wine32-test winecfg

Changed in wine1.6 (Ubuntu):
status: New → Incomplete
Revision history for this message
John Rose (johnaaronrose) wrote : Re: [Bug 1665408] Re: winecfg does not work on 32 bit wine directory

No problem with your suggestion. However, 2 hours later it did the same
again!

John

On 16/02/17 18:13, jre wrote:
> With these commands you were still using ~/.wine. You have to either export WINEPREFIX or specify it for every command.
> Further I think I've seen Wine complaining about "~" in the past, so maybe either use $HOME or the path directly.
>
> To rule out any issues with existing profiles, let's start fresh again,
> and make sure that the first command is done and the wineserver had time
> to shut down between the commands. So what happens for:
>
> WINEARCH=win32 WINEPREFIX=/home/john/.wine32-test wine wineboot
> sleep 10
> WINEPREFIX=/home/john/.wine32-test winecfg
>
>
> ** Changed in: wine1.6 (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message
jre (jre-phoenix) wrote :

Did you use exactly the same command at that time?

Revision history for this message
John Rose (johnaaronrose) wrote :

Yes.

John

On 17/02/17 14:16, jre wrote:
> Did you use exactly the same command at that time?
>

Revision history for this message
jre (jre-phoenix) wrote :

So you created a new prefix with
  WINEARCH=win32 WINEPREFIX=/home/john/.wine32-test wine wineboot

Testing this with
  WINEPREFIX=/home/john/.wine32-test winecfg
worked.

Then 2 hours later the same command
  WINEPREFIX=/home/john/.wine32-test winecfg
failed.

Right?

Were you using Wine in this prefix between? What did you do?

Were there any running Wine processes before you unsuccessfully tried to start winecfg?

Did you get the same error message then?
  fixme:shell:SIC_Initialize Failed to load IDI_SHELL_DOCUMENT icon!
  err:ole:apartment_createwindowifneeded CreateWindow failed with error 127

If you find how to reliably reproduce this I suggest you report this upstream, and report back here.
E.g. in a quick search I found *similar* things reported on winehq.org:
https://bugs.winehq.org/show_bug.cgi?id=32959 (probably fixed in Wine 1.7.50 or earlier)
https://bugs.winehq.org/show_bug.cgi?id=39223 (probably something else, other error code)
https://bugs.winehq.org/show_bug.cgi?id=27151 (probably something else)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.