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)?
