Comment # 4 on bug 1221763 from Jiri Slaby

(In reply to Giuliano Belinassi from comment #0)
> Recent updates of tumbleweed broke `ptrace(PTRACE_ATTACH, ...)` when
> attaching to a process from the same user. This breaks attaching a debugger
> (gdb) to a process and userspace livepatching. A single line reproducer in a
> clean system is:
> 
> ```
> $ sleep 5000 & gdb -p $(pidof sleep)
> ```
> 
> If you see the following message:
> 
> ```
> Attaching to process 12606
> ptrace: Operation not permitted.
> ```
> This means ptrace is not working. As a contrast, running gdb with sudo works
> as intended.
> 
> Value of  /proc/sys/kernel/yama/ptrace_scope:
> ```
> $ cat /proc/sys/kernel/yama/ptrace_scope
> 1
> ```

So this actually works as expected and was supposed to work like this forever.
Could you clarify what "Recent updates of tumbleweed" broke this?