Closed GoogleCodeExporter closed 8 years ago
I have the same problem on the newest reversion winetricks r888
Original comment by zhumeng1...@gmail.com
on 18 Aug 2012 at 8:07
I hacked this problem by creating one logo.bmp in that folder. But it crashed
when install dotnet30sp1.
Original comment by zhumeng1...@gmail.com
on 18 Aug 2012 at 8:54
console output from r888 please
Original comment by daniel.r...@gmail.com
on 18 Aug 2012 at 2:38
I changed my Wine to the stable version 1.4.1, and used the r897 winetricks.
This time it does't say "...logo.bmp not found", instead something as my
Attached log.
Original comment by zhumeng1...@gmail.com
on 19 Aug 2012 at 8:14
Attachments:
It's possible that exit code 67 means 'user requested system reboot'.
Run 'winetricks dotnet_verifier' and then 'wine netfx_setupverifier.exe'
and see if it thinks the dotnet30 install is complete.
Original comment by daniel.r...@gmail.com
on 19 Aug 2012 at 2:59
For the record, winetricks r899 still behaves this way with latest Wine 1.5
PPA. Tried both before and after upgrading to 1.5.10-0ubuntu1~pulse19+build4
from build2
Original comment by stefan.h...@gmail.com
on 20 Aug 2012 at 12:44
Please run 'winetricks dotnet_verifier' and then 'wine netfx_setupverifier.exe'
and see if it thinks the dotnet30 install is complete. And/or run some app
that needs .net 3, and see if that works.
Original comment by daniel.r...@gmail.com
on 20 Aug 2012 at 4:13
Oh, I found the similar symptoms in Issue 205. That resolved it for me.
For Ubuntu 12.04 32bit, Wine 1.4.1, you could follow this link:
http://www.codeweavers.com/compatibility/browse/name/?app_id=4662;tips=1
Original comment by zhumeng1...@gmail.com
on 20 Aug 2012 at 5:15
Oh, good. Note that winetricks as of r884 warns at the start of dotnet30
"If install fails, set /proc/sys/kernel/yama/ptrace_scope to 0. See
http://bugs.winehq.org/show_bug.cgi?id=30410 "
Did you see that warning?
Original comment by daniel.r...@gmail.com
on 20 Aug 2012 at 2:34
Oh crap!
cat /proc/sys/kernel/yama/ptrace_scope
1
But I fail to understand why this popped up now, because with 1.5.9 PPA (?) I
verified that my ptrace was off by default. What on earth changed so it is now
suddenly default on again?
In any case, Ill verify both this and the other bug I reported as soon as I
have time and close them if setting ptrace 0 fixes it.
Original comment by stefan.h...@gmail.com
on 20 Aug 2012 at 7:59
The current Ubuntu packages are supposed to have a clean workaround so
they don't care if /proc/sys/kernel/yama/ptrace_scope is 1.
It's possible that got dropped somehow, but I doubt it.
BTW, /proc/sys/kernel/yama/ptrace_scope being 0 means ptrace is fully on.
Higher values of that variable tighten up security and reduce access to ptrace.
Original comment by daniel.r...@gmail.com
on 20 Aug 2012 at 8:10
Confirmed the issue that the original poster had. This happens for me using
winetricks r905 with wine 1.5.11 on openSUSE 12.2 RC2. The log is identical to
the one in the original post (and gives me a GUI error "A problem has been
encountered while loading the setup components. Canceling setup.", sic.) This
has nothing to do with ptrace, it would appear, since openSUSE doesn't even
have a /proc/sys/kernel/yama directory to begin with...
Original comment by past...@gmail.com
on 23 Aug 2012 at 9:19
A regression test - either along wine or along winetricks - would be helpful,
if you have a known good past setup.
Original comment by daniel.r...@gmail.com
on 23 Aug 2012 at 1:47
Unfortunately, I don't have one... I tried this for the first time in a really
long while.
Original comment by past...@gmail.com
on 23 Aug 2012 at 2:17
Just had the opportunity again to try this issue again with ptrace 0
As has been reported, ptrace 0 doesnt fix it. As for regression test, I'm
fairly confident that installing dotnet 3.0 worked without a hitch in the PPA
for wine 1.5.9 and stopped working when I upgraded to PPA wine 1.5.10
Original comment by stefan.h...@gmail.com
on 24 Aug 2012 at 6:27
If you could reverify that, I'd appreciate it. I'm kind of swamped.
Original comment by daniel.r...@gmail.com
on 24 Aug 2012 at 4:20
Had set some time aside to try and test old version today, but didnt manage to
find the old 1.5.9 PPA anywhere online. Maybe no old versions are kept around?
Guess, from now on, I should probably manually download the packages and run
them locally instead of relying on the Ubuntu software update feature.
Original comment by stefan.h...@gmail.com
on 2 Sep 2012 at 8:55
I just tested wine 1.5.9 (x86) from the PlayOnLinux build archive and it loaded
the installer and completed successfully. Using winetricks svn 909.
Guess that means a regression?
Original comment by timothyb89@gmail.com
on 3 Sep 2012 at 9:37
Yeah. Now it's time to start bisecting...
Original comment by daniel.r...@gmail.com
on 3 Sep 2012 at 2:29
I have just finished bisecting wine and identified commit
f180de40dd7820753479f823b6cb08a34b479c66 (msi: Implement the
RemoveExistingProducts standard action.) as the one which breaks the
installation. Reverting it makes the error disappear in the most recent git
version of wine.
Original comment by sha...@umbrox.de
on 9 Sep 2012 at 7:05
Further investigation revealed something interesting.
Installing dotnet3 via winetricks dotnet30 does not result in the error, even
when the installation of dotnet3 as a dependency of dotnet35 fails.
After comparing the load_dotnet30 and the load_dotnet35 sections in winetricks
I noticed that dotnet30 only installs dotnet20 while dotnet35 installs
dotnet20sp1 as dependency. I therefore changed the dotnet20sp1 part in
load_dotnet35 to dotnet20 as it is in load_dotnet30. This removed the error
during the installation of dotnet30 but made the installation then abort while
installing dotnet35.
Original comment by sha...@umbrox.de
on 9 Sep 2012 at 7:56
Aha, seems to be
http://bugs.winehq.org/show_bug.cgi?id=31652
Original comment by daniel.r...@gmail.com
on 10 Sep 2012 at 1:21
Original issue reported on code.google.com by
stefan.h...@gmail.com
on 5 Aug 2012 at 8:20Attachments: