Alexander Mikhalitsyn
Alexander Mikhalitsyn
> Yes we would need to use the later version of apparmor tooling inside the snap. yes, I thought about this option previously when I was looking into fix for...
> Right now it looks like we depend on the apparmor in core22 Of course. AppArmor was a dependency too in core20. I wanted to say that you can't just...
I think one of possible solutions is to overmount `/snap/lxd/current/bin/lxd` during snap refresh with a shell script which you posted in https://github.com/canonical/lxd/pull/14182. That's what we have in lxc container generated...
> Good idea, I'll try that. I might just remove the callhook conditional entirely and force the same set of LD_LIBRARY_PATHs for all invocations. yeah, but then `LD_LIBRARY_PATH` has to...
https://lore.kernel.org/all/[email protected]
I think we can merge this today, so we can test if there are any problems with it. For me it looks perfectly safe and valid. We have merged two...
Theoretically, this should allow using this option in snap store https://git.launchpad.net/review-tools/commit/reviewtools/sr_common.py?id=08e83bf8d0b36eb8ff82ae74e774f00d56493d5f
@roosterfish thanks for reporting this, Julian! Related to: https://bugs.launchpad.net/apparmor/+bug/2067900
Hi @webdock-io Thanks for your report! I'm working on your case right now. Second one is interesting: ``` 00000000000222fb : 222fb: f3 0f 1e fa endbr64 222ff: 55 push %rbp...
Hm, interesting. All 3 cases are a bit different, but root cause is the same. Invalid value of `INTTYPE_TO_PTR(fi->fh)`.