http://bugs.winehq.org/show_bug.cgi?id=15492
Summary: Clamwin installer doesn't parse %SystemDrive% correctly Product: Wine Version: 1.1.5 Platform: Other URL: http://sourceforge.net/project/downloading.php?groupname =clamwin&filename=clamwin-0.94- setup.exe&use_mirror=superb-east OS/Version: other Status: NEW Keywords: download, Installer, source Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: austinenglish@gmail.com
Created an attachment (id=16404) --> (http://bugs.winehq.org/attachment.cgi?id=16404) +shell in git, bzip2 -9'ed
Installing Clamwin works fine, except that instead of installing to: C:\Program Files\Clamwin
it defaults to: Z:\home\austin%SystemDrive%\Program Files\ClamWin
I've seen this on a couple other installers as well, but can't think of them off hand.
+shell attached
http://bugs.winehq.org/show_bug.cgi?id=15492
--- Comment #1 from Austin English austinenglish@gmail.com 2008-10-01 16:13:17 --- Interestingly, it only occurs if ~/.wine doesn't exist. If you run wineboot beforehand, then run the installer, works fine.
http://bugs.winehq.org/show_bug.cgi?id=15492
Andrey Turkin andrey.turkin@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andrey.turkin@gmail.com
--- Comment #2 from Andrey Turkin andrey.turkin@gmail.com 2008-10-02 02:19:37 --- Works for me... When started without .wine wineprefixcreate started first, .wine is created and when installation works as intended.
http://bugs.winehq.org/show_bug.cgi?id=15492
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID
--- Comment #3 from Austin English austinenglish@gmail.com 2008-10-02 12:23:38 --- Well poo. Seems my slow machine is the cause. Works fine on my desktop.
http://bugs.winehq.org/show_bug.cgi?id=15492
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Austin English austinenglish@gmail.com 2008-10-02 12:23:45 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=15492
--- Comment #5 from Andrey Turkin andrey.turkin@gmail.com 2008-10-02 12:38:39 --- If you can reproduce this bug on slow machine then there can be some sort of race condition during prefix creation and then this would be valid bug.
http://bugs.winehq.org/show_bug.cgi?id=15492
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|INVALID |
--- Comment #6 from Austin English austinenglish@gmail.com 2008-10-02 13:04:31 --- True. It's a VM that has had similar issues before, some of which were considered invalid. I'll reopen until there's more consensus.
Yes, it's reproducible EVERY time.
http://bugs.winehq.org/show_bug.cgi?id=15492
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Clamwin installer doesn't |Wineboot has a race |parse %SystemDrive% |condition |correctly |
--- Comment #7 from Austin English austinenglish@gmail.com 2008-10-24 15:56:38 --- I'm seeing this as well when running winecfg. If I do: $ rm -rf ~/.wine && winecfg
the default windows version will sometimes be Win 2k
But if I do: $ rm -rf ~/.wine && wineboot && winecfg
It's okay (Win XP).
http://bugs.winehq.org/show_bug.cgi?id=15492
--- Comment #8 from Andrey Turkin andrey.turkin@gmail.com 2008-10-25 08:43:58 --- Please try running rm -rf ~/.wine && WINEDEBUG=+warn winecfg and see if it says "boot event wait timed out"
http://bugs.winehq.org/show_bug.cgi?id=15492
--- Comment #9 from Austin English austinenglish@gmail.com 2008-10-27 13:10:31 --- warn:process:__wine_kernel_init boot event wait timed out warn:file:wine_nt_to_unix_file_name L"wineboot.exe" not found in /home/austin/.wine/dosdevices/c:/windows/system32 warn:ntdll:NtCreateFile L"\??\C:\windows\system32\wineboot.exe" not found (c0000034) warn:file:wine_nt_to_unix_file_name L"wineboot.exe.manifest" not found in /home/austin/.wine/dosdevices/c:/windows/system32 warn:ntdll:NtCreateFile L"\??\C:\windows\system32\wineboot.exe.manifest" not found (c0000034)
http://bugs.winehq.org/show_bug.cgi?id=15492
--- Comment #10 from Andrey Turkin andrey.turkin@gmail.com 2008-10-27 13:27:08 --- 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?
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)
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.
http://bugs.winehq.org/show_bug.cgi?id=15492
--- Comment #12 from Austin English austinenglish@gmail.com 2008-10-27 14:13:10 --- Created an attachment (id=16935) --> (http://bugs.winehq.org/attachment.cgi?id=16935) WINEDEBUG=warn+all,+process wineboot &> boot.txt
http://bugs.winehq.org/show_bug.cgi?id=15492
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |novakyu@novakyu.net
--- Comment #13 from Austin English austinenglish@gmail.com 2009-05-31 16:00:05 --- *** Bug 18702 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=15492
--- Comment #14 from Dark Ebola darkebola@the-organisation.net 2010-10-02 16:24:32 CDT --- Created an attachment (id=31078) --> (http://bugs.winehq.org/attachment.cgi?id=31078) wineboot with missing ~/.wine
seems like I'm hit by the bug;
except that it happens with an intel q8200 and 8Go of RAM wine-1.3.3
http://bugs.winehq.org/show_bug.cgi?id=15492
Night Nord NightNord@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |NightNord@gmail.com
--- Comment #15 from Night Nord NightNord@gmail.com 2010-11-23 15:27:38 CST --- Same bug. Stable reproducible from wine-1.2 to wine-1.3.6. Actually, I just can't create wineprefix under any circumstances, don't know why and when it had happened. Running wineboot beforehand doesn't help either.
I can't run winedbg, as it requires prefix to be created and gdb can't load symbols for PE binaries.
This is on Core2Duo T6600, 4Gb ram.
http://bugs.winehq.org/show_bug.cgi?id=15492
--- Comment #16 from Night Nord NightNord@gmail.com 2010-12-08 13:40:52 CST --- Confirmed, that such hang appears only when active Internet connection available. Some kind of reverse DNS resolving problem?
http://bugs.winehq.org/show_bug.cgi?id=15492
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com
--- Comment #17 from Bruno Jesus 00cpxxx@gmail.com 2012-09-14 13:20:10 CDT --- Is this still an issue in wine 1.5.12 (or newer)? I have never experienced these issues in 1 year of wine testing.
http://bugs.winehq.org/show_bug.cgi?id=15492
--- Comment #18 from Austin English austinenglish@gmail.com 2012-09-18 04:16:30 CDT --- I only got it in a slow VM, which I no longer have access to.
https://bugs.winehq.org/show_bug.cgi?id=15492
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |frederic.delanoy@gmail.com Resolution|--- |ABANDONED
--- Comment #19 from Frédéric Delanoy frederic.delanoy@gmail.com --- (In reply to Austin English from comment #18)
I only got it in a slow VM, which I no longer have access to.
Marking abandoned.
Feel free to reopen if problem persists with the latest wine version (1.7.40 or later).
https://bugs.winehq.org/show_bug.cgi?id=15492
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #20 from Frédéric Delanoy frederic.delanoy@gmail.com --- Closing
-
wine-bugs＠winehq.org