wine users - May 2011 - Wine taking unacceptably long to start up (Fedora 14 x86_64)

Whenever I run any application with wine it takes upwards of five minutes to
start, even apps included with wine like wine cmd. I have been googling this for
hours and cannot find anything really applicable to my situation.

I am running Fedora 14 x86_64.

I don't have a network printer.

As far as I am aware fc-cache-32 doesn't exist on Fedora.

I am trying to get some other program to run and having problems so I need to do
some trial-and-error stuff to get it to run so this slowness is basically
intolerable for the purposes of trying to test and figure out what I need to do
to get it to run. Having to wait 5 minutes on each attempt only to have it fail
yet again is frustrating. Thanks for any help or advice.

Hm, apparently you can't edit posts here?

I forgot to mention, `wineboot --update` also does nothing.

jjmckenzie wrote:
> On 5/14/11 6:30 AM, Scott5114 wrote:
> 
> > jjmckenzie wrote:
> > 
> > > Can you open another terminal window and run:
> > > 
> > > Code:
> > > 
> > > ps -ef | grep wine
> > > 
> > > 
> > > 
> > > 
> > > and advise what you get in return?
> > > 
> > > James McKenzie
> > > 
> > 
> > This is what I get (using `wine cmd`) as a test :
> > 
> > Code:
> > 
> > $ ps -ef | grep wine
> > scott    16247     1  0 May13 ?        00:00:02 /usr/bin/wineserver
> > scott    16283 16281  0 May13 ?        00:00:00
C:\windows\system32\winedevice.exe MountMgr
> > scott    18853 18611  0 May13 pts/0    00:00:00 wineboot.exe --update
> > scott    24852 20437  0 08:27 pts/4    00:00:00 grep --color=auto wine
> > 
> > 
> > 
> What happens if try with a fresh Wineprefix?
> 
> Does the wineboot --update command still hang?
> 
> Also, can you issue the following command:
> 
> echo $WINEPREFIX
> 
> and provide the response.
> 
> James McKenzie
> 
> > 
> > 
> > vitamin wrote:
> > > In most cases it's caused by a network printer that does not
respond. If you have such a printer configured - try removing it. Or make sure
it's available. Or you can try stopping cups.
> > 
> > I don't have a network printer. Stopping cups seemed to have no
effect.
> > 
> 
> This may not be the only reason your boot up is 'hanging'.
> 
> James McKenzie

Interesting. Echoing $WINEPREFIX doesn't return anything. Should I try
setting it to ~/.wine (as that is where I have all my wine programs installed)?

jjmckenzie wrote:
> On 5/14/11 4:54 PM, Scott5114 wrote:
> 
> > jjmckenzie wrote:
> > 
> > > On 5/14/11 6:30 AM, Scott5114 wrote:
> > > 
> > > 
> > > > jjmckenzie wrote:
> > > > 
> > > > 
> > > > > Can you open another terminal window and run:
> > > > > 
> > > > > Code:
> > > > > 
> > > > > ps -ef | grep wine
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > and advise what you get in return?
> > > > > 
> > > > > James McKenzie
> > > > > 
> > > > > 
> > > > This is what I get (using `wine cmd`) as a test :
> > > > 
> > > > Code:
> > > > 
> > > > $ ps -ef | grep wine
> > > > scott    16247     1  0 May13 ?        00:00:02
/usr/bin/wineserver
> > > > scott    16283 16281  0 May13 ?        00:00:00
C:\windows\system32\winedevice.exe MountMgr
> > > > scott    18853 18611  0 May13 pts/0    00:00:00 wineboot.exe
--update
> > > > scott    24852 20437  0 08:27 pts/4    00:00:00 grep
--color=auto wine
> > > > 
> > > > 
> > > > 
> > > > 
> > > What happens if try with a fresh Wineprefix?
> > > 
> > > Does the wineboot --update command still hang?
> > > 
> > > Also, can you issue the following command:
> > > 
> > > echo $WINEPREFIX
> > > 
> > > and provide the response.
> > > 
> > > James McKenzie
> > > 
> > > 
> > > > 
> > > > vitamin wrote:
> > > > 
> > > > > In most cases it's caused by a network printer that
does not respond. If you have such a printer configured - try removing it. Or
make sure it's available. Or you can try stopping cups.
> > > > > 
> > > > I don't have a network printer. Stopping cups seemed to
have no effect.
> > > > 
> > > > 
> > > This may not be the only reason your boot up is
'hanging'.
> > > 
> > > James McKenzie
> > > 
> > 
> > Interesting. Echoing $WINEPREFIX doesn't return anything. Should I
try setting it to ~/.wine (as that is where I have all my wine programs
installed)?
> > 
> > 
> That is what I expected.  Sometimes folks try to link Wine's 'fake 
> Windows' directories to an actual Windows installation.  Great way to 
> break both Wine and Windows.
> 
> Do you have ANYTHING that you cannot re-install into Wine?
> 
> James McKenzie

Nope! If I need to nuke it and start fresh I can do that.

jjmckenzie wrote:
> On 5/14/11 5:19 PM, Scott5114 wrote:
> 
> > jjmckenzie wrote:
> > 
> > > On 5/14/11 4:54 PM, Scott5114 wrote:
> > > 
> > > 
> > > > jjmckenzie wrote:
> > > > 
> > > > 
> > > > > On 5/14/11 6:30 AM, Scott5114 wrote:
> > > > > 
> > > > > 
> > > > > 
> > > > > > jjmckenzie wrote:
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > > Can you open another terminal window and run:
> > > > > > > 
> > > > > > > Code:
> > > > > > > 
> > > > > > > ps -ef | grep wine
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > and advise what you get in return?
> > > > > > > 
> > > > > > > James McKenzie
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > This is what I get (using `wine cmd`) as a test :
> > > > > > 
> > > > > > Code:
> > > > > > 
> > > > > > $ ps -ef | grep wine
> > > > > > scott    16247     1  0 May13 ?        00:00:02
/usr/bin/wineserver
> > > > > > scott    16283 16281  0 May13 ?        00:00:00
C:\windows\system32\winedevice.exe MountMgr
> > > > > > scott    18853 18611  0 May13 pts/0    00:00:00
wineboot.exe --update
> > > > > > scott    24852 20437  0 08:27 pts/4    00:00:00
grep --color=auto wine
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > What happens if try with a fresh Wineprefix?
> > > > > 
> > > > > Does the wineboot --update command still hang?
> > > > > 
> > > > > Also, can you issue the following command:
> > > > > 
> > > > > echo $WINEPREFIX
> > > > > 
> > > > > and provide the response.
> > > > > 
> > > > > James McKenzie
> > > > > 
> > > > > 
> > > > > 
> > > > > > vitamin wrote:
> > > > > > 
> > > > > > 
> > > > > > > In most cases it's caused by a network
printer that does not respond. If you have such a printer configured - try
removing it. Or make sure it's available. Or you can try stopping cups.
> > > > > > > 
> > > > > > > 
> > > > > > I don't have a network printer. Stopping cups
seemed to have no effect.
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > This may not be the only reason your boot up is
'hanging'.
> > > > > 
> > > > > James McKenzie
> > > > > 
> > > > > 
> > > > Interesting. Echoing $WINEPREFIX doesn't return
anything. Should I try setting it to ~/.wine (as that is where I have all my
wine programs installed)?
> > > > 
> > > > 
> > > > 
> > > That is what I expected.  Sometimes folks try to link Wine's
'fake
> > > Windows' directories to an actual Windows installation. 
Great way to
> > > break both Wine and Windows.
> > > 
> > > Do you have ANYTHING that you cannot re-install into Wine?
> > > 
> > > James McKenzie
> > > 
> > 
> > Nope! If I need to nuke it and start fresh I can do that.
> > 
> > 
> Do it.  Your Wine 'fake' Windows directories may be corrupt.
> 
> James McKenzie


Code:

$ mkdir .wine2
$ export WINEPREFIX=$HOME/.wine2/
$ winecfg




This seems to have done the trick. Standard wine programs like `wine cmd` and
winefile from the new install are coming up within seconds now. I have not yet
tried any non-wine-distro programs, but I'll give them a shot. Thanks for
the help.