booman |
Saturday 20 April 2013 at 16:15
|
booman
|
I have been installing dotnet30 for a long time and never seen this error before. I'm using Wine 1.4.1 I try to install package dotnet30 and get this error:
Error in sourcePackage installatio nwill fail until you set /proc/sys/kernel/yama/ptrace_scope to 0
I even deleted the dotnet30 folder from the PlayOnLinux resource directory and still get the error. Is there anything else I can remove to avoid conflicts?
|
GNU_Raziel |
Saturday 20 April 2013 at 17:07
|
GNU_Raziel
|
Hi, you must disable this GNU/Linux KERNEL feature or the dotnet30 install cannot complete. To disable it, use this command in a terminal then reboot (not sure reboot is needed): sudo echo "0" > /proc/sys/kernel/yama/ptrace_scope
This is a paranoid extra security feature that conflict with many things, including wine. Regards, GNU_Raziel Edited by GNU_Raziel
|
booman |
Saturday 20 April 2013 at 17:25
|
booman
|
Hey, thanks a lot, I'll try the command and see what happens. I wonder why I suddenly got this error when I have never received it before?
|
Ronin DUSETTE |
Saturday 20 April 2013 at 17:50
|
Ronin DUSETTE
|
I know Ubuntu has had some kernel updates recently. Have you done any upgrades?
|
booman |
Monday 22 April 2013 at 17:20
|
booman
|
I don't think so. I have some updates waiting in Mint, but they are all networking updates. I'll check again because maybe some more have been added.
|
booman |
Tuesday 23 April 2013 at 15:06
|
booman
|
ok, I ran that in the terminal and tried installing dotnet30 again... This time PlayOnLinux downloaded these packages: NetFx20SPx86.exe dotnetfx3.exe I havn't seen these before, so there must have been some changes this year... Then I got a RegSvce.exe Fatal Error Oh well, it was probably a conflict of wine versions. I am using Wine 1.4.1
|
GNU_Raziel |
Tuesday 23 April 2013 at 19:15
|
GNU_Raziel
|
It is, no matter wine version dotnet support is still very incomplete but the "most suitable" wine builds fot dotnet up to 3.5 SP1 are wine 1.5.12 to 1.5.20. With wine 1.4.x dotnet installations are partials...basic dotnet use work but no advanced features. the RegSvr error can be ignored until you want advanced features...then I recommand using wine 1.5.20. For dotnet 4.0, wine 1.5.21 or better is recommanded. Dotnet 4.5 is not supported at all, nothing work with it. Edited by GNU_Raziel
|
booman |
Tuesday 23 April 2013 at 19:44
|
booman
|
Thanks, I'm going to make a new post because this problem is about running Warhammer 40K: Space Marine. Hopefully you guys can help me...
|
GNU_Raziel |
Tuesday 23 April 2013 at 22:01
|
GNU_Raziel
|
As far as I remember, this game do not need dotnet to run...the actuall PoL script is pretty old and I will make a review as soon as possible but no dotnet needed (except if it change with updates).
|
booman |
Tuesday 23 April 2013 at 22:45
|
booman
|
I kinda figured, but was trying anything I could to get it running. I'm going to try different versions of wine and if no success, I'll be posting a new thread.
|
booman |
Friday 26 April 2013 at 18:17
|
booman
|
I did try sudo echo "0" > /proc/sys/kernel/yama/ptrace_scope and it worked! I could install dotnet30 and the 35 service packs. Didn't make any difference in my game, but just wanted to let you all know it worked.
|
petch |
Friday 26 April 2013 at 20:13
|
petch
|
Thinking of it, it should not work as written (and indeed did not work when I tried on a Linux Mint). The problem is that the redirection is set up by the user shell before the command is run, including the use of sudo. To keep the explanation short, the command is interpreted as (sudo echo "0") > /proc/sys/kernel/yama/ptrace_scopeand not sudo (echo "0" > /proc/sys/kernel/yama/ptrace_scope)And results in $ sudo echo "0" > /proc/sys/kernel/yama/ptrace_scope Bash: /proc/sys/kernel/yama/ptrace_score: permission denied(unless your user has write access to /proc/sys/kernel/yama/ptrace_scope, but in this case you're not concerned by security anymore :p That's why original instructions involved the use of tee, as a way to avoid using redirection: echo "0"|sudo tee /proc/sys/kernel/yama/ptrace_scopeShould also work: sudo bash -c 'echo "0" > /proc/sys/kernel/yama/ptrace_scope'(I tried to use sudo -s, but couldn't get it to work as I wanted)
|
booman |
Friday 26 April 2013 at 23:16
|
booman
|
ok, I"ll put ptrace_scope back to "1" for securities sake
|
petch |
Friday 26 April 2013 at 23:31
|
petch
|
That's not sticky anyway, it will be back to its default value on next reboot
|
booman |
Friday 26 April 2013 at 23:35
|
booman
|
oh, nevermind then, I've already rebooted. should I check to make sure?
|
Ronin DUSETTE |
Saturday 27 April 2013 at 2:20
|
Ronin DUSETTE
|
|
booman |
Saturday 27 April 2013 at 16:06
|
booman
|
I ran sudo echo "1" > /proc/sys/kernel/yama/ptrace_scope and sudo echo "1" > /proc/sys/kernel/yama/ptrace_scope and get "permission denied" for both
|
Ronin DUSETTE |
Saturday 27 April 2013 at 16:32
|
Ronin DUSETTE
|
Like he said; use a pipe and a tee. echo "0"|sudo tee /proc/sys/kernel/yama/ptrace_scope
If you do it the other way, its only running sudo on echo "1", and not giving permissions to write to that file, which is why you get the perm issue. With this one, echo doesnt need sudo, but writing that file does, so putting the pipe ("|") in between those commands, tells whatever the output of echo, pipe it to /proc/sys/kernel/yama/ptrace_scope using tee with sudo permissions.
|
booman |
Sunday 28 April 2013 at 2:20
|
booman
|
I think I understand what you mean with "tee" and piping it to the output, but what am I really doing with ptrace_scope in the first place?
|
Ronin DUSETTE |
Sunday 28 April 2013 at 19:08
|
Ronin DUSETTE
|
Changing a "1" to a "0" or vice-versa. tee is a program, piping is exactly what it sounds like. To be honest, Im not sure what it does exactly, but the command is essentially putting a 0 in that section of that file to turn it off or on. Again, I have no idea what it actually does, though.
|