[Bug 1665408] Re: winecfg does not work on 32 bit wine directory

2017-02-17 Thread jre
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

Re: [Bug 1665408] Re: winecfg does not work on 32 bit wine directory

2017-02-17 Thread John Rose
Yes. John On 17/02/17 14:16, jre wrote: > Did you use exactly the same command at that time? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665408 Title: winecfg does not work on 32 bit wine

[Bug 1665408] Re: winecfg does not work on 32 bit wine directory

2017-02-17 Thread jre
Did you use exactly the same command at that time? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665408 Title: winecfg does not work on 32 bit wine directory To manage notifications about this

Re: [Bug 1665408] Re: winecfg does not work on 32 bit wine directory

2017-02-17 Thread John Rose
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 "~"

[Bug 1665408] Re: winecfg does not work on 32 bit wine directory

2017-02-16 Thread jre
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