(In reply to comment #187)
> How did you manage to tun the security feature off?
>
> When I try this:
>
> "sudo echo 0 > /proc/sys/kernel/yama/ptrace_scope"
>
> I got the following output:
>
> "bash: /proc/sys/kernel/yama/ptrace_scope: Permission denied"
>
>
> And I'm not able to run an older/newer (beta/mainline) kernel. The installation
> process wents fine but when I try to boot I don't have a gui anymore :/
The way that is interpreted is:
(sudo echo 0) > /proc/sys/kernel/blah/blah
Meaning you only used sudo to run echo, which bash then tried to write (without sudo permissions).
You'd need to either do:
echo 0 | sudo tee /proc/sys/kernel/etc/etc
or
sudo sh -c "echo 0 > /proc/sys/blah/blah"
Anyway, this isn't a wine bug, the two issues that cause it are well known and addressed... I'd say this can be closed.
(In reply to comment #187) kernel/ yama/ptrace_ scope" kernel/ yama/ptrace_ scope: Permission denied"
> How did you manage to tun the security feature off?
>
> When I try this:
>
> "sudo echo 0 > /proc/sys/
>
> I got the following output:
>
> "bash: /proc/sys/
>
>
> And I'm not able to run an older/newer (beta/mainline) kernel. The installation
> process wents fine but when I try to boot I don't have a gui anymore :/
The way that is interpreted is: kernel/ blah/blah
(sudo echo 0) > /proc/sys/
Meaning you only used sudo to run echo, which bash then tried to write (without sudo permissions).
You'd need to either do: kernel/ etc/etc blah/blah"
echo 0 | sudo tee /proc/sys/
or
sudo sh -c "echo 0 > /proc/sys/
Anyway, this isn't a wine bug, the two issues that cause it are well known and addressed... I'd say this can be closed.