http://bugs.winehq.org/show_bug.cgi?id=15492
--- Comment #11 from Austin English austinenglish@gmail.com 2008-10-27 14:04:21 --- (In reply to comment #10)
Hm, that's strange. kernel32 waits for wineboot completion up to 30 seconds which should be enough even for slow vm. Is there 30 seconds gap before winecfg window appear? Also, could you please get WINEDEBUG=+process,+warn log?
Running wineboot by itself: austin@austin-desktop:~$ time wineboot wine: created the configuration directory '/home/austin/.wine'
real 0m54.681s user 0m2.340s sys 0m1.292s austin@austin-desktop:~$ Could not load Mozilla. HTML rendering will be disabled. wine: configuration in '/home/austin/.wine' has been updated.
austin@austin-desktop:~$ time wineboot
real 0m3.819s user 0m0.352s sys 0m1.152s
I might try a fresh install of this vm, to see if it's repeatable. While 30s is probably enough for most cases, wineboot shouldn't exit cleanly, but instead issue a warning/error saying that it timed out. Otherwise, these kinds of errors appear.
FWIW, tried on winecfg: austin@austin-desktop:~$ time winecfg wine: created the configuration directory '/home/austin/.wine' Could not load Mozilla. HTML rendering will be disabled.
real 0m37.689s user 0m1.860s sys 0m0.940s
#OS version is 2k austin@austin-desktop:~$ time winecfg wine: configuration in '/home/austin/.wine' has been updated.
real 0m12.112s user 0m1.932s sys 0m1.048s
#OS version is XP
So seems once you run it a second time, it picks up where it left off?
Log on its way.